vyktormvmpay25
Senior Member
It is kind of situation where I pass to another unit. It depends on user/technician if want and have time to give it a try.
PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
DeadEnd
Senior Member
These photos are even worse than the one before. I cannot see the traces well. I could see them much better in the first picture... Try to clean off the paste and take another picture that is similar to the first one where copper traces can be seen properly. You need to determine if they are broken or not. Now that I had another look, they do seem damaged.
Last edited:
Hi, just make sure I did it right. Here's what I did:
Get two 3.3V USB-TTL adapter, first one /dev/ttyUSB0 connected to SYSCON 4 wires as we all did here, second one /dev/ttyUSB1 connected to SB_RxD and SB_TxD, and one common GND. Then start a serial program on my linux like:
Code:
$ picocom -b 115200 /dev/ttyUSB1Then enter the internal mode of syscon:
Code:
$ python3 ps3_syscon_uart_script.py /dev/ttyUSB0 CXRFWrite 0x02 to EEPROM address 0x7202:
Code:
w 7202 02Finally auth and bringup. This should let the serial port on /dev/ttyUSB1 i.e. the second serial port print out southbridge messages right?
I used a YLOD COK-002 board for testing, when it stopped at 3034 errors(RSX problem), the SB serial port only print out 1 or 2 garbage characters. Here's my SB serial port output:
Code:
picocom -b 115200 /dev/ttyUSB1
picocom v2.2
port is : /dev/ttyUSB1
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
Type [C-a] [C-h] to see available commands
Terminal ready
��
Thanks for using picocomI soldered the SB serial wire like this:
What could have gone wrong? Is the empty serial port means SB hasn't started to work yet(because of the RSX error)? Thanks a lot!
vyktormvmpay25
Senior Member
Running bringup twice and I can tell if you can see SB or not.
Up to now seems fine.
Hi, I tried the bringup-shutdown loop multiple times, the only difference is syscon serial is spitting some more thermal errors, but SB UART is either silence or output one or two garbage characters. The syscon UART log is like:
Code:
>$ br
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
[SERV THERM] Thermal Error Cleared!
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
>$ sd
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SERV THERM] Thermal Error Detected!
[SSM] fatalreq delayed.
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[ERROR]: 0xa0401200
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] *** Thermal Alert (ZONE) ***
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
[ADT7461] *** alert flags still stay high(sts_reg:82) ***
>$ sd
shutdown
Do nothing. (PowerOff State)
>$ br
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
>$
[SERV THERM] Thermal Error Cleared!
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$
>$ sd
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
>$ br
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
>$
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$
>$ br
bringup
Do nothing. (FatalOff State)
>$ sd
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
>$ br
bbringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
>$ r
bringup
Do nothing. (UpBusy State)
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404402
[ERROR]: 0xa0403034
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$
>$ sd
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)vyktormvmpay25
Senior Member
No it won't start, SB uart working when hdmi ic only issue or av ic, or glod, it is a rsx error so won't be able to use SB.
DeadEnd
Senior Member
You have RSX failure. Bga or bumpgate, either way it's something about RSX. Either replace it or reball . I'm not sure why are you trying to read SB log. I don't think it will print anything because your system is stuck in PowSeq fail. Sb log prints messages only if you don't get stuck in bittraining or any other POWSEQ errors.
Thanks guys. That makes sense. I did it to a RSX BGA failed COK-002 only to test it before I try the GLOD one. Now the boot sequence is a bit clearer to me, so yeah if all the steps and the soldering were right, I'd do it to that GLOD COK-002.
vyktormvmpay25
Senior Member
Again running bringup twice and put log here, I'm trying to see one full log, if not I will use mine later to add example. I really need time.
DeadEnd
Senior Member
I would also say that it is possible in some cases that GLOD is also caused by RSX error. I had a board like that. There was no errors in the syscon log. The SB log was printing that xmb is loaded and there were no issues with the HDMI chip. But RSX wasn't setting the resolution, so it was GLOD. Quite an unusual fault it was.
vyktormvmpay25
Senior Member
Yes that is my "special glod" were XMB is on but no display on any port, exchanged rsx working fine.
Only here SB uart port is helping us to understand our problem.
Only here SB uart port is helping us to understand our problem.
Hello,
and I have a non-working fat - CECHC03 with a motherboard COK-002.
Before its first opening, it gave the GLOD.
After thorough cleaning and replacement of thermal paste - instant YLOD.
After diagnosis give these codes: A0232102, A0403034, A0902120, A0404002.
I read that they are for reballing.
I reflow with a hot air gun
After diagnosis give only this code: A0232102
Again instant YLOD.
In my opinion, something happened with cleaning (with vacuum cleaner), because it changed from GLOD to YLOD without doing anything else.
And can this code A0232102 be understood where it comes from. I will be grateful for any help.
and I have a non-working fat - CECHC03 with a motherboard COK-002.
Before its first opening, it gave the GLOD.
After thorough cleaning and replacement of thermal paste - instant YLOD.
After diagnosis give these codes: A0232102, A0403034, A0902120, A0404002.
I read that they are for reballing.
I reflow with a hot air gun
After diagnosis give only this code: A0232102
Again instant YLOD.
In my opinion, something happened with cleaning (with vacuum cleaner), because it changed from GLOD to YLOD without doing anything else.
And can this code A0232102 be understood where it comes from. I will be grateful for any help.
RIP-Felix
Senior Member
You are not the first to have reported a 23 2102 (Fatal RSX Error) in connection with 3034 before. I have it in my notes that it can be related, such as a failed reflow/reball. There are alot of errors that can be caused bad RSX solder connection.Hello,
and I have a non-working fat - CECHC03 with a motherboard COK-002.
Before its first opening, it gave the GLOD.
After thorough cleaning and replacement of thermal paste - instant YLOD.
After diagnosis give these codes: A0232102, A0403034, A0902120, A0404002.
I read that they are for reballing.
I reflow with a hot air gun
After diagnosis give only this code: A0232102
Again instant YLOD.
In my opinion, something happened with cleaning (with vacuum cleaner), because it changed from GLOD to YLOD without doing anything else.
And can this code A0232102 be understood where it comes from. I will be grateful for any help.
- Your reflow method is very important to achieve an optimal results. You must control temperatures. Strict cleaning and reflow procedures.
- Reflows suck because they can't remove the oxidation on pads. So the solder won't adhere to them even if it goes molten. So the best you can hope for is a console that works for a few months, if at all.
- The only viable substitute for a reball is to replace the RSX with a more reliable model, because even if you do achieve a good reball, bumpgate will troll you sooner or later. @DeadEnd has finally convinced me of that. Having said that, it should last at least a year after a successful reball.
Last edited:
DeadEnd
Senior Member
Not necessarily more damage. Notice, he had this error before as well. His reflow has eliminated 3034 and all the rest, so technically it wasn't entirely fruitless.
Hello,
and I have a non-working fat - CECHC03 with a motherboard COK-002.
Before its first opening, it gave the GLOD.
After thorough cleaning and replacement of thermal paste - instant YLOD.
After diagnosis give these codes: A0232102, A0403034, A0902120, A0404002.
I read that they are for reballing.
I reflow with a hot air gun
After diagnosis give only this code: A0232102
Again instant YLOD.
In my opinion, something happened with cleaning (with vacuum cleaner), because it changed from GLOD to YLOD without doing anything else.
And can this code A0232102 be understood where it comes from. I will be grateful for any help.
I must ask if the error logs were cleared after reflowing ? Maybe the errors are the same, they just couldn't fit into the log. Also bringup command could be interesting to see. But I guess if it doesn't get to bittraining, then it might not show anything new.
RIP-Felix
Senior Member
Tuoche...hmm.
I was/am assuming that when a #23 fatal error is encountered, the system does not proceed to bittraining. @amxcs can you post the errorlogs? Did you record the timestamps so we can see if those 232102's happened at the same time as the 3034/4002's? If they did, then my assumption that 232101 will YLOD then and there without proceeding is wrong.
OTOH, if these 3034/4002's were previous errors to the 232102's, then the 3034/4002's were/are probably still there, but the POS doesn't get that far. So maybe you didn't do more damage. You just didn't get anywhere with the reflow.
Thanks, I managed to get SB UART working on my GLOD COK-002. Still stuck at
Here's the SB UART:
Code:
Boot Loader SE Version 4.8.2 (Build ID: 5336,50677, Build Date: 2017-08-24_13:10:12)
SDK Version: 482.000
Copyright(C) 2017 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.2, SB:PX1.1
Device: PATAC0:Cable Not Connect
Cell OS SDK4.8.2 000 (release build: r50677 2017_08_24_130000)
Copyright 2017 Sony Computer Entertainment Inc.
revision: 50653
date: Thu Aug 24 13:12:48 JST 2017
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size: 12MB+640KB (heap:3492KB page pool:4736KB)
lv2(0): user memory size: 237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.8.2
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50677
lv2(2): build date: 2017/08/24 13:19:54
lv2(2): processor: Broadband Engine Ver 0x0000 Rev 0x0202
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx: b02 500/650 vpe:ff shd:7d [4K0305701:1:3:9:b:3:4:f:1][39:2:1:1:1:3:1][0:0:0]
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2):
lv2(2): ###
lv2(2): ### Safe mode
lv2(2): ###
lv2(2):
lv2(2): creating the recover process (for safe mode) : OKAt the same time, SYSCON UART:
Code:
>$ br
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[mullion]$If I do hdmi chstat 0, here is the output, still waiting for resolution:
Code:
>$ hdmi chstat 0
hdmi chstat 0
[HDMI] ----------------------------
[HDMI] -- HDMI Channel 0 Context --
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[System Management]
[HDMI] - SSM Task ID : 13
[HDMI] * Task Status : WAITING
[HDMI] * Wait Cause : EVENT FLAG
[HDMI] - SSM State : WaitResolution
[HDMI] - SSM Mutex Information : ID[2] LockTID[0] WaitTID[0]
[HDMI] - SSM Event Flag Info : ID[2] WaitTID[13] FlagPattern[0]
[HDMI] - SSM Mode : HDMI
[HDMI] ------------------------------------------------------------------------------------
[HDMI] - Authentication Status : NotStart
[HDMI] - Repeater : Sink
[HDMI] - KSVs : 0
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[Interrupt]
[HDMI] - External Interrupt Number of Mullion : 7
[HDMI] - Interrupt Mask Pattern in SiI : [0x0000E0]
[HDMI] - Interrupt Register Size : 3
[HDMI] - Interrupt Task ID : 12
[HDMI] * Task Status : WAITING
[HDMI] * Wait Cause : SLEEPING
[HDMI] - Semapho Information : ID[38] WaitingTID[0] Count[1]
[HDMI] - Plug Status : PowerOn
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[SiIType]
[HDMI] - Chip Type : 9132
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[EDID]
[HDMI] - EDID Mutex ID : 3
[HDMI] - EDID Mutex Information : ID[3] LockTID[0] WaitTID[0]
[HDMI] - EDID Block Size : 2
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[I2C Bus]
[HDMI] - Device Address 0x72(0) 0x7A(1)
[HDMI] - Semapho Information : ID[36] WaitingTID[0] Count[1]
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[AV Setting]
[HDMI] - Audio Setting State : Unset
[HDMI] Mute ; Mute
[HDMI] - Video Setting State : Unset
[HDMI] Mute ; Mute
[HDMI] Setting : 00 00 00 00 00 00 00 00 00 00 00 00
[HDMI] : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[HDMI]
[mullion]$RIP-Felix
Senior Member
Power Control Topology - Part 2
(Power Good & Voltage Regulation)
(Power Good & Voltage Regulation)
Wikipedia said:
The PlayStation 3 Power Supply Unit (PSU) outputs 2 voltages from which all other system voltages are derived - 12V_MAIN and 5V_EVER. I made the following flowchart of a COK-001 to illustrate.
Here is the text version...
PSU +5V_EVER
--> /SYSCON_RST (IC6004)
--> +3.3V_THERMAL (IC6009)
--> +1.8V_VDD_MEM (IC6302/Q6301) (JL9647)
PSU +12V_MAIN--> +3.3V_THERMAL (IC6009)
--> IC1101
--> IC2101
--> IC3101
--> +3.3V_EVER (IC6005)--> IC2101
--> IC3101
-->Q6311 --> What's happening here?
--> Base Q3501 to Drain +3.3V_MISC --> +3.3V_ESW
--> +1.8V_EVER (IC6006)--> Base Q3501 to Drain +3.3V_MISC --> +3.3V_ESW
--> +1.8V_VDD_MEM (IC6302/Q6301) (JL9647)
--> /POW_FAIL (IC6023) (Error A0003001)
--> +12V_BD (Q6010) (JL6064)
--> +5V_ANA (IC2403)
--> +5V_MISC (IC6003/Q6002)
--> +1.2V_RSX_VDDC
--> +12V_BD (Q6010) (JL6064)
--> +5V_ANA (IC2403)
--> +5V_MISC (IC6003/Q6002)
--> +5V_HDD (Q6006/Q6007) (JL6067)
--> +5V_USB (Q6006/Q6008) (JL6057)
--> +5V_BD (Q6010) (JL9658)
--> +3.3V_MK_VDD (IC6020) (JL6053)
--> +3.3V_Bridge (IC6022) (JL6070)
--> +3.3V_DRCG_VDD_DIG_+3.3V1 (IC6605) (JL6360)
--> +3.1V_EEGS_AVDA_DIG_+3.1V1 (IC6600) (JL6359)
--> +1.2V_RSX_VDDR (IC6200) (JL9651)
--> +1.5V_RSX_VDDIO (IC6017) (JL9656)
--> +1.5V_YC_RC_VDDA (IC6304) (JL9655)
--> +1.2V_EEGS_VDD_DIG_+1.2V1 (IC6302) (JL6361)
--> +1.2V_YC_RC_VDDIO (IC6303) (JL9652)
--> +1.2V_SB_VDDC (IC6305) (JL9648)
--> +1.2V_ESW (IC3501) (JL9649)
--> +1.2V_RSX_VDDC, RSX VRM (2 Phase)
-->+3.3V_MISC (IC6003/Q6601)--> +5V_USB (Q6006/Q6008) (JL6057)
--> +5V_BD (Q6010) (JL9658)
--> +3.3V_MK_VDD (IC6020) (JL6053)
--> +3.3V_Bridge (IC6022) (JL6070)
--> +3.3V_DRCG_VDD_DIG_+3.3V1 (IC6605) (JL6360)
--> +3.1V_EEGS_AVDA_DIG_+3.1V1 (IC6600) (JL6359)
--> +1.2V_RSX_VDDR (IC6200) (JL9651)
--> +1.5V_RSX_VDDIO (IC6017) (JL9656)
--> +1.5V_YC_RC_VDDA (IC6304) (JL9655)
--> +1.2V_EEGS_VDD_DIG_+1.2V1 (IC6302) (JL6361)
--> +1.2V_YC_RC_VDDIO (IC6303) (JL9652)
--> +1.2V_SB_VDDC (IC6305) (JL9648)
--> +1.2V_ESW (IC3501) (JL9649)
--> +1.2V_RSX_VDDC, RSX VRM (2 Phase)
--> IC6202 (JL6205/6)
--> IC6203 (JL6207/8)
--> +1.0V_BE_VDDC, CELL BE VRM (3 phase)--> IC6203 (JL6207/8)
--> IC6104 (JL6109/10)
-->IC6105 (JL6111/12)
-->IC6106 (JL6113/14)
-->IC6105 (JL6111/12)
-->IC6106 (JL6113/14)
--> +3.3V_SB_VDDIO (Q6004) (JL6058)
--> +3.3V_ESW (Q5303) (JL3551)
--> +2.5V_EEGS_PLLVDD1_DIG_+2.5V1 (IC6601) (JL6357)
--> +2.5V_RDRAM_VDD_DIG_+2.5V3 (IC6607) (JL6358)
--> +2.5V_SB_PLL_VDDC (IC6011) (JL6060)
--> +2.5V_LREG_XCG_500_MEM (IC6013) (JL6054)
--> +1.8V_RSX_PLL_VDD (IC6008) (JL6048)
--> +1.8V_SB_PERI (IC6014) (JL6061)
--> +1.8V_EEGS_VDDIO_DIG_+1.8V1 (IC6603) (JL6355)
--> +1.8V_RDRAM_VCMOS_DIG_+1.8V1 (IC6604) (JL6356)
--> +1.6V_BE_VDDA (IC6007) (JL9654)
--> +1.5V_AVCG_VDDIO (IC6019) (JL6056)
--> +1.5V_Bridge (IC6021) (JL6069)
--> +1.5V_EEGS_VDDO_DIG_+1.5V4 (IC6606) (JL6354)
--> Q6311 (What's happening here?)
--> +1.2V_MC2_VDDIO (IC6012) (JL6063)
--> +1.2V_RSX_VDDC (IC6204) --> DRVON --> ENABLE (IC6202/3)
--> +1.0V_BE_VDDC (IC6107) --> DRVON --> ENABLE (IC6104/5/6)
--> +1.7V_MISC (IC6301/Q6305) (JL9656)--> +3.3V_ESW (Q5303) (JL3551)
--> +2.5V_EEGS_PLLVDD1_DIG_+2.5V1 (IC6601) (JL6357)
--> +2.5V_RDRAM_VDD_DIG_+2.5V3 (IC6607) (JL6358)
--> +2.5V_SB_PLL_VDDC (IC6011) (JL6060)
--> +2.5V_LREG_XCG_500_MEM (IC6013) (JL6054)
--> +1.8V_RSX_PLL_VDD (IC6008) (JL6048)
--> +1.8V_SB_PERI (IC6014) (JL6061)
--> +1.8V_EEGS_VDDIO_DIG_+1.8V1 (IC6603) (JL6355)
--> +1.8V_RDRAM_VCMOS_DIG_+1.8V1 (IC6604) (JL6356)
--> +1.6V_BE_VDDA (IC6007) (JL9654)
--> +1.5V_AVCG_VDDIO (IC6019) (JL6056)
--> +1.5V_Bridge (IC6021) (JL6069)
--> +1.5V_EEGS_VDDO_DIG_+1.5V4 (IC6606) (JL6354)
--> Q6311 (What's happening here?)
--> +1.2V_MC2_VDDIO (IC6012) (JL6063)
--> +1.2V_RSX_VDDC (IC6204) --> DRVON --> ENABLE (IC6202/3)
--> +1.0V_BE_VDDC (IC6107) --> DRVON --> ENABLE (IC6104/5/6)
--> +1.5V_YC_RC_VDDA (Q6308) (JL9655)
--> +1.2V_SB_VDDC (Q6309) (JL9648)
--> +1.2V_SB_VDDR (Q6309) (JL9648)
--> +1.2V_YC_RC_VDDIO (Q6310 ) (JL9652)
--> +1.2V_RSX_VDDR (Q6200) (JL9651)
--> +1.2V_EEGS_VDD_DIG_+1.2V1 (Q6600) (JL6361)
--> +1.2V_ESW (Q3504) (JL9649)
--> +1.8V_RSX_FBVDDQ (IC6301/Q6304) (JL9657)--> +1.2V_SB_VDDC (Q6309) (JL9648)
--> +1.2V_SB_VDDR (Q6309) (JL9648)
--> +1.2V_YC_RC_VDDIO (Q6310 ) (JL9652)
--> +1.2V_RSX_VDDR (Q6200) (JL9651)
--> +1.2V_EEGS_VDD_DIG_+1.2V1 (Q6600) (JL6361)
--> +1.2V_ESW (Q3504) (JL9649)
--> +1.2V_RSX_VDDC
--> IC6201 (2 Phase Buck Controller)
--> +1.0V_BE_VDDC-->IC6202 (JL6205/6)
-->IC6203 (JL6207/8)
-->IC6203 (JL6207/8)
--> IC6103 (3 Phase Buck Controller)
--> IC6104 (JL6109/10)
--> IC6105 (JL6111/12)
--> IC6106 (JL6113/14)
--> IC6105 (JL6111/12)
--> IC6106 (JL6113/14)
12V_MAIN is the one from which most other system voltages are derived (5V, 3.3v, 1.8v, 1.7, 1.2, 1.0 etc). The CPU/GPU/SB, are all powered from this 12V_MAIN. But each one of them has a chain of chips before the correct voltage can get to them. The purpose of these chips is to provide stable voltage and control of when that voltage is delivered.
For example, the CPU's 1.0V_BE_VDDC is produced by its Voltage Regulation Module (VRM). It includes IC6103, a buck controller which drives IC6104, IC6105, IC6106 buck converters. That controller is enabled by the syscon chip at the appropriate time to turn on the CPU. IC6107 is involved in the coordination of this effort. So too are the NEC/TOKIN bulk filtering capacitors. And also the array of MLCC bypass caps. Collectively they constitute the CPU's Voltage Regulation Module.
The RSX has it's own VRM, the SB too. Most subsystems have have an IC controller that enables their voltage at the appropriate time in the Power On Sequence. The Voltage flowchart I made above is the general manner in which these subsystems recieve their voltages. Not every IC in the PS3 is listed, just the major ones involved in producing the system voltages marked by a square box. Also that image was based off the COK-001 Service Manual. It does not apply to all models, but can be used as a general guide for them. Obviously, the PS2 Hardware section will not be included in non-backward compatible models.
How does this relate to power good? Well, each system voltage in a box in that image has a controller IC that is monitoring it's output voltage. If that voltage is within regulation, it will report power good to the SYSCON "system control." If any one of them falls out of regulation and reports no power good, the syscon will refuse to boot.
The voltage flowchart above combined with the MB Side B "Jumper Lead" Test Pad locations below should make diagnosing and troubleshooting easier.
I made this one from scratch, with high enough resolution to read the Labels and to still upload to the forum. I was really pushing the limit here. This will make it easier for you to search the service manual when you find a voltage that's missing. When I say this took a long time to make, it's an understatement.
Speaking of time consuming projects. Here's more fruit from that effort.
ATA = Hard Drive Interface
BC = PS2 Bridge Chip
BEI = Redwood Broadband Engine Interface Controller (AKA RC)
CE = Control Enable
CELL BE = CPU ("Cell Broadband Engine")
CG = Clock Generator
CLK = Clock
CONT = Control
CTL = Control
EE = Emotion Engine (PS2 CPU)
EIB = Element Interconnect Bus
EN = Enable
ESW = Ethernet Switch or Switchable
FB = Feedback
FlexIO = Redwood Rambus FlexIO CPU/GPU Interface
GS = Graphics Synthesizer (PS2 GPU)
MC2 = ? (VDDIO à BE_SPI, CHKSTP, JTAG, TBEN, & P_L_BYPASS)
MIC = Yellowstone Memory Interface Controller (AKA YC)
PCI = PS2 Hardware Interface
PLL = Phase-Locked Loop
PPE = Power Processor Element (main dual threaded CPU)
PWRGD = Power Good
RC = Redwood Broadband Engine Interface Controller (AKA BEI)
RRAC = Redwood Rambus FlexIO CPU/GPU Interface Voltage (VDDR)
RST = Reset
RSX = GPU ("Reality Synthesizer")
SB = South Bridge
SPE = Synergistic Processing Element (8x, 1 disabled for redundancy)
STBY = Standby
SW = Switch
VDD = Positive Field Emitting Transistor (FET) Voltage
VDDA = Positive FET Voltage Supply for Analog Subsystems
X = Rambus XDRAM Memory Subsystem
XDR = Yellowstone XDRAMTM System Memory (Y0_XDR0, Y0_XDR1, Y1_XDR0, & Y1_XDR1)
XGC = XDRAM Clock Generator
XIO = Yellowstone Rambus CPU/XDR Memory Interface ("Extreme Data Rate IO")
YC = Yellowstone Memory Interface Controller (AKA MIC)
YRAC = Yellowstone Rambus CPU/XDR Memory Interface Voltage
BC = PS2 Bridge Chip
BEI = Redwood Broadband Engine Interface Controller (AKA RC)
CE = Control Enable
CELL BE = CPU ("Cell Broadband Engine")
CG = Clock Generator
CLK = Clock
CONT = Control
CTL = Control
EE = Emotion Engine (PS2 CPU)
EIB = Element Interconnect Bus
EN = Enable
ESW = Ethernet Switch or Switchable
FB = Feedback
FlexIO = Redwood Rambus FlexIO CPU/GPU Interface
GS = Graphics Synthesizer (PS2 GPU)
MC2 = ? (VDDIO à BE_SPI, CHKSTP, JTAG, TBEN, & P_L_BYPASS)
MIC = Yellowstone Memory Interface Controller (AKA YC)
PCI = PS2 Hardware Interface
PLL = Phase-Locked Loop
PPE = Power Processor Element (main dual threaded CPU)
PWRGD = Power Good
RC = Redwood Broadband Engine Interface Controller (AKA BEI)
RRAC = Redwood Rambus FlexIO CPU/GPU Interface Voltage (VDDR)
RST = Reset
RSX = GPU ("Reality Synthesizer")
SB = South Bridge
SPE = Synergistic Processing Element (8x, 1 disabled for redundancy)
STBY = Standby
SW = Switch
VDD = Positive Field Emitting Transistor (FET) Voltage
VDDA = Positive FET Voltage Supply for Analog Subsystems
X = Rambus XDRAM Memory Subsystem
XDR = Yellowstone XDRAMTM System Memory (Y0_XDR0, Y0_XDR1, Y1_XDR0, & Y1_XDR1)
XGC = XDRAM Clock Generator
XIO = Yellowstone Rambus CPU/XDR Memory Interface ("Extreme Data Rate IO")
YC = Yellowstone Memory Interface Controller (AKA MIC)
YRAC = Yellowstone Rambus CPU/XDR Memory Interface Voltage
+1.0V_BE_VDDC = Cell Be Processor Core (PPE/SPEs)
+1.5V_BE_THERMAL_VDDA = CPU Thermal Power?
+1.6V_BE_VDDA = CPU ADC Voltage for PLL & Thermal
+1.5V_BE_YC_VDDA = CPU/XDR Yellowstone XIO Controller ADC Interface
+1.5V_BE_RC_VDDA = SB/CPU Redwood Rambus FlexIO Controller ADC Interface
+1.2V_RSX_VDDR = RSX Redwood Rambus FlexIO Core
+1.2V_RSX_VDDC = RSX Processor Core
+1.5V_RSX_RC_VDDA = RSX Redwood Rambus FlexIO Controller ADC Interface
+1.5V_RSX_VDDIO = VDDP_VO (Voltage for Picture, Video Out to DVE/HDMI)
+1.8V_RSX_PLL_VDD = RSX Phase-Locked Loop
+1.8V_RSX_FBVDDQ = RSX DRAM
+1.2V_YC_RC_VDDIO = XDR/CPU/SB Yellowstone XIO & Redwood Rambus FlexIO Core
+1.2V_MC2_VDDIO = BE_SPI, CHKSTP, JTAG, TBEN, & P_L_BYPASS
+1.5V_XDR_YC_VDDA = Yellowstone Memory Interface Controller
+1.5V_YC_RC_VDDA = CPU/SB Yellowstone XIO & Rambus FlexIO Controller ADC Interface
+1.8V_VDD_MEM = XDRAM Voltage
+1.2V_ESW = Ethernet Controller (IC3503) VDD_Core (IC3501/Q3504)
+1.9V_ESW = Ethernet Controller (IC3503) VDDAH (IC3502)
+3.3V_ESW = Ethernet Controller (IC3503) VDDO (Q3501)
+1.2V_SB_VDDC = Southbridge Processor Core
+1.2V_SB_VDDR = SB Redwood Rambus FlexIO Core
+1.8V_SB_PERI
+3.3V_SB_VDDIO
+1.5V_BE_THERMAL_VDDA = CPU Thermal Power?
+1.6V_BE_VDDA = CPU ADC Voltage for PLL & Thermal
+1.5V_BE_YC_VDDA = CPU/XDR Yellowstone XIO Controller ADC Interface
+1.5V_BE_RC_VDDA = SB/CPU Redwood Rambus FlexIO Controller ADC Interface
+1.2V_RSX_VDDR = RSX Redwood Rambus FlexIO Core
+1.2V_RSX_VDDC = RSX Processor Core
+1.5V_RSX_RC_VDDA = RSX Redwood Rambus FlexIO Controller ADC Interface
+1.5V_RSX_VDDIO = VDDP_VO (Voltage for Picture, Video Out to DVE/HDMI)
+1.8V_RSX_PLL_VDD = RSX Phase-Locked Loop
+1.8V_RSX_FBVDDQ = RSX DRAM
+1.2V_YC_RC_VDDIO = XDR/CPU/SB Yellowstone XIO & Redwood Rambus FlexIO Core
+1.2V_MC2_VDDIO = BE_SPI, CHKSTP, JTAG, TBEN, & P_L_BYPASS
+1.5V_XDR_YC_VDDA = Yellowstone Memory Interface Controller
+1.5V_YC_RC_VDDA = CPU/SB Yellowstone XIO & Rambus FlexIO Controller ADC Interface
+1.8V_VDD_MEM = XDRAM Voltage
+1.2V_ESW = Ethernet Controller (IC3503) VDD_Core (IC3501/Q3504)
+1.9V_ESW = Ethernet Controller (IC3503) VDDAH (IC3502)
+3.3V_ESW = Ethernet Controller (IC3503) VDDO (Q3501)
+1.2V_SB_VDDC = Southbridge Processor Core
+1.2V_SB_VDDR = SB Redwood Rambus FlexIO Core
+1.8V_SB_PERI
= VCC18 Starship2 Flash Controller
= VDDP Starship2 Flash Controller
= SB_ATA1 (P34)
= Power (P60)
+2.5V_SB_PLL_VDDC =Southbridge Phase-Locked Loop= VDDP Starship2 Flash Controller
= SB_ATA1 (P34)
= Power (P60)
+3.3V_SB_VDDIO
= VDD33 Starship2 Flash Controller
= Nand Flash 0 & 1
= SB_Main EBUS (P30)
= SB_Peripheral Parts (P31)
= SB_Rear USB, ATA0, & PCI (P32)
= SB_Front USB (P33)
= SB_ATA1 (P34)
= SB_EtherWS (P35)
= Power (P60)
= Nand Flash 0 & 1
= SB_Main EBUS (P30)
= SB_Peripheral Parts (P31)
= SB_Rear USB, ATA0, & PCI (P32)
= SB_Front USB (P33)
= SB_ATA1 (P34)
= SB_EtherWS (P35)
= Power (P60)
/SYSCON_RST --> EN Pin 3 (IC6009) --> +3.3V_THERMAL
/BE_POW_FAIL <-- PWRGD Pin 7 (IC6103) (JL6103)
/RSX_POW_FAIL <-- PWRGD Pin 7 (IC6201) (JL6201)
/POW_FAIL (12V) --> OUT Pin 4 (IC6023)
SW_ATA --> Enables Gate Pin 2 (Q6006) --> Enables Gate (Q6007) --> +5V_HDD
SW_PCI
SW_0
SW_1_A --> CONT Pin 5 (IC6020) --> +3.3V_MK_VDD (IC5001)
SW_4_A
SW_6
SW_7_A
SW_8_A
SW_8_B
SW_8_C
To PS2 Bridge
SW_1.2 --> EN Pin 3 (IC6602) --> +1.2V_EEGS_VDD_DIG_+1.2V1 (JL6361)
SW_1.5 --> CE Pin 5 (IC6606) --> +1.5V_EEGS_VDDO_DIG_+1.5V4 (JL6354)
SW_1.8 --> EN Pin 3 (IC6604) --> +1.8V_RDRAM_VCMOS_DIG_+1.8V1 (JL6356)
SW_1.81 --> CONT Pin 5 (IC6603) --> +1.8V_EEGS_VDDIO_DIG_+1.8V1 (JL6355)
SW_2.5 --> EN Pin 3 (IC6601) --> +2.5V_EEGS_PLLVDD1_DIG_+2.5V1 (JL6357)
SW_2.65 --> CONT Pin 5 (IC6607) --> +2.5V_RDRAM_VDD_DIG_+2.5V3 (JL6358)
SW_3.1 --> CE Pin 3 (IC6600) --> +3.1V_EEGS_AVDA_DIG_+3.1V1 (JL6359)
SW_3.3 -->CONT Pin 3 (IC6605) --> +3.3V_DRCG_VDD_DIG_+3.3V1 (JL6360)
AUDIO Pin 16 (IC2102)
--> Vdd Pin 1 (IC1101)
--> Vdd Pin 1 (IC2101)
--> VDD Pin 8 (IC3101)
--> Vdd Pin 1 (IC2101)
--> VDD Pin 8 (IC3101)
/BE_POW_FAIL <-- PWRGD Pin 7 (IC6103) (JL6103)
/RSX_POW_FAIL <-- PWRGD Pin 7 (IC6201) (JL6201)
/POW_FAIL (12V) --> OUT Pin 4 (IC6023)
SW_ATA --> Enables Gate Pin 2 (Q6006) --> Enables Gate (Q6007) --> +5V_HDD
SW_PCI
--> CONT Pin 5 (IC6021) --> +1.5V_Bridge (IC7301)
--> CONT Pin 5 (IC6022) --> +3.3V_Bridge (IC7301)
--> CONT Pin 5 (IC6022) --> +3.3V_Bridge (IC7301)
SW_0
--> CTL1 Pin 9 (IC6003) --> +5V_MISC
--> CTL2 Pin 10 (IC6003) --> +3.3V_MISC
--> STBY2 Pin 10 (IC6301) --> +1.7V_MISC
--> CTL2 Pin 10 (IC6003) --> +3.3V_MISC
--> STBY2 Pin 10 (IC6301) --> +1.7V_MISC
SW_1_A --> CONT Pin 5 (IC6020) --> +3.3V_MK_VDD (IC5001)
- For Clock Synthesizer
- Analog Voltage for the core PLL of IC5004, which is an ICS9214 Clock Generator used to support the Rambus XDR memory subsystem and Redwood logic interface.
--> IN_PSV Pin 1 (IC6302) --> +1.8V_VDD_MEM (JL9647)
SW_3--> EN Pin 3 (IC6305)
--> +1.2V_SB_VDDC (JL9648)
--> +1.2V_SB_VDDR (JL9648)
--> +1.2V_SB_VDDR (JL9648)
SW_4_A
--> Base Q3501
SW_4_B--> Enable Pin 3 (IC3501) --> +1.2V_ESW
--> CONT Pin 5 (IC3502) --> +1.9V_ESW
--> Base (Q3502) --> Base (Q3503) --> +3.3V_ESW
--> P3_ENABLE PD Pin 93 (IC3503) --> Ethernet Controller
--> CONT Pin 5 (IC3502) --> +1.9V_ESW
--> Base (Q3502) --> Base (Q3503) --> +3.3V_ESW
--> P3_ENABLE PD Pin 93 (IC3503) --> Ethernet Controller
--> Enables Gate Pin 5 (Q6006) --> Enables Gate (Q6008) --> +5V_USB
--> CONT Pin 5 (IC6014) --> +1.8V_SB_PERI
--> EN Pin 3 (IC6011) --> +2.5V_SB_PLL_VDDC
SW_5_A--> CONT Pin 5 (IC6014) --> +1.8V_SB_PERI
--> EN Pin 3 (IC6011) --> +2.5V_SB_PLL_VDDC
--> Enable Pin 29 (IC6201)
--> PWM Pin 3 (IC6202) --> +1.2V_RSX_VDDC (JL6205/6)
--> PWM Pin 3 (IC6203) --> +1.2V_RSX_VDDC (JL6207/8)
--> PWM Pin 3 (IC6203) --> +1.2V_RSX_VDDC (JL6207/8)
SW_6
--> CE Pin 3 (IC6012) --> +1.2V_MC2_VDDIO
--> EN Pin 3 (IC6303) --> +1.2V_YC_RC_VDDIO (JL9652)
--> EN Pin 3 (IC6303) --> +1.2V_YC_RC_VDDIO (JL9652)
SW_7_A
--> Enable Pin 29 (IC6103)
--> PWM Pin 3 (IC6004) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6005) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6006) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6005) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6006) --> +1.0V_BE_VDDC
SW_8_A
--> EN Pin 3 (IC6007) --> +1.6V_BE_VDDA (JL9654)
--> EN Pin 3 (IC6304) --> +1.5V_YC_RC_VDDA (JL9655)
--> EN Pin 3 (IC6304) --> +1.5V_YC_RC_VDDA (JL9655)
SW_8_B
-->EN Pin 3 (IC6019) --> +1.5V_AVCG_VDDIO (IC2102)
--> EN Pin 3 (IC6017) --> +1.5V_RSX_VDDIO
--> EN Pin 3 (IC6017) --> +1.5V_RSX_VDDIO
SW_8_C
--> EN Pin 3 (IC6008) --> +1.8V_RSX_PLL_VDD
--> STBY1 Pin 9 (IC6301) --> +1.8V_RSX_FBVDDQ
--> STBY1 Pin 9 (IC6301) --> +1.8V_RSX_FBVDDQ
To PS2 Bridge
SW_1.2 --> EN Pin 3 (IC6602) --> +1.2V_EEGS_VDD_DIG_+1.2V1 (JL6361)
SW_1.5 --> CE Pin 5 (IC6606) --> +1.5V_EEGS_VDDO_DIG_+1.5V4 (JL6354)
SW_1.8 --> EN Pin 3 (IC6604) --> +1.8V_RDRAM_VCMOS_DIG_+1.8V1 (JL6356)
SW_1.81 --> CONT Pin 5 (IC6603) --> +1.8V_EEGS_VDDIO_DIG_+1.8V1 (JL6355)
SW_2.5 --> EN Pin 3 (IC6601) --> +2.5V_EEGS_PLLVDD1_DIG_+2.5V1 (JL6357)
SW_2.65 --> CONT Pin 5 (IC6607) --> +2.5V_RDRAM_VDD_DIG_+2.5V3 (JL6358)
SW_3.1 --> CE Pin 3 (IC6600) --> +3.1V_EEGS_AVDA_DIG_+3.1V1 (JL6359)
SW_3.3 -->CONT Pin 3 (IC6605) --> +3.3V_DRCG_VDD_DIG_+3.3V1 (JL6360)
AUDIO Pin 16 (IC2102)
- --> RSX_AVCLK3
- --> A1 Pin 2 (IC2105)
- --> DRCG_GEN18M --> Xin Pin 4 (IC7001) --> IC7002 (RDRAM)
- --> IC7003 (RDRAM)
- --> IC7004 (EE+GS)
- --> DRCG_GEN18M --> Xin Pin 4 (IC7001) --> IC7002 (RDRAM)
Do not take the above as gospel. If you notice anything needing updated let me know and I'll edit back as necessary.
Getting back to Power good:
Notice the GPU Buck Controller (IC6201). It's locate at B5. This controller is what controls power to the RSX. I have labeled the jumper locations for Enable, which is the signal SYSCON sends to power on the RSX. I also labeled Power Good (PWRGD), which is the signal the controller sends back to the SYSCON about the power regulation. If it's bad, /RSX_POW_FAIL goes low and the syscon throws an error. Which error? 3004 or 1002. Which one is a mystery still. I hypothesize it depends upon the Step number of the Power On Sequence. Basically, when power good went low. The hypothesis is that earlier step numbers = 3004. Later step numbers = 1002. However, the earliest reported 1002 was 06, and 3004 was 09. So that is inconsistant with my hypothesis. The 06 1002 report could be inaccurate, but reports are all I have to go off of.
The last pad I labeled on the RSX VRM Controller is the voltage feedback/drop jumper. This is what the controller is monitoring to decide if power is good or not. We should be able to probe this point to see voltage drop across RSX_VDDC. If it drops too much it triggers under voltage lock out and the controller will send no power good (PWRGD low). The syscon will error. The CPU has the same and other controllers around the board have a similar function.
Since, preventing voltage drops on the CPU/GPU is important for system stability, the NEC/TOKIN's are a concern. If they can't sustain the voltage for long enough underload, the voltage drop will fall out of regulation. One way to prevent this is to replace failing/aged tokins with new tantalum capacitors. Everyone is already familar with that. But there is another way. By adjusting the power good voltage dropout threshold, so that there is a wider range the voltage can fall before triggering an error.
Adjusting Power Good Threshold
Vid pins VID0-5 on the buck controller form a 6-digit code corresponding to the Vout No load setpoint. Power Good Vmin and Vmax thresholds are relative to that set point. With the stock COK-00X voltage divider values (15K and 20k), Vmin = -163mV. Vmax is always +100mV. The Vout voltage cannot deviate more than that. If it does power good goes low and the SYSCON will error.
In some official SONY refurbished consoles, new resistor values (27K and 10K) change Vmin = -400mV. So the Low Voltage threshold is now more than twice as low, allowing much more voltage ripple before it triggers an error. My hypothesis is SONY did this to reduce the frequency of 1001 and 1002's errors. That would explain why they did it to both buck controllers (CPU and GPU). A sort of admission of guilt that they either set it too aggressively or were compensating for bad NEC/TOKINs without replacing them.
Power good low voltage threshold is there to prevent system instability, but if SONY decided it was okay to loosen it, then perhaps we can follow suit. It could be particularly important because we're seeing a lot of unexplained 1001's recently. Currently, 1002's are assumed to be bad NEC/TOKIN's. Replacing aged bulk filter capacitors certainly works, but just because changing them fixes the error doesn't mean that's the only way to skin a cat.
I have intentionally held off recommending this mod to people, because I'm only freshly aware of it's potential. Before I conclude this is okay to do, I would like to know what the VID at idle is, so we can compare actual voltage measurements with the low voltage threshold. On a console with 1001/1002 errors, Vout should drop more than that before it experiences a YLOD. That means I need oscilloscope measurements of Vout on both the CPU/GPU and PWRGD. Then, by replicating Sony's mod, I would like to see if the error goes away AND the system is stable (requires stress testing)! If so, then we have discovered an easier method of resolving these errors.
Replacing those resistors is fine micro-soldering work that pretty much requires a microscope. And I need oscilloscope measurements of the voltage drop and PWRGD (Cell BE for 1001 and RSX for 1002). So it's not too easy or cheap.
That's more than enough to digest for now.
To be concluded...
Last edited:
vyktormvmpay25
Senior Member
@feng_ye your software side is fine, otherwise you won't be able to see "Connecting to Debug Device (SB UART)."
This is either one missing resistance from rsx side to AV ic /Hdmi ic, either that special glod. If you want to try exchange AV ic or Hdmi ic is your choice, or focus and compare that area. not sure what to say from here, but I am sure no software errors on that unit.
Also check that AV and Hdmi area parts very well.
You can also exchange both but start with AV ic, testing after each exchange.
This is either one missing resistance from rsx side to AV ic /Hdmi ic, either that special glod. If you want to try exchange AV ic or Hdmi ic is your choice, or focus and compare that area. not sure what to say from here, but I am sure no software errors on that unit.
Also check that AV and Hdmi area parts very well.
You can also exchange both but start with AV ic, testing after each exchange.
Last edited:
DeadEnd
Senior Member
No need to exchange HDMI IC, you can just check it by running commands like "hdmi chstat 0" a "hdmi ports" and "hdmi redid". I think it should be done when it's connected to a tv/monitor.
vyktormvmpay25
Senior Member
So it is special glod?
Similar threads
-
-
PS3 CECHA00 with several SYSCON errors (3004, 1001,1002, 2120,3011)
- Started by LSL
- Replies: 7
-
PS3 Interesting PS3 Errors (1802, 1701, 1601) and Capacitor Replacement- Started by Cheshire UK
- Replies: 2
-