devkitPro/wut

Doesn't work on actual hardware?

shinyquagsire23 opened this issue · 3 comments

Doing a test with the Hello World sample using Loadiine yields only a "There is a problem with the system memory." error. While it shouldn't display anything as-is, even doing an OSFatal to get it to print something seems to only show the same error. Given how it looks I was expecting it to just enter and exit cleanly.

exjam commented

I am not surprised it doesn't work on actual hardware, I have not tested it. I am not sure why though, seems like it would be something very hard to debug.

There are still a few minor places where the rpx generated from this differ to a real rpx, so maybe once I get around to fixing those (such as SHT_RPL_IMPORTS missing crc) and there are probably some fields in RPL_FILEINFO I didn't set.

Yeah I suppose SHT_RPL_IMPORTS being missing would do it, Loadiine still seems to go through loader.elf which errors if that crc is incorrect. It actually seems to log a "sLiSetupOneAllocSection: Expected 0x%08X, CRC32 0x%08X, ZLibCRC32 0x%08X" in the event that it's incorrect, but that goes to syslog I think. Might try and see if I can figure out what it crcs.

Works on hardware as of 2c69f7d