Talk:Syscon Hardware
Main table problem
Syscon_Hardware#Retail assumes that each PS3 model does have an unique Syscon associated with it, but that's not true. 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) is a 1:1 mapping to the suffix -XXXGB. So each -XXXGB does have a unique SoftID (in case of retail chips).
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.
For the sherwoods i been thinking in creating another 2 more tables with the same style, based in the package we have 3 groups: all the "mullions BGA 200 balls" (this is confirmed in many ways, all the mullions shares the same pinout, we have the COK-001 and COK-002 refurbishements with the latest mullion versions CXR714120-303GB and CXR714120-304GB, a metal gear solid special edition COK-002 with a CXR714120-301GB, and the COOKIE-13 and other prototypes with a CXR713F120A), "Sherwoods SW & SW2 QFP 128 pins", and "Sherwoods SW3 QFP 100 pins". The point of grouping them this way is because indicates which ones can be replaced by each others, also im guessing the members of each group are "pinout compatibles" with each others
The other reason is because in the actual table style im keeping the names of the "syscon model", "motherboard model" and "PS3 model" to leverage a bit the skills required to read the wiki pages. With the actual table style the group for the "mullions BGA 200 balls" requires to display the names of 5 retail motherboards in the same table row (one more for the "F"), "Sherwoods SW & SW2 QFP 128 pins" is composed by 5 motherboards, and "Sherwoods SW3 QFP 100 pins" by 8 motherboards. That numbers are fine for splitting the table in 3 groups, otherway if we joing together all the sherwoods it would be needed to have 13 columns 5+8) for the motherboard names and the width of the table would be excesive--Sandungas (talk) 11:58, 23 April 2021 (UTC)
I like the new table. I don't know if it makes sense to include the ports into the table since Sony never changed them. In theory even the SW(1) chips work on Mullion boards if you adapt them. The "F" syscon problem is interesting, since that model is only used on prototypes and the marking XXXGB doesn't map to a particular firmware (especially since they reuse the chips). We would have to somehow get the TMU-510, TMU-520 and all the prototype boards into the table or just say that the "F" model does support both the retail firmware and then list the known prototype firmwares, this would mean that we only need to add the TMU-520.
Sherwood would need 3 tables since the SW and the SW2 are not interchangable (because of the CEC handling which uses hardcoded HDMI stuff), but I like that idea.
So about the "SoftID" and the platform id: Sony never uses the CECHXxx code internally, the same for 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 SKU_Models_Nonretail#Prototype_model_names. On 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.
So how they do it is start 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. 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...
M4j0r (talk) 13:49, 23 April 2021 (UTC)
Mullions done, please review the affected pages--Sandungas (talk) 00:51, 30 May 2021 (UTC)
Multipage Correction
Clocks
SysCon clocks:
T4 XTAL / T5 EXTAL goes to [X4001] of 16.9344 MHz C16 OSCIN / B16 OSCOUT goes to [X4002] of 32.768 kHz
http://oi52.tinypic.com/2s9ziw0.jpg
Backup Mode / Diag
BACKUP_MODE / DIAG_MODE pins on Gen 2 might be pins 110 and 111. They are pulled low. Not completely sure, but looking at those pins in relation to what's around them seems like it could be those two.
SEM-001 CECHG
Pink is N15 BACKUP_MODE Blue is N16 DIAG_MODE
picture: http://psx-scene.com/forums/attachments/f149/26456d1300550098-brick-recovery-research-untitled-1.jpg source: http://psx-scene.com/forums/780185-post344.html !unverified!
According to schematics, DIAG and BACKUP_MODE are are shown in the following picture for COK-001 and COK-002 Motherboards - http://goput.it/69k.jpg These pins are tied to 3.3v so grounding them should enable each mode respectively. !unverified! - DIAG mode has been verified to work - a seperate grounding of the P16 pin on the SYSCON
SoftID
A SoftID is just a 0x4 code that tells you the hardware revision of the syscon. This info can be get through the More System Information method.
You can find them also inside the SYS_CON_FIRMWARE_*********.pkg (Syscon Firmware) at the offset 0x28E
Every SoftID is associated with the ps3 mainboard. this means that you can know if a SC is compatible with your board without opening a PS3 (Syscon Hardware)
VER-001 with syscon SW-301 or SW-302
It seems VER-001 is the only PS3 motherboard that was shipped from factory with 2 posible syscon models, either SW-301 or SW-302. If we stick to the random reports in wiki and forums it seems the SW-301 was the more commonly used (and it was also the first retail sherwood) and the SW-302 should be some kind of minor revision
If we keep in mind the special syscons made specifically for the frankensteins COK-001 refurbs with 40nm and 65nm RSX maybe something similar happened with the sw-302. The point is... maybe the SW-302 adds support for a newer revision of one of the critical components of the motherboard
And that component could be CELL... the info we have in wiki about the CELL revisions used in VER-001 is not so clear, but it seems the CELL was upgraded from 65nm to 45nm inmediatly after VER-001 (or in the last produced VER-001 models)
It seems the production of VER-001 lasted for long because it was used in CECHLxx, CECHMxx, CECHPxx, CECHQxx, if we find someone reporting info about one of the newest produced VER-001 motherboards with the sw-302 the next thing we should ask is about the CELL revision to see if this theory is correct
COK-002 with 0DBF syscon
Information: https://lh5.googleusercontent.com/-UiaHRjhdt50/UesKSGuxdFI/AAAAAAAAGOU/0FV8Fazyl60/s800/TV2013072019053700.jpg
Board type: https://lh6.googleusercontent.com/-K1sc66WzJxo/Ue1Mdr5mHeI/AAAAAAAAGO8/rnqlidQAVfY/s800/DSC01591.JPG
Syscon: https://lh6.googleusercontent.com/-OTxjx3qJV0M/Ue1L2itOfRI/AAAAAAAAGO0/Bv6zli_xQQg/s800/DSC01590.JPG
-This breaks lot of standards/pages/tables in wiki, can you add some notes please ?. E.g: the board came from official repair service, bought in a normal shop, or is a frankenstein made at home ?, it boots correctly and allows firmware updates ?. If it works normally i think this proves CXR713120-20xGB and CXR714120-30xGB shares the same pinout, but the fact that is using 0DBF SoftID is a bit shocking (maybe because is the minimal SoftID allowed by CXR714120-30xGB ?... check SoftID examples in this table) --Sandungas 22:07, 24 July 2013 (MSK)
-The console is a CECHE01 MG (Metal Gear Solid 4 edition) and came with a 3rd generation BD drive (the first type with 2 lens). It had never been to SONY for service. It works normally, correctly and as you could see, has a minimum version which is compatible with the motherboard type. --l_oliveira