Changes

Jump to navigation Jump to search
1,564 bytes added ,  21:42, 28 June 2017
...
Line 3: Line 3:  
== General ==
 
== General ==
 
* What is the CTR abbreviation?
 
* What is the CTR abbreviation?
 +
: C may stand for Chiheisen ("horizon" in Japanese, the O3DS's codename being "Project Horizon").
 +
:: Not true, Horizon refers to the OS.
    
== Hardware ==
 
== Hardware ==
=== Why are there two CTRCARD controllers ===
+
=== Why are there two CTRCARD controllers? ===
 +
'''Background:''' Also [http://problemkaputt.de/twl-core.jpg DSi SoC pinout] shows evidence of dual NTRCARD controllers on the final DSi SoC. (This was a [http://i.imgur.com/0kJlbEw.png planned feature] of the DSi before being axed later in development)
 +
 
 
=== Why are there two EMMC controllers? ===
 
=== Why are there two EMMC controllers? ===
 
'''Theory:''' At some point during 3DS hardware development there was an idea to split up CTR and TWL nand into two different chips.
 
'''Theory:''' At some point during 3DS hardware development there was an idea to split up CTR and TWL nand into two different chips.
Line 14: Line 18:  
'''Background:''' There's dead code in NWM referencing it.
 
'''Background:''' There's dead code in NWM referencing it.
 
=== Why did they put NTRCARD accessible from ARM11? ===
 
=== Why did they put NTRCARD accessible from ARM11? ===
 +
'''Theory:''' At some point during 3DS hardware development there was a concept where ARM11 ran a menu with DS(i) icons while ARM9 was in TWL mode.
 +
 
=== Is there a secret message embedded in the 3DS keyscrambler constant? ===
 
=== Is there a secret message embedded in the 3DS keyscrambler constant? ===
'''Background:''' TWL keyscrambler constant was Nintendo in Japanese, utf-8 encoded.
+
'''Background:''' TWL key scrambler constant was "Nintendo Co., Ltd" in Japanese ("任天堂株式会社"), UTF-16LE encoded, with byte order mark.  The 3DS key scrambler constant, by comparison, is random-looking.
 +
 
 +
=== What is the PDN abbreviation? ===
 +
: Power distribution network
 +
 
 +
=== How does Nintendo reflash bricked systems? ===
 +
'''Theory:''' Before trying to boot from NAND, the bootrom checks to see if a key combination (Start + Select + X) is being held, and whether the shell is closed. If so, it tries to boot from an inserted NTR (Nintendo DS) cartridge.
 +
This allows to execute a FIRM that is probably used by Nintendo to reflash the system.
    
== Software ==
 
== Software ==
Line 22: Line 35:  
=== What did SVC 0x74 in the ARM11 kernel do before it got stubbed? ===
 
=== What did SVC 0x74 in the ARM11 kernel do before it got stubbed? ===
 
=== What is the PTM abbreviation? ===
 
=== What is the PTM abbreviation? ===
=== What is the PDN abbreviation? ===
+
: Power/time management
 +
 
 
=== Why is the DTCM not used anywhere except bootrom? ===
 
=== Why is the DTCM not used anywhere except bootrom? ===
 
'''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? ===
 +
'''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? ===
31

edits

Navigation menu