#159403 - PypeBros - Mon Jun 30, 2008 8:54 am
Hello all.
It looks like my custom ARM7 code doesn't get properly initialized on the R4DS, and i'm looking for hints on how i could determine whether it has actually be loaded by the R4 firmware or not, etc.
Anything like a 7-9 synchronization (like in the ndswifi library) stalls, and i don't seem to receive any input (touchscreen, buttons...) anymore. The same binary works flawlessly on SCSD and in desmume, so despite there may be something wrong with my code, i'm more suspecting something wrong (a step missed) with "how to run your homebrew on R4DS" ...
I know from .map file that my ARM7 code should be located in the IWRAM region, which (afaik) is not mapped from the ARM9, so i cannot "remotely" check that the proper code is in place except from its interaction with shared WRAM.
I am using dkp-r21, if that matters. Any hint would be welcome.
_________________
SEDS: Sprite Edition on DS :: modplayer
It looks like my custom ARM7 code doesn't get properly initialized on the R4DS, and i'm looking for hints on how i could determine whether it has actually be loaded by the R4 firmware or not, etc.
Anything like a 7-9 synchronization (like in the ndswifi library) stalls, and i don't seem to receive any input (touchscreen, buttons...) anymore. The same binary works flawlessly on SCSD and in desmume, so despite there may be something wrong with my code, i'm more suspecting something wrong (a step missed) with "how to run your homebrew on R4DS" ...
I know from .map file that my ARM7 code should be located in the IWRAM region, which (afaik) is not mapped from the ARM9, so i cannot "remotely" check that the proper code is in place except from its interaction with shared WRAM.
I am using dkp-r21, if that matters. Any hint would be welcome.
_________________
SEDS: Sprite Edition on DS :: modplayer