Editing Talk:Syscon Hardware

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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 1: Line 1:
== Notes ==
== Notes ==
*Every syscon within a series (CXR, SW, SW2, SW3) is backwards compatible, e.g. every CXR Syscon works on the COK-001, but only 202GB and newer on a COK-002.
*The SoftID (Syscon firmware build id) of retail chips is a 1:1 mapping to the syscon model. So each syscon model does have a unique SoftID.
*The SoftID (Syscon firmware build id) of retail chips is a 1:1 mapping to the syscon model. So each syscon model does have a unique SoftID.
*Every syscon within a series (CXR, SW, SW2, SW3) is backwards compatible, e.g. every CXR Syscon works on the COK-001, but only 202GB and newer on a COK-002.
*The SW and the SW2 are not interchangable (because of the CEC handling which uses hardcoded HDMI stuff).
*The actual platform configuration which defines the board on the which Syscon resides is stored in the EEPROM (CXR) or Flash data section (SW), it can be mapped to the platform id.
*The actual platform configuration which defines the board on the which Syscon resides is stored in the EEPROM (CXR) or Flash data section (SW), it can be mapped to the platform id.
*In theory even the SW(1) chips work on Mullion boards if you adapt them.
*In theory even the SW(1) chips work on Mullion boards if you adapt them.
*The SW and the SW2 are not interchangable (because of the CEC handling which uses hardcoded HDMI stuff).
Sony never uses the CECHXxx code internally, neither the motherboard label (e.g. COK-001), the only thing which they use to identify the hardware is '''the platform id, which contains the chassis id''' . On [[SKU_Models_Nonretail#Prototype_model_names|prototype units]] it's not only stored in syscon, but also on a label on the board and part of the board_id inside cISD1. They starts with the platform id, then get the chassis id which then maps to the numeric model code (1000, 1200, 1300...) and the model type byte inside the IDPS. The actual SKU name then gets assigned based on what they want it to be marketed as.<br>


== Prototype sherwoods ==
That's why I think the SKU name and board name are maybe misleading if you don't know how Sony works with them. The platform id is mapped 1:1 to your actual hardware, the SKU codes (especially for the early models) are all over the place. For example there're CECHA/DECHA with COK-001, COK-001 (with COK-002 syscon) and COK-002, also models certified as CECHE are sold as CECHA in some regions. The CECHM either had a VER-001 or DIA-001, completely different architecture and I wonder how many of these cases we haven't identified yet...<br>
The sherwood table already have a row for D79F0073, should we add a couple more rows for D79F0086 and D79F0123 ?
[[User:M4j0r|M4j0r]] ([[User talk:M4j0r|talk]]) 13:49, 23 April 2021 (UTC)
Please note that all contributions to PS3 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS3 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)