RIP-Felix
Senior Member
Sure, I'll bite. I am curious to take a stab at it.
PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
Dariush Aghaee
Member
Hi every body
I managed to get a BC PS3 CECHA12 in working state that factory seal is not broken. the first thing I did to this device was a syscon errlog dump (just a bunch of 801001) so I upload the code here to see what your opinion is and any suggestions
Firmware Version: 4.88 (build 50731)
Platform ID: Cok14
Product Code: 00 8E
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 1242, Shutdown Count: 1118
Runtime: 81 Days, 13 Hours, 44 Minutes, 15 Seconds
Error Log
01: A0801001 Mon Mar 23 14:05:01 2020
02: A0801001 Mon Mar 23 14:02:10 2020
03: A0801001 Mon Mar 23 13:57:47 2020
04: A0801001 Thu Apr 18 17:48:02 2019
05: A0801001 Sun Apr 2 02:06:49 2017
06: A0801001 Thu Oct 6 13:41:34 2016
07: A0801001 Thu Sep 8 16:19:50 2016
08: A0801001 Wed Jul 27 23:16:29 2016
09: A0801001 Sun Feb 28 23:33:06 2016
10: A0801001 Sun Feb 28 23:23:32 2016
11: A0801001 Wed Feb 24 15:42:44 2016
12: A0801001 Wed Feb 24 15:17:12 2016
13: A0801001 Mon Feb 1 22:19:52 2016
14: A0801001 Wed Nov 11 17:54:54 2015
15: A0801001 Tue Dec 2 10:41:37 2014
16: A0801001 Tue Jul 22 17:07:42 2014
17: A0801001 Sun Jun 8 10:34:01 2014
18: A0801001 Thu Nov 28 19:06:56 2013
19: A0801004 Wed Oct 23 17:21:13 2013
20: A0801001 Sat Mar 2 16:41:30 2013
21: A0801001 Thu Nov 3 15:06:42 2011
22: A0801001 Wed Aug 10 15:32:34 2011
23: A0801001 Tue Aug 9 12:28:53 2011
24: A0801001 Thu Jul 28 21:24:31 2011
25: A0801001 Sun Jul 10 17:18:35 2011
26: A0801001 Sun Jul 10 10:31:36 2011
27: A0801001 Wed Feb 16 20:00:45 2011
28: A0801001 Wed Feb 16 15:21:38 2011
29: A0801001 Sun Feb 13 14:13:09 2011
30: A0801001 Sun Feb 13 14:10:27 2011
31: A0801001 Sun Feb 13 13:56:25 2011
32: FFFFFFFF Tue Feb 8 19:33:39 2011
thank you.
I managed to get a BC PS3 CECHA12 in working state that factory seal is not broken. the first thing I did to this device was a syscon errlog dump (just a bunch of 801001) so I upload the code here to see what your opinion is and any suggestions
Firmware Version: 4.88 (build 50731)
Platform ID: Cok14
Product Code: 00 8E
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 1242, Shutdown Count: 1118
Runtime: 81 Days, 13 Hours, 44 Minutes, 15 Seconds
Error Log
01: A0801001 Mon Mar 23 14:05:01 2020
02: A0801001 Mon Mar 23 14:02:10 2020
03: A0801001 Mon Mar 23 13:57:47 2020
04: A0801001 Thu Apr 18 17:48:02 2019
05: A0801001 Sun Apr 2 02:06:49 2017
06: A0801001 Thu Oct 6 13:41:34 2016
07: A0801001 Thu Sep 8 16:19:50 2016
08: A0801001 Wed Jul 27 23:16:29 2016
09: A0801001 Sun Feb 28 23:33:06 2016
10: A0801001 Sun Feb 28 23:23:32 2016
11: A0801001 Wed Feb 24 15:42:44 2016
12: A0801001 Wed Feb 24 15:17:12 2016
13: A0801001 Mon Feb 1 22:19:52 2016
14: A0801001 Wed Nov 11 17:54:54 2015
15: A0801001 Tue Dec 2 10:41:37 2014
16: A0801001 Tue Jul 22 17:07:42 2014
17: A0801001 Sun Jun 8 10:34:01 2014
18: A0801001 Thu Nov 28 19:06:56 2013
19: A0801004 Wed Oct 23 17:21:13 2013
20: A0801001 Sat Mar 2 16:41:30 2013
21: A0801001 Thu Nov 3 15:06:42 2011
22: A0801001 Wed Aug 10 15:32:34 2011
23: A0801001 Tue Aug 9 12:28:53 2011
24: A0801001 Thu Jul 28 21:24:31 2011
25: A0801001 Sun Jul 10 17:18:35 2011
26: A0801001 Sun Jul 10 10:31:36 2011
27: A0801001 Wed Feb 16 20:00:45 2011
28: A0801001 Wed Feb 16 15:21:38 2011
29: A0801001 Sun Feb 13 14:13:09 2011
30: A0801001 Sun Feb 13 14:10:27 2011
31: A0801001 Sun Feb 13 13:56:25 2011
32: FFFFFFFF Tue Feb 8 19:33:39 2011
thank you.
Last edited:
Dariush Aghaee
Member
Thank you for your reply. I tested TLOU, the console ran normally and no YLOD happened. Temps were fine but I'm not going to stress it so much before a nice clean and a safe delid. Considering the less amount of working time of this console, does the difference between turn ON/OFF counts prove that 801001s are all related to force shutdowns?
Could you please explain more about the dates?
there is also a 801004. Is it related to PSU?
Thanks again.
RIP-Felix
Senior Member
So if' it's stable in intense games, don't sweat it. The errors are probably a non-issue. Some local power grids are pretty spotty, so This is a pretty normal errorlog to see in a perfectly working console. It would be better to have no errors, but that's not likely for something this old.
So the 1004 can happen when the PWR is interrupted while the console was on. 1001 and 1004 can both happen when you flip the rocker at the back without gracefully shutting down first, like a power outage or disruption. It's also possible the PSU is going out. If you are opening it anyway, check if it's a ZSSR. They are less efficient anyway, so maybe consider replacing it with an APS-226 while you're in there.
Yours has a pretty close startup/shutdown ratio, so the 81 days of use should be accurate. Only 1 out of 10 times it wasn't shutdown properly.
Arcadesnafu
Forum Noob
No service manual how do u find IC5001?
Rozus
Member
Hello, got a bit of an odd error I've not seen before. This is from a PS3 slim CECH-2003, the error code it keeps spitting out in the syscon is A0092114.
I have attached the bringup output and the error log. Any help would be appreciated!
I have attached the bringup output and the error log. Any help would be appreciated!
Attachments
Hello,
today I had free time and looked at the motherboard again, I compared with another working one and I don't see any differences.
With a hardware flasher, is it possible to install official firmware bypassing the error?
Error_404
Forum Noob
Any insights? Wish there was a GLOD thread but this seems to be the most relevant area for this to go.
RIP-Felix
Senior Member
This is strange. It says it's running a prerelease bootloader version (0.9.5). A build ID that's not on the wiki too.#4
It should be a GLOD if it's running a system FW lower than 2.30, or there about, which is when the 65nm got support. @vyktormvmpay25 ran into this with @mathieulh board. So what I don't understand is how you managed to get it working at all? It says it was sucessful and had 7 days of use at that point. It has 9 days of use now.
How can it have a pre-release bootloader on it? One with a build ID not on the dev wiki? I've ordered a FlashcatUSB Xport and TSOP-48 NAND programmer. I'll try dumping the NAND and flashing with FW 3.55 to see if that fixes the GLOD, but i don't get how this console ever worked with a 65nm in the first place if it was a prototype with low firmware.
DeadEnd
Senior Member
Seems like it's on devwiki after all https://www.psdevwiki.com/ps3/Talk:Flash:bootldr
From M4j0r's words Sony considers everything >= 0.93 < 1.00 as 1.00 on retail platforms.
I update all consoles to the latest official firmware release prior to stress testing, and the customer had it for 2 or 3 months before he started having problems.
I don't mess around with custom firmware on these beyond knowing enough to remarry drives and remove custom firmware, so anything exotic that happened to it from that direction would have been the customer's doing.
(shrug emoticon)
RIP-Felix
Senior Member
Yeah, I added a disclaimer to the tutorial about that. To be safe 3.55 should be considered the min FW for both. Tenchnically the 65nm should work below that (possibly 2.30), but we're not 100% sure how low and if that applies to every model revision. But 3.55 is a safe assumption and has been tested.
The there is a possibility the customer attempted to install an early FW. If they did the only way to recover from the GLOD is a FSM jig or HW flasher.
Perhaps you would like to try playing with u COK-001 board that YLODs only under heavy load (example, sewers in TLOU). Would make an interesting example for this thread and the other nec/tokin thread
RIP-Felix
Senior Member
PS3 #16 - Frankie Down!
(Part 1...)
(Part 1...)
I took him up on that offer and here it is on the bench...
He just sent me the MB, nothing else. My first impressions were this is the cleanest board I've ever seen. Board is immaculate and shiny. On the bench today we have a COK-001 with a 65nm CXD2982 RSX previously installed by @squeept. This was a warranty return that came back to him only a few months later. Squeept prides himself on quality. His repairs are of the top tier you can find, so I have little doubt the mod was done right! Here's the inspection sheet from this motherboard before it left the shop...
First up was to dump the errorlog. It's always nice when the previous guy already enabled internal SYSCON access so you can AUTH strait in...
Code:
Microsoft Windows [Version 10.0.19044.1826]
(c) Microsoft Corporation. All rights reserved.
C:\Users\HTPC\Desktop\PS3\SYSCON>ps3_syscon_uart_script.py COM7 CXRF
>$ AUTH
Auth successful
>$ errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0x288339d2 2021/07/15 18:24:18
ofst[ 8]:err_code:0xa0801001, clock:0x28833a17 2021/07/15 18:25:27
ofst[ 12]:err_code:0xa0801001, clock:0x28833a95 2021/07/15 18:27:33
ofst[ 16]:err_code:0xa0801001, clock:0x28833c39 2021/07/15 18:34:33
ofst[ 20]:err_code:0xa0801001, clock:0x28833d74 2021/07/15 18:39:48
ofst[ 24]:err_code:0xa0801001, clock:0x28833dc8 2021/07/15 18:41:12
ofst[ 28]:err_code:0xa0801001, clock:0x28833e38 2021/07/15 18:43:04
ofst[ 32]:err_code:0xa0801001, clock:0x299c2fe1 2022/02/13 21:08:49
ofst[ 36]:err_code:0xa0801001, clock:0x299c3023 2022/02/13 21:09:55
ofst[ 40]:err_code:0xa0801001, clock:0x299c30e4 2022/02/13 21:13:08
ofst[ 44]:err_code:0xa0801001, clock:0x299c312d 2022/02/13 21:14:21
ofst[ 48]:err_code:0xa0801001, clock:0x299c3211 2022/02/13 21:18:09
ofst[ 52]:err_code:0xa0801001, clock:0x299c3238 2022/02/13 21:18:48
ofst[ 56]:err_code:0xa0801001, clock:0x29d3a3d4 2022/03/27 22:38:12
ofst[ 60]:err_code:0xa0801001, clock:0x29d3ab9f 2022/03/27 23:11:27
ofst[ 64]:err_code:0xa0801001, clock:0x29da8c96 2022/04/02 04:24:54
ofst[ 68]:err_code:0xa0801200, clock:0x0b488688 2005/12/31 00:00:08
ofst[ 72]:err_code:0xa0801001, clock:0xffffffff
ofst[ 76]:err_code:0xa0801001, clock:0x0b488845 2005/12/31 00:07:33
ofst[ 80]:err_code:0xa0801001, clock:0x0b4886d9 2005/12/31 00:01:29
ofst[ 84]:err_code:0xa0801001, clock:0x0b488688 2005/12/31 00:00:08
ofst[ 88]:err_code:0xa0801001, clock:0x0b4886c2 2005/12/31 00:01:06
ofst[ 92]:err_code:0xa0801001, clock:0x0b48872f 2005/12/31 00:02:55
ofst[ 96]:err_code:0xa0801701, clock:0x0bb4d217 2006/03/23 03:27:19
ofst[100]:err_code:0xa0801601, clock:0x0bb4d217 2006/03/23 03:27:19
ofst[104]:err_code:0xa0801701, clock:0x0bb51c20 2006/03/23 08:43:12
ofst[108]:err_code:0xa0801601, clock:0x0bb51c20 2006/03/23 08:43:12
ofst[112]:err_code:0xa0801001, clock:0x27f627d1 2021/03/30 18:17:53
ofst[116]:err_code:0xa0801001, clock:0x27f6284a 2021/03/30 18:19:54
ofst[120]:err_code:0xa0801001, clock:0x27f628bf 2021/03/30 18:21:51
ofst[124]:err_code:0xa0801001, clock:0x27f6296d 2021/03/30 18:24:45
ofst[ 0]:err_code:0xa0801001, clock:0xffffffff
[mullion]$
>$ becount
becount
Bringup : 256 times
Shutdown: 164 times
Power-on: 9day 20hour 46min 06sec
[mullion]$
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
>$ errlog
errlog
ofst[ 0]:err_code:0xffffffff, clock:0xffffffff
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
[mullion]$
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[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:0x20e2
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
Copyright(C) 2006 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_DUMP000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PTC_DUMP000000000a190a6f000000000ab10b0b000000000acd0b27000000000ab60b0c000000000a0e0a65000000000a250a76000000000a190a6f000000000ab60b130000000000000000000000000aa30af8000000000a990af10000000009e40a36000000000a950af10000000009eb0a450000000009dc0a3a0000000009e90a41000000000aa50afe00000000000000000000000009f50a550000000009e50a3a000000000a770ad30000000009d10a2c0000000009ce0a260000000009d60a2a0000000009f40a52000000000a670abb0000000000000000000000000a530ab1000000000a650ab6000000000a080a59000000000a880adb0000000009f00a47000000000a830ae1000000000a790ad3000000000a930ae900000000000000000000000009f60a4e000000000a6c0ac7000000000a3c0a950000000009cb0a22000000000a530ab3000000000a560ab30000000009e90a38000000000a690ac30000000000000000000000000a370a92000000000a290a8a0000000009ea0a3f000000000a490aa70000000009c70a190000000009e00a3a0000000009c70a1b0000000009b60a0b0000000000000000000000000a1e0a710000000009f10a4a000000000ab30b03000000000aa30af20000000009d70a2e0000000009e60a380000000000000000000000000aaa0b020000000000000000000000000ac20b11000000000a9a0aed000000000a100a66000000000ab90b0a000000000a260a83000000000a0b0a6c000000000ab80b0c000000000ad10b1f0000000000000000
MIC_DUMP0000000000000000000000000000000000000000000000003200000000000000000000000000000000000000000000000000000fffffff8000000000000120000000000000100000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b87000000000000140002000000000006804000000000000100000000000000c8000000000000000000000000000000000010000000000000000000000000001b87000000000000140002000000000004810000000000000100000000000000c800000000000000000000000000000000001000000000000000000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000061101700000000040000000000000007cfe000000000000e1c0000000000000000000000000000000000000000000000000fd400000000000000280000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000130000000000000000
XIO_DUMP00010002000900000211000003810000000000180000000000000212000710e109410000000f000f00200000a080000800010008000008540c540000000000010bad000000000000000000000000000c000c000c000c00580058005800580000000000000000007f007f007f007f4438443
>$
00000000000000404000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000090f00000000000000a7e2000000000000000000000000000000003531000000000000003735000000000000000000000000000000000000000000000000003c3c000000000000003c3c00000000000000313100000000000000505000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000373700000000000000000100000000000000000000000000000000404000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000090f0000000000000078bb000000000000000000000000000000003f2d000000000000003b33000000000000000000000000000000000000000000000000003c3c000000000000003c3c00000000000000313100000000000000505000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000373700000000000000
IOW_DUMP15c6164003a5041e15cb163f03aa042115ca163d03a8042015c9163f03a7041d15c7163e03a6041a15c3163c03a3041b15c9164203a5041e15c8163e03a6041b15ce164203be043415cb164303ab042215cb163e03ad042215c5163e03a6041f15c7163b03aa041e15c9163d03a3042015c3163903a9041b15ca164203a6041c15c9163703a9041615d5163803be042815ca164003a0041815c3163f03a5041a15c6163e03a7041a15ca163d03a9041f15c7163d03a9041a15c6164203a5041715c8164203a2041815ca163f03a9041915d0164003c2043115c4163b03a4041915bf163703a3041815c7164003a7041b15c6164003a5041f15c31639039f041715bd163703a1041a15c0163b03a0041715c2163a03a4041715ce163103c1042815c7164003a5041915ca164103a5041b15cb163b03a9041a15c7163b03aa042115c9164103a8041f15c21639039e041515c7163e03a3041815c6163903a1041515d2163a03c3042d15c0163703a3041715c7163a03a6041a15c2163a03a4041a15c0163903a1041915c116390399041215bf1637039c041515c0163a039b041515c4163a03a2041815d0163803c4042b15ca163e03b2042915ca163c03b3042515cd163903b6042915cd163a03ba042b15c6163b03af042915ca163d03aa041e000000ff000000ff15cc163c03b6042a000000ff000000ff15c6163803b3042715ca163203ba042715c4163703ad042415cb163603b6042815c3163503b0042715c5163603ae042315c7163003b3041f15c7163403aa0419000000ff000000ff
[SERV NVS] WRITE CMD
[mullion]$
>$ powerstate
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]$
>$ tmp 0
tmp 0
TZone No:00
1st BE Primary Temperature:62.82(0x3ed4)
[mullion]$
>$ tmp 1
tmp 1
TZone No:01
RSX Primary Temperature:33.00(0x2100)
[mullion]$
>$Errors are as squeept described. Mainly 1001. One 1200 (CPU overheat), I assume from HS not being on during first test. Probably expected a YLOD, not a GLOD. There is a 1701/1601 in there too. All of these occurred at step# 80 (power on state), so the console doesn't have any power related issue that prevent it from making POST.
Becount is super low! Only 9 days of use.
After saving the log I cleared it and used the bringup command to start the console. It compleated Power On Sequencing and began the FW sequence that starts the Boot Loader. There were no errors that triggered a YLOD or that would indicate there's an issue with HW. The only one that I found confusing was the "[ERROR]: 0xb0002002 (FATAL) XDR Link not initilized."
It then proceeded to Dump the ITC, PTC, MIC, and XIO. I do not know how to make sense of the specific information they might contain. Perhaps someone more familiar with the bootloader can shed some light on whether or not this is useful.
Powerstate says everything is powered and available (Except PCI, which is only enabled when you load a PS2 game). Temps suggest the CPU is on and the RSX is idle.
Beyond that the only other interesting this I learned from the SYSCON "Boot Loader SE Version 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)." According to the PS3 Dev Wiki, this version (0.9.5) is not on CEX (Retail) models and this particular Build ID (1634) isn't listed there. But @DeadEnd did find it here.
Ok, so we have a console that Squeept updated before selling. Then it comes back to him running a pre-release Bootloader version?!
I attempted a SB UART, but couldn't get anything to output. I think it's not getting far enough into the bootloader for the SB to output anything, but I'm not %100 sure I did it correctly. This was the first time I've attempted the SB UART.
The only thing I can think of is the customer downgraded the console to a system firmware that is incompatible with the 65nm RSX. Anything below 2.15 - 2.30 (Not sure exactly) will cause a GLOD. @vyktormvmpay25 discovered this in a MB he Frankied for @mathieulh. He was able to get into Safe mode, but couldn't see anything.
I tried to get into safe mode, but it doesn't trigger. The procedure just turns the console off every time. No 1-beep, 2-beep, etc. However, safe mode isn't present on early system firmware, so if the customer did downgrade that could be normal. I'm not 100% sure that's what's going on here, but I have suspicions.
Can anyone confirm that the "Boot Loader Version" is updated when "System Firmware" is? Would the bootloder being at 0.9.5 confirm that they must have downgraded the FW below 2.30?
I've ordered a FlashcatUSB xPort and a TSOP-48 NAND Programmer.
@vyktormvmpay25 @sandungas @M4j0r you guy's would have a better idea of how I should proceed. I think dumping the NAND and then attempting to upgrade to 3.55 would be the first place to start, but if you have any other suggestion I'm all ears.
Last edited:
Arcadesnafu
Forum Noob
Hey Felix, sorry to bother u during your busy day. May I know if is it possible for me to dm u somewhere to seek your direct help regarding ps3 repairs? (Thanks)
M4j0r
Developer
That means either the XDR RAM can't be initialized or it can't be run at full speed. You can get that error if the clock sources are configured wrong (e.g. from wrong CELL overclocking) or not working.
The Syscon log is from lv0ldr which loads lv0. lv0 will then output over Syscon UART and South Bridge UART. lv0ldr Version 0.9.5 is not pre-release and bound to the console at the factory.
The firmware isn't even loaded at that stage, lv0ldr would tell you if lv0 was loaded - it wasn't (since the RAM has to be initialized for that).
vyktormvmpay25
Senior Member
Idk if you see those M4j0r, it was 3,15 I've dumped and installed 3554drex in fsm, once software installed and got XMB in fsm I just used that level 2 file to get out of fsm then up to 4842 drex and all fine. I found sur board with first 40nm rsx is on 3,20 min fw but I'll say stages of 355 is most compatible with fsm patches to use fsm old ways.
RIP-Felix
Senior Member
Good to know.
So what should I try next? Is there anything besides replacing ram modules and hoping one crapped out? Or should I still try flashing the NAND?
Similar threads
-
-
PS3 CECHA00 with several SYSCON errors (3004, 1001,1002, 2120,3011)
- Started by LSL
- Replies: 7
-
PS3 Interesting PS3 Errors (1802, 1701, 1601) and Capacitor Replacement- Started by Cheshire UK
- Replies: 2
-