Changes

29 bytes removed ,  16:39, 9 September 2021
Fix grammar
Line 7: Line 7:     
==Wii==
 
==Wii==
The Wii stores a small amount of data here; some of it is Wii-specific (such as NAND keys), but the hash of the version of boot1 used in that Wii is also stored (making boot1 impossible to update) and the common key used in the Wii.
+
The Wii stores a small amount of data here; some of it is Wii-specific (such as NAND keys), and the hash of the Wii's boot1 is stored (making boot1 impossible to update) and the common key used in the Wii.
 
===eFuse Contents===
 
===eFuse Contents===
 
The following things are stored inside the eFuses:
 
The following things are stored inside the eFuses:
{| style="border: 1px solid #bbb; border-collapse: collapse; background-color: #eef; padding: 0.2em 0.2em 0.2em 0.2em;" border="1" cellpadding="2"
+
{| style="border: 1px solid #bbb; border-collapse: collapse; background-color: #eef; padding: 0.2em 0.2em 0.2em 0.2em;" cellpadding="2" border="1"
 
|- style="background-color: #ddd;"
 
|- style="background-color: #ddd;"
 
!Address
 
!Address
Line 33: Line 33:  
|}
 
|}
   −
=== eFuse Programming ===
+
===eFuse Programming===
 
The Wii's eFuses are programmed via JTAG at chip manufacture time with a special power pin. Since the JTAG has a disabling flag in the eFuse region itself which is normally set on most [[Hollywood]] chips, the eFuses can never be programmed again once this flag is set and this is the case for almost all Wii units in existence (including final devkits).
 
The Wii's eFuses are programmed via JTAG at chip manufacture time with a special power pin. Since the JTAG has a disabling flag in the eFuse region itself which is normally set on most [[Hollywood]] chips, the eFuses can never be programmed again once this flag is set and this is the case for almost all Wii units in existence (including final devkits).
  
43

edits