Kostaslgr7
Forum Noob
What's your suggestion nowadays for nand writing?
PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
vyktormvmpay25
Senior Member
I have another programmer which is to expensive for this area tnm5000, is getting obsolete as well but still good for Windows 10.
Anyway focus on E3 with linker and Windows 7. You have this nor model=ver001.
On that teensy should work if you fallow schematic and understand to separate 5v from 3v3. Not only from those pads but somewhere near ic they still have 5v line short with 3v3. Just check between 5v and 3v3 pad now and see if there is any short even if pad is cutted.
Oh by the way if flash is corrupted won't see any SB log. It will stay open but SB won't show nothing in putty.
Did few tests, there was only one case here when I've seen in forum wrong flash.
It will stop after PS4 ok then that 00000000 ok nothing more. No further message with "sb debugging connected".
Anyway focus on E3 with linker and Windows 7. You have this nor model=ver001.
On that teensy should work if you fallow schematic and understand to separate 5v from 3v3. Not only from those pads but somewhere near ic they still have 5v line short with 3v3. Just check between 5v and 3v3 pad now and see if there is any short even if pad is cutted.
Oh by the way if flash is corrupted won't see any SB log. It will stay open but SB won't show nothing in putty.
Did few tests, there was only one case here when I've seen in forum wrong flash.
It will stop after PS4 ok then that 00000000 ok nothing more. No further message with "sb debugging connected".
Last edited:
Kostaslgr7
Forum Noob
Okay, what do you suggest I do now? I don't want to pull off rsx and reball yet, it's a bit risky. Again thank you for all your help.
vyktormvmpay25
Senior Member
All depends on you now, it is your opinion to go further or follow any other users advice.
As last simple test we all know nand/nor corruption is like glod without any video or sync controller . You can insert his hdd and connect controller, with cable sync should stay paired with first position red led on. In same time follow on screen SB log from putty and post as example. I have one kte001 that I'll record and refer here on forum as working example with and without hdd on parallel pc log în putty. From my point of view you are quite out of opinions, again I neither don't like to "jump reball all " as most people say about me in the world but not because I like, because it is working fine with that. Well at least worked well until I've found this special glod condition which is good signs of obsolete ps3 /not maintained on time units started to kill rsx in this unknown way.
As last simple test we all know nand/nor corruption is like glod without any video or sync controller . You can insert his hdd and connect controller, with cable sync should stay paired with first position red led on. In same time follow on screen SB log from putty and post as example. I have one kte001 that I'll record and refer here on forum as working example with and without hdd on parallel pc log în putty. From my point of view you are quite out of opinions, again I neither don't like to "jump reball all " as most people say about me in the world but not because I like, because it is working fine with that. Well at least worked well until I've found this special glod condition which is good signs of obsolete ps3 /not maintained on time units started to kill rsx in this unknown way.
Kostaslgr7
Forum Noob
Hello, not sure exactly how but having controller connected by USB i get this different result in SB uart(hdd attached before supplying power to console)
Boot Loader SE Version 4.8.6 (Build ID: 5353,50715, Build Date: 2020-01-30_11:2 3:58)
SDK Version: 486.000
Copyright(C) 2020 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:11S DD1.0, SB:SX1.2
Cell OS SDK4.8.6 000 (release build: r50715 2020_01_30_110000)
Copyright 2020 Sony Computer Entertainment Inc.
revision: 50702
date: Thu Jan 30 11:25:44 JST 2020
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size: 12MB+640KB (heap:3492KB page pool:4736KB)
lv2(0): user memory size: 237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.8.6
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50715
lv2(2): build date: 2020/01/30 11:30:24
lv2(2): processor: Broadband Engine Ver 0x0000 Rev 0x1000
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx: rsx65 a06 500/650 vpe:ff shd:6f [AP0011327:1:1:a:b:13:2:5:1][ 3d:0:2:0:1:2:0][2:1:0]
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : ........... Failed (error code:0x800100 2b)
lv2(2):
lv2(2): ###
lv2(2): ### Vflash recovery mode
lv2(2): ###
lv2(2):
lv2(2): creating the vflash recover process (emergency program) : OK
lv2(2): probe hdd
lv2(2): (v)HDD found.
lv2(2): probe hdd done
lv2(2): vflash is enabled. search system region.
lv2(2): search system region
lv2(2): device_id = 0x101000000000007, system_region_id = 0x1
lv2(2): sys_storage_get_region_acl() failure = 0x6
lv2(2): system region not found(mode = 0).
lv2(2): search system region done.
lv2(2): search flash regions
lv2(2): /dev_flash is broken. need format(ret = 0x8001002b)
lv2(2): sys_storage_get_device_info() failure = 0x80010002
lv2(2): system region size is invalid
lv2(2): not found flash regions.
lv2(2): vflash region is broken. force to create system region.
lv2(2): search normal region
lv2(2): storage region not found.
lv2(2): normal region 1 not found.
lv2(2): search normal region done.
lv2(2): search normal region
lv2(2): storage region not found.
lv2(2): normal region 2 not found.
lv2(2): search normal region done.
SDK Version: 486.000
Copyright(C) 2020 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:11S DD1.0, SB:SX1.2
Cell OS SDK4.8.6 000 (release build: r50715 2020_01_30_110000)
Copyright 2020 Sony Computer Entertainment Inc.
revision: 50702
date: Thu Jan 30 11:25:44 JST 2020
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size: 12MB+640KB (heap:3492KB page pool:4736KB)
lv2(0): user memory size: 237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.8.6
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50715
lv2(2): build date: 2020/01/30 11:30:24
lv2(2): processor: Broadband Engine Ver 0x0000 Rev 0x1000
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx: rsx65 a06 500/650 vpe:ff shd:6f [AP0011327:1:1:a:b:13:2:5:1][ 3d:0:2:0:1:2:0][2:1:0]
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : ........... Failed (error code:0x800100 2b)
lv2(2):
lv2(2): ###
lv2(2): ### Vflash recovery mode
lv2(2): ###
lv2(2):
lv2(2): creating the vflash recover process (emergency program) : OK
lv2(2): probe hdd
lv2(2): (v)HDD found.
lv2(2): probe hdd done
lv2(2): vflash is enabled. search system region.
lv2(2): search system region
lv2(2): device_id = 0x101000000000007, system_region_id = 0x1
lv2(2): sys_storage_get_region_acl() failure = 0x6
lv2(2): system region not found(mode = 0).
lv2(2): search system region done.
lv2(2): search flash regions
lv2(2): /dev_flash is broken. need format(ret = 0x8001002b)
lv2(2): sys_storage_get_device_info() failure = 0x80010002
lv2(2): system region size is invalid
lv2(2): not found flash regions.
lv2(2): vflash region is broken. force to create system region.
lv2(2): search normal region
lv2(2): storage region not found.
lv2(2): normal region 1 not found.
lv2(2): search normal region done.
lv2(2): search normal region
lv2(2): storage region not found.
lv2(2): normal region 2 not found.
lv2(2): search normal region done.
vyktormvmpay25
Senior Member
Is it controller led 1 always open or it is blinking if you push PS (home button to controller)?
Not worth reball with lower power rework station. You will need at least 2000 watts power on bottom and 400 watts on top won't make any difference if is ir or hot air for top . Rather let someone else to handle.
You can follow few Felix advice about how to set this thermal profile. He posted some of his setup.
Not worth reball with lower power rework station. You will need at least 2000 watts power on bottom and 400 watts on top won't make any difference if is ir or hot air for top . Rather let someone else to handle.
You can follow few Felix advice about how to set this thermal profile. He posted some of his setup.
Kostaslgr7
Forum Noob
After SB uart loads up to "Safe mode", controller is charging then if I press ps button led 1 solid.
vyktormvmpay25
Senior Member
In my opinion rsx faulty, wait more advices . I really don't know what else to suggest.
Kostaslgr7
Forum Noob
Okay then, waiting for advice, I'll attemp the rsx reball you suggest if nothing else comes up, just thought to let you know I just dumped the nor and it passed all 137 checks in Swizzly's dump checker
Attachments
Shawn Shakir
Member
Attempted a Frankenstein on a COK001 motherboard today. Everything seems to have went well but when I powered on, got YLOD, pulled syscon and got the following
>$ ERRLOG GET 00
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 06
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 07
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 08
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 09
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 0A
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 0B
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 0C
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 0D
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 0E
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 0F
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 10
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 11
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 12
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 13
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 14
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 15
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 16
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 17
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 18
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 19
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 1A
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 1B
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 1C
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 1D
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 1E
00000000 A0902120 FFFFFFFF
Any idea where I should start?
>$ ERRLOG GET 00
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 06
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 07
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 08
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 09
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 0A
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 0B
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 0C
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 0D
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 0E
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 0F
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 10
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 11
00000000 A0003001 FFFFFFFF
>$ ERRLOG GET 12
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 13
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 14
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 15
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 16
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 17
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 18
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 19
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 1A
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 1B
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 1C
00000000 A0902120 FFFFFFFF
>$ ERRLOG GET 1D
00000000 A0232102 FFFFFFFF
>$ ERRLOG GET 1E
00000000 A0902120 FFFFFFFF
Any idea where I should start?
vyktormvmpay25
Senior Member
Fuse 6301? 12 v line test for short/missing ? Hdmi area or short power for ic/dead ic. What errors were before attempting to fix this?
Also you have to log onto CXRF and clear errlog, run bringup up with unit semiassblbed and then post again errlog after power on.
Remember if rsx is not working should come first thing 3034 error and something 44xx.bad setup of modchip rsx always 4002.
Last edited:
RIP-Felix
Senior Member
PS3 #12 - GLOD E01
(Inspection, Teardown, and Diagnosis)
(Inspection, Teardown, and Diagnosis)
Initial SYSCON reading = becount shows over 512 days of use, 12,291 Hours of uptime, with over 1000 sessions that weren't logged. This is one of the most used consoles I have ever seen. Errorlog shows the console had experienced a YLOD (BGA/bump = 3034/4412) defect previously. I'm guessing the console was reflowed or reballed professionally, because now it has a GLOD.
Code:
Auth successful
>$ becount
becount
Bringup : 3615 times
Shutdown: 2435 times
Power-on: 512day 03hour 31min 07sec
[mullion]$
>$ errlog
errlog
ofst[108]:err_code:0xffffffff, clock:0x18bb160b 2013/02/23 05:54:19
ofst[112]:err_code:0xa0801701, clock:0x1946e078 2013/06/09 06:43:04
ofst[116]:err_code:0xa0801601, clock:0x1946e078 2013/06/09 06:43:04
ofst[120]:err_code:0xa0404412, clock:0x19496d29 2013/06/11 05:07:53
ofst[124]:err_code:0xa0403034, clock:0x19496d29 2013/06/11 05:07:53
ofst[ 0]:err_code:0xa0404412, clock:0x19496d40 2013/06/11 05:08:16
ofst[ 4]:err_code:0xa0403034, clock:0x19496d40 2013/06/11 05:08:16
ofst[ 8]:err_code:0xa0801701, clock:0x194be6c6 2013/06/13 02:11:18
ofst[ 12]:err_code:0xa0801601, clock:0x194be6c6 2013/06/13 02:11:18
ofst[ 16]:err_code:0xa0404412, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff
ofst[ 28]:err_code:0xa0404412, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0404412, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0404412, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0801701, clock:0x0b48869c 2005/12/31 00:00:28
ofst[ 56]:err_code:0xa0801601, clock:0x0b48869c 2005/12/31 00:00:28
ofst[ 60]:err_code:0xa0404412, clock:0x0b4888cd 2005/12/31 00:09:49
ofst[ 64]:err_code:0xa0403034, clock:0x0b4888cd 2005/12/31 00:09:49
ofst[ 68]:err_code:0xa0404412, clock:0x0b97ec4c 2006/03/01 05:23:24
ofst[ 72]:err_code:0xa0403034, clock:0x0b97ec4c 2006/03/01 05:23:24
ofst[ 76]:err_code:0xa0404412, clock:0x0b9812ad 2006/03/01 08:07:09
ofst[ 80]:err_code:0xa0403034, clock:0x0b9812ad 2006/03/01 08:07:09
ofst[ 84]:err_code:0xa0404412, clock:0x0b9a653d 2006/03/03 02:23:57
ofst[ 88]:err_code:0xa0403034, clock:0x0b9a653d 2006/03/03 02:23:57
ofst[ 92]:err_code:0xa0404412, clock:0x0b9a654e 2006/03/03 02:24:14
ofst[ 96]:err_code:0xa0403034, clock:0x0b9a654e 2006/03/03 02:24:14
ofst[100]:err_code:0xa0902120, clock:0x0b9a654e 2006/03/03 02:24:14
ofst[104]:err_code:0xa0901001, clock:0xffffffff
[mullion]$
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
>$ 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:0x21e2
>$
[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 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
[SERV NVS] READ CMD
[mullion]$
>$
[SERV THERM] Thermal Error Detected!
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SSM] *** Thermal Alert (ZONE) ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801200
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SERV NVS] *** sending error ***
[mullion]$
>$ disp_err
disp_err
CheckStop: None
PLLUnlock: 0
RSX Int: None
PowerSeq: ff
[mullion]$
>$ lasterrlog
lasterrlog
Last Error Code:0xa0801200, Time:0x0b488687 2005/12/31 00:00:07
[mullion]$
>$ errlog
errlog
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
ofst[ 0]:err_code:0xa0801200, clock:0x0b488687 2005/12/31 00:00:07
[mullion]$
>$
Code:
>$ hdmi vbs
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module : Unset
[HDMI VBS] ( 1) Command Module : Unset
[HDMI VBS] ( 2) I2C Module : Unset
[HDMI VBS] ( 3) Interrupt Module : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module : Unset
[HDMI VBS] ( 6) State Machine Module : Unset
[HDMI VBS] ( 7) EDID Read Module : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module : Unset
[HDMI VBS] ( 9) FRAME Module : Unset
[HDMI VBS] (10) HW Module : Unset
[HDMI VBS] (11) SET Module : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module : Unset
[HDMI VBS] (13) REQ Module : Unset
[HDMI VBS] (14) SystemEvent Module : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module : Unset
[HDMI VBS] (17) CH1 Module : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module : Unset
[HDMI VBS] (25) EEPROM Module : Unset
[HDMI VBS] (30) Hdmi System : Unset
[HDMI VBS] (31) Hdmi ERROR : Unset
[mullion]$
>$ shutdownI did get some new codes while pressing on the chip though...
Code:
>$ 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]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[SSM] fatalreq delayed.
[ERROR]: 0xa0901001
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
[SSM] *** Power Fail BE ***
[SSM] state: 0000 -> 0800
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
>$ errlog
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0800 -> 0600
(PowerOff State) (Fatal)
errlog
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
ofst[ 0]:err_code:0xa0801200, clock:0x0b488687 2005/12/31 00:00:07
ofst[ 4]:err_code:0xa0801004, clock:0x0b488a0b 2005/12/31 00:15:07
ofst[ 8]:err_code:0xa0801200, clock:0x0b488f02 2005/12/31 00:36:18
ofst[ 12]:err_code:0xa0901001, clock:0x0b488692 2005/12/31 00:00:18
ofst[ 16]:err_code:0xa0901001, clock:0x0b488800 2005/12/31 00:06:24
[mullion]$
>$ clearerr
clearerr
*** Unknown Command ***
[mullion]$
>$ bringup
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
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] fatalreq delayed.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[ERROR]: 0xa0101001
[SSM] *** Power Fail BE ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
>$ bringup
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
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:0x21e2
>$ hdmi vbs
[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 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
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module : Unset
[HDMI VBS] ( 1) Command Module : Unset
[HDMI VBS] ( 2) I2C Module : Unset
[HDMI VBS] ( 3) Interrupt Module : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module : Unset
[HDMI VBS] ( 6) State Machine Module : Unset
[HDMI VBS] ( 7) EDID Read Module : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module : Unset
[HDMI VBS] ( 9) FRAME Module : Unset
[HDMI VBS] (10) HW Module : Unset
[HDMI VBS] (11) SET Module : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module : Unset
[HDMI VBS] (13) REQ Module : Unset
[HDMI VBS] (14) SystemEvent Module : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module : Unset
[HDMI VBS] (17) CH1 Module : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module : Unset
[HDMI VBS] (25) EEPROM Module : Unset
[HDMI VBS] (30) Hdmi System : Unset
[HDMI VBS] (31) Hdmi ERROR : Unset
[mullion]$ [SERV NVS] READ CMD
>$ hdmi vbs
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module : Unset
[HDMI VBS] ( 1) Command Module : Unset
[HDMI VBS] ( 2) I2C Module : Unset
[HDMI VBS] ( 3) Interrupt Module : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module : Unset
[HDMI VBS] ( 6) State Machine Module : Unset
[HDMI VBS] ( 7) EDID Read Module : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module : Unset
[HDMI VBS] ( 9) FRAME Module : Unset
[HDMI VBS] (10) HW Module : Unset
[HDMI VBS] (11) SET Module : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module : Unset
[HDMI VBS] (13) REQ Module : Unset
[HDMI VBS] (14) SystemEvent Module : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module : Unset
[HDMI VBS] (17) CH1 Module : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module : Unset
[HDMI VBS] (25) EEPROM Module : Unset
[HDMI VBS] (30) Hdmi System : Unset
[HDMI VBS] (31) Hdmi ERROR : Unset
[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:67.98(0x43ff)
[mullion]$
>$
POWER Button pressed
Power Button Long Long Pressed..
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
[mullion]$
>$ errlog
errlog
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
ofst[ 0]:err_code:0xa0801200, clock:0x0b488687 2005/12/31 00:00:07
ofst[ 4]:err_code:0xa0801004, clock:0x0b488a0b 2005/12/31 00:15:07
ofst[ 8]:err_code:0xa0801200, clock:0x0b488f02 2005/12/31 00:36:18
ofst[ 12]:err_code:0xa0901001, clock:0x0b488692 2005/12/31 00:00:18
ofst[ 16]:err_code:0xa0901001, clock:0x0b488800 2005/12/31 00:06:24
ofst[ 20]:err_code:0xa0101001, clock:0x0b4888ba 2005/12/31 00:09:30
[mullion]$
>$Continued on Frankenstein Phat thread Here...
Last edited:
Workz_777
Senior Member
Wow 12,291 hours!
In the data sheet, the Proadlizers are rated at 1000 hrs at 105°C
https://datasheetspdf.com/pdf-file/716581/NEC/PFAF250E128MTE/1
...being so close to hot RSX/CELL, surely their life-span is close / near the end?
RIP-Felix
Senior Member
Yes. Here's everyone in my spreadsheet with that 2102 error. You can readup on their symptoms and maybey it'll help you find a path forward.
@LSL on page 4 and again on page 80
@Kostasigr7 on page 36
@TimeWalker75a on page 50
@johs854 on page 83
@ps06 on page 91
@N3Star on page 97
@poot36 on page 99
@amxcs on page105
SSM state:
202 -> 103
- 2 steps (23 & 30)
- 23 2102 = Fatal RSX Error (IC2001)
- Must be some kind of RSX initilization/checks
IC6301 is a Dual channel Video amp that provides +1.7V_MISC for several DC/DC converters & +1.8V_FBVDDQ. He must have installed it improperly or destroyed a nearby SMD. There are several downstream fuses he could have blown to cause this error.
Last edited:
CurieOS
Forum Noob
I didn't realize how much work was going into documenting all of this. I really wish I found this before the YLOD "fix" that's seemingly everywhere, including iFixit. Fortunately that didn't break my original system, though my foolishness certainly did.
I got a new system to try to fix, but I'm running into issues with getting AV output. I posted some details in another thread. I have syscon logs from before I got it booting and bringup logs from after my repairs. I didn't grab becount stats, but I can grab those when I next have time to dig into the console.
Someone definitely got into the console before me. The smaller screws holding the RF shield on were mismatched and stripped, the ones holding the hard drive bay to the board were missing, the longer screw holding the motherboard to the case near the PSU was gone, the thermal compound was partially(?) removed, and portions of the console were incorrectly assembled. Kinda weird seeing 2013 in the errlog as the last time an error was reported. I wonder what the person in before me was even doing?
I'm not 100% sure what fixed my issue. I reflowed the leads of the thermal monitors with some flux and a hand iron and replaced the Power/Eject board since I read on another thread that that fixed these errors for someone else. As you can see the error that happened during bringup was related to a power issue, I didn't have 12V hooked up. I was at home and I don't have as much room here as I do at my local makerspace to work.
Right now I'm not getting any video out on AV or HDMI except in safe mode. I can do some more testing, though the only analog video device I have at home is my TV and its composite input. I think the makerspace might have something with component. If anyone can give me some pointers they would be much appreciated.
I got a new system to try to fix, but I'm running into issues with getting AV output. I posted some details in another thread. I have syscon logs from before I got it booting and bringup logs from after my repairs. I didn't grab becount stats, but I can grab those when I next have time to dig into the console.
Code:
>$ powerstate
powerstate
ATA Power : OFF
PCI Power : OFF
RSX Power : OFF
XDR Power : OFF
Eurus Power : OFF
SB Power : OFF
RSX Thermal Sensor : UNAVAILABLE
BE Thermal Sensor : UNAVAILABLE
[mullion]$
>$ 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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0003001
[ERROR]: 0xa0003001
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
>$ lasterrlog
lasterrlog
Last Error Code:0xa0003001, Time:0xffffffff
[mullion]$
Code:
errlog
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
ofst[ 0]:err_code:0xa0801200, clock:0x11de5d07 2009/07/01 17:44:39
ofst[ 4]:err_code:0xa0801200, clock:0x125bbade 2009/10/04 19:58:22
ofst[ 8]:err_code:0xa0801200, clock:0x13157738 2010/02/22 17:11:20
ofst[ 12]:err_code:0xa0801200, clock:0x15040cdb 2011/03/04 20:49:31
ofst[ 16]:err_code:0xa0801200, clock:0x150421e0 2011/03/04 22:19:12
ofst[ 20]:err_code:0xa0801200, clock:0x158e9caf 2011/06/17 23:15:59
ofst[ 24]:err_code:0xa0801200, clock:0x158ecbce 2011/06/18 02:37:02
ofst[ 28]:err_code:0xa0801200, clock:0x15ca5015 2011/08/02 06:05:09
ofst[ 32]:err_code:0xa0801200, clock:0x17665ae2 2012/06/09 19:05:06
ofst[ 36]:err_code:0xa0801200, clock:0x17a616c1 2012/07/28 03:19:29
ofst[ 40]:err_code:0xa0801200, clock:0x17a63978 2012/07/28 05:47:36
ofst[ 44]:err_code:0xa0801200, clock:0x17a717a1 2012/07/28 21:35:29
ofst[ 48]:err_code:0xa0a02030, clock:0x1870eaec 2012/12/28 23:42:36
ofst[ 52]:err_code:0xa0a02030, clock:0x1870eaee 2012/12/28 23:42:38
ofst[ 56]:err_code:0xa0082031, clock:0x1870eaef 2012/12/28 23:42:39
ofst[ 60]:err_code:0xa0a02030, clock:0x18b9a58c 2013/02/22 03:42:04
ofst[ 64]:err_code:0xa0a02030, clock:0x18b9a5a4 2013/02/22 03:42:28
ofst[ 68]:err_code:0xa0801200, clock:0x18d7a7bf 2013/03/16 21:59:27Someone definitely got into the console before me. The smaller screws holding the RF shield on were mismatched and stripped, the ones holding the hard drive bay to the board were missing, the longer screw holding the motherboard to the case near the PSU was gone, the thermal compound was partially(?) removed, and portions of the console were incorrectly assembled. Kinda weird seeing 2013 in the errlog as the last time an error was reported. I wonder what the person in before me was even doing?
I'm not 100% sure what fixed my issue. I reflowed the leads of the thermal monitors with some flux and a hand iron and replaced the Power/Eject board since I read on another thread that that fixed these errors for someone else. As you can see the error that happened during bringup was related to a power issue, I didn't have 12V hooked up. I was at home and I don't have as much room here as I do at my local makerspace to work.
Right now I'm not getting any video out on AV or HDMI except in safe mode. I can do some more testing, though the only analog video device I have at home is my TV and its composite input. I think the makerspace might have something with component. If anyone can give me some pointers they would be much appreciated.
BwE
Member
Bro this is fucking CONTENT! Holy shit I love this. I'm posting this on my discord <3
RIP-Felix
Senior Member
Your CPU is overheating. Need to delid and test. 3001 is usually because you didn't have 12v prongs of PSU inserted when you tested. If you did, then bad PSU or fuse.
Workz_777
Senior Member
@RIP-Felix ...should i also post my SYSCON logs here?
(I already posted them to the YLOD NEC/Tokin thread)
(I already posted them to the YLOD NEC/Tokin thread)
Workz_777
Senior Member
Hi @Kostaslgr7 ...i have 1 x spare (new) Teensy++ 2.0 if you want it, PM me if you are still wanting one.
I purchased 4 x Teensy++ 2.0 (~2 years ago) ...they are great for reading / writing to PS3 NAND/NOR. I followed @littlebalup TEENSY2PS3 guide. You would also need to buy a few more items to make it all work, see / download the guide / tutorial below.
Also see TEENSY2PS3 thread on psx-place here:-
https://www.psx-place.com/threads/teensy2ps3-pcb-linker-teensy-2-0-ps3.1728/
This TEENSY2PS3 PCB above, i purchased on eBay, but you can get it made by a PCB fab.
Gerber Files:- http://www.mediafire.com/download/fd8zqt1aykfi58p/TEENSY2PS3_v1.01.zip
Also, you might need to buy a TSOP-48 to DIP-48 - IC Socket (see photo below) instead of the "360-Clip". So you can desolder the NAND from the board and place it into the TSOP-48 to DIP-48 socket. Because for me the "360-Clip" didn't work very well, i couldn't get good contact to the NAND while it's still on the PS3 board.
But if you still want a "360-Clip" / "Wii-Clip" this is where i got mine one from:-
https://www.ic2005.com/shop/home.php?cat=16
Littlebalup TEENSY2PS3 Guide:-
http://www.mediafire.com/file/vg7410g3vo9w3dt/TEENSY2PS3_v1.01_manual_EN.pdf/file
Attachments
CurieOS
Forum Noob
I must have been unclear. The errlog I posted is from before I reflowed the thermal monitors and replaced the power/eject board. After I did that, I had the 12V prongs disconnected when I got that bringup log. Right now I'm at a GLOD state. I haven't grabbed a new syscon log since because I've been really busy.
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
-