ARandomOSDever
Forum Noob
Hello everyone, I recently got a broken CECH-3008B from a friend (he didn't want it repaired, he just gave it to me for free). He told me that it shuts down after pressing the power button (I couldn't confirm with the power button since the button board FFC contacts were broken), so I checked the PSU, however it's OK (5VSB measures ~5.5V, 12V measures ~12.6V). When I connected the Syscon UART to my PC (via a Raspberry Pi Pico 2W with https://github.com/Noltari/pico-uart-bridge), I got the following messages:
>$ auth
Auth successful
Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS2 ok.
# [PowSeq] Error:9103
# [SSM] PS3 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# CODE CLOCK
# A0403034 FFFFFFFF
# A0404432 FFFFFFFF
# all the other entries were FFFFFFFF FFFFFFFF as I cleared the errlog
I decided to fully disassemble the PS3 to check the fuses (all of the labeled ones are OK), and when I reassembled it and reconnected the Syscon bus, I instead got these errors:
>$ bringup
E00000E0
# [SSM] Bringup Start.
# [PowSeq] Error:8402
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=F4D0.
Press Ctrl+C to exit
>$ HALT
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)
>$ errlog
00000000
# CODE CLOCK
# A0012041 FFFFFFFF
# others were either A0012041 or FFFFFFFF
The error wasn't described on PSDevWiki but a similar error (2040) with the same PowSeq error (but different Cond/Fatal) said this could happen because something on the 5V line is shorting, but the 5V line from the PSU measured normally. It also didn't trigger a automatic shutdown so I had to shutdown manually.
The Syscon is a SW3-301 with FW version 2.3.0, the board is KTE-001 and I don't know if there's a YLOD (since the button board FFC is broken)
>$ auth
Auth successful
Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
Press Ctrl+C to exit
>$ errlog
00000000
# [SSM] PS2 ok.
# [PowSeq] Error:9103
# [SSM] PS3 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# CODE CLOCK
# A0403034 FFFFFFFF
# A0404432 FFFFFFFF
# all the other entries were FFFFFFFF FFFFFFFF as I cleared the errlog
I decided to fully disassemble the PS3 to check the fuses (all of the labeled ones are OK), and when I reassembled it and reconnected the Syscon bus, I instead got these errors:
>$ bringup
E00000E0
# [SSM] Bringup Start.
# [PowSeq] Error:8402
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=F4D0.
Press Ctrl+C to exit
>$ HALT
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)
>$ errlog
00000000
# CODE CLOCK
# A0012041 FFFFFFFF
# others were either A0012041 or FFFFFFFF
The error wasn't described on PSDevWiki but a similar error (2040) with the same PowSeq error (but different Cond/Fatal) said this could happen because something on the 5V line is shorting, but the 5V line from the PSU measured normally. It also didn't trigger a automatic shutdown so I had to shutdown manually.
The Syscon is a SW3-301 with FW version 2.3.0, the board is KTE-001 and I don't know if there's a YLOD (since the button board FFC is broken)
