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

Hello, I have a PS3 Super Slim (CECH-4011B) that turns on, then goes completely off, not even on standby (RED led, then green, then nothing).

I followed Felix's tutorial on how to access the syscon chip, and I successfully accessed it. Could someone help me troubleshoot my PS3?

Thanks.
The syscon session has been attached below.

Code: 
C:\Users\Abraham K. Jenkins\ps3syscon\Linux>python ps3_syscon_uart_script.py COM4 SW
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 4.1.5
#!(Build ID: 4759,49024,
#!Build Date: 2012-04-12_22:37:02)
#!
#!Copyright(C) 2012 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=24AC.
# [SSM] Fataldown Start.
# [SSM] Msg 24AE : being delayed.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Msg 24AE : ignored.
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$
 
RIP-Felix said:
Does anyone know how to enable internal permissions in sherwood to allow the use of INT commands? Such as `hversion` to get the Platform_ID. @M4j0r? Devwiki says it needs to be patched, but doesn't say how.
Click to expand...
You need to patch the actual firmware, either by using a prototype syscon (this has been done) or by using a syscon patch (has not been researched yet, might not be possible).

Edit: Found this which says `r 0 1` is the byte that has the hex value of the Platform_ID. But there was a bit about it only being for SW3 in KTE or later. I just tried it on a 2001a and it returned 61 (CECH-20xxA/B | DYN-001 | CokG11) which is correct, but I wasn't expecting it to work since this model predates the KTE. So now I'm wondering if it would work for all SW?
Click to expand...
The byte at 0x0 will always be there. But the string after it ('r 0 9') should only be present on consoles which deviate from the target specified by the byte.
 
luixiun0 said:
Hello, I have a PS3 Super Slim (CECH-4011B) that turns on, then goes completely off, not even on standby (RED led, then green, then nothing).

I followed Felix's tutorial on how to access the syscon chip, and I successfully accessed it. Could someone help me troubleshoot my PS3?

Thanks.
The syscon session has been attached below.

Code: 
C:\Users\Abraham K. Jenkins\ps3syscon\Linux>python ps3_syscon_uart_script.py COM4 SW
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 4.1.5
#!(Build ID: 4759,49024,
#!Build Date: 2012-04-12_22:37:02)
#!
#!Copyright(C) 2012 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=24AC.
# [SSM] Fataldown Start.
# [SSM] Msg 24AE : being delayed.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Msg 24AE : ignored.
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$
Click to expand...

I'd say RSX going bad, given there's 1701 and 14FF together. I don't see any trace of 1601 though.
 
Does anyone know what this error means? I replaced the HDMI encoder and it did nothing. Is [ERROR]: 0xa0081002 a 1002 error? why does it give the 2120 in the log but no 1002's?

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] fatalreq delayed.
[ERROR]: 0xa0081002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
 
Ganjo said:
Does anyone know what this error means? I replaced the HDMI encoder and it did nothing. Is [ERROR]: 0xa0081002 a 1002 error? why does it give the 2120 in the log but no 1002's?

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] fatalreq delayed.
[ERROR]: 0xa0081002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
Click to expand...
Can you post an errorlog?
 
Ganjo said:
Does anyone know what this error means? I replaced the HDMI encoder and it did nothing. Is [ERROR]: 0xa0081002 a 1002 error? why does it give the 2120 in the log but no 1002's?

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] fatalreq delayed.
[ERROR]: 0xa0081002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
Click to expand...

What model? Other notes like dust, was it sealed, previous signs of rework would also be helpful.

It's saying you have a GPU voltage regulation failure...which usually means bad NEC/Tokins.
 
luixiun0 said:
Hello, I have a PS3 Super Slim (CECH-4011B) that turns on, then goes completely off, not even on standby (RED led, then green, then nothing).

I followed Felix's tutorial on how to access the syscon chip, and I successfully accessed it. Could someone help me troubleshoot my PS3?

Thanks.
The syscon session has been attached below.

Code: 
C:\Users\Abraham K. Jenkins\ps3syscon\Linux>python ps3_syscon_uart_script.py COM4 SW
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF
# A08014FF FFFFFFFF
# A0801701 FFFFFFFF

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 4.1.5
#!(Build ID: 4759,49024,
#!Build Date: 2012-04-12_22:37:02)
#!
#!Copyright(C) 2012 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=24AC.
# [SSM] Fataldown Start.
# [SSM] Msg 24AE : being delayed.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Msg 24AE : ignored.
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$
Click to expand...
Try a known good HDD.

Reballing may help if the issue is the BGA. ATM, you want to rule out easier common causes. HDD, Bluray drive, software issues (like Hen and HB that may be running). Try refreshing the database, etc.
 
RIP-Felix said:
Try a known good HDD.

Reballing may help if the issue is the BGA. ATM, you want to rule out easier common causes. HDD, Bluray drive, software issues (like Hen and HB that may be running). Try refreshing the database, etc.
Click to expand...
Hello Felix, thanks for your reply.

However, I can't seem to get into the system, I have the fully naked board with only a PSU connected, and even then it doesn't turn on.

So I don't think I can do anything in the system, I have another drive with Windows on it i can try to see if it gets recognized in some way.

I do have HEN currently installed in the system, but I don't know how it could fail without the common components like an HDD, BluRay drive, etc being connected to the board.

I have an E3 flasher, is there anything I can do with that?

Thanks.
 
RIP-Felix said:
What model? Other notes like dust, was it sealed, previous signs of rework would also be helpful.

It's saying you have a GPU voltage regulation failure...which usually means bad NEC/Tokins.
Click to expand...

It was an opened E01, and I put a 65nm (2991ggb) RSX from a slim on it. The RSX IHS was already removed. This person sent me another one that had the CELL popcorned from too much heat gunning so who knows what they did to this one.
I made another post with the syscon dump on the previous page. I was reading low resistance on the FBVDDQ line so I removed the RSX again. Would a missing C2162 capacitor cause it? From the schematic it appears to part of an array of caps on 1.2v-yc-rc-vddio. I noticed it was not attached after I removed the RSX.

Does this RSX look bad? The VDDR, VDDA, PLL lines are abnormally out of range.

RSX RESISTANCES
FBVDD 160
PLL 10.3M
VDDA 139K
VDDIO 1.31K
VDDIORW 800
VDDR 305
VDDC 3

Thanks
 
luixiun0 said:
Hello Felix, thanks for your reply.

However, I can't seem to get into the system, I have the fully naked board with only a PSU connected, and even then it doesn't turn on.

So I don't think I can do anything in the system, I have another drive with Windows on it i can try to see if it gets recognized in some way.

I do have HEN currently installed in the system, but I don't know how it could fail without the common components like an HDD, BluRay drive, etc being connected to the board.

I have an E3 flasher, is there anything I can do with that?

Thanks.
Click to expand...
Note that when powered on, the HDD has a spin-up, a read (i think?) then it abruptly shuts down with no soft shutdown sign.
 
luixiun0 said:
Can you post an errorlog?
Click to expand...
This is what I dumped yesterday
[mullion]$
errlog
ofst[ 0]:err_code:0xa0202120, clock:0xffffffff
ofst[ 4]:err_code:0xa0202120, clock:0xffffffff
ofst[ 8]:err_code:0xa0202120, clock:0xffffffff
ofst[ 12]:err_code:0xa0202120, clock:0xffffffff
ofst[ 16]:err_code:0xa0202120, clock:0xffffffff
ofst[ 20]:err_code:0xa0202120, clock:0xffffffff
ofst[ 24]:err_code:0xa0202120, clock:0xffffffff
ofst[ 28]:err_code:0xa0202120, clock:0xffffffff
ofst[ 32]:err_code:0xa0202120, clock:0xffffffff
ofst[ 36]:err_code:0xa0213013, clock:0xffffffff
ofst[ 40]:err_code:0xa0202120, clock:0xffffffff
ofst[ 44]:err_code:0xa0202120, clock:0xffffffff
ofst[ 48]:err_code:0xa0202120, clock:0xffffffff
ofst[ 52]:err_code:0xa0202120, clock:0xffffffff
ofst[ 56]:err_code:0xa0202120, clock:0xffffffff
ofst[ 60]:err_code:0xa0202120, clock:0xffffffff
ofst[ 64]:err_code:0xa0202120, clock:0xffffffff
ofst[ 68]:err_code:0xa0202120, clock:0xffffffff
ofst[ 72]:err_code:0xa0202120, clock:0xffffffff
ofst[ 76]:err_code:0xa0202120, clock:0xffffffff
ofst[ 80]:err_code:0xa0213013, clock:0xffffffff
ofst[ 84]:err_code:0xa0202120, clock:0xffffffff
ofst[ 88]:err_code:0xa0202120, clock:0xffffffff
ofst[ 92]:err_code:0xa0202120, clock:0xffffffff
ofst[ 96]:err_code:0xa0202120, clock:0xffffffff
ofst[100]:err_code:0xa0202120, clock:0xffffffff
ofst[104]:err_code:0xa0202120, clock:0xffffffff
ofst[108]:err_code:0xa0202120, clock:0xffffffff
ofst[112]:err_code:0xa0202120, clock:0xffffffff
ofst[116]:err_code:0xa0202120, clock:0xffffffff
ofst[120]:err_code:0xa0202120, clock:0xffffffff
ofst[124]:err_code:0xa0213013, clock:0xffffffff
[mullion]$
 
luixiun0 said:
Hello Felix, thanks for your reply.

However, I can't seem to get into the system, I have the fully naked board with only a PSU connected, and even then it doesn't turn on.

So I don't think I can do anything in the system, I have another drive with Windows on it i can try to see if it gets recognized in some way.

I do have HEN currently installed in the system, but I don't know how it could fail without the common components like an HDD, BluRay drive, etc being connected to the board.

I have an E3 flasher, is there anything I can do with that?

Thanks.
Click to expand...
The NOR models keep important OS information on the HDD, it wont boot up without one. That's why I asked you to plug one in and try a known working one. You may need to rebuild the OS or whatever it's called. I dont work on slims much so I've never had to do it.
 
Ganjo said:
It was an opened E01, and I put a 65nm (2991ggb) RSX from a slim on it. The RSX IHS was already removed. This person sent me another one that had the CELL popcorned from too much heat gunning so who knows what they did to this one.
I made another post with the syscon dump on the previous page. I was reading low resistance on the FBVDDQ line so I removed the RSX again. Would a missing C2162 capacitor cause it? From the schematic it appears to part of an array of caps on 1.2v-yc-rc-vddio. I noticed it was not attached after I removed the RSX.

Does this RSX look bad? The VDDR, VDDA, PLL lines are abnormally out of range.

RSX RESISTANCES
FBVDD 160
PLL 10.3M
VDDA 139K
VDDIO 1.31K
VDDIORW 800
VDDR 305
VDDC 3

Thanks
Click to expand...
VDDA look way high. It should be closer to 4ohms
 
RIP-Felix said:
The NOR models keep important OS information on the HDD, it wont boot up without one. That's why I asked you to plug one in and try a known working one. You may need to rebuild the OS or whatever it's called. I dont work on slims much so I've never had to do it.
Click to expand...
This is a Super Slim, don't know if it can be flashed because it has a big chunky SATA connector next to a memory-looking chip.

Anyways, are you suggesting that I use a clean hard drive or clone my previous one to another one?

Thanks.

EDIT: Just keeping you updated, I bought the E3 Nor Flasher for a Slim PS3 that's currently alive and well.
 
Last edited:
Hello I have an a01 with I believe a dc/dc power problem I have already replaced the power unit and it is giving me the same type of error is there another problem / how do I diagnose and fix this one
Code: 
>$ ERRLOG GET 00
00000000 A0231004 0B4B4980
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0011004 0B48C396
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0801004 0B48C2D4
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0021004 0B48B506
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0051004 0B48A656
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0801004 0B48A0DB
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0801004 0B48A073
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0801004 0B489F4D
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0031004 0B48981E
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0801004 0B489814
Press Ctrl+C to exit
>$ ERRLOG GET 0a
00000000 A0011004 0B48951B
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0801004 0B489284
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0801004 0B48911F
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801004 0B488FFD
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0041004 0B488F69
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801004 0B488CD8
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0801004 0B488CAD
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0011004 0B488C07
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0801004 0B488B69
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0801004 0B488B5B
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0801004 0B4888CA
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0801004 0B4887FB
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0801004 0B4886A0
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0801004 2D1FC236
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0801004 2D1FC20E
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0801004 2D1FC205
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0081004 2D1FC1F8
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0801004 2D1F6029
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0801004 2D1F5FF2
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0801004 2D1F5FEA
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0801004 2D1F5F07
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF 2D13DB27
Press Ctrl+C to exit

ofst[ 52]:err_code:0xffffffff, clock:0x2d1f5f07  2023/12/27 22:17:43

ofst[ 56]:err_code:0xa0801004, clock:0x2d1f5fea  2023/12/27 22:21:30

ofst[ 60]:err_code:0xa0801004, clock:0x2d1f5ff2  2023/12/27 22:21:38

ofst[ 64]:err_code:0xa0801004, clock:0x2d1f6029  2023/12/27 22:22:33

ofst[ 68]:err_code:0xa0081004, clock:0x2d1fc1f8  2023/12/28 05:19:52

ofst[ 72]:err_code:0xa0801004, clock:0x2d1fc205  2023/12/28 05:20:05

ofst[ 76]:err_code:0xa0801004, clock:0x2d1fc20e  2023/12/28 05:20:14

ofst[ 80]:err_code:0xa0801004, clock:0x2d1fc236  2023/12/28 05:20:54

ofst[ 84]:err_code:0xa0801004, clock:0x0b4886a0  2005/12/31 00:00:32

ofst[ 88]:err_code:0xa0801004, clock:0x0b4887fb  2005/12/31 00:06:19

ofst[ 92]:err_code:0xa0801004, clock:0x0b4888ca  2005/12/31 00:09:46

ofst[ 96]:err_code:0xa0801004, clock:0x0b488b5b  2005/12/31 00:20:43

ofst[100]:err_code:0xa0801004, clock:0x0b488b69  2005/12/31 00:20:57

ofst[104]:err_code:0xa0011004, clock:0x0b488c07  2005/12/31 00:23:35

ofst[108]:err_code:0xa0801004, clock:0x0b488cad  2005/12/31 00:26:21

ofst[112]:err_code:0xa0801004, clock:0x0b488cd8  2005/12/31 00:27:04

ofst[116]:err_code:0xa0041004, clock:0x0b488f69  2005/12/31 00:38:01

ofst[120]:err_code:0xa0801004, clock:0x0b488ffd  2005/12/31 00:40:29

ofst[124]:err_code:0xa0801004, clock:0x0b48911f  2005/12/31 00:45:19

ofst[  0]:err_code:0xa0801004, clock:0x0b489284  2005/12/31 00:51:16

ofst[  4]:err_code:0xa0011004, clock:0x0b48951b  2005/12/31 01:02:19

ofst[  8]:err_code:0xa0801004, clock:0x0b489814  2005/12/31 01:15:00

ofst[ 12]:err_code:0xa0031004, clock:0x0b48981e  2005/12/31 01:15:10

ofst[ 16]:err_code:0xa0801004, clock:0x0b489f4d  2005/12/31 01:45:49

ofst[ 20]:err_code:0xa0801004, clock:0x0b48a073  2005/12/31 01:50:43

ofst[ 24]:err_code:0xa0801004, clock:0x0b48a0db  2005/12/31 01:52:27

ofst[ 28]:err_code:0xa0051004, clock:0x0b48a656  2005/12/31 02:15:50

ofst[ 32]:err_code:0xa0021004, clock:0x0b48b506  2005/12/31 03:18:30

ofst[ 36]:err_code:0xa0801004, clock:0x0b48c2d4  2005/12/31 04:17:24

ofst[ 40]:err_code:0xa0011004, clock:0x0b48c396  2005/12/31 04:20:38

ofst[ 44]:err_code:0xa0231004, clock:0x0b4b4980  2006/01/02 02:16:32

ofst[ 48]:err_code:0xa0021004, clock:0x0b4bac34  2006/01/02 09:17:40
 
Hello everyone, I am new here but I have been studying the Frankie method for a long time to revive a cecha00, I understand 90% of the work but I have 2 doubts, I hope you can resolve these doubts for me and thank you.

The rsx to install will be 40nm from a slim model working correctly (error 3034 diagnosed via syscon error log in internal mode) apply a slight reflow to confirm that it is the rsx and the ps3 revived for a couple of hours and died again

My 2 questions are: the commands to overwrite the syscon 40nm RSX Series: CXD5300xxx, CDX5301xxx, & CXD5302xxx
w 3242 03 61 82 80 01 91
w 3254 21 EC
w 348B 8B
w 34AF 8B. Are they written directly in internal mode or is there a command before these to just start writing the commands already mentioned? First question

Second question: Are the values in the image shown from a factory RSX? Or is it from a new RSX? Are those values correct or can they vary? And to check if the RSX after reballing is correct, do you measure only the board or do you need the power source with energy to see if it worked correctly? The reballing will be done by a professional external person with 20 years of experience so there is a 99% chance that everything will turn out well but I would like to make sure anyway. That would be all. I would appreciate your help in this and if everything goes well I will publish the result, thank you for reading.
mb_ohm_test_points-jpg.36295
 
RIP-Felix said:
VDDA look way high. It should be closer to 4ohms
Click to expand...

I put a 2991EGB on it and it works now except for the YLOD on shutdown. VDDA on this chip was 110k. Chip came from working slim with BD issues.

ofst[ 92]:err_code:0xa0801001, clock:0x0b488684 2005/12/31 00:00:04

Thanks
 
Not sure if it applies in your case, but my main C04 in the sig also YLOD on shutdown w/ 1001, and replacing the caps on the CELL bottom side fixed it.

Again, YMMV, but that is what worked for my unit.
 
Raidmax said:
Not sure if it applies in your case, but my main C04 in the sig also YLOD on shutdown w/ 1001, and replacing the caps on the CELL bottom side fixed it.

Again, YMMV, but that is what worked for my unit.
Click to expand...

Ok, thanks for the info. Ive got some kemet caps coming in a few days i'll try it when I get them.
 
You must log in or register to reply here.

Similar threads

Back
Top