Views: 1,394,695 | Main | Rules/FAQ | Memberlist | Active users | Last posts | Calendar | Stats | Online users | Search | 04-23-24 09:29 AM |
Guest: |
0 users reading Unlaunch.dsi released - DSi bootcode hack | 1 bot |
Main - Reverse-engineering - Unlaunch.dsi released - DSi bootcode hack | Hide post layouts | New reply |
ApacheThunder |
| ||
Member Normal user Level: 12 Posts: 24/24 EXP: 6196 Next: 1725 Since: 09-14-16 Last post: 2118 days ago Last view: 1967 days ago |
Ok we worked around the secure area by just loading arm9 to a higher ram address and moving it back to 0x2000800 and having arm9 jump to it. I just compile a simple bootstub that does this for me using existing code Fix94 made for me some time back. (originally meant for moving arm7 code before starting it for using old homebrew as DSiWare on 3DS. But this works for a similar purpose on arm9. ) I don't know why I didn't think to just do this when Unlaunch 0.9 first came out, but now that I have my DSi XL back, that idea came back to me.
So I suppose for now you don't really need to do anything now unless you decide to fix booting Launcher SRL as bootcode.dsi. That would get rid of the need to use HiyaCFW's launcher entirely. But for now I have a solution for booting HiyaCFW in a way that doesn't break auto booting into things with Launcher. I confirmed if I load arm9 to a higher address, Unlaunch doesn't touch the first part of 0x2000000 at all so soft reset data isn't destroyed. |
nocash |
| ||
Normal user Level: 20 Posts: 76/77 EXP: 37734 Next: 4705 Since: 10-09-15 Last post: 1885 days ago Last view: 1801 days ago |
Released unlaunch v1.0, and, moved to yet another forum:
http://forums.nesdev.com/viewtopic.php?f=23&t=17581 (see there for details). |
Main - Reverse-engineering - Unlaunch.dsi released - DSi bootcode hack | Hide post layouts | New reply |
Page rendered in 0.018 seconds. (2048KB of memory used) MySQL - queries: 28, rows: 67/67, time: 0.012 seconds. Acmlmboard 2.064 (2018-07-20) © 2005-2008 Acmlm, Xkeeper, blackhole89 et al. |