OTP Registers: Difference between revisions
No edit summary |
Wrong size fixed |
||
| (One intermediate revision by one other user not shown) | |||
| Line 34: | Line 34: | ||
! Size | ! Size | ||
! Description | ! Description | ||
|- | |- | ||
| 0x0 | | 0x0 | ||
| Line 49: | Line 45: | ||
| 0x8 | | 0x8 | ||
| 0x10 | | 0x10 | ||
| This is the fall-back keyY used for movable.sed keyY when movable.sed doesn't exist in NAND(the | | This is the fall-back keyY used for movable.sed keyY when movable.sed doesn't exist in NAND(the first two words here are used on retail for generating console-unique TWL keydata/etc). This is also used for "LocalFriendCodeSeed", etc. | ||
|- | |- | ||
| 0x18 | | 0x18 | ||
| Line 80: | Line 76: | ||
|- | |- | ||
| 0x90 | | 0x90 | ||
| | | 0x50 | ||
| Used by Boot9 for generating the console-unique AES [[AES_Registers|keyXs]]. However, due to a bug(?) in Boot9, only the first 0x1C-bytes here actually affect console-unique key generation. The rest of the data is used for hashing, but that output hash only gets overwritten without being used afterwards. | | Used by Boot9 for generating the console-unique AES [[AES_Registers|keyXs]]. However, due to a bug(?) in Boot9, only the first 0x1C-bytes here actually affect console-unique key generation. The rest of the data is used for hashing, but that output hash only gets overwritten without being used afterwards. | ||