#149240 - TwentySeven - Thu Jan 17, 2008 3:12 am
What I'd like to be able to do is to build a .nds (both arm7 and arm9) that can load another special seperately compiled arm9 executable binary *into ram only* and then execute it.
My current working premise is that you'd have a "stub" .nds (about 200-300k or so) that would possibly be modified to load itself "high" into ram, lets say at the 3MB mark.
Then the stub would download (or read from the cart) and store the new "child" executable in ram at 0x0000, and hand execution over to it.
This would effectively destroy the stub, which is desirable.
My current question: (assuming this is feasible!)
Is it possible to modify the current libnds .nds compiles to build a stub that starts high in ram leaving 0x000 onwards free? Does anyone have experience with this?
My current working premise is that you'd have a "stub" .nds (about 200-300k or so) that would possibly be modified to load itself "high" into ram, lets say at the 3MB mark.
Then the stub would download (or read from the cart) and store the new "child" executable in ram at 0x0000, and hand execution over to it.
This would effectively destroy the stub, which is desirable.
My current question: (assuming this is feasible!)
Is it possible to modify the current libnds .nds compiles to build a stub that starts high in ram leaving 0x000 onwards free? Does anyone have experience with this?