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

[Iridule]

2022 error is for av hdmi analog converter I think mention as dve but that shouldn't be giving any problems right now.

Thanks for the reply. I was just curious about syscon. I may replace the thermal paste on the IHS now that I found out the MX-5 was likely bad. Was wondering would it be good to solder onto the board to get more syscon function vs using CFW pkgs? As far as I can find I can only dump syscon to usb or use the bringup command. no way to clear the codes or any other things. As a side note does bringup mean that is the lifetime start up of the console? if so this was what I got.
Bringup Count: 1956, Shutdown Count: 1763
Runtime: 98 Days, 20 Hours, 0 Minutes, 44 Seconds

 

[Fallen777]

Thanks for the reply. I was just curious about syscon. I may replace the thermal paste on the IHS now that I found out the MX-5 was likely bad. Was wondering would it be good to solder onto the board to get more syscon function vs using CFW pkgs? As far as I can find I can only dump syscon to usb or use the bringup command. no way to clear the codes or any other things. As a side note does bringup mean that is the lifetime start up of the console? if so this was what I got.
Bringup Count: 1956, Shutdown Count: 1763
Runtime: 98 Days, 20 Hours, 0 Minutes, 44 Seconds

Well you can use clear errlog command with syscon uart.That will only clear the currently storely errors while the error will still up in log if not resolved on motherboard other than that you can only take measurements from board and compare them with healty measurements to rule out any suspecting future error such as tokien measurements cold solder joint etc.And don't use arctic mx use the silver variant instead mx5 might come in handy for silicon form replacement if you ever think about de-lidding.

 

[Iridule]

Well you can use clear errlog command with syscon uart.That will only clear the currently storely errors while the error will still up in log if not resolved on motherboard other than that you can only take measurements from board and compare them with healty measurements to rule out any suspecting future error such as tokien measurements cold solder joint etc.And don't use arctic mx use the silver variant instead mx5 might come in handy for silicon form replacement if you ever think about de-lidding.

I was doing some reading and wondering if these errors came from stock factory firmware? there are no errors after 2007 ...
I wonder if this has anything to do with it? In June of 2007 Sony gave this specific Syscon an update noting "System firmware 1.81 (June 15, 2007). Patch for the HDMI display data channel read function (only for 0B8E and 0C16)" ...maybe it was something from the factory settings...since there are no errors after 2007? System seems to work fine so far...according to bringup it has less than 100 days of runtime.

 

[wwamann]

Hi everyone, have G model phat that I am trying to learn on before I tackle my A01. Got the simple exe version working for basic codes but having trouble setting up the next level ps3syscon. Using "win10" and either the directions are too vague or I am too dense. I decided to try the Debian VM version by db260179 on page one. Does anyone know the login info for this VM. Already spent many hours looking, found one reference to where that information was kept and still cannot seem to find it. If anyone can help I would appreciate it. Thank You...

 

[Fallen777]

Hi everyone, have G model phat that I am trying to learn on before I tackle my A01. Got the simple exe version working for basic codes but having trouble setting up the next level ps3syscon. Using "win10" and either the directions are too vague or I am too dense. I decided to try the Debian VM version by db260179 on page one. Does anyone know the login info for this VM. Already spent many hours looking, found one reference to where that information was kept and still cannot seem to find it. If anyone can help I would appreciate it. Thank You...

be specific about what level are you looking to access on fats internal and external modes are available for syscon.External is what you access by default are authorization and internal mode is obtained by shorting the diag pin to ground.its quite easy on windows you just need the gui for auth in cxr then read how to use internal mode with cmd. By the way what are you extactly planning to do with syscon diagonstics other than errors codes.

 

[BalancedLightSwitch]

Hello Everyone,
I'm new here but came across the forum from RIP Felix's YouTube video on the YLOD. I have a CECHH01 Phat PS3 (DIA-001, RSX 90nm, Manufactured October 2007) that I would like to get up and running to back up the game saves on the HDD. I was able to get Internal SYSCON working and would appreciate any guidance on where to start and what to try first. I've provided as much information as I could think of about the system and the logs from SYSCON.

Spoiler: Console History

• Purchased the system brand new in the summer of 2008.
• System YLOD sometime during the summer of 2016 while trying to load into NFS game (Press power button, stayed on for 1-3 sec, YLOD, blinking red light). I don't remember ever hearing the fans spin up to jet engine equivalents while it worked though.
• Attempted to reflow later that summer with a heat gun but was too scared to really put some of heat into the RSX and CELL. I was young and didn't really know anything about the PS3 hardware or reflowing. All I knew was that everyone was saying reflow/reball will fix it.
• Removed the IHS from both the RSX and CELL to replace the thermal paste with MX-4.
• Same summer noticed that the F6001 fuse looked blown(I can't remember exactly how it looked but I vaguely remember it being burnt. The reason I assumed this was because the "YD" writing on the fuse looked burned off). I purchased a replacement fuse and soldered it on. This fuse still looks fine to this day but since the fuse was replaced so long ago, I can't find any receipts or information about what I bought. I do remember looking into it at the time and buying one that matched the information found online. If anyone has a recommended fuse though, I was thinking about replacing it with something I know is good.
• Since then, the system still YLOD but after those "repairs" it stays on for 20 seconds before YLOD and shutting down. The fan does not go jet mode either.

Note: The system was never reballed, and none of the Nec/Tokins have been replaced. I was also the first and only one to open the system.

Spoiler: becount

>$ becount
becount
Bringup : 2684 times
Shutdown: 2597 times
Power-on: 99day 01hour 43min 23sec
>$

Spoiler: bringup

>$ 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] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.9.7 (Build ID: 2588,26593, Build Data: 2007-10-01_16:19:11)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[ERROR]: 0xb0002002 (FATAL) XDR Link not initilized.
ITC_DUMP [removed but can add back if needed]
PTC_DUMP [removed but can add back if needed]
MIC_DUMP [removed but can add back if needed]
XIO_DUMP [removed but can add back if needed]
>$
XDR_DUMP [removed but can add back if needed]
IOW_DUMP [removed but can add back if needed]
>$

Spoiler: errlog

>$ errlog
errlog
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xa0902203, clock:0xffffffff
ofst[ 36]:err_code:0xa0801200, clock:0xffffffff
ofst[ 40]:err_code:0xa0902203, clock:0xffffffff
ofst[ 44]:err_code:0xa0902203, clock:0xffffffff
ofst[ 48]:err_code:0xa0902203, clock:0xffffffff
ofst[ 52]:err_code:0xa0902203, clock:0xffffffff
ofst[ 56]:err_code:0xa0801200, clock:0xffffffff
ofst[ 60]:err_code:0xa0902203, clock:0xffffffff
ofst[ 64]:err_code:0xa0801200, clock:0xffffffff
ofst[ 68]:err_code:0xa0902203, clock:0xffffffff
ofst[ 72]:err_code:0xa0902203, clock:0xffffffff
ofst[ 76]:err_code:0xa0902203, clock:0xffffffff
ofst[ 80]:err_code:0xa0902203, clock:0xffffffff
ofst[ 84]:err_code:0xa0801200, clock:0xffffffff
ofst[ 88]:err_code:0xa0902203, clock:0xffffffff
ofst[ 92]:err_code:0xa0902203, clock:0xffffffff
ofst[ 96]:err_code:0xa0902203, clock:0xffffffff
ofst[100]:err_code:0xa0801200, clock:0xffffffff
ofst[104]:err_code:0xa0902203, clock:0xffffffff
ofst[108]:err_code:0xa0902203, clock:0xffffffff
ofst[112]:err_code:0xa0902203, clock:0xffffffff
ofst[116]:err_code:0xa0902203, clock:0xffffffff
ofst[120]:err_code:0xa0801200, clock:0xffffffff
ofst[124]:err_code:0xa0902203, clock:0xffffffff
ofst[  0]:err_code:0xa0801200, clock:0xffffffff
ofst[  4]:err_code:0xa0003001, clock:0xffffffff
ofst[  8]:err_code:0xa0003001, clock:0xffffffff
ofst[ 12]:err_code:0xa0801200, clock:0xffffffff
ofst[ 16]:err_code:0xa0902203, clock:0xffffffff
ofst[ 20]:err_code:0xa0801200, clock:0xffffffff
ofst[ 24]:err_code:0xa0902203, clock:0xffffffff
>$

I know that error 3001 is PSU failure. Is it recommended to replace the power supply in this case as its an older error?
I know that error 1200 is CELL overheating. Since I've replaced the thermal paste and the fan doesn't spin up, could be the temperature monitor chip as stated on PSDevWiki? Is there any way to check this?
Lastly, I'm not too familiar with the 2203 error or the southbridge. According to the PSDevWiki, it seems as though this error has only been created in sabotage tests. What might be the best way to trouble shoot this one?

Thank you all.

 

[Fallen777]

Hello Everyone,
I'm new here but came across the forum from RIP Felix's YouTube video on the YLOD. I have a CECHH01 Phat PS3 (DIA-001, RSX 90nm, Manufactured October 2007) that I would like to get up and running to back up the game saves on the HDD. I was able to get Internal SYSCON working and would appreciate any guidance on where to start and what to try first. I've provided as much information as I could think of about the system and the logs from SYSCON.

Spoiler: Console History

• Purchased the system brand new in the summer of 2008.
• System YLOD sometime during the summer of 2016 while trying to load into NFS game (Press power button, stayed on for 1-3 sec, YLOD, blinking red light). I don't remember ever hearing the fans spin up to jet engine equivalents while it worked though.
• Attempted to reflow later that summer with a heat gun but was too scared to really put some of heat into the RSX and CELL. I was young and didn't really know anything about the PS3 hardware or reflowing. All I knew was that everyone was saying reflow/reball will fix it.
• Removed the IHS from both the RSX and CELL to replace the thermal paste with MX-4.
• Same summer noticed that the F6001 fuse looked blown(I can't remember exactly how it looked but I vaguely remember it being burnt. The reason I assumed this was because the "YD" writing on the fuse looked burned off). I purchased a replacement fuse and soldered it on. This fuse still looks fine to this day but since the fuse was replaced so long ago, I can't find any receipts or information about what I bought. I do remember looking into it at the time and buying one that matched the information found online. If anyone has a recommended fuse though, I was thinking about replacing it with something I know is good.
• Since then, the system still YLOD but after those "repairs" it stays on for 20 seconds before YLOD and shutting down. The fan does not go jet mode either.

Note: The system was never reballed, and none of the Nec/Tokins have been replaced. I was also the first and only one to open the system.

Spoiler: becount

>$ becount
becount
Bringup : 2684 times
Shutdown: 2597 times
Power-on: 99day 01hour 43min 23sec
>$

Spoiler: bringup

>$ 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] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.9.7 (Build ID: 2588,26593, Build Data: 2007-10-01_16:19:11)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[ERROR]: 0xb0002002 (FATAL) XDR Link not initilized.
ITC_DUMP [removed but can add back if needed]
PTC_DUMP [removed but can add back if needed]
MIC_DUMP [removed but can add back if needed]
XIO_DUMP [removed but can add back if needed]
>$
XDR_DUMP [removed but can add back if needed]
IOW_DUMP [removed but can add back if needed]
>$

Spoiler: errlog

>$ errlog
errlog
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xa0902203, clock:0xffffffff
ofst[ 36]:err_code:0xa0801200, clock:0xffffffff
ofst[ 40]:err_code:0xa0902203, clock:0xffffffff
ofst[ 44]:err_code:0xa0902203, clock:0xffffffff
ofst[ 48]:err_code:0xa0902203, clock:0xffffffff
ofst[ 52]:err_code:0xa0902203, clock:0xffffffff
ofst[ 56]:err_code:0xa0801200, clock:0xffffffff
ofst[ 60]:err_code:0xa0902203, clock:0xffffffff
ofst[ 64]:err_code:0xa0801200, clock:0xffffffff
ofst[ 68]:err_code:0xa0902203, clock:0xffffffff
ofst[ 72]:err_code:0xa0902203, clock:0xffffffff
ofst[ 76]:err_code:0xa0902203, clock:0xffffffff
ofst[ 80]:err_code:0xa0902203, clock:0xffffffff
ofst[ 84]:err_code:0xa0801200, clock:0xffffffff
ofst[ 88]:err_code:0xa0902203, clock:0xffffffff
ofst[ 92]:err_code:0xa0902203, clock:0xffffffff
ofst[ 96]:err_code:0xa0902203, clock:0xffffffff
ofst[100]:err_code:0xa0801200, clock:0xffffffff
ofst[104]:err_code:0xa0902203, clock:0xffffffff
ofst[108]:err_code:0xa0902203, clock:0xffffffff
ofst[112]:err_code:0xa0902203, clock:0xffffffff
ofst[116]:err_code:0xa0902203, clock:0xffffffff
ofst[120]:err_code:0xa0801200, clock:0xffffffff
ofst[124]:err_code:0xa0902203, clock:0xffffffff
ofst[  0]:err_code:0xa0801200, clock:0xffffffff
ofst[  4]:err_code:0xa0003001, clock:0xffffffff
ofst[  8]:err_code:0xa0003001, clock:0xffffffff
ofst[ 12]:err_code:0xa0801200, clock:0xffffffff
ofst[ 16]:err_code:0xa0902203, clock:0xffffffff
ofst[ 20]:err_code:0xa0801200, clock:0xffffffff
ofst[ 24]:err_code:0xa0902203, clock:0xffffffff
>$

I know that error 3001 is PSU failure. Is it recommended to replace the power supply in this case as its an older error?
I know that error 1200 is CELL overheating. Since I've replaced the thermal paste and the fan doesn't spin up, could be the temperature monitor chip as stated on PSDevWiki? Is there any way to check this?
Lastly, I'm not too familiar with the 2203 error or the southbridge. According to the PSDevWiki, it seems as though this error has only been created in sabotage tests. What might be the best way to trouble shoot this one?

Thank you all.

yes you should go ahead with psu but there are other components you should check on 12v rail and 1200 overheating error isn't just ihs thermal paste related the cell thermal monitor is also known for causing this error.as for the 2203 error test the volatage rails around southbridge replace any dead component.For spare parts best choice is to get a scrap dia-001 board but be carefull to replace the Thermal monitor with same part no.

 

[BalancedLightSwitch]

yes you should go ahead with psu but there are other components you should check on 12v rail and 1200 overheating error isn't just ihs thermal paste related the cell thermal monitor is also known for causing this error.as for the 2203 error test the volatage rails around southbridge replace any dead component.For spare parts best choice is to get a scrap dia-001 board but be carefull to replace the Thermal monitor with same part no.

Thank you for the reply,
I'll start looking around for a new PSU or possibly a donor board/system. In the mean time, I'll start probing around the 12v rail and southbridge for any dead components. You mentioned that the CELL thermal monitor could be bad, is there a way to test this while its on the board or is it just best to replace?

>$ bringup bringup...

Also, I didn't see a way to edit my previous post but out of curiosity I ran the bringup command again and hit enter a few times while the system was booting and got a bit more information in the console then before. Just thought I would add it in case its of use. This came after the dumps.

Spoiler: bringup (more information after dumps)

[SERV NVS] WRITE CMD
[ERROR]: 0xb0002002 (FATAL) XDR Link not initilized.
[SERV NVS] WRITE CMD
[SERV NVS] WRITE CMD
[SSM] *** FATAL ERROR requested by OS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

 

[Fallen777]

Thank you for the reply,
I'll start looking around for a new PSU or possibly a donor board/system. In the mean time, I'll start probing around the 12v rail and southbridge for any dead components. You mentioned that the CELL thermal monitor could be bad, is there a way to test this while its on the board or is it just best to replace?


Also, I didn't see a way to edit my previous post but out of curiosity I ran the bringup command again and hit enter a few times while the system was booting and got a bit more information in the console then before. Just thought I would add it in case its of use. This came after the dumps.

Spoiler: bringup (more information after dumps)

[SERV NVS] WRITE CMD
[ERROR]: 0xb0002002 (FATAL) XDR Link not initilized.
[SERV NVS] WRITE CMD
[SERV NVS] WRITE CMD
[SSM] *** FATAL ERROR requested by OS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

No sure if there is anyway to test thermal if on board but there are report cases of them being the issue and people resolved 1200 error by replacing it with identical ic.Althrough I myself have a 1200 error on my superslim that haven't gotten to resolve due to lack of donor board rightnow.
Also every error has a power-state prefix before it the 3001 and 2003 error have off-state errors so circuit couldn't complete and 80 prefix in 1200 error probably means the cell was initialized successfully but syscon halted boot process to protect cell from damaging due to temperature report over-reaching stock temp configuration.

 

[RIP-Felix]

XDR not initialized happens when there us a commuication issue between the CPU and RAM. Can mean an XDR module has failed or that the CPU's BGA has. Can happen as a result of a fall for example.

@squeept gave me a board with this issue and I haven't been able to sort it out yet. I did all kinds of pressure testing around the CPU and XDR, but it doesn't respond. And on thermal cam, all 4 RAM modules light up, indicating they're getting power. So I was planning to start by replacing the XDR and if that doesn't work, reball the CPU. But I wont get to that for awhile. Too cold for reballing ATM and I'm working on other projects. Probably will circle back to it this summer.

 

[fadia bd alnour]

Did not tested voltage so far I want to go further with 5 Super slims. All dead. One with some vertical strange lines on screen after swapped rsx still same issue on screen.
About 1.5 v on ram it has to normal to slims and super slim. Why? Because on ps4 all rams are out of gpu and all powered in parallel from a strong line with same 1.5v.
Ps4 designed very similar to ps3.

Edit
Testing Nxp001 motherboard superslim models

I think I may be out of faulty table?

hi my friend i have the same problem

> errlog
00000000
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF


do you have any solution the problem

plz help me thanks .

 

[Fallen777]

hi my friend i have the same problem

> errlog
00000000
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF


do you have any solution the problem

plz help me thanks .

look's like either clock generator error or firmware brick what board no is it and what are your syptoms

 

[wwamann]

Thanks for the response Fallen777 . Figured out the Debian VM login/password in location, You load the VM file into new VBOX machine , go to settings, general, description and there it is, exactly where he said it would be, who knew. in case any one else has a problem finding this info here.

Debian VBOX VM Logon: ps3user / password: syscon

Got CXF/CXRF script working on cechg box retrieved codes, caps/lowercase matters. great...

Tried on cecha01 board, CXR works but CXRF keeps giving me "scopen response invalid" Is it different syscon's giving me my problem and if so where do I find the correct CXR/CXRF script.
I have managed to set 3961 to 00 in CXR, cycled power, I have the data at ground and now have flashing red light at standby with back power switch on. it will not boot which is what the instructions said, no problem, but keep getting "scopen response invalid" at auth. I need some direction please. Thank You....

 

[Fallen777]

Thanks for the response Fallen777 . Figured out the Debian VM login/password in location, You load the VM file into new VBOX machine , go to settings, general, description and there it is, exactly where he said it would be, who knew. in case any one else has a problem finding this info here.

Debian VBOX VM Logon: ps3user / password: syscon

Got CXF/CXRF script working on cechg box retrieved codes, caps/lowercase matters. great...

Tried on cecha01 board, CXR works but CXRF keeps giving me "scopen response invalid" Is it different syscon's giving me my problem and if so where do I find the correct CXR/CXRF script.
I have managed to set 3961 to 00 in CXR, cycled power, I have the data at ground and now have flashing red light at standby with back power switch on. it will not boot which is what the instructions said, no problem, but keep getting "scopen response invalid" at auth. I need some direction please. Thank You....

no diag pin has to be ground not rx or tx and by the switching rx and tx works sometimes too

 

[db260179]

The login details are in the description section once imported in virtualbox

ps3user
syscon

Hi everyone, have G model phat that I am trying to learn on before I tackle my A01. Got the simple exe version working for basic codes but having trouble setting up the next level ps3syscon. Using "win10" and either the directions are too vague or I am too dense. I decided to try the Debian VM version by db260179 on page one. Does anyone know the login info for this VM. Already spent many hours looking, found one reference to where that information was kept and still cannot seem to find it. If anyone can help I would appreciate it. Thank You...

 

[Fallen777]

The login details are in the description section once imported in virtualbox

ps3user
syscon

hey what does a0601002 mean I know 1002 is rsx vrm failure but also mention as vram failure in your git repository.
what really confuses me is 60 prefix what power state is it and I have 3003 and 3004 errors for tokin caps but unfortunately don't have tantulum polymer capacitors available in my range. are there any alternatives some link to aliexpress or wondering if I can use caps of a mpx 001 board

 

[k1netic]

I've fired up the cech-c02 without replacing the 2nd resistor, sick of waiting for the part, and run the last of us for a while on evilnat 4.88.2 and a fan profile to keep it at or under 65 celcius. It runs fine. Fan speed gets to 33-34%. I haven't delid either the GPU or CPU as I have only tried once on another console so won't risk it before more practice.

Since this post, I replaced the missing resistor, and used the console. At random times the fuse f6302 has blown again. Dashboard, during games, whenever.

I finally got a voltage injection tool and checked for hot components, nothing. I've come to the conclusion that I bought cheap fuses and am paying for that now. I measured amp draw over the fuse point with the console running games and never saw more than 1.4 amps drawn.

I installed the fuse each time with a hot air gun, I think this was also a problem, weakening the fuse. The final time I installed the fuse with a soldering iron and so far so good.

Is there anything I could be missing from this behaviour besides a weak fuse?

 

[Intruder_911]

hi my friend i have the same problem

> errlog
00000000
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF


do you have any solution the problem

plz help me thanks .

hi there. the 5FFF is XDR error as usual, in some cases firmware error. to make it sure write bringup command, if you have XDR error the board will not turn off immediatly. write shutdown command for turn off, after bringup again, and press enter 3-4 times. You will get error at the end "#![ERROR]: 0xb0002002 (FATAL) XDR Link not initilized." and every time you press enter you will get multiple flood symbols. the example below. Solution is CELL reball. Once i got such board after other repair shops, there were some resistors broken on B side of board under XDR memory. Also this may occur beacause of scratches on the CELL after bad deliding.

 

[Fallen777]

hey what does a0601002 mean I know 1002 is rsx vrm failure but also mention as vram failure in your git repository.
what really confuses me is 60 prefix what power state is it and I have 3003 and 3004 errors for tokin caps but unfortunately don't have tantulum polymer capacitors available in my range. are there any alternatives some link to aliexpress or wondering if I can use caps of a mpx 001 board

hey I got this cech4001c as donor for temp sensor has msx-001 board and these errors in errorlog
===================================
ERR 00: 00000000 A0203010 FFFFFFFF
ERR 01: 00000000 A0203010 FFFFFFFF
ERR 02: 00000000 A0203010 FFFFFFFF
ERR 03: 00000000 A0203010 FFFFFFFF
ERR 04: 00000000 A0203010 FFFFFFFF
ERR 05: 00000000 A0203010 FFFFFFFF
ERR 06: 00000000 A0203010 FFFFFFFF
ERR 07: 00000000 A0801701 259CF9C9
ERR 08: 00000000 A08014FF 259CF9C8
ERR 09: 00000000 A0801701 259CF8F8
ERR 10: 00000000 A0802130 23219CD2
ERR 11: 00000000 A0801200 214DEEAA
ERR 12: 00000000 A0801200 214DEE92
ERR 13: 00000000 A0801200 1C4B1B6F
ERR 14: 00000000 A0801200 1C4B1B56
ERR 15: 00000000 A0801200 1A71D3E3
ERR 16: 00000000 A0801200 1A71D3A3
ERR 17: 00000000 A0801200 1A71D1A0
ERR 18: 00000000 FFFFFFFF FFFFFFFF
ERR 19: 00000000 FFFFFFFF FFFFFFFF
===================================
Console had been to repair previously
probably by an idiot
Bt/wifi chip is missing bottom side and cell rsx as well as the whole flexio bridge is completely covered in flux probably reflowed.
Is this console fixable or even if tmp411a and caps are harvestable for tantulum fix.Also its missing screws, fan and doesent have thermal paste and rsx had solderballs stuck in hard glue/flux don't know for sure near on rsx vram glue .

Edit
I replaced the thermal paste and touched the tmp411a pins with soldering iron to refresh the solder and removed solidified flux.
And now I got additional 2130 and 2131 error by only thermal paste replacement.
Ran clear errlog and now all 85fffffs with one 3010 at beginning any guessed where to start diagonstic

 

[Fallen777]

hey I got this cech4001c as donor for temp sensor has msx-001 board and these errors in errorlog
===================================
ERR 00: 00000000 A0203010 FFFFFFFF
ERR 01: 00000000 A0203010 FFFFFFFF
ERR 02: 00000000 A0203010 FFFFFFFF
ERR 03: 00000000 A0203010 FFFFFFFF
ERR 04: 00000000 A0203010 FFFFFFFF
ERR 05: 00000000 A0203010 FFFFFFFF
ERR 06: 00000000 A0203010 FFFFFFFF
ERR 07: 00000000 A0801701 259CF9C9
ERR 08: 00000000 A08014FF 259CF9C8
ERR 09: 00000000 A0801701 259CF8F8
ERR 10: 00000000 A0802130 23219CD2
ERR 11: 00000000 A0801200 214DEEAA
ERR 12: 00000000 A0801200 214DEE92
ERR 13: 00000000 A0801200 1C4B1B6F
ERR 14: 00000000 A0801200 1C4B1B56
ERR 15: 00000000 A0801200 1A71D3E3
ERR 16: 00000000 A0801200 1A71D3A3
ERR 17: 00000000 A0801200 1A71D1A0
ERR 18: 00000000 FFFFFFFF FFFFFFFF
ERR 19: 00000000 FFFFFFFF FFFFFFFF
===================================
Console had been to repair previously probably by an idiot
Bt/wifi chip is missing bottom side and cell rsx as well as the whole flexio bridge is completely covered in flux probably reflowed.
Is this console fixable or even if tmp411a and caps are harvestable for tantulum fix.Also its missing screws, fan and doesent have thermal paste and rsx had solderballs stuck in hard glue/flux don't know for sure near on rsx vram glue .

@RIP-Felix do the tantulun on msx-001qualify for ps3 fat dia-002 65mm cell and rsx.I think I got like 16 or 12 of them on board.