Mysteries: Difference between revisions
boot9strap allows code bootROM code execution, but this is not normal behaviour. The NTR path is just another path to boot a FIRM. |
Why not |
||
| Line 40: | Line 40: | ||
'''Background:''' Bootrom is known to use part of DTCM as state, memsetting it to 0 when it's done. After that, it is never used again. | '''Background:''' Bootrom is known to use part of DTCM as state, memsetting it to 0 when it's done. After that, it is never used again. | ||
=== How is CTRAging launched during factory setup? === | === How is CTRAging launched during factory setup? === | ||
'''Background:''' No TestMenu version is capable of launching CTRAging directly: O3DS factory TestMenu can only launch DevMenu installed on NAND, the inserted cartridge and the TWL/AGB test apps; N3DS factory TestMenu can only launch DevMenu installed on NAND, the inserted cartridge and System Settings. | '''Background:''' No TestMenu version is capable of launching CTRAging directly: O3DS factory TestMenu can only launch DevMenu installed on NAND, the inserted cartridge and the TWL/AGB test apps; N3DS factory TestMenu can only launch DevMenu installed on NAND, the inserted cartridge and System Settings. | ||
'''Theory:''' NtrBoot another time | |||
=== Why are there 4 stubbed syscalls named SendSyncRequest1-4? === | === Why are there 4 stubbed syscalls named SendSyncRequest1-4? === | ||