Changes

Jump to navigation Jump to search
37 bytes added ,  21:41, 28 June 2017
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? ===
31

edits

Navigation menu