PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

db260179 said:
The only good way to diagnose GLOD, is enable the debug option for SB uart in the syscon, then connect up the RX and TX to the SB uart pins on the board (still alot of unknowns, where the pins are) then watch to boot log and see where it gets stuck at.

GLOD is varies issues that dont report any error logs. USB controller, bad FLASH, CELL faulty... the list goes on
Click to expand...
I think that might have been where I got stuck with mine it has an intermittent GLoD that sometimes YLoDs. I keep trying to read the errors from it but it just locks up.
 
db260179 said:
The only good way to diagnose GLOD, is enable the debug option for SB uart in the syscon, then connect up the RX and TX to the SB uart pins on the board (still alot of unknowns, where the pins are) then watch to boot log and see where it gets stuck at.

GLOD is varies issues that dont report any error logs. USB controller, bad FLASH, CELL faulty... the list goes on
Click to expand...

Is there a way to debug after the lv2 loaded? I have a few units that loads past lv2 ( lv2(2): initial system process done.) but still black screen. Sometimes beeps once or twice later, but nothing on syscon or SB uart.
 
Would a response of F0000003 no matter which command I use be a potential indication of a dead syscon @db260179? I switched back to using the linux script so I could get a better idea of why the windows script kept crashing on me but that's the only thing I get when using it on this DECHA and CECHA.
I've only see one other person mention getting this error and he also had a GLoD.
 
Last edited:
CodeKiller said:
Is there a way to debug after the lv2 loaded? I have a few units that loads past lv2 ( lv2(2): initial system process done.) but still black screen. Sometimes beeps once or twice later, but nothing on syscon or SB uart.
Click to expand...

https://www.psdevwiki.com/ps3/SC_EEPROM

You need to enable it first - sb uart - 2

0x48C021Network Device Mode (sys.dbgcard.dgbe / debug interface (select_net_device) (-1: Ethernet 2, 0: IFB, 1: CP, 2: SB UART, 3: CP ch4, 5: invalid ))
then up the debug level

0x48C111bootrom trace level (0x00: fatal errors, 0x01: errors, 0x02: information messages, 0x03: debug messages)
As quoted by M4jor - https://www.psx-place.com/threads/fun-with-syscon-and-serial-commands.29913/#post-245865

If this doesnt help, then there are some basic checks to do.

Verify boot order - https://www.psdevwiki.com/ps3/Boot_Order

When powered on, does the HDD flash more than once?
Plugging in a usb cable to controller, does the controller flash or operate?

in the syscon shell, run the hdmi commands to verify the hdmi controller picking up a cable or monitor.

Can hardware read the flash chips? - if not indicates bad flash chip

Can you enter recovery mode, hold pwr button then switch on

Otherwise its an unknown issue ive not come across.
 
Last edited:
db260179 said:
https://www.psdevwiki.com/ps3/SC_EEPROM

You need to enable it first - sb uart - 2

0x48C021Network Device Mode (sys.dbgcard.dgbe / debug interface (select_net_device) (-1: Ethernet 2, 0: IFB, 1: CP, 2: SB UART, 3: CP ch4, 5: invalid ))
then up the debug level

0x48C111bootrom trace level (0x00: fatal errors, 0x01: errors, 0x02: information messages, 0x03: debug messages)
As quoted by M4jor - https://www.psx-place.com/threads/fun-with-syscon-and-serial-commands.29913/#post-245865

If this doesnt help, then there are some basic checks to do.

Verify boot order - https://www.psdevwiki.com/ps3/Boot_Order

When powered on, does the HDD flash more than once?
Plugging in a usb cable to controller, does the controller flash or operate?

in the syscon shell, run the hdmi commands to verify the hdmi controller picking up a cable or monitor.

Can hardware read the flash chips? - if not indicates bad flash chip

Can you enter recovery mode, hold pwr button then switch on

Otherwise its an unknown issue ive not come across.
Click to expand...
Been there done that --- that's how I got the 'lv2...done.' in the first place. (at least in COK002 boards)

I would not look into this deep if the recovery mode would work
HDMI status: waiting / WaitResolution /Unset... -- also no screen on DVE (analog AV out)

On the Slims have one (3000) that gives the following LED sequence after Fan-test: GGGR GGRG GGGG GGGG whatever that's mean.
The other Slim (2000) does not even run through entirely the Fan-test, 3 beeps and blinking red LED .. but no new entry in the errlog --- on the other hand it gives the following message:
Code: 
# [SSM] Cond/Fatal received, msg=26AA.
any idea what does that mean? (there were a lot of A0801002 before but since recapped -- still no picture)
 
CodeKiller said:
Been there done that --- that's how I got the 'lv2...done.' in the first place. (at least in COK002 boards)

I would not look into this deep if the recovery mode would work
HDMI status: waiting / WaitResolution /Unset... -- also no screen on DVE (analog AV out)

On the Slims have one (3000) that gives the following LED sequence after Fan-test: GGGR GGRG GGGG GGGG whatever that's mean.
The other Slim (2000) does not even run through entirely the Fan-test, 3 beeps and blinking red LED .. but no new entry in the errlog --- on the other hand it gives the following message:
Code: 
# [SSM] Cond/Fatal received, msg=26AA.
any idea what does that mean? (there were a lot of A0801002 before but since recapped -- still no picture)
Click to expand...
I remember seeing a page in the devwiki that listed a few LED sequences and their (possible) meaning. At the time I didn't have a slim, so I didn't think much about it, but I know it's there somewhere.
 
Last edited:
From the wiki (thanks @sandungas for finding it, it's exactly what I was thinking)

On my bricked slim (CECH-2501B) the first sequence of 4 is: green red green red.
On my working slim (CECH-2101B) the first sequence is: red red red red.
On my other working slim (CECH-3001A) the first sequence is: red red red red.
On all three consoles the next 3 sequence's, are all red.
So it seems that red=good and green=bad. Also I removed the Blu-ray drive on my bricked slim and the codes did not change. sorry I don't know more about this.

It's too bad that we don't have syscon error codes to go with those, but there has to be a correlation, right? I would bet Sony introduced these led codes as a faster way to get diagnostics, instead of having to plug into the syscon and all that fun stuff. Maybe @db260179 knows something about this?
 
marciolsf said:
From the wiki (thanks @sandungas for finding it, it's exactly what I was thinking)

On my bricked slim (CECH-2501B) the first sequence of 4 is: green red green red.
On my working slim (CECH-2101B) the first sequence is: red red red red.
On my other working slim (CECH-3001A) the first sequence is: red red red red.
On all three consoles the next 3 sequence's, are all red.
So it seems that red=good and green=bad. Also I removed the Blu-ray drive on my bricked slim and the codes did not change. sorry I don't know more about this.

It's too bad that we don't have syscon error codes to go with those, but there has to be a correlation, right? I would bet Sony introduced these led codes as a faster way to get diagnostics, instead of having to plug into the syscon and all that fun stuff. Maybe @db260179 knows something about this?
Click to expand...

I've got a (now) working 2500 and that shows an LED code of GGRR GGGG GGGG GGRR .. so it doesn't really help.

I think it's not the syscon but some minimal FW code -- but maybe @M4j0r or @zecoxao could clarify it.

It would also be nice to find a new way to externally enable the QA Flags now as (at least some) have access to syscon dumps.
 
CodeKiller said:
Been there done that --- that's how I got the 'lv2...done.' in the first place. (at least in COK002 boards)

I would not look into this deep if the recovery mode would work
HDMI status: waiting / WaitResolution /Unset... -- also no screen on DVE (analog AV out)

On the Slims have one (3000) that gives the following LED sequence after Fan-test: GGGR GGRG GGGG GGGG whatever that's mean.
The other Slim (2000) does not even run through entirely the Fan-test, 3 beeps and blinking red LED .. but no new entry in the errlog --- on the other hand it gives the following message:
Code: 
# [SSM] Cond/Fatal received, msg=26AA.
any idea what does that mean? (there were a lot of A0801002 before but since recapped -- still no picture)
Click to expand...

A0801002 is RSX VRAM power fail, so that can be NEC tokins, IC buck power chips or Bad RSX. Unfortunately the retail syscons dont have rsx diag code, otherwise its possible to check the onboard RSX.

im guessing this hasnt had a rsx replaced yet?
 
marciolsf said:
From the wiki (thanks @sandungas for finding it, it's exactly what I was thinking)

On my bricked slim (CECH-2501B) the first sequence of 4 is: green red green red.
On my working slim (CECH-2101B) the first sequence is: red red red red.
On my other working slim (CECH-3001A) the first sequence is: red red red red.
On all three consoles the next 3 sequence's, are all red.
So it seems that red=good and green=bad. Also I removed the Blu-ray drive on my bricked slim and the codes did not change. sorry I don't know more about this.

It's too bad that we don't have syscon error codes to go with those, but there has to be a correlation, right? I would bet Sony introduced these led codes as a faster way to get diagnostics, instead of having to plug into the syscon and all that fun stuff. Maybe @db260179 knows something about this?
Click to expand...

No info on this at all. I tend to reference the schematics and expected readings to diagnose faults. Also the fat models, early ones dont have these sequences.
 
I thought I should post this here also. I have noticed alot of 90 2120 HDMI errors are associated with 40 3034. It happened on my system where the HDMI encoder is fine, but the BGA is not. I got a 2120 on PS3#7, a reballed system that definitely has a good HDMI encoder. It was working in game before the latest Tantalum installation using the SoulKilla PCB. I had to dump a lot of heat into the area near the RSX (just used an Iron, no hot air or anything crazy), but it was apparently enough to pop a BGA connection. The BGA is very delicate and the TOKINs are right there next to the BGA with a very thick Copper plane to conduct the heat. It now has a classic BGA defect SYSCON error, a 40 3034. And it also had a 90 2120.

I have a theory about the 2120. Since the RSX is not communicating correctly during bittraining (3034), the system tries to shutdown. The SYSCON is probably expecting some kind of confirmation from the HDMI encoder that it received the shutdown signal, or there is come coordination between the RSX and the HDMI encoder that was expected, but since the RSX isn't powered on that signal isn't working. The BGA defects on the RSX causing the 40 3034 is the bigger issue. The 2120 is meaningless...

At least that's what I thought until I had an idea. I wondered if the 2120 only happens when the HDMI cable is plugged into the console while trying to boot. So I just unplugged the HDMI cable, ran the bringup command to capture the YLOD --> Only got a 3034. Then Plugged the HDMI cable back in and ran the console again --> got the 3034 and 2120. So yeah, that's all it is. If the HDMI cable is plugged in, it must be seen by the SYSCON as ready to receive a signal or something, but when the RSX never get's powered on and the shutdown error state is initialized the HDMI encoder must send some kind of "Hey I never heard anything from my friend the RSX?"

In any case, now we know to expect a 2120 if the HDMI cable is plugged into the console when there is a BGA defect (3034) - That it doesn't mean there's a problem with the HDMI encoder. And that if there is, it'll show up in a different context (like the cable is unplugged or there are no BGA defects).
Code: 
Microsoft Windows [Version 10.0.18363.1379]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\HTPC>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ AUTH
Auth successful
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[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] stat
>$ lasterrlog
e: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[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]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0403034, Time:0x0b569e8e  2006/01/10 16:34:22
[mullion]$
>$ lasterrlog
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
[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:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[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]: 0xa0403034
[ERROR]: 0xa0902120
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0902120, Time:0x0b569ec7  2006/01/10 16:35:19
[mullion]$
>$
 
Last edited:
RIP-Felix said:
I thought I should post this here also. I have noticed alot of 90 2120 HDMI errors are associated with 40 3034. It happened on my system where the HDMI encoder is fine, but the BGA is not. I got a 2120 on PS3#7, a reballed system that definitely has a good HDMI encoder. It was working in game before the latest Tantalum installation using the SoulKilla PCB. I had to dump a lot of heat into the area near the RSX (just used an Iron, no hot air or anything crazy), but it was apparently enough to pop a BGA connection. The BGA is very delicate and the TOKINs are right there next to the BGA with a very thick Copper plane to conduct the heat. It now has a classic BGA defect SYSCON error, a 40 3034. And it also had a 90 2120.

I have a theory about the 2120. Since the RSX is not communicating correctly during bittraining (3034), the system tries to shutdown. The SYSCON is probably expecting some kind of confirmation from the HDMI encoder that it received the shutdown signal, or there is come coordination between the RSX and the HDMI encoder that was expected, but since the RSX isn't powered on that signal isn't working. The BGA defects on the RSX causing the 40 3034 is the bigger issue. The 2120 is meaningless...

At least that's what I thought until I had an idea. I wondered if the 2120 only happens when the HDMI cable is plugged into the console while trying to boot. So I just unplugged the HDMI cable, ran the bringup command to capture the YLOD --> Only got a 3034. Then Plugged the HDMI cable back in and ran the console again --> got the 3034 and 2120. So yeah, that's all it is. If the HDMI cable is plugged in, it must be seen by the SYSCON as ready to receive a signal or something, but when the RSX never get's powered on and the shutdown error state is initialized the HDMI encoder must send some kind of "Hey I never heard anything from my friend the RSX?"

In any case, now we know to expect a 2120 if the HDMI cable is plugged into the console when there is a BGA defect (3034) - That it doesn't mean there's a problem with the HDMI encoder. And that if there is, it'll show up in a different context (like the cable is unplugged or there are no BGA defects).
Click to expand...

If you look the available schematics carefully, you can see the HDMI chip does not get any control signal from the RSX, just sync, video data and audio data. The Syscon is the one that can interface with its I2C bus and setup or init or something -- that's why there is that much HDMI commands in the Syscon already.
Also, you could try to command it during bringup, and maybe the response would be interleaved in the bringup log.
 
@db260179 Hello, I have a cechc04 (PAL) with glod, it just hands at glod and shuts off. I can get it into safe mode but freezes if I select 6. System update option. Given the bluray ribbon cable issue it has, could possibly be that bluray disconnected during update and system fw is corrupt.

I'm going to buy a teensy ++2 and do more reasearch to attempt to fix it but i was wondering how I can read the sb uart. I did manage to read syscon but no helpful errors( no rsx erros though so thats good, plus no artifacts). It's a COK-001(or 002, I forgot) console and was wondering if you could provide some guidance about enabling debug option for SB through syscon and also when you say "then connect up the RX and TX to the SB uart pins on the board" do you mean the same place where you connect to read syscon or different pins?

I just wish i can get this cechc04 working for me. Many thanks in advance for your time and everything you have offered.
 
Last edited by a moderator:
So I just did the error dump and got the following. Appears the same two codes. What do they mean?

===================================
ERR 00: 00000000 A0A02031 FFFFFFFF
ERR 01: 00000000 A0A02031 FFFFFFFF
ERR 02: 00000000 A0A02031 FFFFFFFF
ERR 03: 00000000 A0022110 FFFFFFFF
ERR 04: 00000000 A0A02031 FFFFFFFF
ERR 05: 00000000 A0022110 FFFFFFFF
ERR 06: 00000000 A0A02031 FFFFFFFF
ERR 07: 00000000 A0A02031 FFFFFFFF
ERR 08: 00000000 A0022110 FFFFFFFF
ERR 09: 00000000 A0A02031 FFFFFFFF
ERR 10: 00000000 A0A02031 FFFFFFFF
ERR 11: 00000000 A0A02031 FFFFFFFF
ERR 12: 00000000 A0A02031 FFFFFFFF
ERR 13: 00000000 A0022110 FFFFFFFF
ERR 14: 00000000 A0A02031 FFFFFFFF
ERR 15: 00000000 A0A02031 FFFFFFFF
ERR 16: 00000000 A0022110 FFFFFFFF
ERR 17: 00000000 A0A02031 FFFFFFFF
ERR 18: 00000000 A0022110 FFFFFFFF
ERR 19: 00000000 A0A02031 FFFFFFFF
===================================

So after doing some research, I understand the 2031 error to be "thermal sensor error ic2101". What does this mean? What is ic2101 mean?
Also the 22110 error means "clock generator error ic5001". Same problem what does the clock generator mean and ic5001? My guess ic5001 is something on the pcb that's faulty?
 
Last edited:
So after doing some research, I understand the 2031 error to be "thermal sensor error ic2101". What does this mean? What is ic2101 mean?
Also the 22110 error means "clock generator error ic5001". Same problem what does the clock generator mean and ic5001? My guess ic5001 is something on the pcb that's faulty?

UPDATE: I used the schematics pdf (below) for SEM-001 ( I need one for DIA-001) and identified the chips for ic5001 and ic2101. It should be noted that this specific board has been reballed (not sure if I was successful without killing the chip) and also had all the necks (both sides) replaced and a bridged (total of 8 bridges, 2x rsx top, 2x rsx bottom, 2x cpu top and 2x cpu bottom).
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top