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

I have seen this progression before. 1601/1701 (crashes in game or XMB) leads to a 3037/1802 (Definate RSX related). The user that had that code only caught it once before it went to 3034. It's rare because the break that caused the 3037/1802 wasnt bad enough to cause a fault in bitTraining (step# 40), but bad enough to prevent POST from completing.
Screenshot_20230526-100605_Firefox.jpg
link to Power on topology 3.

But by the very next power on it was full blown 3034. So between 3034 and the 1701/1601 there is a possability the break can intermittent enough to have another code get registered (50 1802/3037). It's rare to capture that, since it's such a short window of time before it fully breaks. And it could have to do with where the break occurs too. That's unknown.

But to me the diagnosis and solution is the same. RSX solder joints (BGA or Bumps) and it needs replaced, preferrably with a more reliable model.

Edit: Would you be willing to thermal cycle (1hr on 1hr off) the console until the YLOD returns and see if it progresses to 3034? That will confirm the other result.
 
Last edited:
I`ll let it cool down for a while now, and will report back. It runs pretty bad now, it stutters like crazy on the XMB. Sometimes it hangs for a solid 10 seconds before recovering. I will report back later today if the error codes will change.
 
I begin to question if the RSX really is the problem. I now only get 1601 and 1701 errors, with an occasional 1802. It always turns back on after an YLOD now, even though it doesn`t stay on for long. One time i succeeded to boot in to the opening scene of the last of us, and it didn`t crash whilst it was running that scene. But as soon as i got back to the XMB, it started stuttering with an YLOD not short after that. Other times the YLOD was there before the PS3 logo disappeared of the screen. Does the RSX also handle the sound output?I noticed that the sound during startup makes cracking noises when it starts stuttering in the animation. Or does that point to some other failing component? Here are the erros that are now in the log:

Error 0: 0xA0801601 Time: Sat, 31 Dec 2005 07:50:22 GMT
Error 1: 0xA0801701 Time: Sat, 31 Dec 2005 07:50:22 GMT
Error 2: 0xA0801601 Time: Sat, 31 Dec 2005 07:49:42 GMT
Error 3: 0xA0801701 Time: Sat, 31 Dec 2005 07:49:42 GMT
Error 4: 0xA0801802 Time: Sat, 31 Dec 2005 07:48:56 GMT
Error 5: 0xA0801601 Time: Sat, 31 Dec 2005 07:48:29 GMT
Error 6: 0xA0801701 Time: Sat, 31 Dec 2005 07:48:29 GMT
Error 7: OxA0801601 Time: Sat, 31 Dec 2005 07:46:09 GMT
Error 8: 0xA0801701 Time: Sat, 31 Dec 2005 07:46:09 GMT
Error 9: 0xA0801601 Time: Sat, 31 Dec 2005 07:45:36 GMT
Error 10: 0xA0801701 Time: Sat, 31 Dec 2005 07:45:36 GMT
Error 11: 0xA0801601 Time: Sat, 31 Dec 2005 07:44:55 GMT
Error 12: 0xA0801701 Time: Sat, 31 Dec 2005 07:44:55 GMT
Error 13: 0xA0801601 Time: Sat, 31 Dec 2005 07:44:22 GMT
Error 14: 0xA0801701 Time: Sat, 31 Dec 2005 07:44:21 GMT
Error 15: 0xA0801601 Time: Sat, 31 Dec 2005 07:43:19 GMT
Error 16: 0xA0801701 Time: Sat, 31 Dec 2005 07:43:18 GMT
Error 17: OxA0801802 Time: Sat, 31 Dec 2005 06:56:43 GMT
Error 18: 0xA0801601 Time: Sat, 31 Dec 2005 06:55:28 GMT
Error 19: 0xA0801701 Time: Sat, 31 Dec 2005 06:55:28 GMT
Error 20: 0xA0801601 Time: Sat, 31 Dec 2005 06:53:13 GMT
Error 21: OxA0801701 Time: Sat, 31 Dec 2005 06:53:13 GMT
Error 22: 0xA0801802 Time: Sat, 31 Dec 2005 06:43:53 GMT
Error 23: 0xA0801601 Time: Sat, 31 Dec 2005 06:42:55 GMT
Error 24: 0xA0801701 Time: Sat, 31 Dec 2005 06:42:55 GMT
Error 25: 0xA0801601 Time: Sat, 31 Dec 2005 06:41:12 GMT
Error 26: 0xA0801701 Time: Sat, 31 Dec 2005 06:41:12 GMT
Error 27: 0xA0801601 Time: Sat, 31 Dec 2005 04:18:38 GMT
Error 28: 0xA0801701 Time: Sat, 31 Dec 2005 04:18:38 GMT
Error 29: 0xA0801802 Time: Sat, 31 Dec 2005 04:16:14 GMT
Error 30: 0xA0801601 Time: Sat, 31 Dec 2005 04:16:09 GMT
Error 31: 0xFFFFFFFF Time: Thu, 01 Jan 1970 00:00:00 GMT
 
I would advise you do it using the comand terminal. Here's a tutorial.


Hi All,

I have managed to use the python script and have obtained the following dump file. From what I can tell from the guides is that I have an issue with RSX power, probably Tokins. Is this others conclusions or am I missing something?

I have included the becount, bringup, powerstate and errlog outputs.

I have had the console its whole life, had no issues with it its whole life until this issue occurred. No work has been done on it except soldering the diagnostic wires onto it.

Based on this error log what would my next steps be?

Cheers

Code:

Code:
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ becount
becount
Bringup : 3500 times
Shutdown: 3466 times
Power-on: 366day 05hour 52min 00sec
[mullion]$
Press Ctrl+C to exit
>$ 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)
Press Ctrl+C to exit
>$ powerstate
[SERV NVS] READ CMD

Boot Loader SE Version 2.3.5 (Build ID: 3034,32025, Build Data: 2008-05-12_15:29:27)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
powerstate
ATA Power          : ON
PCI Power          : OFF
RSX Power          : ON
XDR Power          : ON
Eurus Power        : ON
SB Power           : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor  : AVAILABLE
[mullion]$
Press Ctrl+C to exit
>$ errlog                                    *//system crashed at the same time as I input this code.
[SERV NVS] READ CMD                   
[SERV NVS] READ CMD
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801002
errlog
ofst[ 76]:err_code:0xffffffff, clock:0x22e5de52  2018/07/21 12:06:42
ofst[ 80]:err_code:0xa0801002, clock:0x22e5dfcf  2018/07/21 12:13:03
ofst[ 84]:err_code:0xa0801002, clock:0x23399a21  2018/09/23 00:26:09
ofst[ 88]:err_code:0xa0801002, clock:0x236c80f3  2018/10/31 15:04:19
ofst[ 92]:err_code:0xa0902120, clock:0x236c80f3  2018/10/31 15:04:19
ofst[ 96]:err_code:0xa0801002, clock:0x23b875bd  2018/12/28 05:48:45
ofst[100]:err_code:0xa0801002, clock:0x240c0ef2  2019/03/01 15:40:34
ofst[104]:err_code:0xa0801002, clock:0x2466e38c  2019/05/09 13:11:40
ofst[108]:err_code:0xa0801002, clock:0x246acf47  2019/05/12 12:34:15
ofst[112]:err_code:0xa0801002, clock:0x246acfb4  2019/05/12 12:36:04
ofst[116]:err_code:0xa0801002, clock:0x246ad078  2019/05/12 12:39:20
ofst[120]:err_code:0xa0801002, clock:0x24a9e468  2019/06/29 08:57:12
ofst[124]:err_code:0xa0801002, clock:0x24a9e634  2019/06/29 09:04:52
ofst[  0]:err_code:0xa0801002, clock:0x255308f4  2019/11/04 16:06:12
ofst[  4]:err_code:0xa0801002, clock:0x255309cb  2019/11/04 16:09:47
ofst[  8]:err_code:0xa0801002, clock:0x25540e56  2019/11/05 10:41:26
ofst[ 12]:err_code:0xa0801002, clock:0x25540ec3  2019/11/05 10:43:15
ofst[ 16]:err_code:0xa0801002, clock:0x25540f57  2019/11/05 10:45:43
ofst[ 20]:err_code:0xa0801002, clock:0x25542249  2019/11/05 12:06:33
ofst[ 24]:err_code:0xa0801002, clock:0x272858d5  2020/10/25 15:40:05
ofst[ 28]:err_code:0xa0801002, clock:0x272858e1  2020/10/25 15:40:17
ofst[ 32]:err_code:0xa0801002, clock:0x2bc3e36b  2023/04/08 08:33:47
ofst[ 36]:err_code:0xa0801002, clock:0x2bc3e393  2023/04/08 08:34:27
ofst[ 40]:err_code:0xa0801002, clock:0x2bc3e406  2023/04/08 08:36:22
ofst[ 44]:err_code:0xa0801002, clock:0x2bc3e44a  2023/04/08 08:37:30
ofst[ 48]:err_code:0xa0801002, clock:0x2bc92452  2023/04/12 08:12:02
ofst[ 52]:err_code:0xa0801002, clock:0x2bc928b8  2023/04/12 08:30:48
ofst[ 56]:err_code:0xa0801002, clock:0x2bc92b21  2023/04/12 08:41:05
ofst[ 60]:err_code:0xa0801002, clock:0x2c033eeb[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
  2023/05/26 09:56:59
ofst[ 64]:err_code:0xa0002120, clock:0x2c033eec  2023/05/26 09:57:00
ofst[ 68]:err_code:0xa0801001, clock:0x2c033f14  2023/05/26 09:57:40
(PowerOff State) (Fatal)
ofst[ 72]:err_code:0xa0801002, clock:0x2c034086  2023/05/26 10:03:50
[mullion]$ [ERROR]: 0xa0002120
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 80]:err_code:0xffffffff, clock:0x22e5dfcf  2018/07/21 12:13:03
ofst[ 84]:err_code:0xa0801002, clock:0x23399a21  2018/09/23 00:26:09
ofst[ 88]:err_code:0xa0801002, clock:0x236c80f3  2018/10/31 15:04:19
ofst[ 92]:err_code:0xa0902120, clock:0x236c80f3  2018/10/31 15:04:19
ofst[ 96]:err_code:0xa0801002, clock:0x23b875bd  2018/12/28 05:48:45
ofst[100]:err_code:0xa0801002, clock:0x240c0ef2  2019/03/01 15:40:34
ofst[104]:err_code:0xa0801002, clock:0x2466e38c  2019/05/09 13:11:40
ofst[108]:err_code:0xa0801002, clock:0x246acf47  2019/05/12 12:34:15
ofst[112]:err_code:0xa0801002, clock:0x246acfb4  2019/05/12 12:36:04
ofst[116]:err_code:0xa0801002, clock:0x246ad078  2019/05/12 12:39:20
ofst[120]:err_code:0xa0801002, clock:0x24a9e468  2019/06/29 08:57:12
ofst[124]:err_code:0xa0801002, clock:0x24a9e634  2019/06/29 09:04:52
ofst[  0]:err_code:0xa0801002, clock:0x255308f4  2019/11/04 16:06:12
ofst[  4]:err_code:0xa0801002, clock:0x255309cb  2019/11/04 16:09:47
ofst[  8]:err_code:0xa0801002, clock:0x25540e56  2019/11/05 10:41:26
ofst[ 12]:err_code:0xa0801002, clock:0x25540ec3  2019/11/05 10:43:15
ofst[ 16]:err_code:0xa0801002, clock:0x25540f57  2019/11/05 10:45:43
ofst[ 20]:err_code:0xa0801002, clock:0x25542249  2019/11/05 12:06:33
ofst[ 24]:err_code:0xa0801002, clock:0x272858d5  2020/10/25 15:40:05
ofst[ 28]:err_code:0xa0801002, clock:0x272858e1  2020/10/25 15:40:17
ofst[ 32]:err_code:0xa0801002, clock:0x2bc3e36b  2023/04/08 08:33:47
ofst[ 36]:err_code:0xa0801002, clock:0x2bc3e393  2023/04/08 08:34:27
ofst[ 40]:err_code:0xa0801002, clock:0x2bc3e406  2023/04/08 08:36:22
ofst[ 44]:err_code:0xa0801002, clock:0x2bc3e44a  2023/04/08 08:37:30
ofst[ 48]:err_code:0xa0801002, clock:0x2bc92452  2023/04/12 08:12:02
ofst[ 52]:err_code:0xa0801002, clock:0x2bc928b8  2023/04/12 08:30:48
ofst[ 56]:err_code:0xa0801002, clock:0x2bc92b21  2023/04/12 08:41:05
ofst[ 60]:err_code:0xa0801002, clock:0x2c033eeb  2023/05/26 09:56:59
ofst[ 64]:err_code:0xa0002120, clock:0x2c033eec  2023/05/26 09:57:00
ofst[ 68]:err_code:0xa0801001, clock:0x2c033f14  2023/05/26 09:57:40
ofst[ 72]:err_code:0xa0801002, clock:0x2c034086  2023/05/26 10:03:50
ofst[ 76]:err_code:0xa0002120, clock:0x2c034087  2023/05/26 10:03:51
[mullion]$
Press Ctrl+C to exit
>$
 
Sorry for bad english.
Hi, I bought a PS3 FAT CECHC04 from eBay. The console has ylod. I did the syscon test error 1017 (no other error) that if I understand correctly is a generic error. Could you help me, the console does not have hdd (if you could need to know). You may need to do a reballing (there is no error 3034)?
 
I have seen this progression before. 1601/1701 (crashes in game or XMB) leads to a 3037/1802 (Definate RSX related). The user that had that code only caught it once before it went to 3034. It's rare because the break that caused the 3037/1802 wasnt bad enough to cause a fault in bitTraining (step# 40), but bad enough to prevent POST from completing.
View attachment 40655
link to Power on topology 3.

But by the very next power on it was full blown 3034. So between 3034 and the 1701/1601 there is a possability the break can intermittent enough to have another code get registered (50 1802/3037). It's rare to capture that, since it's such a short window of time before it fully breaks. And it could have to do with where the break occurs too. That's unknown.

But to me the diagnosis and solution is the same. RSX solder joints (BGA or Bumps) and it needs replaced, preferrably with a more reliable model.

Edit: Would you be willing to thermal cycle (1hr on 1hr off) the console until the YLOD returns and see if it progresses to 3034? That will confirm the other result.

I've put the console through a few cycles today, and contrary to expectations, the console seems more and more stable after each cycle.

This morning it booted mostly fine, it generated one more 3037 code during multiple attempts to get it to stay on for long enough to heat up. But after that one only loads of 1601, 1701 and 1802 error codes. Each time the ylod appeared after a different amount of time. Sometimes a few seconds after boot, sometimes more than 10 minutes later. I also observed that sometimes, it will just freeze and stay on a green light. The console won't react to anything, but also won't shut off on its own. I've let it be in this state a 2 times for over 30 minutes.

Later this afternoon, it was at the point that I've played the last of us three times for an hour straight, with 1 hour of cooling down between each session, without any more ylod or stuttering. If you didn't now the history of the console, you couldn't notice anything wrong.

I now have a few hypothesis:
1. A BGA/bump failure on the RSX on some non critical for bit training part of the chip. The heat generated by the last of us combined with some luck might have been just enough to connect just the necessary points to where it's stable again, and the ylod will return very soon.
2. The RSX has problems with it's VRAM, on psdevwiki it was reported that a problem with the VRAM could result in a GLOD combined with a 1701 error. This could explain the totally random nature of the YLOD, because it gets into a livelock condition when it needs something that wasn't reachable in VRAM.
3. There is some other problem on the board, possibly CELL, that has problems. This doesn't seem that likely to me.

Disclaimer:
I don't know how right or wrong these hypothesis are. I don't have much experience with diagnosing these kinds of problems and this PS3 is mostly a learning experience for me. Please correct me if I think something that isn't possible.

Edit:
Also, if there are any recommendations for further steps in diagnosing and fixing the issues I really appreciate it. I don't really want to just throw a expensive Frankenstein mod at a console and hope for the best.
 
Update:
I did the internal mode test to syscom and result is:

errlog
ofst[116]:err_code:0xffffffff, clock:0x1662ee6a 2011/11/26 00:25:14
ofst[120]:err_code:0xa0801701, clock:0x1662ee74 2011/11/26 00:25:24
ofst[124]:err_code:0xa0801701, clock:0x1662ee81 2011/11/26 00:25:37
ofst[ 0]:err_code:0xa0801701, clock:0x1662ee90 2011/11/26 00:25:52
ofst[ 4]:err_code:0xa0801701, clock:0x1662eea4 2011/11/26 00:26:12
ofst[ 8]:err_code:0xa0801701, clock:0x1662eeb0 2011/11/26 00:26:24
ofst[ 12]:err_code:0xa0801701, clock:0x1662eebf 2011/11/26 00:26:39
ofst[ 16]:err_code:0xa0801701, clock:0x1663ef0e 2011/11/26 18:40:14
ofst[ 20]:err_code:0xa0801701, clock:0x166c3dbc 2011/12/03 01:54:04
ofst[ 24]:err_code:0xa0801701, clock:0x167aaad0 2011/12/14 00:31:12
ofst[ 28]:err_code:0xa0801701, clock:0x167aaad9 2011/12/14 00:31:21
ofst[ 32]:err_code:0xa0801701, clock:0x167aaafb 2011/12/14 00:31:55
ofst[ 36]:err_code:0xa0801701, clock:0x168c4647 2011/12/27 09:03:03
ofst[ 40]:err_code:0xa0801701, clock:0x169cb573 2012/01/08 20:13:39
ofst[ 44]:err_code:0xa0801701, clock:0x169cc7c5 2012/01/08 21:31:49
ofst[ 48]:err_code:0xa0801701, clock:0x2bf76fef 2023/05/17 10:58:55
ofst[ 52]:err_code:0xa0801701, clock:0x2bf77007 2023/05/17 10:59:19
ofst[ 56]:err_code:0xa0801701, clock:0x2bf77010 2023/05/17 10:59:28
ofst[ 60]:err_code:0xa0801701, clock:0x2bf77018 2023/05/17 10:59:36
ofst[ 64]:err_code:0xa0801701, clock:0x2bf77030 2023/05/17 11:00:00
ofst[ 68]:err_code:0xa0801701, clock:0x2bf7706c 2023/05/17 11:01:00
ofst[ 72]:err_code:0xa0801701, clock:0x2bffc229 2023/05/23 18:27:53
ofst[ 76]:err_code:0xa0801701, clock:0x2bffc243 2023/05/23 18:28:19
ofst[ 80]:err_code:0xa0801701, clock:0xffffffff
ofst[ 84]:err_code:0xa0801701, clock:0xffffffff
ofst[ 88]:err_code:0xa0801701, clock:0xffffffff
ofst[ 92]:err_code:0xa0901200, clock:0xffffffff
ofst[ 96]:err_code:0xa0801200, clock:0xffffffff
ofst[100]:err_code:0xa0801701, clock:0xffffffff
ofst[104]:err_code:0xa0801200, clock:0xffffffff
ofst[108]:err_code:0xa0801200, clock:0xffffffff
ofst[112]:err_code:0xa0801200, clock:0xffffffff

> bringup
bringup
Do nothing. (FatalOff State)
> shutdown
shutdown
[SSM] cannot clear fatal error state because of unrecoverable error.
[mullion]$
> shutdown
shutdown
[SSM] cannot clear fatal error state because of unrecoverable error.

> becount
becount
Bringup : 2395 times
Shutdown: 2332 times
Power-on: 145day 20hour 26min 22sec

appear 1017 and 1200 now (I started the ps3 without intercooler) Can you help me?
 
Last edited:
Edit: I also have this information
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:0x21e2
> power off
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SSM] Attention BE : Detected !
[SSM] BE Attention signal is detected !!
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801701
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
power off
*** Unknown Command ***
 
It would be helpful to see the full errorlog, not just the last one in the log. Other codes preceeding it can lend context to the current code and help build a story. Also, other notes about the condition of the console would be useful. Such as any visible damage, missing parts, amout of dust, whether or not the console was previously worked on and if so what they may have done (flux residue, scortching, replaced parts...etc), and so on.

Not trying to be a prude, but just posting one code doesn't give us much to go on. Especially one that hasn't been entered into the dev wiki. Clearly we've not encountered it before and don't know what it means. So of course we need more context.

Please provide the full bringup, becount (if possable), and errorlog when asking for help. Otherwise, how can we? Error codes can be, and often are ambiguous and need to be placed in context with other evidence to make a diagnosis. Rarely are the diagnostic on their own.
Thanks for the reply RIP-Felix. Apologies for not including more context!

bringup
```
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOFF State)
# [SSM] Bringup Start.
# [PowSeq] Error:A115
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOFF State)
```
ErrLog - same log for the past 20 attempts to boot
```
# CODE CLOCK
# A0111B01 FFFFFFFF
# A0111B01 FFFFFFFF
# A0111B01 FFFFFFFF
# A0111B01 FFFFFFFF
# A0111B01 FFFFFFFF
```

Only modifications AFTER this error was received is a replacement of the NEC/TOKIN's , which reading from your previous investigations and videos is not surprise to you i'm sure.

Never been worked on. Barely used since ownership and dust level is low, however now has been fully cleaned.
The symptoms over time started with freezing while playing GTA5, which a reboot eventually resolves it. However after an hour or so playing again results in freeze. Now the behaviour is simply not booting, YLOD, three beeps and then flashing red light.

Hope that helps!
 
Thanks for the reply RIP-Felix. Apologies for not including more context!

bringup
```
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOFF State)
# [SSM] Bringup Start.
# [PowSeq] Error:A115
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOFF State)
```
ErrLog - same log for the past 20 attempts to boot
```
# CODE CLOCK
# A0111B01 FFFFFFFF
# A0111B01 FFFFFFFF
# A0111B01 FFFFFFFF
# A0111B01 FFFFFFFF
# A0111B01 FFFFFFFF
```

Only modifications AFTER this error was received is a replacement of the NEC/TOKIN's , which reading from your previous investigations and videos is not surprise to you i'm sure.

Never been worked on. Barely used since ownership and dust level is low, however now has been fully cleaned.
The symptoms over time started with freezing while playing GTA5, which a reboot eventually resolves it. However after an hour or so playing again results in freeze. Now the behaviour is simply not booting, YLOD, three beeps and then flashing red light.

Hope that helps!
Which caps were used and can you provide pics of the work and general area? The behavior sounds like it might be a botched tantalum install.

11 is a common step number for VRM errors. While 1B01 is a unusual code, the behavior, previous work history in the area, and step# it's associated with suggest the Voltage Regulation Module (tokins, buck converters, voltage compensation network of SMDs).
 
I've put the console through a few cycles today, and contrary to expectations, the console seems more and more stable after each cycle.

This morning it booted mostly fine, it generated one more 3037 code during multiple attempts to get it to stay on for long enough to heat up. But after that one only loads of 1601, 1701 and 1802 error codes. Each time the ylod appeared after a different amount of time. Sometimes a few seconds after boot, sometimes more than 10 minutes later. I also observed that sometimes, it will just freeze and stay on a green light. The console won't react to anything, but also won't shut off on its own. I've let it be in this state a 2 times for over 30 minutes.

Later this afternoon, it was at the point that I've played the last of us three times for an hour straight, with 1 hour of cooling down between each session, without any more ylod or stuttering. If you didn't now the history of the console, you couldn't notice anything wrong.

I now have a few hypothesis:
1. A BGA/bump failure on the RSX on some non critical for bit training part of the chip. The heat generated by the last of us combined with some luck might have been just enough to connect just the necessary points to where it's stable again, and the ylod will return very soon.
2. The RSX has problems with it's VRAM, on psdevwiki it was reported that a problem with the VRAM could result in a GLOD combined with a 1701 error. This could explain the totally random nature of the YLOD, because it gets into a livelock condition when it needs something that wasn't reachable in VRAM.
3. There is some other problem on the board, possibly CELL, that has problems. This doesn't seem that likely to me.

Disclaimer:
I don't know how right or wrong these hypothesis are. I don't have much experience with diagnosing these kinds of problems and this PS3 is mostly a learning experience for me. Please correct me if I think something that isn't possible.

Edit:
Also, if there are any recommendations for further steps in diagnosing and fixing the issues I really appreciate it. I don't really want to just throw a expensive Frankenstein mod at a console and hope for the best.
So there's not much more to try. It would have been more clear if it had changed to a 3034, but the errors are consistent with GPU issues regardless. In either case, hypothesis 1 or 2, the solution is the same. Replace the RSX and hope that was it.

About the cost. It is usually considered not worth repairing when a large BGA package like a GPU needs removed. For a large company paying hourly workers, performing thousands of repairs a month it might be possable to offer the service for a reasonable price. And those companies still exist. But they're not familiar with this process specifically and will require an additional motherboard/fee for developing a reflow profile. For most other techs and consoles, it's not worth it. In the case of backwards compatible models it is worth the effort because they hold value (monitary and sentimental). Reballing was expensive before the Frankie. So it's only natural they charge more for a better alternative.

If you want it done by someone with experiance doing these specifically, you'll have to pay their ransom, which is high because their overhead is high, being small scale. If you want a better deal, you can try a professio al rework company, explain the mod in detail and hope they do it right. I trust their equipment, but not familiarity with this board or process. And an hourly worker rushing the board, under a deadline to keep cost down doesn't led itself well to the quality work expected for this kind of thing. But that could just be paranoia and they would do a good job.
 
Last edited:
So there's not much more to try. It would have been more clear if it had changed to a 3034, but the errors are consistent with GPU issues regardless. In either case, hypothesis 1 or 2, the solution is the same. Replace the RSX and hope that was it.

About the cost. It is usually considered not worth repairing when a large BGA package like a GPU needs removed. For a large company paying hourly workers, performing thousands of repairs a month it might be possable to offer the service for a reasonable price. And those companies still exist. But they're not familiar with this process specifically and will require an additional motherboard/fee for developing a reflow profile. For most other techs and consoles, it's not worth it. In the case of backwards compatible models it is worth the effort because they hold value (monitary and sentimental). Reballing was expensive before the Frankie. So it's only natural they charge more for a better alternative.

If you want it done by someone with experiance doing these specifically, you'll have to pay their ransom, which is high because their overhead is high, being small scale. If you want a better deal, you can try a professio al rework company, explain the mod in detail and hope they do it right. I trust their equipment, but not familiarity with this board or process. And an hourly worker rushing the board, under a deadline to keep cost down doesn't led itself well to the quality work expected for this kind of thing. But that could just be paranoia and they would do a good job.

Thanks for the reply. I`ve delidded the CPU now, and its heavily discolored. And i mean heavily, it`s deep purple. I`ve never seen a cell discolored so much in the 5 CECHC consoles I`ve owned and delidded. Is that bad or doesn`t that matter much?

Edit: Did a bunch more research on the console today. If it's cold, it will throw a YLOD within a random amount of time. The XMB slows down and will eventually freeze, with a YLOD and 1601 and 1701 code following. The console will try to boot up every time tho. As soon as the console is up to temp, the ylod won't return. You can do anything with it and it won't ylod. So it has a problem somewhere not significant enough to prevent booting, but enough to throw a YLOD. And when it warms up, it expands just enough to fix the issues. After 15+ cycles the symptoms don't seem to change.

I'm adding one new hypothesis now, and that's a issue related to the southbridge. I've seen the 0802203 code a few times now, but the sd card reader, usb ports, wifi, Bluetooth and Ethernet all seem to work just fine. Are there any other known symptoms of a failing southbridge? It doesn't seem likely that it's the problem, but Syscon doesn't throw that error for fun I imagine.
 
Last edited:
Hi guys, I'm new to the forum but I found out about it last weekend so I've been doing some tests with some ps3s around here and I found this error log



C:\Windows\system32>Python "C:\Users\Alexandre\Desktop\Syscon Connection Drivers and Diagrams ByNSC\PS3_Syscon_(Mullion_Sherwood)_script.py" COM3 CXR
> AUTH
Auth1 response invalid
> AUTH
Auth successful
> ERRLOG GET
F0000006
> ERRLOG GET 00
00000000 A0022110 FFFFFFFF
> ERRLOG GET 00
00000000 A0022110 FFFFFFFF
> ERRLOG GET 01
00000000 A0022110 FFFFFFFF
> ERRLOG GET 02
00000000 A0093003 FFFFFFFF
> ERRLOG GET 03
00000000 A0093003 FFFFFFFF
> ERRLOG GET 04
00000000 A0051004 FFFFFFFF
> ERRLOG GET 05
00000000 A0093003 FFFFFFFF
> ERRLOG GET 06
00000000 A0801001 FFFFFFFF
> ERRLOG GET 07
00000000 A0801001 0B4C5C58
> ERRLOG GET 08
00000000 A0801001 0B4C5C4C
> ERRLOG GET 09
00000000 A0801001 0B4C5C37
> ERRLOG GET 10
00000000 A0801001 0B4AC7CC
> ERRLOG GET 11
00000000 A0101001 0B4AC7C4
> ERRLOG GET 12
00000000 A0801001 0B4AC6C2
> ERRLOG GET 13
00000000 A0101001 0B4AC6B3
> ERRLOG GET 14
00000000 A0101001 0B4AC6AF
> ERRLOG GET 15
00000000 A0801001 0B4AC44B
> ERRLOG GET 16
00000000 A0101001 0B4AC35D
> ERRLOG GET 17
00000000 A0101001 0B4AC359
> ERRLOG GET 18
00000000 A0101001 0B4AC353
> ERRLOG GET 19
00000000 A0801001 0B4AC1D9

so I would like to ask if this would be a ps3 where the rsx is in good condition conditions?
Thanks and sorry for any mistakes
model cech e01
 
motherboard DIA-001
** GLOD **
UART no error
I made a replacement for RSX with a similar one - the result returned to GlOD
also tried to warm up SOUTH BRIDGE
Resetting video settings doesn't help.
no video by AV & HDMI
power comes to the USB ports but there is no reading from a USB flash drive,
flash drive with indication, just glows and nothing happens
also when connecting a gamepad - no initialization,
it only blinks that it is charging

also connected HDD
the indication flashes at start a couple of times and nothing else flashes, the engine is spinning ...
what can be done?​

  • I'm thinking of replacing SOUTH BRIDGE, but I doubt
  • or read the firmware and check it

here are the logs:


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
(Power On State)
Press Ctrl+C to exit
>$
[SERV NVS] READ CMD
Boot Loader SE Version 2.1.0 (Build ID: 2709,28222, Build Data: 2007-12-05_13:32:28)
Copyright(C) 2007 Sony Computer Entertainment Inc. All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD

 
motherboard DIA-001
** GLOD **
UART no error
I made a replacement for RSX with a similar one - the result returned to GlOD
also tried to warm up SOUTH BRIDGE
Resetting video settings doesn't help.
no video by AV & HDMI
power comes to the USB ports but there is no reading from a USB flash drive,
flash drive with indication, just glows and nothing happens
also when connecting a gamepad - no initialization,
it only blinks that it is charging

also connected HDD
the indication flashes at start a couple of times and nothing else flashes, the engine is spinning ...
what can be done?​

  • I'm thinking of replacing SOUTH BRIDGE, but I doubt
  • or read the firmware and check it

here are the logs:


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
(Power On State)
Press Ctrl+C to exit
>$
[SERV NVS] READ CMD
Boot Loader SE Version 2.1.0 (Build ID: 2709,28222, Build Data: 2007-12-05_13:32:28)
Copyright(C) 2007 Sony Computer Entertainment Inc. All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD

Can you please write on uart port w 4202 02. This should enable sb uart debugging view.
Now we need to solder rx from uart adaptor to sb uart Tx on mobo and receive on pc via putty some messages from lv0. If it goes up to safe mode you have still dead rsx. Did this unit worked before. Can't be a brick issues?
Cracked cell ball very rare will glod.
This can be that case where cell need reball but first get debugging log fro sb
 

i wrote the command
w 4202 02
complete!
further connected to
SB_SIO0_TXD_M on motherboard
launched PYtty
COM3 settings 115200
but when running the console, there is nothing in the PYtty terminal
Checked several times the soldering and the rest
Only GND and TXD pins are connected to the board



w 4202 02
is the command correct for my board?

now dumped the firmware 3 times
and it turned out to be bad, tell me what can be done

Dumps in .zip attached
https://dropmefiles.com/RZidl
https://fex.net/ru/s/formnl8



Dump Checker LOG ver3 said:
********************************************
PS3 Dump Checker v1.0 (Build: 503)
Check started: 03.06.2023 22:54:55
********************************************
22:54:55 : Reading image into memory and checking statistics...
22:54:55 : Statistics check skipped! (nothing to check)
22:54:55 : Binary check Started!
22:54:55 : Binary check for 001.02 First Region Header Magic Started... Result: OK!
22:54:55 : Binary check for 002.01 Flash Format String Started... Result: OK!
22:54:55 : Binary check for 002.02 Flash Format Version Started... Result: OK!
22:54:55 : Binary check for 003.01 Flash Region Table Header Started... Result: OK!
22:54:55 : Binary check for 003.02 asecure_loader Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.03 asecure_loader Name Started... Result: OK!
22:54:55 : Binary check for 003.04 eEID Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.05 eEID Name Started... Result: OK!
22:54:55 : Binary check for 003.06 cISD Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.07 cISD Name Started... Result: OK!
22:54:55 : Binary check for 003.08 cCSD Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.09 cCSD Name Started... Result: OK!
22:54:55 : Binary check for 003.10 trvk_prg0 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.11 trvk_prg0 Name Started... Result: OK!
22:54:55 : Binary check for 003.12 trvk_prg1 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.13 trvk_prg1 Name Started... Result: OK!
22:54:55 : Binary check for 003.14 trvk_pkg0 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.15 trvk_pkg0 Name Started... Result: OK!
22:54:55 : Binary check for 003.16 trvk_pkg1 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.17 trvk_pkg1 Name Started... Result: OK!
22:54:55 : Binary check for 003.18 ros0 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.19 ros0 Name Started... Result: OK!
22:54:55 : Binary check for 003.20 ros1 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.21 ros1 Name Started... Result: OK!
22:54:55 : Binary check for 003.22 cvtrm Offset - Length Started... Result: OK!
22:54:55 : Binary check for 003.23 cvtrm Name Started... Result: OK!
22:54:55 : Binary check for 004.01 asecure_loader Header Started... Result: OK!
22:54:55 : Binary check for 004.02 metldr Offset Started... Result: OK!
22:54:55 : Binary check for 004.03 metldr Length Started... Result: OK!
22:54:55 : Binary check for 004.04 metldr Name Started... Result: OK!
22:54:55 : Binary check for 004.05 metldr RevKey Started... Result: OK!
22:54:55 : Binary check for 004.06 metldr Binary Size Started... Result: OK!
22:54:55 : Binary check for 005.01 eEID Header Started... Result: OK!
22:54:55 : Binary check for 005.02 EID0 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 005.03 EID1 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 005.04 EID2 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 005.05 EID3 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 005.06 EID4 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 005.07 EID5 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 005.08 EID0 IDPS0 Started... Result: OK!
22:54:55 : Binary check for 005.09 EID0 IDPS1 Started... Result: OK!
22:54:55 : Binary check for 005.10 EID0 Static Started... Result: OK!
22:54:55 : Binary check for 005.11 EID2 BlockSize/Padding Started... Result: OK!
22:54:55 : Binary check for 005.12 EID3 Static0 Started... Result: OK!
22:54:55 : Binary check for 005.13 EID3 Static1 Started... Result: OK!
22:54:55 : Binary check for 005.14 EID3 Static2 Started... Result: OK!
22:54:55 : Binary check for 005.15 EID5 IDPS0 Started... Result: OK!
22:54:55 : Binary check for 005.16 EID5 IDPS1 Started... Result: OK!
22:54:55 : Binary check for 005.17 EID5 Static Started... Result: OK!
22:54:55 : Binary check for 006.01 cISD Header Started... Result: OK!
22:54:55 : Binary check for 006.02 cISD0 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 006.03 cISD1 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 006.04 cISD2 Offset - Length Started... Result: OK!
22:54:55 : Binary check for 006.06 cISD1 IDLog Header Started... Result: OK!
22:54:55 : Binary check for 006.07 cISD1 Semistatic 1 Started... Result: OK!
22:54:55 : Binary check for 006.08 cISD1 Semistatic 2 Started... Result: OK!
22:54:55 : Binary check for 006.10 cISD1 Static Started... Result: OK!
22:54:55 : Binary check for 006.11 cISD1 Semistatic 3 Started... Result: OK!
22:54:55 : Binary check for 006.14 cISD2 Started... Result: OK!
22:54:55 : Binary check for 007.01 cCSD Header Started... Result: OK!
22:54:55 : Binary check for 007.02 cCSD Entry Table Started... Result: OK!
22:54:55 : Binary check for 008.01 trvk_prg0 SCE Started... Result: OK!
22:54:55 : Binary check for 008.02 trvk_prg1 SCE Started... Result: FAILED! Offset: 0x60010
Expected data:
53 43 45 00
Ascii Value: SCE
Actual data: FF FF FF FF
Ascii Value: ????
22:54:55 : Binary check for 008.03 trvk_pkg0 SCE Started... Result: FAILED! Offset: 0x80010
Expected data:
53 43 45 00
Ascii Value: SCE
Actual data: FF FF 00 45
Ascii Value: ?? E
22:54:55 : Binary check for 008.04 trvk_pkg1 SCE Started... Result: FAILED! Offset: 0xA0010
Expected data:
53 43 45 00
Ascii Value: SCE
Actual data: FF FF FF FF
Ascii Value: ????
22:54:55 : Binary check for 009.01 ROS0 Header Started... Result: FAILED! Offset: 0xC0000
Expected data:
00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0
Actual data: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
22:54:55 : Binary check for 009.04 ROS1 Header Started... Result: FAILED! Offset: 0x7C0000
Expected data:
00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0
Actual data: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
22:54:55 : Binary check for 010.02 cvtrm0 Header Started... Result: FAILED! Offset: 0xEC0000
53 43 45 49 FF FD FF FF FF FF FF FF FF FF FF FF
53 43 45 49 FF FF FF FF FF FF FF FF FF FF FF FF
00 00 00 00 FF FD FF FF FF FF FF FF FF FF FF FF
00 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
Actual data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
22:54:55 : Binary check for 010.04 vtrm0 Magic Started... Result: FAILED! Offset: 0xEC4000
Expected data:
00 00 00 00 56 54 52 4D 00 00 00 00 00 00
Ascii Value: VTRM
Actual data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Ascii Value:
22:54:55 : Binary check for 010.05 vtrm0 Reserved Entries Started... Result: FAILED! Offset: 0xEC4028
Expected data:
00 00 00 00 00 00 02 09
Actual data: 00 00 00 00 00 00 00 00
22:54:55 : Binary check for 010.07 cvtrm1 Header Started... Result: FAILED! Offset: 0xEE0000
53 43 45 49 FF FD FF FF FF FF FF FF FF FF FF FF
53 43 45 49 FF FF FF FF FF FF FF FF FF FF FF FF
00 00 00 00 FF FD FF FF FF FF FF FF FF FF FF FF
00 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
Actual data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
22:54:55 : Binary check for 010.09 vtrm1 Magic Started... Result: FAILED! Offset: 0xEE4000
Expected data:
00 00 00 00 56 54 52 4D 00 00 00 00 00 00
Ascii Value: VTRM
Actual data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Ascii Value:
22:54:55 : Binary check for 010.10 vtrm1 Reserved Entries Started... Result: FAILED! Offset: 0xEE4028
Expected data:
00 00 00 00 00 00 02 09
Actual data: 00 00 00 00 00 00 00 00
22:54:55 : Binary check for 011.02 Second Region Header Magic Started... Result: FAILED! Offset: 0xF00010
Expected data:
00 00 00 00 0F AC E0 FF 00 00 00 00 DE AD FA CE
Actual data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
22:54:55 : Binary check for 011.03 Second Region Header Count Started... Result: FAILED! Offset: 0xF00020
Expected data:
00 00 00 00 00 00 00 03
Actual data: 00 00 00 00 00 00 00 00
22:54:55 : Binary check for 011.05 Second Region Unknown Block 0 Started... Result: FAILED! Offset: 0xF000C0
Expected data:
00 00 00 00 00 00 79 00 00 00 00 00 00 00 01 00
10 70 00 00 01 00 00 01 00 00 00 00 00 00 00 03
10 70 00 00 02 00 00 01 00 00 00 00 00 00 00 03
Actual data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
22:54:55 : Binary check for 011.07 Second Region Unknown Block 1 Started... Result: FAILED! Offset: 0xF00150
Expected data:
00 00 00 00 00 00 7A 00 00 00 00 00 00 00 04 00
10 70 00 00 01 00 00 01 00 00 00 00 00 00 00 03
10 70 00 00 02 00 00 01 00 00 00 00 00 00 00 03
Actual data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
22:54:55 : Binary check for 013.01 CELL_EXTNOR_AREA Header Started... Result: FAILED! Offset: 0xF20000
Expected data:
43 45 4C 4C 5F 45 58 54 4E 4F 52 5F 41 52 45 41
Ascii Value: CELL_EXTNOR_AREA
Actual data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Ascii Value:
22:54:55 : Binary check for 014.01 bootldr0 Started... Result: FAILED! Offset: 0xFC0000
00 00 2F 1C
00 00 2E F4
00 00 2E E3
00 00 2E AB
00 00 2E B3
00 00 2F 13
00 00 2F 3B
00 00 2F 4B
00 00 2F 53
00 00 2F 5B
00 00 2F FB
00 00 30 03
00 00 30 0B
00 00 30 1B
Actual data: FF FF FF FF
22:54:55 : Binary check for 014.02 bootldr1 Started... Result: FAILED! Offset: 0xFC0010
00 00 2F 1C
00 00 2E F4
00 00 2E E3
00 00 2E AB
00 00 2E B3
00 00 2F 13
00 00 2F 3B
00 00 2F 4B
00 00 2F 53
00 00 2F 5B
00 00 2F FB
00 00 30 03
00 00 30 0B
00 00 30 1B
Actual data: FF FF FF FF
22:54:55 : Binary check for 014.03 bootldr Rev key Started... Result: FAILED! Offset: 0xFC0004
06 5B 86 0C 5C F7 6A C4 59 8D D7 B4
89 EF FD 15 B3 85 0E 3B 2A 73 44 84
6E ED 04 A0 4E 41 53 2A C1 23 C7 18
E6 44 A0 75 B6 0B 79 96 C1 29 7A A0
7B 09 CB EE 00 2F AF 51 59 F8 D5 A8
ED 4C 79 D6 5D 60 28 76 FF AD A6 FD
B1 94 34 A3 3C F1 C8 66 DF 42 0E 50
83 EF B9 76 C4 DE D1 35 32 7C D3 77
61 D1 9B A5 41 68 16 3C 01 9F 88 4B
92 AC 2C 21 57 A5 77 C8 4D DF EC DB
41 F7 93 C7 09 41 8F 93 89 44 BA 7A
FA 46 EC 86 57 0F CA AA 06 4E 8A 86
F5 A2 21 B5 C0 5F 21 42 01 97 9D AA
77 80 B1 34 B6 DF 25 8A 1A BB AB 4D
CB 9E 15 24 28 B4 4F D2 F9 3F BC 43
EF B3 45 5D 6A 9F D7 51 00 5E 34 BC
53 92 1C E7 F7 33 41 76 9B 7A 1E D6
53 E6 A0 BB B0 AF A2 00 67 D0 B3 9A
AA 3A EA 6E 3D A0 9A 58 1E 1E 21 00
C5 A4 27 71 EE 5E 21 9A 3B FC 2C 45
13 EC A7 4A 8E 14 D4 73 12 91 28 E8
63 B9 D9 81 30 DB 7B B0 F3 9D 12 4F
BB CC BF 29 EC D8 02 84 4E B2 8A E6
2E 60 41 04 D9 43 D1 B5 34 D4 C5 F5
1F DC 1E 2D F0 0D A3 67 01 E2 F8 F6
6F C7 33 26 24 24 65 AE 91 5F 6E D9
84 D9 14 5F 34 53 E0 F6 B1 4D 5F 6E
EF A7 05 0F A2 54 7E 11 4F B2 D5 BC
D3 85 A0 89 30 F3 65 2E 3C 16 D5 B5
4B 3C 0C 95 18 2D 43 E9 8D 7B C2 86
CB AA F7 B8 EB 4A 6D 76 41 E1 E6 8E
21 A5 99 A0 B8 0D 4D BE 8D 4D 55 9A
6E BC CF 18 F9 06 39 94 49 E5 CB 06
C2 08 8D 62 3A 38 EF E1 A5 8F 08 09
Actual data: FF FF FF FF FF FF FF FF FF FF FF FF
22:54:55 : Data check Started!
22:54:55 : Data Statistics check for 004.07 metldr Statistics Started... Result: OK!
22:54:55 : Data Statistics check for 005.19 eEID Statistics0 Started... Result: OK!
22:54:55 : Data Statistics check for 005.20 eEID Statistics1 Started... Result: 22:54:55 : Statistics check Failed! 0x00 doesn't match expected percentage: lower then 1,2% Actual value: 1,86%
FAILED! Offset checked: 0x2FB90
Length checked: 0x1240
Everything should be less then 1,20%
Actual data: 0x00 : 1,86%
0x01 : 0,43%
0x02 : 0,39%
0x03 : 0,43%
0x04 : 0,54%
0x05 : 0,34%
0x06 : 0,47%
0x07 : 0,43%
0x08 : 0,30%
0x09 : 0,26%
0x0A : 0,36%
0x0B : 0,43%
0x0C : 0,34%
0x0D : 0,34%
0x0E : 0,28%
0x0F : 0,41%
0x10 : 0,60%
0x11 : 0,34%
0x12 : 0,41%
0x13 : 0,32%
0x14 : 0,32%
0x15 : 0,62%
0x16 : 0,34%
0x17 : 0,41%
0x18 : 0,45%
0x19 : 0,34%
0x1A : 0,36%
0x1B : 0,41%
0x1C : 0,43%
0x1D : 0,43%
0x1E : 0,34%
0x1F : 0,54%
0x20 : 0,60%
0x21 : 0,32%
0x22 : 0,41%
0x23 : 0,39%
0x24 : 0,47%
0x25 : 0,43%
0x26 : 0,30%
0x27 : 0,21%
0x28 : 0,28%
0x29 : 0,36%
0x2A : 0,21%
0x2B : 0,54%
0x2C : 0,30%
0x2D : 0,36%
0x2E : 0,36%
0x2F : 0,39%
0x30 : 0,43%
0x31 : 0,28%
0x32 : 0,34%
0x33 : 0,36%
0x34 : 0,39%
0x35 : 0,30%
0x36 : 0,51%
0x37 : 0,43%
0x38 : 0,34%
0x39 : 0,39%
0x3A : 0,32%
0x3B : 0,43%
0x3C : 0,54%
0x3D : 0,36%
0x3E : 0,36%
0x3F : 0,28%
0x40 : 0,34%
0x41 : 0,26%
0x42 : 0,54%
0x43 : 0,30%
0x44 : 0,49%
0x45 : 0,34%
0x46 : 0,32%
0x47 : 0,34%
0x48 : 0,24%
0x49 : 0,32%
0x4A : 0,34%
0x4B : 0,30%
0x4C : 0,32%
0x4D : 0,36%
0x4E : 0,36%
0x4F : 0,32%
0x50 : 0,26%
0x51 : 0,60%
0x52 : 0,36%
0x53 : 0,36%
0x54 : 0,43%
0x55 : 0,34%
0x56 : 0,45%
0x57 : 0,32%
0x58 : 0,30%
0x59 : 0,58%
0x5A : 0,41%
0x5B : 0,51%
0x5C : 0,26%
0x5D : 0,49%
0x5E : 0,41%
0x5F : 0,32%
0x60 : 0,36%
0x61 : 0,32%
0x62 : 0,34%
0x63 : 0,30%
0x64 : 0,47%
0x65 : 0,34%
0x66 : 0,26%
0x67 : 0,45%
0x68 : 0,39%
0x69 : 0,34%
0x6A : 0,32%
0x6B : 0,39%
0x6C : 0,28%
0x6D : 0,51%
0x6E : 0,34%
0x6F : 0,28%
0x70 : 0,30%
0x71 : 0,36%
0x72 : 0,41%
0x73 : 0,30%
0x74 : 0,32%
0x75 : 0,60%
0x76 : 0,19%
0x77 : 0,39%
0x78 : 0,26%
0x79 : 0,34%
0x7A : 0,58%
0x7B : 0,32%
0x7C : 0,36%
0x7D : 0,34%
0x7E : 0,32%
0x7F : 0,36%
0x80 : 0,43%
0x81 : 0,45%
0x82 : 0,26%
0x83 : 0,21%
0x84 : 0,47%
0x85 : 0,32%
0x86 : 0,36%
0x87 : 0,36%
0x88 : 0,41%
0x89 : 0,39%
0x8A : 0,30%
0x8B : 0,51%
0x8C : 0,41%
0x8D : 0,41%
0x8E : 0,60%
0x8F : 0,34%
0x90 : 0,21%
0x91 : 0,41%
0x92 : 0,62%
0x93 : 0,28%
0x94 : 0,51%
0x95 : 0,34%
0x96 : 0,49%
0x97 : 0,32%
0x98 : 0,30%
0x99 : 0,30%
0x9A : 0,28%
0x9B : 0,43%
0x9C : 0,41%
0x9D : 0,36%
0x9E : 0,41%
0x9F : 0,41%
0xA0 : 0,26%
0xA1 : 0,34%
0xA2 : 0,39%
0xA3 : 0,47%
0xA4 : 0,15%
0xA5 : 0,39%
0xA6 : 0,41%
0xA7 : 0,34%
0xA8 : 0,24%
0xA9 : 0,45%
0xAA : 0,60%
0xAB : 0,34%
0xAC : 0,28%
0xAD : 0,45%
0xAE : 0,51%
0xAF : 0,41%
0xB0 : 0,45%
0xB1 : 0,49%
0xB2 : 0,36%
0xB3 : 0,30%
0xB4 : 0,43%
0xB5 : 0,32%
0xB6 : 0,41%
0xB7 : 0,24%
0xB8 : 0,51%
0xB9 : 0,30%
0xBA : 0,36%
0xBB : 0,39%
0xBC : 0,47%
0xBD : 0,28%
0xBE : 0,34%
0xBF : 0,39%
0xC0 : 0,51%
0xC1 : 0,34%
0xC2 : 0,58%
0xC3 : 0,49%
0xC4 : 0,51%
0xC5 : 0,30%
0xC6 : 0,36%
0xC7 : 0,54%
0xC8 : 0,51%
0xC9 : 0,45%
0xCA : 0,47%
0xCB : 0,34%
0xCC : 0,34%
0xCD : 0,30%
0xCE : 0,32%
0xCF : 0,28%
0xD0 : 0,39%
0xD1 : 0,34%
0xD2 : 0,49%
0xD3 : 0,30%
0xD4 : 0,32%
0xD5 : 0,43%
0xD6 : 0,28%
0xD7 : 0,58%
0xD8 : 0,51%
0xD9 : 0,26%
0xDA : 0,41%
0xDB : 0,41%
0xDC : 0,47%
0xDD : 0,30%
0xDE : 0,47%
0xDF : 0,56%
0xE0 : 0,36%
0xE1 : 0,41%
0xE2 : 0,34%
0xE3 : 0,41%
0xE4 : 0,32%
0xE5 : 0,39%
0xE6 : 0,49%
0xE7 : 0,43%
0xE8 : 0,45%
0xE9 : 0,34%
0xEA : 0,49%
0xEB : 0,39%
0xEC : 0,30%
0xED : 0,26%
0xEE : 0,24%
0xEF : 0,58%
0xF0 : 0,49%
0xF1 : 0,34%
0xF2 : 0,39%
0xF3 : 0,43%
0xF4 : 0,45%
0xF5 : 0,49%
0xF6 : 0,47%
0xF7 : 0,34%
0xF8 : 0,43%
0xF9 : 0,30%
0xFA : 0,36%
0xFB : 0,43%
0xFC : 0,39%
0xFD : 0,41%
0xFE : 0,54%
0xFF : 0,45%
22:54:55 : Data Statistics check for 006.13 cISD1 Statistics Started... Result: OK!
22:54:55 : Data Statistics check for 014.04 bootldr Statistics Started... Result: FAILED! (Bad size data)
22:54:55 : Hash check Started!
22:54:55 : Hash check for 009.02 ROS0 Hash Started... Result: FAILED!
Actual data: MD5 Hash: 16F2EA0BB439664A557A12D5E497B549
22:54:55 : Hash check for 009.05 ROS1 Hash Started... Result: FAILED!
Actual data: MD5 Hash: F12BEC7CA4216ABC8D98A7DE8C2C01C1
22:54:55 : ROS Version check Started!
22:54:55 : ROS Version check for ROS0 Started... Result: OK! (482.000)
22:54:55 : ROS Version check for ROS1 Started... Result: FAILED!
22:54:55 : Repetitions check Started!
22:54:55 : Repetitions check for Header Magic0 Repetitions Started... Result: FAILED!
Actual data:
Header Magic0 Repetitions Found at 2 offset(s): 0x10010 0x808010
Header Magic0 Repetitions Expected at: 0x10
22:54:55 : Repetitions check for asecure_loader Repetitions Started... Result: FAILED!
Actual data:
asecure_loader Repetitions Found at 1 offset(s): 0x800420
asecure_loader Repetitions Expected at: 0x420
22:54:55 : Repetitions check for eEID Repetitions Started... Result: FAILED!
Actual data:
eEID Repetitions Found at 1 offset(s): 0x800450
eEID Repetitions Expected at: 0x450
22:54:55 : Repetitions check for cISD Repetitions Started... Result: FAILED!
Actual data:
cISD Repetitions Found at 1 offset(s): 0x800480
cISD Repetitions Expected at: 0x480
22:54:55 : Repetitions check for cCSD Repetitions Started... Result: FAILED!
Actual data:
cCSD Repetitions Found at 1 offset(s): 0x8004B0
cCSD Repetitions Expected at: 0x4B0
22:54:55 : Repetitions check for trvk_prg0 Repetitions Started... Result: FAILED!
Actual data:
trvk_prg0 Repetitions Found at 1 offset(s): 0x8004E0
trvk_prg0 Repetitions Expected at: 0x4E0
22:54:55 : Repetitions check for trvk_prg1 Repetitions Started... Result: FAILED!
Actual data:
trvk_prg1 Repetitions Found at 1 offset(s): 0x800510
trvk_prg1 Repetitions Expected at: 0x510
22:54:55 : Repetitions check for trvk_pkg0 Repetitions Started... Result: FAILED!
Actual data:
trvk_pkg0 Repetitions Found at 1 offset(s): 0x800540
trvk_pkg0 Repetitions Expected at: 0x540
22:54:55 : Repetitions check for trvk_pkg1 Repetitions Started... Result: FAILED!
Actual data:
trvk_pkg1 Repetitions Found at 1 offset(s): 0x800570
trvk_pkg1 Repetitions Expected at: 0x570
22:54:55 : Repetitions check for ros0 Repetitions Started... Result: FAILED!
Actual data:
ros0 Repetitions Found at 1 offset(s): 0x8005A0
ros0 Repetitions Expected at: 0x5A0
22:54:56 : Repetitions check for ros1 Repetitions Started... Result: FAILED!
Actual data:
ros1 Repetitions Found at 1 offset(s): 0x8005D0
ros1 Repetitions Expected at: 0x5D0
22:54:56 : Repetitions check for cvtrm Repetitions Started... Result: FAILED!
Actual data:
cvtrm Repetitions Found at 1 offset(s): 0x800600
cvtrm Repetitions Expected at: 0x600
22:54:56 : Data Match check Started!
22:54:56 : Datamatch for: bootldr size Started Result: OK!
22:54:56 : Datamatch for: per console nonce Started Result: Failed!
metldr :
4D EF 98 9D E0 2D 12 BC 1F E8 B1 73
eid0 :
4D EF 98 9D E0 2D 12 BC 1F E8 B1 73
eid3 :
4D EF 98 9D E0 2D 12 BC 1F E8 B1 73
eid5 :
4D EF 98 9D E0 2D 12 BC 1F E8 B1 73
bootldr :
FF FF FF FF FF FF FF FF FF FF FF FF
22:54:56 : Datamatch for: CELL_EXTNOR_AREA Hash1 Started Result: OK!
22:54:56 : Datamatch for: CELL_EXTNOR_AREA Hash2 Started Result: OK!
22:54:56 : Datamatch for: metldr size Started Result: OK!
22:54:56 : Datamatch for: vtrm0 Started Result: OK!
22:54:56 : Datamatch for: vtrm1 Started Result: OK!
22:54:56 : Data Fill check Started!
22:54:56 : Data Fill check for: 001.01 First Region Header 0x00 Filled Area 0 Started! Result: OK!
22:54:56 : Data Fill check for: 001.03 First Region Header 0x00 Filled Area 1 Started! Result: OK!
22:54:56 : Data Fill check for: 002.03 Flash Format 0xFF Filled Area Started! Result: OK!
22:54:56 : Data Fill check for: 003.24 Flash Region Table 0x00 Filled Area Started! Result: OK!
22:54:56 : Data Fill check for: 004.08 asecure_loader 0x00 Filled Area Started! Result: FAILED!
The byte @ offset: 0x10014
has the value: 0xAC
Please check the data further down the line manually...
22:54:56 : Data Fill check for: 005.18 eEID Region 0xFF Filled Area Started! Result: OK!
22:54:56 : Data Fill check for: 006.05 cISD0 0xFF Filled Area Started! Result: OK!
22:54:56 : Data Fill check for: 006.09 cISD1 0xFF Filled Area 0 Started! Result: OK!
22:54:56 : Data Fill check for: 006.12 cISD1 0xFF Filled Area 1 Started! Result: OK!
22:54:56 : Data Fill check for: 006.15 cISD 0xFF Filled Area Started! Result: OK!
22:54:56 : Data Fill check for: 007.03 cCSD 0xFF Filled Area Started! Result: OK!
22:54:56 : Data Fill check for: 010.01 Pre cvtrm 0xFF Filled Area Started! Result: FAILED!
The byte @ offset: 0xEBFFF0
has the value: 0x00
Please check the data further down the line manually...
22:54:56 : Data Fill check for: 010.03 cvtrm0 0xFF Filled Area Started! Result: FAILED!
The byte @ offset: 0xEC0010
has the value: 0x00
Please check the data further down the line manually...
22:54:56 : Data Fill check for: 010.08 cvtrm1 0xFF Filled Area Started! Result: FAILED!
The byte @ offset: 0xEE0010
has the value: 0x00
Please check the data further down the line manually...
22:54:56 : Data Fill check for: 011.01 Second Region Header 0x00 Filled Area 0 Started! Result: OK!
22:54:56 : Data Fill check for: 011.04 Second Region Header 0x00 Filled Area 1 Started! Result: OK!
22:54:56 : Data Fill check for: 011.06 Second Region Header 0x00 Filled Area 2 Started! Result: OK!
22:54:56 : Data Fill check for: 011.08 Second Region Header 0x00 Filled Area 3 Started! Result: OK!
22:54:56 : Data Fill check for: 012.01 unreferenced area 0xFF Filled Started! Result: FAILED!
The byte @ offset: 0xF01000
has the value: 0x00
Please check the data further down the line manually...
22:54:56 : Data Fill check for: 013.02 CELL_EXTNOR_AREA 0x00 Filled Area 0 Started! Result: OK!
22:54:56 : Data Fill check for: 013.03 CELL_EXTNOR_AREA 0x00 Filled Area 1 Started! Result: OK!
22:54:56 : Data Fill check for: 013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 Started! Result: OK!
22:54:56 : Data Fill check for: 013.05 CELL_EXTNOR_AREA 0x00 Filled Area 3 Started! Result: OK!
22:54:56 : Data Fill check for: 013.06 CELL_EXTNOR_AREA 0xFF Filled Area 0 Started! Result: FAILED!
The byte @ offset: 0xF69C00
has the value: 0x00
Please check the data further down the line manually...
22:54:56 : Data Fill check for: 013.07 CELL_EXTNOR_AREA 0x00 Filled Area 5 Started! Result: OK!
22:54:56 : Data Fill check for: 013.08 CELL_EXTNOR_AREA 0x00 Filled Area 6 Started! Result: OK!
22:54:56 : Data Fill check for: 013.09 CELL_EXTNOR_AREA 0xFF Filled Area 1 Started! Result: FAILED!
The byte @ offset: 0xFA9C00
has the value: 0x00
Please check the data further down the line manually...
22:54:56 : Data Fill check for: 014.05 bootldr 0xFF Filled Area Started! Result: OK!
22:54:56 : SKU List check Started!
22:54:56 : No matching SKU model found!
22:54:56 : idps = 0006
22:54:56 : metldr0 = E8E0
22:54:56 : metldr1 = 0E8A
22:54:56 : metldrkey = 5E1F9CED758B6B94442BF031
22:54:56 : bootldr0 = FFFF
22:54:56 : bootldr1 = FFFF
22:54:56 : bootldrsize = 100030
22:54:56 : All checks (137 Checks) have been completed after 0 Second(s) and 815 Millisecond(s)
Bad count: 34 of 137 Tests Result: Failed!
 
Last edited:
I can't remember if that port is connected with sb. It may need 2 wires as unpopulated resistance. Anyway beside PCI connector on bottom of SB there are always 2 pads that are sb all ps3. Now apparently that dump is so pretty sure a permanent brick without a better dump.
 
Anyway beside PCI connector on bottom of SB there are always 2 pads that are sb all ps3. .
Can you provide a link for more details on where it is located?



just read the dump and it's ok here's the log
most likely there was a bad contact e3 flasher
So what should I do?

********************************************
PS3 Dump Checker v1.0 (Build: 503)
Check started: 04.06.2023 0:39:58
********************************************
0:39:58 : Reading image into memory and checking statistics...
0:39:58 : Statistics check skipped! (nothing to check)
0:39:58 : Binary check Started!
0:39:58 : Binary check for 001.02 First Region Header Magic Started... Result: OK!
0:39:58 : Binary check for 002.01 Flash Format String Started... Result: OK!
0:39:58 : Binary check for 002.02 Flash Format Version Started... Result: OK!
0:39:58 : Binary check for 003.01 Flash Region Table Header Started... Result: OK!
0:39:58 : Binary check for 003.02 asecure_loader Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.03 asecure_loader Name Started... Result: OK!
0:39:58 : Binary check for 003.04 eEID Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.05 eEID Name Started... Result: OK!
0:39:58 : Binary check for 003.06 cISD Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.07 cISD Name Started... Result: OK!
0:39:58 : Binary check for 003.08 cCSD Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.09 cCSD Name Started... Result: OK!
0:39:58 : Binary check for 003.10 trvk_prg0 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.11 trvk_prg0 Name Started... Result: OK!
0:39:58 : Binary check for 003.12 trvk_prg1 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.13 trvk_prg1 Name Started... Result: OK!
0:39:58 : Binary check for 003.14 trvk_pkg0 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.15 trvk_pkg0 Name Started... Result: OK!
0:39:58 : Binary check for 003.16 trvk_pkg1 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.17 trvk_pkg1 Name Started... Result: OK!
0:39:58 : Binary check for 003.18 ros0 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.19 ros0 Name Started... Result: OK!
0:39:58 : Binary check for 003.20 ros1 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.21 ros1 Name Started... Result: OK!
0:39:58 : Binary check for 003.22 cvtrm Offset - Length Started... Result: OK!
0:39:58 : Binary check for 003.23 cvtrm Name Started... Result: OK!
0:39:58 : Binary check for 004.01 asecure_loader Header Started... Result: OK!
0:39:58 : Binary check for 004.02 metldr Offset Started... Result: OK!
0:39:58 : Binary check for 004.03 metldr Length Started... Result: OK!
0:39:58 : Binary check for 004.04 metldr Name Started... Result: OK!
0:39:58 : Binary check for 004.05 metldr RevKey Started... Result: OK!
0:39:58 : Binary check for 004.06 metldr Binary Size Started... Result: OK!
0:39:58 : Binary check for 005.01 eEID Header Started... Result: OK!
0:39:58 : Binary check for 005.02 EID0 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 005.03 EID1 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 005.04 EID2 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 005.05 EID3 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 005.06 EID4 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 005.07 EID5 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 005.08 EID0 IDPS0 Started... Result: OK!
0:39:58 : Binary check for 005.09 EID0 IDPS1 Started... Result: OK!
0:39:58 : Binary check for 005.10 EID0 Static Started... Result: OK!
0:39:58 : Binary check for 005.11 EID2 BlockSize/Padding Started... Result: OK!
0:39:58 : Binary check for 005.12 EID3 Static0 Started... Result: OK!
0:39:58 : Binary check for 005.13 EID3 Static1 Started... Result: OK!
0:39:58 : Binary check for 005.14 EID3 Static2 Started... Result: OK!
0:39:58 : Binary check for 005.15 EID5 IDPS0 Started... Result: OK!
0:39:58 : Binary check for 005.16 EID5 IDPS1 Started... Result: OK!
0:39:58 : Binary check for 005.17 EID5 Static Started... Result: OK!
0:39:58 : Binary check for 006.01 cISD Header Started... Result: OK!
0:39:58 : Binary check for 006.02 cISD0 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 006.03 cISD1 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 006.04 cISD2 Offset - Length Started... Result: OK!
0:39:58 : Binary check for 006.06 cISD1 IDLog Header Started... Result: OK!
0:39:58 : Binary check for 006.07 cISD1 Semistatic 1 Started... Result: OK!
0:39:58 : Binary check for 006.08 cISD1 Semistatic 2 Started... Result: OK!
0:39:58 : Binary check for 006.10 cISD1 Static Started... Result: OK!
0:39:58 : Binary check for 006.11 cISD1 Semistatic 3 Started... Result: OK!
0:39:58 : Binary check for 006.14 cISD2 Started... Result: OK!
0:39:58 : Binary check for 007.01 cCSD Header Started... Result: OK!
0:39:58 : Binary check for 007.02 cCSD Entry Table Started... Result: OK!
0:39:58 : Binary check for 008.01 trvk_prg0 SCE Started... Result: OK!
0:39:58 : Binary check for 008.02 trvk_prg1 SCE Started... Result: OK!
0:39:58 : Binary check for 008.03 trvk_pkg0 SCE Started... Result: OK!
0:39:58 : Binary check for 008.04 trvk_pkg1 SCE Started... Result: OK!
0:39:58 : Binary check for 009.01 ROS0 Header Started... Result: OK!
0:39:58 : Binary check for 009.04 ROS1 Header Started... Result: OK!
0:39:58 : Binary check for 010.02 cvtrm0 Header Started... Result: OK!
0:39:58 : Binary check for 010.04 vtrm0 Magic Started... Result: OK!
0:39:58 : Binary check for 010.05 vtrm0 Reserved Entries Started... Result: OK!
0:39:58 : Binary check for 010.07 cvtrm1 Header Started... Result: OK!
0:39:58 : Binary check for 010.09 vtrm1 Magic Started... Result: OK!
0:39:58 : Binary check for 010.10 vtrm1 Reserved Entries Started... Result: OK!
0:39:58 : Binary check for 011.02 Second Region Header Magic Started... Result: OK!
0:39:58 : Binary check for 011.03 Second Region Header Count Started... Result: OK!
0:39:58 : Binary check for 011.05 Second Region Unknown Block 0 Started... Result: OK!
0:39:58 : Binary check for 011.07 Second Region Unknown Block 1 Started... Result: OK!
0:39:58 : Binary check for 013.01 CELL_EXTNOR_AREA Header Started... Result: OK!
0:39:58 : Binary check for 014.01 bootldr0 Started... Result: OK!
0:39:58 : Binary check for 014.02 bootldr1 Started... Result: OK!
0:39:58 : Binary check for 014.03 bootldr Rev key Started... Result: OK!
0:39:58 : Data check Started!
0:39:58 : Data Statistics check for 004.07 metldr Statistics Started... Result: OK!
0:39:58 : Data Statistics check for 005.19 eEID Statistics0 Started... Result: OK!
0:39:58 : Data Statistics check for 005.20 eEID Statistics1 Started... Result: OK!
0:39:58 : Data Statistics check for 006.13 cISD1 Statistics Started... Result: OK!
0:39:58 : Data Statistics check for 014.04 bootldr Statistics Started... Result: OK!
0:39:58 : Hash check Started!
0:39:58 : Hash check for 009.02 ROS0 Hash Started... Result: OK!
0:39:58 : Hash check for 009.05 ROS1 Hash Started... Result: OK!
0:39:58 : ROS Version check Started!
0:39:58 : ROS Version check for ROS0 Started... Result: OK! (482.000)
0:39:58 : ROS Version check for ROS1 Started... Result: OK! (481.000)
0:39:58 : Repetitions check Started!
0:39:59 : Repetitions check for Header Magic0 Repetitions Started... Result: OK!
0:39:59 : Repetitions check for asecure_loader Repetitions Started... Result: OK!
0:39:59 : Repetitions check for eEID Repetitions Started... Result: OK!
0:39:59 : Repetitions check for cISD Repetitions Started... Result: OK!
0:39:59 : Repetitions check for cCSD Repetitions Started... Result: OK!
0:39:59 : Repetitions check for trvk_prg0 Repetitions Started... Result: OK!
0:39:59 : Repetitions check for trvk_prg1 Repetitions Started... Result: OK!
0:39:59 : Repetitions check for trvk_pkg0 Repetitions Started... Result: OK!
0:39:59 : Repetitions check for trvk_pkg1 Repetitions Started... Result: OK!
0:39:59 : Repetitions check for ros0 Repetitions Started... Result: OK!
0:39:59 : Repetitions check for ros1 Repetitions Started... Result: OK!
0:39:59 : Repetitions check for cvtrm Repetitions Started... Result: OK!
0:39:59 : Data Match check Started!
0:39:59 : Datamatch for: bootldr size Started Result: OK!
0:39:59 : Datamatch for: per console nonce Started Result: OK!
0:39:59 : Datamatch for: CELL_EXTNOR_AREA Hash1 Started Result: OK!
0:39:59 : Datamatch for: CELL_EXTNOR_AREA Hash2 Started Result: OK!
0:39:59 : Datamatch for: metldr size Started Result: OK!
0:39:59 : Datamatch for: vtrm0 Started Result: OK!
0:39:59 : Datamatch for: vtrm1 Started Result: OK!
0:39:59 : All is OK!
0:39:59 : Data Fill check Started!
0:39:59 : Data Fill check for: 001.01 First Region Header 0x00 Filled Area 0 Started! Result: OK!
0:39:59 : Data Fill check for: 001.03 First Region Header 0x00 Filled Area 1 Started! Result: OK!
0:39:59 : Data Fill check for: 002.03 Flash Format 0xFF Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 003.24 Flash Region Table 0x00 Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 004.08 asecure_loader 0x00 Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 005.18 eEID Region 0xFF Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 006.05 cISD0 0xFF Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 006.09 cISD1 0xFF Filled Area 0 Started! Result: OK!
0:39:59 : Data Fill check for: 006.12 cISD1 0xFF Filled Area 1 Started! Result: OK!
0:39:59 : Data Fill check for: 006.15 cISD 0xFF Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 007.03 cCSD 0xFF Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 010.01 Pre cvtrm 0xFF Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 010.03 cvtrm0 0xFF Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 010.08 cvtrm1 0xFF Filled Area Started! Result: OK!
0:39:59 : Data Fill check for: 011.01 Second Region Header 0x00 Filled Area 0 Started! Result: OK!
0:39:59 : Data Fill check for: 011.04 Second Region Header 0x00 Filled Area 1 Started! Result: OK!
0:39:59 : Data Fill check for: 011.06 Second Region Header 0x00 Filled Area 2 Started! Result: OK!
0:39:59 : Data Fill check for: 011.08 Second Region Header 0x00 Filled Area 3 Started! Result: OK!
0:39:59 : Data Fill check for: 012.01 unreferenced area 0xFF Filled Started! Result: OK!
0:39:59 : Data Fill check for: 013.02 CELL_EXTNOR_AREA 0x00 Filled Area 0 Started! Result: OK!
0:39:59 : Data Fill check for: 013.03 CELL_EXTNOR_AREA 0x00 Filled Area 1 Started! Result: OK!
0:39:59 : Data Fill check for: 013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 Started! Result: OK!
0:39:59 : Data Fill check for: 013.05 CELL_EXTNOR_AREA 0x00 Filled Area 3 Started! Result: OK!
0:39:59 : Data Fill check for: 013.06 CELL_EXTNOR_AREA 0xFF Filled Area 0 Started! Result: OK!
0:39:59 : Data Fill check for: 013.07 CELL_EXTNOR_AREA 0x00 Filled Area 5 Started! Result: OK!
0:39:59 : Data Fill check for: 013.08 CELL_EXTNOR_AREA 0x00 Filled Area 6 Started! Result: OK!
0:39:59 : Data Fill check for: 013.09 CELL_EXTNOR_AREA 0xFF Filled Area 1 Started! Result: OK!
0:39:59 : Data Fill check for: 014.05 bootldr 0xFF Filled Area Started! Result: OK!
0:39:59 : SKU List check Started!
0:39:59 : SKU Model: CECHHxx (DIA-001)
0:39:59 : All checks (137 Checks) have been completed after 0 Second(s) and 910 Millisecond(s)
Tests done: 137 Result: Pass!
 

Similar threads

Back
Top