254
edits
Changes
Jump to navigation
Jump to search
Line 551:
Line 551: + + Line 558:
Line 560: − + − + − + − + − + − + − +
no edit summary
There exists an alternate code path where uploading is done using register 0x3B (decided by making some nonsense conclusions about registers 0x0F and 0x10). This may be a "hack" around early versions of MCU? Register 0x3B is RTC-related on recent versions of MCU, and the "nonsense" condition is not met even on factory MCU firmware.
There exists an alternate code path where uploading is done using register 0x3B (decided by making some nonsense conclusions about registers 0x0F and 0x10). This may be a "hack" around early versions of MCU? Register 0x3B is RTC-related on recent versions of MCU, and the "nonsense" condition is not met even on factory MCU firmware.
On dev-units, the user-facing representation of this firmware version is displayed by first subtracting 0x10 from the major field (raw register 0x00). It is these user-facing versions that are displayed in the table below. It is unknown what bit4 (0x10) actually represents, but it is seemingly always set.
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
| New3DS v8192/safe v9217 (latest)
| New3DS v8192/safe v9217 (latest)
| 19.56
| 3.56
|-
|-
| Old3DS v6145 to v8192 (latest)
| Old3DS v6145 to v8192 (latest)
| 18.37
| 2.37
|-
|-
| Old3DS v5122
| Old3DS v5122
| 18.35
| 2.35
|-
|-
| Old3DS v4102
| Old3DS v4102
| 18.30
| 2.30
|-
|-
| Old3DS v2048
| Old3DS v2048
| 17.52
| 1.52
|-
|-
| Old3DS safe v0
| Old3DS safe v0
| 17.20
| 1.20
|-
|-
| Old3DS factory
| Old3DS factory
| 17.07
| 1.07
|}
|}