Talk:Syscon Hardware: Difference between revisions
(→Main table problem: weekly recap :) |
|||
| Line 10: | Line 10: | ||
What do you think about the new style of the table for mullions [https://www.psdevwiki.com/ps3/Syscon_Hardware#Retail here] ?. In my oppinion is fine because it still allows to add some more columns with new info (i been thinking if adding more columns for "ports" to indicate the JTAG, SPI, etc... that seems to be a popular matter of debate), Also, i been thinking in including another row for the "F" syscon to join together all the mullions for retail and non-retail in the same table)<br> | What do you think about the new style of the table for mullions [https://www.psdevwiki.com/ps3/Syscon_Hardware#Retail here] ?. In my oppinion is fine because it still allows to add some more columns with new info (i been thinking if adding more columns for "ports" to indicate the JTAG, SPI, etc... that seems to be a popular matter of debate), Also, i been thinking in including another row for the "F" syscon to join together all the mullions for retail and non-retail in the same table)<br> | ||
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", "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<br> | 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", "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<br> | ||
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 | 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<br> | ||
Btw, in general is better if all the wiki pages contains some "noob-friendly" info as an introduction (specially if is located at top of the page), if we remove that mentions to "syscon model", "motherboard model" and "PS3 model" (like in [https://www.psdevwiki.com/ps3/index.php?title=System_Controller_Firmware&curid=245&diff=58707&oldid=58702 this edit] the page becomes a lot more hardcore, and im not telling it only for noobs, but for everyone me included, if we keep a long list with only the "SoftID" or the "cokXyy" names for the platform info is very hard (or imposible) to get an overall understanding of what is each with a fast look, you are very used to all that names for platform ID's and SoftID's, but for newcomers (and in general for everyone) is always better to indicate "motherboard model" and "PS3 model" if posible--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 11:58, 23 April 2021 (UTC) | Btw, in general is better if all the wiki pages contains some "noob-friendly" info as an introduction (specially if is located at top of the page), if we remove that mentions to "syscon model", "motherboard model" and "PS3 model" (like in [https://www.psdevwiki.com/ps3/index.php?title=System_Controller_Firmware&curid=245&diff=58707&oldid=58702 this edit] the page becomes a lot more hardcore, and im not telling it only for noobs, but for everyone me included, if we keep a long list with only the "SoftID" or the "cokXyy" names for the platform info is very hard (or imposible) to get an overall understanding of what is each with a fast look, you are very used to all that names for platform ID's and SoftID's, but for newcomers (and in general for everyone) is always better to indicate "motherboard model" and "PS3 model" if posible--[[User:Sandungas|Sandungas]] ([[User talk:Sandungas|talk]]) 11:58, 23 April 2021 (UTC) | ||
Revision as of 13:01, 23 April 2021
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.
Regarding the backward compatibility of the syscon models with motherboard models, the previous versions of the table was intended to represent that but i agree it was not achieving it very well, mostly because the info was 100% based on user reports, there are some combinations that are technically posible but imposible to find in a non-refurbished retail motherboard because was not produced at the same time chronologically (e.g: COK-001 with a CXR714120-302GB), also some of the hacks published latelly was not availables before (replacing the platform config inside syscon or remarrying CELL to Syscon), the table never was intended to represent that rarities that differs from the retail production, but now we can do it
Personally i still had doubts (not much time ago) if the SoftID could be considered a 1:1 mapping of the suffix -XXXGB, this was the kind of doubt that was restricting us a lot when we was trying to figure how to represent all that info in a table, but now that you are insisting in it and you made that table cells "unique" for a single syscon model... is ok, better that way
I only see one way to represent all that accuratelly but it requires a big rebuilding of the table, is needed to "crosscheck" motherboard models and syscon models with YES/NO table cells. Im going to split the table to start the adventure with the mullions. Later we can use the same table design with the sherwoods, but in the new table design the sherwoods are going to be more problematic so i guess we will need to return back to this conversation before sherwoods--Sandungas (talk) 08:08, 19 April 2021 (UTC)
What do you think about the new style of the table for mullions here ?. In my oppinion is fine because it still allows to add some more columns with new info (i been thinking if adding more columns for "ports" to indicate the JTAG, SPI, etc... that seems to be a popular matter of debate), Also, i been thinking in including another row for the "F" syscon to join together all the mullions for retail and non-retail in the same table)
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", "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
Btw, in general is better if all the wiki pages contains some "noob-friendly" info as an introduction (specially if is located at top of the page), if we remove that mentions to "syscon model", "motherboard model" and "PS3 model" (like in this edit the page becomes a lot more hardcore, and im not telling it only for noobs, but for everyone me included, if we keep a long list with only the "SoftID" or the "cokXyy" names for the platform info is very hard (or imposible) to get an overall understanding of what is each with a fast look, you are very used to all that names for platform ID's and SoftID's, but for newcomers (and in general for everyone) is always better to indicate "motherboard model" and "PS3 model" if posible--Sandungas (talk) 11:58, 23 April 2021 (UTC)
PowerON/off HDMI/CEC, WiFi, Bluetooth, GbLAN, buttons etc
- There is no seperate communication processor on the PS3. Powering is handled by syscon.
- This is made by switching a bunch of voltage regulators located around the motherboard (can be considered slaves of syscon), only a few of this connections was documented for PS3 slim models, for reference see the connections of SW2-303 with the voltage regulators
- Power and eject buttons/switchs are connected with syscon (indirectly), there is no protocol involved, the syscon pins related with this buttons has 2 posible states: 3.3v (when button is not pressed)... or 0v (when button is pressed)
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
Note: moved from seperate page, as there are already over 8 different syscon pages and the very same info is mention in depth on the SC firmware and SC hardware page (and in 150 wiki edits on the sysinfo page :/) we dont have a sperate page for every SELF flag either ;) (although there are >4 pages describing SELF :/)
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 (In this link you can found the list of the Syscon update packages)
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)
| SoftID | SC Generation | notes | |
|---|---|---|---|
| Phats | |||
| 0B8E | 1 | - | |
| 0C16 | 2 | COK-002 | |
| 0D52 | 3 | - | |
| 0DBF | 4 | - | |
| 0E69 | 5 | - | |
| 0F29 | 6 | - | |
| 0F38 | 7 | - | |
| 065D | 8 | - | |
| Slims | |||
| 0832 | 9 | - | |
| 08C2 | 10 | - | |
| 0918 | 11 | - | |
Datasheet of SoC similar to syscon
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
PS2 Mechacon vs PSP Syscon vs PS3 Syscon vs PSVita Syscon vs PS4 Syscon
| Production Start Date (<=) | PS2 Mechacon | PSP Syscon | PS3 Syscon | PSVita Syscon | PS4 Syscon | Used IC/CPU Core |
|---|---|---|---|---|---|---|
| 10/1999 | CXP101064 | - | - | - | - | Sony SPC970 (100 pin) |
| 01/2000 | CXP102064 | - | - | - | - | |
| 09/2000 | CXP103049 | - | - | - | - | Sony SPC??? (136 pin) |
| 08/2004 | - | BARxx | - | - | - | NEC D780032AY (78K0/78003xA, 64 pin) |
| 07/2005 | - | B30x | - | - | - | NEC D78F0531 (78K0/KE2 V2.00, 64 pin) |
| 07/2007 | - | B40x / 40xx | - | - | - | NEC D78F0544 (78K0/KF2 V2.00, 84 pin) |
| 07/2008 | - | 3xxx | - | - | - | NEC D78F0534 (78K0/KE2 V2.00, 64 pin) |
| 03/2003 | CXR706080 | - | - | - | - | Sony SR11 (ARM7TDMI) PS2 (Dragon): 164 pin PS3 (Donkey): 200 pin |
| 09/2004 | CXR716080 | - | CXR713120 | - | - | |
| 07/2007 | CXR726080 | - | CXR714120 | - | - | |
| 03/2008 | - | - | SW | - | - | NEC D78F11AA (78K0R/KH3 V3.40, 128 pin) |
| 05/2009 | - | - | SW2 | - | - | NEC D78F11BB (78K0R/KH3 V1.00, 128 pin) |
| 07/2010 | - | - | - | "SC" | - | NEC D79F0109 (78K0R/KH3-L V1.00, 121 pin) |
| 06/2011 | - | - | SW3 | - | - | NEC D78F11CC (78K0R/KG3 V1.00, 100 pin) |
| 07/2013 | - | - | - | - | C0L | Renesas R5F100PL (RL78/G13 V3.03, 100 pin) |
| 08/2013 | - | - | - | A0xxx | - | Renesas R5F1ZCRK (RL78/G13 V3.03, 121 pin) |
| 04/2015 | - | - | - | - | C0L2 | Renesas R5F101LL (RL78/G13 V3.03, 64 pin) |
- The SPC900 core was designed by Texas Instruments ([1])
- CXP101064, CXP102064 are similar to CXP97 (CXP971000, CXP972032, CXP973064, CXP973F064), the CXP103049 matches no COTS because of its OCD support
- In-Circuit-Emulator: Mitek NICE-SPC970 ([2]); Debug software: SVD970; Flash programmer: SFP-2
- A F inside the model name specifies that the IC contains flash memory.
- Mass-produced CXR/SW units don't have/use program flash memory for updates, instead an encrypted firmware patch is stored on the data-"EEPROM"
- CXR7 series uses Sony SR11 CPU (ARM7TDMI)
- Models with public datasheet: CXR702080, CXR702F080, CXR704060
- Prototype PS3 Syscon's:
- CXR713F120A Syscon used on (early) pre-release prototypes, e.g. CEB-2030, DECR-1000, DEH-H1001-D, DEH-H1000A-E
- DEH-FH1500J-A with VERTIGO-02 board and SW series prototype D79F0073
- CBEH-H2001 with SURTEES-03 board and SW2 series prototype D79F0086
- DEH-ML00AK-G with MPX-001 (Prototype) board and SW3 series prototype D79F0123