lostman1234
Forum Noob
Is it safe to use the stock SYSCON temp settings on a Frankie PS3?
Razmann4k
Member
Assuming you have a 40nm RSX, the stock SYSCON fan curve runs the GPU at around 73c most of the time, which is safe for a 40nm but not exactly a great temperature if you want your PS3 to last a really long time.
Good afternoon Felix, after changing the RSX, as I said, I got errors 2120 x10 and 3013....through measurements I realized that I have a short on the +1.5 RSX VDDIO line and also a low resistance on the FBVDDQ line. I compared it to a photo with the resistors and I have a frank mod made here, where I could compare and check the short. As for the +1.5 RSX VDDIO voltage, since its formation, there are only resistors along the way, and it ends directly at rsx. Do you believe it is a short caused by balls, during resoldering of the RSX or would you recommend trying something else on the board before resoldering? If you could guide me, I would be very grateful.
Last edited:
Casualdehid/Aerials
Member
Hi there!
I might probably have succeeded in finding the most heat-generating (but don't know if it's stressful, or just heats it up like Prime95) scenario for the RSX. You'll never belive this... Uncharted 3s title screen. Noticed it on a delidded G model that it the temps have rizen significantly afer....returning to the title screen from the game.
I might probably have succeeded in finding the most heat-generating (but don't know if it's stressful, or just heats it up like Prime95) scenario for the RSX. You'll never belive this... Uncharted 3s title screen. Noticed it on a delidded G model that it the temps have rizen significantly afer....returning to the title screen from the game.
Ganjo
Member
Anyone have any ideas as to why the last 3 systems ive done have all ben GLOD. No controller sync, no output on HDMI or AV, momentary flash of HDD LED, just no signal. Ive put 3 RSX chips on each of them. All A01 models
This system ONLY had 801001 and 801004 errors
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
Press Ctrl+C to exit
>$
[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 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
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 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
This system ONLY had 801001 and 801004 errors
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
Press Ctrl+C to exit
>$
[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 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
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 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
Last edited:
vyktormvmpay25
Senior Member
Can you please add sb uart log, that would tell us more.
Ganjo
Member
Code:
Boot Loader SE Version 3.1.5 (Build ID: 3814,43498, Build Date: 2009-12-01_21:12:04)
SDK Version: 315.000
Copyright(C) 2009 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:DX3.1
Device: PATAC0:Cable Not Connect
Cell OS SDK3.1.5 000 (release build: r43498 2009_12_01_200000)
Copyright 2009 Sony Computer Entertainment Inc.
revision: 43224
date: Tue Dec 1 21:17:12 JST 2009
rsx rom abort!
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size: 12MB+640KB (heap:3692KB page pool:4736KB)
lv2(0): user memory size: 237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 3.1.5
lv2(2): Copyright 2009 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 43498
lv2(2): build date: 2009/12/01 21:31:50
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: rsx40 a01 300/400 vpe:ff shd:3f [NN5687-06:0:4:6:9:5:6:0:1][1e:0:a:0:1:0:1][1:1:0]
lv2(2): Available physical SPUs: 6
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): # RSXAuRSX #410-ffffffff [bbdbfb]
lv2(2): sys_init: system software process set-up done.
lv2(2): initial system process done.
lv2(2): [system utility]: BD Drive connect error.
lv2(2): [system utility]: BD Drive connect error.
Code:
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]
Last edited:
vyktormvmpay25
Senior Member
lv2(2): Cell OS Lv-2 32 bit version 3.1.5
So your software version is not compatible with rsx. What do we do next?
Wait or search a way to install 355 in fsm mode (blind install /no image on any port). Let see what method @RIP-Felix, @Nascar1243, @alty75 or @zecoxao, @M4j0r recomand. I first discovered accidentally and patched nands with hw flasher to fsm and then install 355fsm. But it's a mess and I believe there is a way now to just do it with USB instead of hw flasher. Be prepared for that if USB way won't work. Just keep in mind some models won't work lower than 3.40 ofw for rsx 40nm.
So your software version is not compatible with rsx. What do we do next?
Wait or search a way to install 355 in fsm mode (blind install /no image on any port). Let see what method @RIP-Felix, @Nascar1243, @alty75 or @zecoxao, @M4j0r recomand. I first discovered accidentally and patched nands with hw flasher to fsm and then install 355fsm. But it's a mess and I believe there is a way now to just do it with USB instead of hw flasher. Be prepared for that if USB way won't work. Just keep in mind some models won't work lower than 3.40 ofw for rsx 40nm.
vyktormvmpay25
Senior Member
Ok seems to be like put 3.55 ofw on right location on a fat32 for updates like you would update unit.
Put console in safe mode /recovery.
Now if you see controller connected with unit via cable hit once ps button, keep pressing down d pad and hit x.
If all good hdd should blink mean it is updating. If not it will say all errors.
All this time watch sb uart log. There you will see if it passes.Ace did one video I can't find right now. So all process is blind but you can watch sb uart log to understand what is failing.
Ganjo
Member
Checked it again and the controller still wont sync. Plugged in BT board and tried in safe mode as well. I guess I could reverse the frankenfat and put a 90nm back on it. Id rather not remove this chip since the board has been reworked 3 times. If I do reverse the frankenfat mod does anyone know what the stock data values are on A01 consoles?
I can buy a HW flasher but will that method even work with the no controller sync?
I can buy a HW flasher but will that method even work with the no controller sync?
vyktormvmpay25
Senior Member
Just don't reverse it, wait flasher and patch. Is easy, buy teensy 2++,buy a cheap tsop 48 pins socket adaptor and patch nands for 355. Or let's try once again with pup file for update 355 ofw and lv2diag.self files for fsm on root of usb. Once you power up push eject right after on button. Just both files in root of usb. USB stick must be on most close to bdrom port like from left to right last USB port.
All data to reverse are here but don't have to go back, you're 90nm may not be good to idk.
https://www.psdevwiki.com/ps3/Talk:Rambus_Registers
Ganjo
Member
The USB flashed a few times but the SB log output window shows nothing different. I put both files on the root of a fat32 formatted usb in the right port. I tired putting 355 in the update folder too. I dont need that jig to trigger FSM?
One more question. Is there some way to check the SW version when it has YLOD and wont output anything to the log window?
One more question. Is there some way to check the SW version when it has YLOD and wont output anything to the log window?
Last edited:
nemanjat85
Member
Hello,
I bought 40nm RSX CXD5301DGB from aliexpress and these are my readings. Can someone confirm that this RSX ig good?
RSX_VDDC = 2,5 ohm multimeter beeps
RSX_VDDR=413 ohm
RC_VDDIO=3,404 kohm
RSX_VDDIO=1,653 kohm
RC_VDDA=2,618 kohm
PLL_VDD=11,63 Mohm
FBVDDQ=493,5 ohm
I bought 40nm RSX CXD5301DGB from aliexpress and these are my readings. Can someone confirm that this RSX ig good?
RSX_VDDC = 2,5 ohm multimeter beeps
RSX_VDDR=413 ohm
RC_VDDIO=3,404 kohm
RSX_VDDIO=1,653 kohm
RC_VDDA=2,618 kohm
PLL_VDD=11,63 Mohm
FBVDDQ=493,5 ohm
vyktormvmpay25
Senior Member
Well no way of checking lv2 of software when ylod. Just what I know is when you extract nands as one full dump flash 256 MB you can see with patches tool Ros0 and ros1 level of patches but sometimes it's just not recognised if lower then 355 as most data were input from most devs over 355 so software is bit unknown situation. About jig yes it's needed but thought it may work. Well wait just for flasher and patch for 355 fsm then update blind. It will work without dongle, just by lv2diag.self and 355 ofw on root of usb. That is what I did, just patched and updated blind. Also what I didn't test :now low fw fsm could be triggered with dongle. Instead of desolder try trigger fsm and then try blind update if unit is stopping after 10 seconds it has to work for blind update on second boot by pressing power +eject quick with update on root and USB stick to most nearby bdrom. Also teensy 2++are 2 variants 1286 and 1287, we know Felix had 1287 and didn't trigger fsm, he bought e3 card reader that act like fsm dongle. Teensy should do that too work as dongle but I don't remember when last time I was testing it and what hex I did. If you find a way to get that fsm dongle or I think it's someone selling them in USA.
vyktormvmpay25
Senior Member
That is perfect ic imo
Ganjo
Member
Ok im ordering a teensy but I can only find it from china.
I did another console today and wanna guess what happened? Ya, GLOD. I do have controller sync, I can see the HDD LED going but all I get from the SB log is Device: PATAC0:Cable Not Connect . Sometimes when im doing a video reset I the TV does say Not Support!
Console ONLY had 403034 errors in syscon. Its weird, of the last 6 ive done 4 were mine and all GLOD, 2 were customers and they all worked fine. Im gonna go crazy lol
I did another console today and wanna guess what happened? Ya, GLOD. I do have controller sync, I can see the HDD LED going but all I get from the SB log is Device: PATAC0:Cable Not Connect . Sometimes when im doing a video reset I the TV does say Not Support!
Console ONLY had 403034 errors in syscon. Its weird, of the last 6 ive done 4 were mine and all GLOD, 2 were customers and they all worked fine. Im gonna go crazy lol
vyktormvmpay25
Senior Member
Can you format hdd and try again, if that error comes again keep 5 seconds start and select probably will skip that? That is command for formatting hdd.
Always I got teensy from China, since 2009 I destroyed like 6 or 7 teensy with different glitches probably or heat of ic idk. Make sure is 1286.
Always I got teensy from China, since 2009 I destroyed like 6 or 7 teensy with different glitches probably or heat of ic idk. Make sure is 1286.
Kryder
Member
I very want to make and build similar mod with CECHA.... I have two CECHA01 and CECHA04 - working, condition 4\5 (although the cases are worn), BUT I collected for assembling the "ideal PS3 console" a whole set of cases (or parts of cases) from CECHC in almost perfect condition, a set of different "good" power supplies - APS-226\227\231 2\1\2 pcs almost in perfect condition, a "package" of different 15\19 blade coolers, also 4 drives from CECHC in "new" condition...
But I don't want to heat a live and rare rarity console board, on an "medium level\quality" IR station, although for me not a problem to install a 40nm chip (and i have probably 30+ donors of Slim\SS boards\consoles))....
But I don't want to heat a live and rare rarity console board, on an "medium level\quality" IR station, although for me not a problem to install a 40nm chip (and i have probably 30+ donors of Slim\SS boards\consoles))....
Last edited:
Ganjo
Member
I ordered the teensy 2.0 ++ AT90USB1286. Whats the name of the dongle I should be looking for?
I took the console inside and now its working. I turned it on and after a few seconds the screen started flashing and eventually the XMB came up with some static on screen. I wiggled the HDMI and it started flashing again. So, bad/loose HDMI port. Doesn't explain that SB error or why it wouldn't display out of the AV port. I do remember wiggling the port when it was downstairs. I installed a larger HDD in it and after the format it wouldn't detect the new HDD but after another reboot it was working. Maybe the console was dropped, I'll check the solder connections for the HDMI and HDD in the morning.
Thanks
I took the console inside and now its working. I turned it on and after a few seconds the screen started flashing and eventually the XMB came up with some static on screen. I wiggled the HDMI and it started flashing again. So, bad/loose HDMI port. Doesn't explain that SB error or why it wouldn't display out of the AV port. I do remember wiggling the port when it was downstairs. I installed a larger HDD in it and after the format it wouldn't detect the new HDD but after another reboot it was working. Maybe the console was dropped, I'll check the solder connections for the HDMI and HDD in the morning.
Thanks
Similar threads
-
-
PS3 PS3 CECHA RSX Swap (40nm) – JP Limited – SYSCON Patch, VDDC Mod – Need Detailed Help- Started by jw0710
- Replies: 4
-
-
