Syscon Hardware: Difference between revisions
Jump to navigation
Jump to search
Strike Venom (talk | contribs) |
Strike Venom (talk | contribs) mNo edit summary |
||
Line 1: | Line 1: | ||
[[Category:Hardware]] | [[Category:Hardware]] | ||
[[File:SYSCON_GEN1.JPG|thumb|Syscon 1st Generation (BGA Packaging)]] | [[File:SYSCON_GEN1.JPG|thumb|Syscon 1st Generation (BGA Packaging)]] | ||
Syscon is the main power controller chip. It is responsible for powering up the various power systems and for configuring and initialising the [[CELL BE]], [[RSX]] and [[South Bridge]]. It communicates with these devices via seperate SPI busses. There is external access by JTAG ( | Syscon is the main power controller chip. It is responsible for powering up the various power systems and for configuring and initialising the [[CELL BE]], [[RSX]] and [[South Bridge]]. It communicates with these devices via seperate SPI busses. There is external access by JTAG (ARM7TDMI which is at factory disabled by blowing a fuse) and Serial. | ||
= Serialnumbers @ SKU = | = Serialnumbers @ SKU = |
Revision as of 14:18, 30 October 2012
Syscon is the main power controller chip. It is responsible for powering up the various power systems and for configuring and initialising the CELL BE, RSX and South Bridge. It communicates with these devices via seperate SPI busses. There is external access by JTAG (ARM7TDMI which is at factory disabled by blowing a fuse) and Serial.
Serialnumbers @ SKU
SoftID { 065D, 0832, 08A0, 08C2, 0918, 0B8E, 0C16, 0D52, 0DBF, 0E69, 0F29, 0F38 };
Model | Type | Board | Syscon part no. |
Soft Id. |
Notes | |
---|---|---|---|---|---|---|
CECHAxx | 0x01 | COK-001 | CXR713120-201GB | 0B8E | ||
CECHBxx | 0x02 | COK-001 | CXR713120-201GB | 0B8E | ||
CECHCxx | 0x03 | COK-002 | CXR713120-201GB | 0C16 | ||
CECHDxx | SKU never released | |||||
CECHExx | 0x04 | COK-002 or COK-002W |
CXR713120-201GB | 0C16 | ||
CECHFxx | SKU never released | |||||
CECHGxx | 0x05 | SEM-001 | CXR713120-201GB | 0D52 | ||
CECHHxx | 0x06 | DIA-001 | CXR713120-201GB | 0DBF | ||
CECHIxx | SKU never released | |||||
CECHJxx | 0x07 | DIA-002 | CXR713120-201GB | 0E69 | ||
CECHKxx | 0x07 | DIA-002 | CXR713120-201GB | 0E69 | ||
CECHLxx | 0x08 | VER-001 | SW-301 or SW-302 |
065D | ||
CECHMxx | 0x08 | VER-001 | SW-301 or SW-302 |
065D | ||
CECHNxx | SKU never released | |||||
CECHOxx | SKU never released | |||||
CECHPxx | 0x08 | VER-001 | SW-301 or SW-302 |
065D | ||
CECHQxx | 0x08 | VER-001 | SW-301 or SW-302 |
065D | ||
CECH-20xx | 0x09 | DYN-001 | SW2-301 | 0832 | ||
CECH-21xx | 0x0A | SUR-001 | SW2-301 or SW2-302 |
08C2 | ||
CECH-25xx | 0x0B | JTP-001 or JSD-001 |
SW2-301 or SW2-302 |
08C2 | ||
CECH-30xx | 0x0C | KTE-001 | SW2-301 or SW2-302 |
0918 | ||
CECH-40xx | ?0x0D? | MSX-001 | SW3-302 |
Non-retail
Model | Type | Board | Syscon part no. |
Soft Id. |
Notes |
---|---|---|---|---|---|
DECR10xx | ? | ? | CXR713F120A | ? | CP Helper Processor CXD9790GG |
DEH-H1000xx | ?0x01? | ?COK-001? | ? | 0B67 | |
DECHAxx | 0x01 | COK-001 | CXR713120-201GB | 0B8E | |
DECHJxx | 0x07 | DIA-002 | CXR713120-201GB | 0E69 | |
DECH20xx | 0x09 | DYN-001 | SW2-301 | 0832 | |
DECH25xx | 0x0B | JTP-001 or JSD-001 |
SW2-301 or SW2-302 |
08C2 | |
DECH30xx | 0x0C | KTE-001 | SW2-301 or SW2-302 |
0918 | |
DECH40xx | ?0x0D? | MSX-001 | SW3-302 |
Syscon UART
You can attach a 3.3v TTL cable (LV-TTL) to the UART on syscon. There is a simple plaintext protocol involved. This varies on different syscon models. Example:
<command>:<hash>
Where the hash is the sum of command bytes & 0xFF
you should terminate commands with \r\n, the syscon messages are only terminated with \n
Here are some of the commands/messages encountered:
Messages: Power applied (standby mode) OK 00000000:3A Power on # (PowerOn State):7F Power off (Hard shutdown) # (PowerOff State):DD After Fan test: # (PowerOff State) (Fatal):36 No text, invalid hash: NG F0000002:4D Commands: VER:ED OK 00000000 S1E 00 00 065D:A4 ERRLOG:CB OK 00000000:3A DATE:1E NG F0000003:4E