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

[Nator]

I guess you activated the south bridge log output by executing:

w 7202 02

which sets the network device mode to south bridge, see 0x48C02 in https://www.psdevwiki.com/ps3/SC_EEPROM#SC_EEPROM_Offset_Table_-_Flags_and_Tokens .

If you want additional info from the secure services, you need to activate the ss.common.printf.enabled and then a flag of the services you're interested in. I would advise setting both the common log level (0x48CF0) and the ss.common.debug.level+ss.update.debug.level (0x48CF1) to 0x03 - see also https://www.psdevwiki.com/ps3/SC_EEPROM#SC_EEPROM_Offset_Table_-_Flags_and_Tokens .
This translates to the following syscon commands (by using the translation table (https://www.psdevwiki.com/ps3/SC_EE..._and_Block_Offset_Mapping_Table_(NVS_Service)) :

w 72F0 03
w 72F1 03

The pme_user debug printf flag (0x48CCF) might also be of help, to enable this output, execute:

w 72CF 03

The default value for all of these flags is 0xFF.

Later i will try the commands w 7202 02 w 72CF 03 w 72F0 03 w 72F1 03 and i will confirm if it works.
But now i have a million question. Following RIP-Felix's guide to the letter, i inserted commands for a sherwoods syscon into a mullion syscon, i mean the "w 42CF 03 w 42F0 03 w 42F1 03" commands.
What exactly did i change in Mullion with these Sherwoods commands? Hope i didn't make a mess.

 

[M4j0r]

Ok now i understand better. For the old Mullion syscons, all commands are marked with the number 72, while the new Sherwoods sycons with the number 42.

So for Mullion is:

Activating SB log output:

w 7202 02

Hypervisor message activation:

w 72CF 03
w 72F0 03
w 72F1 03

Disabling Hypervisor Messages:

w 72CF FF
w 72F0 FF
w 72F1 FF

For Sherwoods is:
Activating SB log output:

w 4202 02

Enabling Hypervisor Messages:

w 42CF 03
w 42F0 03
w 42F1 03

Disabling Hypervisor Messages:

w 42CF FF
w 42F0 FF
w 42F1 FF

Mullion (CXR) uses two different addressing schemes, that's what you gave examples for. Sherwood uses other offsets.
Just look at the Physical Offset (CXR713), Physical Offset (CXR714), Virtual Offset (SW) columns in this table: https://www.psdevwiki.com/ps3/SC_EE..._and_Block_Offset_Mapping_Table_(NVS_Service) .

And again, you don't activate any "Hypervisor" messages, you only activate PME or SS logs.
The "SB log enable" already enables all "Hypervisor" messages.

Later i will try the commands w 7202 02 w 72CF 03 w 72F0 03 w 72F1 03 and i will confirm if it works.
But now i have a million question. Following RIP-Felix's guide to the letter, i inserted commands for a sherwoods syscon into a mullion syscon, i mean the "w 42CF 03 w 42F0 03 w 42F1 03" commands.
What exactly did i change in Mullion with these Sherwoods commands? Hope i didn't make a mess.

The 0x4.. region isn't used on your Syscon, you didn't change anything.

 

[Nator]

And again, you don't activate any "Hypervisor" messages, you only activate PME or SS logs.
The "SB log enable" already enables all "Hypervisor" messages.

There was a wrong interpretation of the writing in the syscon guide made by felix: "to get more messages from the Hypervisor....the SB UART log will now be longer and include some information from various Hypervisor services"

The 0x4.. region isn't used on your Syscon, you didn't change anything.

Nice

 

[Nator]

Mullion (CXR) uses two different addressing schemes, that's what you gave examples for. Sherwood uses other offsets.
Just look at the Physical Offset (CXR713), Physical Offset (CXR714), Virtual Offset (SW) columns in this table: https://www.psdevwiki.com/ps3/SC_EE..._and_Block_Offset_Mapping_Table_(NVS_Service) .

And again, you don't activate any "Hypervisor" messages, you only activate PME or SS logs.
The "SB log enable" already enables all "Hypervisor" messages.


The 0x4.. region isn't used on your Syscon, you didn't change anything.

Ok the commands you gave me worked thx, i got more info from the SB log. Now i wonder, who is able to interpret this information? otherwise why would they have been included in the guide?

 

[RIP-Felix]

There was a wrong interpretation of the writing in the syscon guide made by felix: "to get more messages from the Hypervisor....the SB UART log will now be longer and include some information from various Hypervisor services"


Nice

That was a quote from @M4j0r from awhile ago. I included it there for completness, but should update it with the most accurate information. I haven't used it myself. So if you figure it out or have suggestions for how I can improve that section I'll update it. Let me know.

 

[Nator]

That was a quote from @M4j0r from awhile ago. I included it there for completness, but should update it with the most accurate information. I haven't used it myself. So if you figure it out or have suggestions for how I can improve that section I'll update it. Let me know.

It would be better to update the guide, the commands for mullion must be preceded by the number 72 therefore w 72CF 03...w 72F0 03 etc.
I also noticed that after activating the PME or SS logs (what i mistakenly called hypervisor) the PS3 is not slow but simply can no longer enter safe mode, it only enters if i disable these commands.

 

[M4j0r]

That was a quote from @M4j0r from awhile ago. I included it there for completness, but should update it with the most accurate information. I haven't used it myself. So if you figure it out or have suggestions for how I can improve that section I'll update it. Let me know.

You could include offsets for all three types of addressing schemes and maybe explain what the offsets activate, see https://www.psx-place.com/threads/f...nd-error-reporting.30100/page-184#post-373066 .

However, interpreting the information from the log might be hard/impossible for a normal user.

It would be better to update the guide, the commands for mullion must be preceded by the number 72 therefore w 72CF 03...w 72F0 03 etc.
I also noticed that after activating the PME or SS logs (what i mistakenly called hypervisor) the PS3 is not slow but simply can no longer enter safe mode, it only enters if i disable these commands.

You can enter still enter safe mode but the timing for the button presses is off. This feature is normally only intended to be used on units with a communication processor.

 

[MAGOOSKEE]

I have a Sherwood (CECH-2102A) console. RLOD. Dropped, codes are 3010 (Cell voltage?) and 1201 (RSX overheat)

Spoiler: SYSCON Errors

# CODE     CLOCK
# A0203010 FFFFFFFF
# A0203010 FFFFFFFF
# A0203010 FFFFFFFF
# A0203010 FFFFFFFF
# A0201201 FFFFFFFF
# A0203010 2CB517C1
# A0203010 2CB51669
# A0203010 2CAFC524
# A0201201 2CAFC524
# A0203010 2CAFC518
# A0203010 2CAE51C2
# A0203010 2CAE51B7
# A0201201 2CAE51B6
# A0203010 2CAE51A7
# A0203010 1AFC8C17
# A0203010 1AFC8BD6
# A0201201 1AFC8BD5
# A0203010 1AFC8BC7
# A0203010 1AF50AA9
# A0203010 1AF50A94
# A0203010 1AF50A86
# A0201201 1AF50A86
# A0203010 1AF50A7D
# A0203010 1AF504BD
# A0203010 1AF50482
# A0203010 1AF4A387
# A0201201 1AF4A386
# A0203010 1AF3D502
# A0201201 1AF3D501
# A0203010 1AF3C525
# A0203010 1AF3C3BF

Spoiler: Bringup Log

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

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] Msg 2687 : being delayed.
# [PowSeq] Error:A104
# [SSM] PS1 ng.
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$

 

[Nator]

I have a Sherwood (CECH-2102A) console. RLOD. Dropped, codes are 3010 (Cell voltage?) and 1201 (RSX overheat)

Spoiler: SYSCON Errors

# CODE     CLOCK
# A0203010 FFFFFFFF
# A0203010 FFFFFFFF
# A0203010 FFFFFFFF
# A0203010 FFFFFFFF
# A0201201 FFFFFFFF
# A0203010 2CB517C1
# A0203010 2CB51669
# A0203010 2CAFC524
# A0201201 2CAFC524
# A0203010 2CAFC518
# A0203010 2CAE51C2
# A0203010 2CAE51B7
# A0201201 2CAE51B6
# A0203010 2CAE51A7
# A0203010 1AFC8C17
# A0203010 1AFC8BD6
# A0201201 1AFC8BD5
# A0203010 1AFC8BC7
# A0203010 1AF50AA9
# A0203010 1AF50A94
# A0203010 1AF50A86
# A0201201 1AF50A86
# A0203010 1AF50A7D
# A0203010 1AF504BD
# A0203010 1AF50482
# A0203010 1AF4A387
# A0201201 1AF4A386
# A0203010 1AF3D502
# A0201201 1AF3D501
# A0203010 1AF3C525
# A0203010 1AF3C3BF

Spoiler: Bringup Log

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

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] Msg 2687 : being delayed.
# [PowSeq] Error:A104
# [SSM] PS1 ng.
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$

I'm not the most qualified person to do this but I'll try to answer you. RLOD would be the red LED that flashes. The console doesn't seem to even get past the first startup stages, it doesn't get to the southbridge, it doesn't say anything. For me it's a PSU or CELL problem, and even if it gives you an error relating to the temperatures of the RSX, it doesn't give us any information on its functioning.

 

[hidatzu]

hi i need help!! any one here know this error thank you

My PS3 Is CECHL12

>$ ERRLOG
00000000
# CODE     CLOCK
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [PowSeq] Error:A103
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [PowSeq] Error:A103
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$

 

[hidatzu]

This Is the Other PS3 Same Model Thank You

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [PowSeq] Error:A103
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exi

# CODE     CLOCK
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF

 

[MAGOOSKEE]

This Is the Other PS3 Same Model Thank You

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [PowSeq] Error:A103
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exi

# CODE     CLOCK
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF

I don't know anywhere near enough to really be saying this, but I believe that your system isn't even getting to the south bridge on boot, the error 3004 could mean very faulty tokins/tantalums or a short on the BD drive. According to the ps3devwiki page. Before you do anything, wait for a second opinion though. Could be a bad lead.

 

[Angel Scheib]

I repaired a Slim PS3 JSD-001 today that had that fault from UART. I checked all the power supplies and one of them had a short on the dual mosfets and a blown fuse on F6301. All the other supplies had their voltages briefly right when pressing the power button.

I removed the dual mosfet and the short remained so the only available culprits where two caps on the same rail. One of them had a short so replacing it along with the fuse solved the issue. Please be aware that this was my specific case and I think the error points to a generalized problem with one or many of the power supplies of the board so please check all the supplies for shorts, open resistors, crystal oscilators or the PWM Chip itself for that specific power supply just like the psdevwiki suggests for that specific error.

 

[Fallen777]

Hey need a little help here this entire bottom line is ground so that makes this entire circuit a filter cap circuit right
So that means the caps on syscons oscillators are not necessary right since they are only pico fared ones and one on each terminal. If I happen to lose once cap it would cause the console to further damage or explode right someone confirm this?

 

[ZephRay]

Can I get some advice on repairing? Got a CECHA machine with unknown history, the warranty sticker is still there so, no delidding, hardware is all original. After powering on, it does one beep, shows a solid green light, and then after about 30s it shuts off. No video at all.

I attached the SYSCON UART, the errlog is empty. Did a bringup, also does not report any error. So I enabled the SB UART, and got the following boot message:

Spoiler: bootlog

Boot Loader SE Version 4.5.5 (Build ID: 5149,50179, Build Date: 2014-01-28_18:27:36)
SDK Version: 455.000
Copyright(C) 2014 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.1, SBX3.1
Device: PATAC0:Cable Not Connect
Cell OS SDK4.5.5 000 (release build: r50179 2014_01_28_180000)
Copyright 2014 Sony Computer Entertainment Inc.
revision: 50153
date: Tue Jan 28 18:30:01 JST 2014
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.5.5
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50179
lv2(2): build date: 2014/01/28 18:37:25
lv2(2): processor: Broadband Engine Ver 0x0000 Rev 0x0201
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx: b08 500/650 vpe:ff shd:3f [AP0005052:1:1:13:10:13:2:f:1][16:3: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): ### Software update mode
lv2(2): ###
lv2(2):
lv2(2): mounting the builtin HDD1 : ........... Failed (error code:0x8001002b)
lv2(2): creating the initial system process : Failed (path:/dev_hdd1/PS3UPDATE/ps3swu.self)
lv2(2): - The system process image file does not exist (error code:0x8001003a).
lv2(2):
lv2(2):
lv2(2): ###
lv2(2): ### creating the ps3swu process : Failed (path:/dev_hdd1/PS3UPDATE/ps3swu.self, error code:0x00000000)
lv2(2): ### exiting software update mode
lv2(2): ###
lv2(2):
lv2(2): creating the initial system process : Failed (path:/dev_flash/sys/internal/sys_init_osd.self)
lv2(2): - Found the system process image file, but the file is not a valid SELF
lv2(2): (error core:80010009).
lv2(2):
lv2(2):
lv2(2): Prepare to shutdown ....
lv2(2): Going to shutdown.
system event id=0xe1, rtc=0, size=24 [0x5354523a50415441 0x43303a4361626c65 0x204e6f7420436f6e 0x6e65637400000000]

The mounting HDD1 part took a very long time, and it doesn't change if I just don't install HDD at all, or install a HDD from another CECHA PS3, or a blank HDD. (I never looked at SB UART before so I am not sure if this unable to mount hard drive issue is expected or not). Then the sys_init_osd.self error is a bit more worrying. Did the previous owner maybe somehow corrupted the flash content? What should be the first step of trying to fix this? Thanks.

 

[Divano]

Hello, everyone,
I have a ps3 cechl04 (ver 001) that has the following errors.

Spoiler: Errlog

# CODE CLOCK
# A0402124 FFFFFFFF
# A0402124 FFFFFFFF
# A0403034 FFFFFFFF
# A0404011 FFFFFFFF
# A0401002 FFFFFFFF
# A0232124 FFFFFFFF
# A0232124 FFFFFFFF
# A0232124 FFFFFFFF
# A0231002 FFFFFFFF
# A0222124 FFFFFFFF
# A0222124 FFFFFFFF
# A0223012 FFFFFFFF
# A0221002 FFFFFFFF
# A0232124 FFFFFFFF
# A0232124 FFFFFFFF
# A0232124 FFFFFFFF
# A0232124 FFFFFFFF
# A0231002 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF

The console starts up, stays active for about a minute, and shuts down. I do not have any video.
I read that it could be the hdmi encoder, but the error 1002 makes me think of something else....

 

[Fallen777]

Can I get some advice on repairing? Got a CECHA machine with unknown history, the warranty sticker is still there so, no delidding, hardware is all original. After powering on, it does one beep, shows a solid green light, and then after about 30s it shuts off. No video at all.

I attached the SYSCON UART, the errlog is empty. Did a bringup, also does not report any error. So I enabled the SB UART, and got the following boot message:

Spoiler: bootlog

Boot Loader SE Version 4.5.5 (Build ID: 5149,50179, Build Date: 2014-01-28_18:27:36)
SDK Version: 455.000
Copyright(C) 2014 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.1, SBX3.1
Device: PATAC0:Cable Not Connect
Cell OS SDK4.5.5 000 (release build: r50179 2014_01_28_180000)
Copyright 2014 Sony Computer Entertainment Inc.
revision: 50153
date: Tue Jan 28 18:30:01 JST 2014
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.5.5
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50179
lv2(2): build date: 2014/01/28 18:37:25
lv2(2): processor: Broadband Engine Ver 0x0000 Rev 0x0201
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx: b08 500/650 vpe:ff shd:3f [AP0005052:1:1:13:10:13:2:f:1][16:3: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): ### Software update mode
lv2(2): ###
lv2(2):
lv2(2): mounting the builtin HDD1 : ........... Failed (error code:0x8001002b)
lv2(2): creating the initial system process : Failed (path:/dev_hdd1/PS3UPDATE/ps3swu.self)
lv2(2): - The system process image file does not exist (error code:0x8001003a).
lv2(2):
lv2(2):
lv2(2): ###
lv2(2): ### creating the ps3swu process : Failed (path:/dev_hdd1/PS3UPDATE/ps3swu.self, error code:0x00000000)
lv2(2): ### exiting software update mode
lv2(2): ###
lv2(2):
lv2(2): creating the initial system process : Failed (path:/dev_flash/sys/internal/sys_init_osd.self)
lv2(2): - Found the system process image file, but the file is not a valid SELF
lv2(2): (error core:80010009).
lv2(2):
lv2(2):
lv2(2): Prepare to shutdown ....
lv2(2): Going to shutdown.
system event id=0xe1, rtc=0, size=24 [0x5354523a50415441 0x43303a4361626c65 0x204e6f7420436f6e 0x6e65637400000000]

The mounting HDD1 part took a very long time, and it doesn't change if I just don't install HDD at all, or install a HDD from another CECHA PS3, or a blank HDD. (I never looked at SB UART before so I am not sure if this unable to mount hard drive issue is expected or not). Then the sys_init_osd.self error is a bit more worrying. Did the previous owner maybe somehow corrupted the flash content? What should be the first step of trying to fix this? Thanks.

You have 1002 NEC fail a 1003 error and a 1009 both of which are unrecorded in database try changing the cap on NEC and see if it works else thrown it in the litter box

 

[ZephRay]

You have 1002 NEC fail a 1003 error and a 1009 both of which are unrecorded in database try changing the cap on NEC and see if it works else thrown it in the litter box

Thanks for the help, but are you sure about that? The log I posted is SB UART log, not SYSCON UART log, these are not SYSCON error codes (which should start with A0). And the code is really 1003a, 1002b, and 10009 rather than 1002/1003/1009. The syscon err log is empty (all 0xffffffff) so I don't really think replacing the NEC cap would do anything.

 

[Fallen777]

Thanks for the help, but are you sure about that? The log I posted is SB UART log, not SYSCON UART log, these are not SYSCON error codes (which should start with A0). And the code is really 1003a, 1002b, and 10009 rather than 1002/1003/1009. The syscon err log is empty (all 0xffffffff) so I don't really think replacing the NEC cap would do anything.

Unless syscon tests connections first I don't think Stourbridge would wake and talk

 

[ZephRay]

Unless syscon tests connections first I don't think Stourbridge would wake and talk

If I didn't make it clear, these log are obtained from the SB UART pins, not SYSCON UART pins. It should also be obvious these are SB logs not SYSCON logs, they looks entirely different.