Bootloader: Difference between revisions
→Non-NAND FIRM boot: (Verified with st4rk for DS-mode) |
|||
| Line 19: | Line 19: | ||
CTR_word[3] = readsize;//FIRM section size | CTR_word[3] = readsize;//FIRM section size | ||
When booting from NAND fails, boot9 will then attempt to boot from Wifi SPI-flash(this only triggers when the wifi module hw is properly accessible/connected, which is normally the case). The base offset for spiflash FIRM is 0x400. Note that this region is write-protected by the spiflash. | When booting from NAND fails, boot9 will then attempt to boot from Wifi SPI-flash(this only triggers when the wifi module hw is properly accessible/connected, which is normally the case). The base offset for spiflash FIRM is 0x400. Note that this region(all data prior to offset 0x1F300) is write-protected by the spiflash(not writable from 3DS-mode / DS-mode). | ||
For non-NAND booting, NCSD / FIRM-backup is not used. | For non-NAND booting, NCSD / FIRM-backup is not used. | ||