Editing Syscon Hardware
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 23: | Line 23: | ||
! Offset !! Size !! Description !! Notes | ! Offset !! Size !! Description !! Notes | ||
|- | |- | ||
| 0x00000 || 0x20000 || Code | | 0x00000 || 0x20000 || Code Area || | ||
|- | |- | ||
| 0x20000 || 0xD0000 || Reserved || OCDROM is here | | 0x20000 || 0xD0000 || Reserved || OCDROM is here | ||
|- | |- | ||
| 0xF0000 || 0x800 || | | 0xF0000 || 0x800 || SFR Area 1 || | ||
|- | |- | ||
| 0xF0800 || 0x800 || Reserved | | 0xF0800 || 0x800 || Reserved || | ||
|- | |- | ||
| 0xF1000 || 0x1000 || Data | | 0xF1000 || 0x1000 || Data Area || | ||
|- | |- | ||
| 0xF2000 || 0xCF00 || Mirror || Mirror of a portion of | | 0xF2000 || 0xCF00 || Mirror || Mirror of a portion of code area | ||
|- | |- | ||
| 0xFEF00 || 0xFE0 || RAM || | | 0xFEF00 || 0xFE0 || RAM || | ||
|- | |- | ||
| 0xFFEE0 || 0x20 || | | 0xFFEE0 || 0x20 || GPR || | ||
|- | |- | ||
| 0xFFF00 || 0x100 || | | 0xFFF00 || 0x100 || SFR Area 2 || | ||
|} | |} | ||
Line 131: | Line 131: | ||
= Pinout = | = Pinout = | ||
== 100-pin == | == 100-pin == | ||
Line 604: | Line 340: | ||
|} | |} | ||
= | = Dump and Restore = | ||
We are able to make a 1:1 copy of a PS4 Syscon and put it on another chip. This allows to install a dump of a PS4 Syscon to a brand new chip then swap it. | |||
This is often used in firmware revert [[Downgrade]] method to avoid having to flash the same chip each time one wants to revert firmware but instead only have to swap the chips. | |||
= Syscon glitching = | |||
By glitching Syscon, it is possible to dump its EEPROM, including NVS. | |||
To be documented. | |||
* [https://www.sendspace.com/file/377yhw glitch setup (dead link)] |