Editing Talk:Syscon Firmware
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 72: | Line 72: | ||
This should be a good starting point but leaves enough to explore yourself though: http://pastebin.com/NxVkGCdp (for version 1.02) | This should be a good starting point but leaves enough to explore yourself though: http://pastebin.com/NxVkGCdp (for version 1.02) | ||
See [[Graf's PSGroove Payload]] and [[Hypervisor_Reverse_Engineering | See [[Graf's PSGroove Payload]] and [http://www.ps3devwiki.com/index.php?title=Hypervisor_Reverse_Engineering#0x9000_-_SC_Manager HV page #0x9000 - SC_Manager] / [http://www.ps3devwiki.com/index.php?title=Hypervisor_Reverse_Engineering#System_Controller_.28SC_or_SYSCON.29 HVpage #System Controller] | ||
---- | ---- | ||
== Updater log lines related to syscon == | == Updater log lines related to syscon == | ||
| Line 496: | Line 496: | ||
For a backtrack of this talk see the section named "sherwood names format" at the end of [https://www.psdevwiki.com/ps3/index.php?title=System_Controller_Firmware&diff=58966&oldid=58927 this edit], the request for a confirmation [https://www.psdevwiki.com/ps3/index.php?title=System_Controller_Firmware&diff=58971&oldid=58968 here], and the answer [https://www.psdevwiki.com/ps3/index.php?title=System_Controller_Firmware&diff=58973&oldid=58971 here] | For a backtrack of this talk see the section named "sherwood names format" at the end of [https://www.psdevwiki.com/ps3/index.php?title=System_Controller_Firmware&diff=58966&oldid=58927 this edit], the request for a confirmation [https://www.psdevwiki.com/ps3/index.php?title=System_Controller_Firmware&diff=58971&oldid=58968 here], and the answer [https://www.psdevwiki.com/ps3/index.php?title=System_Controller_Firmware&diff=58973&oldid=58971 here] | ||
The patch naming and versioning for mullion is straightforward, both the value displayed in the [[More System Information]] screen and the PKG filename itself contains the 4 integer values of the: "major version", "minor version", "major revision", and "minor revision" that appears in the header of the decrypted patch structure [[ | The patch naming and versioning for mullion is straightforward, both the value displayed in the [[More System Information]] screen and the PKG filename itself contains the 4 integer values of the: "major version", "minor version", "major revision", and "minor revision" that appears in the header of the decrypted patch structure [[System Controller Firmware#Mullion Patch Content]]. Filename SYS_CON_FIRMWARE_0'''1'''0'''1'''0'''3'''0'''3'''.pkg is patch v1.1.3.3. But we cant apply the same rules for sherwood<br> | ||
The only official patch filename sample we have for sherwood is ''SYS_CON_FIRMWARE_S1_000'''1'''000'''2'''0'''83E'''0'''832'''.pkg''. There are many photos in the [[Talk:More System Information]] where can be seen that is displayed as ''0832.000'''1'''000'''2'''0'''83E'''0'''832'''@SC''<br> | The only official patch filename sample we have for sherwood is ''SYS_CON_FIRMWARE_S1_000'''1'''000'''2'''0'''83E'''0'''832'''.pkg''. There are many photos in the [[Talk:More System Information]] where can be seen that is displayed as ''0832.000'''1'''000'''2'''0'''83E'''0'''832'''@SC''<br> | ||
The first 2 integers seems to follow the rules for mullion ("major version" and "minor version") and indicates v1.2... but it seems the base firmware is 1.11... so im wondering if the patch "updates" the firmware to 1.2 (base firmware v1.11 overlayed with the patch becomes v1.2)<br> | The first 2 integers seems to follow the rules for mullion ("major version" and "minor version") and indicates v1.2... but it seems the base firmware is 1.11... so im wondering if the patch "updates" the firmware to 1.2 (base firmware v1.11 overlayed with the patch becomes v1.2)<br> | ||
The last 2 values are the most weird, but also the most interesing, the '''0832''' is the SoftID of the real '''base''' firmware... and im wondering if after applying the patch it becomes '''083E'''. Note both values are very close to each other, the algorythm used by syscon to calculate checksums makes them similar if we change only a few bytes as can be seen when playing around with the "eepcsum" command<br> | The last 2 values are the most weird, but also the most interesing, the '''0832''' is the SoftID of the real '''base''' firmware... and im wondering if after applying the patch it becomes '''083E'''. Note both values are very close to each other, the algorythm used by syscon to calculate checksums makes them similar if we change only a few bytes as can be seen when playing around with the "eepcsum" command<br> | ||
Long story short... im wondering if all the SoftID's are checksums of the base syscon firmware build (not counting the EEPROM areas used for per-console configurations as the "platform config" area or others). And for sherwoods is also a checksum of the resulting data after applying the patch (so in this case is a checksum based in the data in syscon RAM), the header of the decrypted patch structure for sherwoods changed [[ | Long story short... im wondering if all the SoftID's are checksums of the base syscon firmware build (not counting the EEPROM areas used for per-console configurations as the "platform config" area or others). And for sherwoods is also a checksum of the resulting data after applying the patch (so in this case is a checksum based in the data in syscon RAM), the header of the decrypted patch structure for sherwoods changed [[System Controller Firmware#Sherwood Patch Content]] and includes 2 new values "data checksum" (the checksum of the syscon base firmware = SoftID '''before''' aplying the patch ?), and "patch checksum" (the checksum of the syscon base firmware overlayed with the patch data = SoftID '''after''' aplying the patch ?)<br> | ||
So the filename for sherwoods is "major version" (of the patched data), "minor version" (of the patched data), "patch checksum" (of base firmware + patch), "data checksum" (of base firmware) | So the filename for sherwoods is "major version" (of the patched data), "minor version" (of the patched data), "patch checksum" (of base firmware + patch), "data checksum" (of base firmware) | ||
--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 19:32, 1 May 2021 (UTC) | --[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 19:32, 1 May 2021 (UTC) | ||
| Line 506: | Line 506: | ||
Syscon doesn't use the PatchID internally - I guess it's just saved in the patch header for identification purposes. The only thing it's checking is the SoftID.<br> | Syscon doesn't use the PatchID internally - I guess it's just saved in the patch header for identification purposes. The only thing it's checking is the SoftID.<br> | ||
The SoftID (I call it BuildID) is incremental ([[ | The SoftID (I call it BuildID) is incremental ([[System_Controller_Firmware#Syscon_firmwares|see here]]), like for example the [[Index.dat#build|build id]].<br> | ||
The checksums in the Sherwood patch are just for the data saved in the patch (for "integrity" = bad crypto reasons), the HDMI patch on the Mullion syscon does also have a checksum.<br>[[User:M4j0r|M4j0r]] ([[User talk:M4j0r|talk]]) 19:46, 1 May 2021 (UTC) | The checksums in the Sherwood patch are just for the data saved in the patch (for "integrity" = bad crypto reasons), the HDMI patch on the Mullion syscon does also have a checksum.<br>[[User:M4j0r|M4j0r]] ([[User talk:M4j0r|talk]]) 19:46, 1 May 2021 (UTC) | ||
---- | ---- | ||