PS3 GLOD on new COK-002 after reassembly.

Nator

Nator

Member
I'm experimenting a GOLD on a working COK-002 with original FW. The ps3 turns on but the led remains green and no video signal(hdmi). I inserted a disk and it took it but if i try to eject it the blue light flashes and makes 3 beeps(also with the console turned off in standby). Once there was a 720x576 video signal but the screen was black. Here the entire syscon and southbridge logs.
Hope someone can help me.
N7XcJ7n.jpg

mnD3Prh.jpg
2IP2zpR.jpg

For safety I tried to insulate the contacts with high temperature silicone, I don't know if it's a good idea.
1ovQujq.jpg
becount
Code: 
>$ becount
becount
Bringup : 2970 times
Shutdown: 1834 times
Power-on: 104day 23hour 29min 08sec
bringup
Code: 
>$ 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
Press Ctrl+C to exit
>$
[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
[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
powerstate
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
shutdown
Code: 
>$ 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
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
Errolog
Code: 
>$ errlog
ofst[ 24]:err_code:0xffffffff, clock:0x1b9cc1e3  2014/09/05 18:48:03
ofst[ 28]:err_code:0xa0801004, clock:0x1baf102c  2014/09/19 16:02:52
ofst[ 32]:err_code:0xa0801004, clock:0x1bbc2621  2014/09/29 14:16:01
ofst[ 36]:err_code:0xa0801004, clock:0x1bc227e9  2014/10/04 03:37:13
ofst[ 40]:err_code:0xa0801004, clock:0x1c320565  2014/12/28 00:03:49
ofst[ 44]:err_code:0xa0801001, clock:0x1c32d931  2014/12/28 15:07:29
ofst[ 48]:err_code:0xa0801004, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 52]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 56]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 60]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 64]:err_code:0xa0801001, clock:0x1c80ca64  2015/02/25 18:01:08
ofst[ 68]:err_code:0xa0801004, clock:0x1c82604d  2015/02/26 22:53:01
ofst[ 72]:err_code:0xa0801004, clock:0x1c826123  2015/02/26 22:56:35
ofst[ 76]:err_code:0xa0801004, clock:0x1c962726  2015/03/13 22:54:30
ofst[ 80]:err_code:0xa0801004, clock:0x1cfc0ce2  2015/05/30 05:53:38
ofst[ 84]:err_code:0xa0801004, clock:0x1d0f4931  2015/06/13 20:04:01
ofst[ 88]:err_code:0xa0801004, clock:0x1d0f4c84  2015/06/13 20:18:12
ofst[ 92]:err_code:0xa0801004, clock:0x1d0f835d  2015/06/14 00:12:13
ofst[ 96]:err_code:0xa0801004, clock:0x1d7372d6  2015/08/28 19:28:22
ofst[100]:err_code:0xa0801004, clock:0x1db94915  2015/10/20 18:48:53
ofst[104]:err_code:0xa0801001, clock:0x1dba9ce9  2015/10/21 18:58:49
ofst[108]:err_code:0xa0801001, clock:0x1dbbe883  2015/10/22 18:33:39
ofst[112]:err_code:0xa0801001, clock:0x1e6cdc60  2016/03/04 23:53:04
ofst[116]:err_code:0xa0801001, clock:0x1ff560c8  2016/12/27 17:26:32
ofst[120]:err_code:0xa0801004, clock:0x1ff89df8  2016/12/30 04:24:24
ofst[124]:err_code:0xa0801004, clock:0x1ffaf612  2016/12/31 23:04:50
ofst[  0]:err_code:0xa0801001, clock:0x208406da  2017/04/14 22:16:58
ofst[  4]:err_code:0xa0801001, clock:0x2c0668ae  2023/05/28 19:31:58
ofst[  8]:err_code:0xa0801001, clock:0x2c0668c4  2023/05/28 19:32:20
ofst[ 12]:err_code:0xa0801001, clock:0x2c079cc7  2023/05/29 17:26:31
ofst[ 16]:err_code:0xa0801004, clock:0x2c79357a  2023/08/23 21:24:10
ofst[ 20]:err_code:0xa0801001, clock:0x0b488702  2005/12/31 00:02:10

Code: 
Boot Loader SE Version 4.9.0 (Build ID: 5370,50747, Build Date: 2022-12-12_15:06:40)
SDK Version: 490.000
Copyright(C) 2022 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.1, SB:PX1.1
Cell OS SDK4.9.0 000 (release build: r50747 2022_12_12_130000)
Copyright 2022 Sony Computer Entertainment Inc.
revision: 50747
date:     Mon Dec 12 15:08:07 JST 2022
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.9.0
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50747
lv2(2): build date: 2022/12/12 15:11:54
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x0201
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      b02 500/650 vpe:ff shd:3f  [4K0301701:1:3:f:7:5:4:f:1][39:2:1:1:1:3:1][0:0:0]

lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2): creating the initial system process : OK
lv2(2): entering stand-alone mode.
lv2(2): system software: PS3 console mode (game memsize=200MB)
lv2(2): creating the system software process : OK
lv2(2): sys_init: system software process set-up done.
lv2(2): initial system process done.
After activating the hypervisor in syscon the southbridge log shows same results, my console is not CWF, maybe it has something to do with it?
Code: 
>$ hdmi chstat 0
hdmi chstat 0
[HDMI] ----------------------------
[HDMI] -- HDMI Channel 0 Context --
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[System Management]
[HDMI]     - SSM Task ID : 13
[HDMI]         * Task Status : WAITING
[HDMI]         * Wait Cause  : EVENT FLAG
[HDMI]     - SSM State : WaitResolution
[HDMI]     - SSM Mutex Information : ID[2] LockTID[0] WaitTID[0]
[HDMI]     - SSM Event Flag Info : ID[2] WaitTID[13] FlagPattern[0]
[HDMI]     - SSM Mode : HDMI
[HDMI] ------------------------------------------------------------------------------------
[HDMI]     - Authentication Status : NotStart
[HDMI]     - Repeater : Sink
[HDMI]     - KSVs     : 0
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[Interrupt]
[HDMI]     - External Interrupt Number of Mullion : 7
[HDMI]     - Interrupt Mask Pattern in SiI : [0x0000E0]
[HDMI]     - Interrupt Register Size : 3
[HDMI]     - Interrupt Task ID : 12
[HDMI]         * Task Status : WAITING
[HDMI]         * Wait Cause  : SLEEPING
[HDMI]     - Semapho Information : ID[38] WaitingTID[0] Count[1]
[HDMI]     - Plug Status : PowerOn
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[SiIType]
[HDMI]     - Chip Type : 9132
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[EDID]
[HDMI]     - EDID Mutex ID : 3
[HDMI]     - EDID Mutex Information : ID[3] LockTID[0] WaitTID[0]
[HDMI]     - EDID Block Size : 2
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[I2C Bus]
[HDMI]     - Device Address 0x72(0) 0x7A(1)
[HDMI]     - Semapho Information : ID[36] WaitingTID[0] Count[1]
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[AV Setting]
[HDMI]     - Audio Setting State : Unset
[HDMI]                     Mute  ; Mute
[HDMI]     - Video Setting State : Unset
[HDMI]                     Mute  ; Mute
[HDMI]                  Setting  : 00 00 00 00 00 00 00 00 00 00 00 00
[HDMI]                           : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[HDMI]
Code: 
>$ hdmi ports
hdmi ports
HDMI Ports[1]  DVE Ports[1]
[mullion]$

Press Ctrl+C to exit
>$ hdmi redid 0
hdmi redid 0
[HDMI] - Ch.0 EDID Block 0 -
[HDMI] Addr :  0  1  2  3| 4  5  6  7| 8  9  A  B| C  D  E  F
[HDMI] -----:------------+-----------+-----------+-----------
[HDMI]  00  : 00 ff ff ff|ff ff ff 00|4c 2d 7a 0a|00 00 00 00
[HDMI]  10  : 2e 16 01 03|80 46 27 78|0a ee 91 a3|54 4c 99 26
[HDMI]  20  : 0f 50 54 bd|ef 80 71 4f|81 c0 81 00|81 80 95 00
[HDMI]  30  : a9 c0 b3 00|01 01 02 3a|80 18 71 38|2d 40 58 2c
[HDMI]  40  : 45 00 24 72|42 00 00 1e|66 21 56 aa|51 00 1e 30
[HDMI]  50  : 46 8f 33 00|24 72 42 00|00 1e 00 00|00 fd 00 18
[HDMI]  60  : 4b 0f 51 17|00 0a 20 20|20 20 20 20|00 00 00 fc
[HDMI]  70  : 00 53 41 4d|53 55 4e 47|0a 20 20 20|20 20 01 89

[HDMI] - Ch.0 EDID Block 1 -
[HDMI] Addr :  0  1  2  3| 4  5  6  7| 8  9  A  B| C  D  E  F
[HDMI] -----:------------+-----------+-----------+-----------
[HDMI]  00  : 02 03 25 f1|4d 90 1f 04|13 05 14 03|12 20 21 22
[HDMI]  10  : 07 16 23 09|07 07 83 01|00 00 e2 00|0f 67 03 0c
[HDMI]  20  : 00 10 00 b8|2d 01 1d 80|d0 72 1c 16|20 10 2c 25
[HDMI]  30  : 80 24 72 42|00 00 9e 01|1d 80 18 71|1c 16 20 58
[HDMI]  40  : 2c 25 00 24|72 42 00 00|9e 01 1d 00|bc 52 d0 1e
[HDMI]  50  : 20 b8 28 55|40 24 72 42|00 00 1e 01|1d 00 72 51
[HDMI]  60  : d0 1e 20 6e|28 55 00 24|72 42 00 00|1e 8c 0a d0
[HDMI]  70  : 90 20 40 31|20 0c 40 55|00 24 72 42|00 00 18 3c
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]$
Strange things:
The PS3 heats up a lot, after a few seconds of being turned on with syscon i hear the fan speed increase slightly.
 
Last edited:
vyktormvmpay25 said:
This is simple, make it Frankie. Don't lose your time.
Click to expand...
Don't you think it would be better to diagnose further with the southbridge log? Maybe we find the problem elsewhere, or if we don't, then i might think about making it Frankie but i have to be sure first because the PS3 worked perfectly before and i can't think that the RSX has suddenly been ruined inside.

vyktormvmpay25 said:
This is simple, make it Frankie. Don't lose your time.
Click to expand...
I have updated the log with the southbridge log and other hdmi test logs, i suggest you read it again. I don't think it gave me any errors. Strangely i had to connect the Rx of the SB to the Tx of the UART to get the log. Hypervisor enabled or disabled doesn't change anything for me, maybe because i'm not in CFW. The console gets very hot on the touch side near the syscon connections, maybe there is a short?
 
Last edited by a moderator:
I simply call this type of glod (green light of death) "special glod".
You have 2 option that in 12 years I never managed to fix it =reball same gpu but goes worst for me or second Frankie. Ask Louise Rosman when he left this legendary meme "Reball is but..." [emoji16]
Try power unit without bdrom fcc connected. If that give you image then that's your problem.
Thank you for your reply Felix.
 
He hasn't confirmed that the HDD is fine or that he tried the video reset in recovery options menu. It eating disks is normal for a disc feed sensor wire getting broken or for the BD not being reseated properly.

So before jumping to the RSX related GLOD scenarios, he should rule out the routine causes first.
 
I thought he tested without hdd

lv2(2): entering stand-alone mode.
Also please make it work for sb with only Tx from mobo to rx from uart adaptor and gnd. Only 2 wires. You only need to see log, we can't write anything to sb.
 
Last edited:
vyktormvmpay25 said:
I thought he tested without hdd

lv2(2): entering stand-alone mode.
Also please make it work for sb with only Tx from mobo to rx from uart adaptor and gnd. Only 2 wires. You only need to see log, we can't write anything to sb.
Click to expand...
Ok, i'll try soldering the GND wire too. It remains strange that i managed to extrapolate the SB log by connecting its Tx with the UART's Tx. Maybe i swapped the mobo's SB pads? Can you confirm that this is the right pad?
img_20221227_200047_compress87-jpg.39990
N7XcJ7n.jpg
After having made the connection to the GND i have to test the power on and the SB log after having physically removed the blueray drive unit and the hdd right? I haven't done any of these things yet.
 
Yes you can do reset image while test unit without hdd or bdrom fcc removed from motherboard not simple let fcc into connector.
SB uart log can test later if you don't get image.
 
RIP-Felix said:
He hasn't confirmed that the HDD is fine or that he tried the video reset in recovery options menu. It eating disks is normal for a disc feed sensor wire getting broken or for the BD not being reseated properly.

So before jumping to the RSX related GLOD scenarios, he should rule out the routine causes first.
Click to expand...
I assume the hdd is good because it worked before. I will do the video reset but obviously not the recovery mode menu because i can't enter any menu if the screen is black. For this reason i should receive an AV cable tomorrow to exclude that the video can pass into this mode. Now i try to solder the GND and do the things you said.

vyktormvmpay25 said:
Yes you can do reset image while test unit without hdd or bdrom fcc removed from motherboard not simple let fcc into connector.
SB uart log can test later if you don't get image.
Click to expand...
Ok I'll try. I need to better understand what you mean by "fcc", do you mean the ribbon cable that connects the bd drive to the mobo? However, i remove the entire bd with its cables and then try to turn on and reset the video. Give me some time. Thanks for the advices.
 
Last edited by a moderator:
The pad you circled and said you soldered to is attached to pin 79 on CN3208 corresponding to SB_SIO0_TXD. It is the SB_Tx (transmit).

On my diagrams I label it Rx because people find it confusing that their UART adapter's Rx should be connected to the MB's Tx pad. So to make it more intuitive I label the location Rx, which is where their Adapter's RX wire should be soldered. It makes it easier for them, without have to explain the Sc_Rx <-- USB_Tx / Sc_Tx --> USB_Rx thing.
 
Last edited:
vyktormvmpay25 said:
Fcc flat cable connector.
Click to expand...
Ok i tested again with GND and without the bd drive and hdd completely extracted but the screen is still black. The sb log detects the absence of the bd drive (and also warns me "Device PATAC0Cable Not Connect").
I ran the test with just one power-on beep then with the second beep holding down the power button
Code: 
Boot Loader SE Version 4.9.0 (Build ID 5370,50747, Build Date 2022-12-12_150640)
SDK Version 490.000
Copyright(C) 2022 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] BE3.1, SBPX1.1
Device PATAC0Cable Not Connect
Cell OS SDK4.9.0 000 (release build r50747 2022_12_12_130000)
Copyright 2022 Sony Computer Entertainment Inc.
revision 50747
date     Mon Dec 12 150807 JST 2022
skip 2nd initialization step
lv2(0) total memory size 249MB+640KB
lv2(0) kern memory size   12MB+640KB (heap3492KB  page pool4736KB)
lv2(0) user memory size  237MB
lv2(2)
lv2(2) Cell OS Lv-2 32 bit version 4.9.0
lv2(2) Copyright 2011 Sony Computer Entertainment Inc.
lv2(2) All Rights Reserved.
lv2(2)
lv2(2) revision 50747
lv2(2) build date 20221212 151154
lv2(2) processor Broadband Engine  Ver 0x0000  Rev 0x0201
lv2(2) PPU0, Thread0 is enabled.
lv2(2) PPU0, Thread1 is enabled.
lv2(2) rsx      b02 500650 vpeff shd3f  [4K030170113f754f1][39211131][000]

lv2(2) Available physical SPUs 67
lv2(2) mounting the flash file system  OK
lv2(2) creating the initial system process  OK
lv2(2) entering stand-alone mode.
lv2(2) system software PS3 console mode (game memsize=200MB)
lv2(2) creating the system software process  OK
lv2(2) sys_init system software process set-up done.
lv2(2) initial system process done.
then the 2 beeps while holding button down until it enters the safe mode which the sb log report
Code: 
Boot Loader SE Version 4.9.0 (Build ID 5370,50747, Build Date 2022-12-12_150640)
SDK Version 490.000
Copyright(C) 2022 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] BE3.1, SBPX1.1
Device PATAC0Cable Not Connect
Cell OS SDK4.9.0 000 (release build r50747 2022_12_12_130000)
Copyright 2022 Sony Computer Entertainment Inc.
revision 50747
date     Mon Dec 12 150807 JST 2022
skip 2nd initialization step
lv2(0) total memory size 249MB+640KB
lv2(0) kern memory size   12MB+640KB (heap3492KB  page pool4736KB)
lv2(0) user memory size  237MB
lv2(2)
lv2(2) Cell OS Lv-2 32 bit version 4.9.0
lv2(2) Copyright 2011 Sony Computer Entertainment Inc.
lv2(2) All Rights Reserved.
lv2(2)
lv2(2) revision 50747
lv2(2) build date 20221212 151154
lv2(2) processor Broadband Engine  Ver 0x0000  Rev 0x0201
lv2(2) PPU0, Thread0 is enabled.
lv2(2) PPU0, Thread1 is enabled.
lv2(2) rsx      b02 500650 vpeff shd3f  [4K030170113f754f1][39211131][000]

lv2(2) Available physical SPUs 67
lv2(2) mounting the flash file system  OK
lv2(2)
lv2(2) ###
lv2(2) ### Safe mode
lv2(2) ###
lv2(2)
lv2(2) creating the recover process (for safe mode)  OK
lv2(2)
lv2(2) Prepare to shutdown ....
lv2(2) Going to shutdown.
system event id=0xe1, rtc=189303367, size=24 [0x5354523a50415441 0x43303a4361626c65 0x204e6f7420436f6e 0x6e65637400000000]
In safemode it allows me to turn off the console simply by pressing the power button, which i cannot do in any other mode as it should be normal to do. Also in this mode if i plug in the xboxone controller it vibrates and turns on.
So i still have to try the AV cable, it should arrive soon. After that i think we've ruled out all the other possibilities other than RSX, right?
 
RIP-Felix said:
The pad you circled and said you soldered to is attached to pin 79 on CN3208 corresponding to SB_SIO0_TXD. It is the SB_Tx (transmit).

On my diagrams I label it Rx because people find it confusing that their UART adapter's Rx should be connected to the MB's Tx pad. So to make it more intuitive I label the location Rx, which is where their Adapter's RX wire should be soldered. It makes it easier for them, without have to explain the Sc_Rx <-- USB_Tx / Sc_Tx --> USB_Rx thing.
Click to expand...
Ok now i understand. However as i wrote above i tested without BDdrive and hhd, nothing to do the screen remains black. I can enter safe mode and turn off the console by pressing the power button (which it doesn't let me do in other modes as should be normal).
So if it's not a drive, software or CPU problem, only the RSX remains. But i wonder, could it be something else? the hdmi i chip ot the GS chip? I would have to know how the ps3 image output system works to say that.

vyktormvmpay25 said:
I thought he tested without hdd
lv2(2): entering stand-alone mode.
Click to expand...
No, it gives me that message even with the HDD inserted
 
Last edited by a moderator:
Ok i tried to see if the HDD led blink briefly and found that it does. When turned on in normal mode it blinks briefly, while in safe mode when turned off it lights up for a long time. Safe mode is the only mode that allows me to turn off the console simply by pressing the power button for about 2 seconds, in normal mode I have to hold it until it turns off.
This is shutdown in safe mode
This in normal mode, hdd flashes briefly.

Obviously with the HDD removed there is no LED activity.

Yesterday i tried to get the temperatures(and other stuff) from syscon, and i had to note that while the temperature of the rsx seems normal, that of the cell is quite high at 73,92°, why? Also @M4j0r checked the SB log after activating the PME or SS logs (the ones called hypervisors in the guide) and no errors were found. I can't believe there isn't a single error, everything works (apart from the strange behavior of the BDdrive which flashes and doesn't return the disc) but there is no video.
Code: 
>$ tzone
tzone
00: 1st BE Primary
01: RSX Primary
14: SB
[mullion]$

>$ tmp 0
tmp 0
TZone No:00
1st BE Primary  Temperature:73.92(0x49ef)
[mullion]$
Press Ctrl+C to exit
>$ tmp 1
tmp 1
TZone No:01
RSX Primary  Temperature:56.75(0x38c0)
[mullion]$
Press Ctrl+C to exit

>$ duty get 1
duty get 1
CrntDuty(0x1):25%(0x40)
[mullion]$
Press Ctrl+C to exit
>$ duty get 0
duty get 0
CrntDuty(0x0):25%(0x40)
[mullion]$
Press Ctrl+C to exit


>$ version
version
v1.1.3_k1
[mullion]$
Press Ctrl+C to exit

>$ hversion
hversion
CokB10
Press Ctrl+C to exit

>$ disp_err
disp_err
CheckStop:     None
PLLUnlock:     0
RSX Int:       None
PowerSeq:      ff
[mullion]$
Press Ctrl+C to exit

>$ ejectsw
ejectsw
loading_status:0x3
Press Ctrl+C to exit

>$ csum
csum
Checksum: [032156E5] [B8600D39] [F5B2EEA5]
[mullion]$

>$ bstatus
bstatus
OK
Press Ctrl+C to exit

>$ bestat
bestat
(PowerOn State)
[mullion]$
 
Last edited by a moderator:
Just in case anyone else ends up here, I had the exact issue described after swapping a 40nm RSX onto a COK-002 and it turns out I accidentally skipped the 'resistor mod' step (R2054, R2001, R2153). Without setting those you won't get video output. SB log will show an RSX driver timeout if you power it off from safe mode. I set the resistors properly and everything works fine.
 
You must log in or register to reply here.

Similar threads

Back
Top