PS3 (Research/Experimental) - NEC/TOKIN Capacitors Replacement - YLOD

[M4j0r]

So I just syscon'd a mullion MB (COK-001) and noticed that when you "auth" in lowecase there are less commands available. It'll let you retrieve the errlog, but nothing else. I had to "AUTH" in uppercase to get the becount and other commands. Just an FYI. I'll make a note about it in my tutorial.

I've heard that multiple times, but that's not possible with the official version of the script (https://www.psdevwiki.com/ps3/Talk:..._squeasy_way_.28UART.29_.28CXR.2FCXRF.2FSW.29).
It'll always convert the input to the lower case before doing the comparison, so running "AUTH", "auth", "Auth", "AuTh" is all the same:

if(in_data.lower() == 'auth')

python .\ps3_syscon_uart_script.py com3 cxr
Traceback (most recent call last):
File "C:\Users\iamma\source\repos\ps3syscon\ps3_syscon_uart_script.py", line 190, in <module>
main(len(sys.argv), sys.argv)
File "C:\Users\iamma\source\repos\ps3syscon\ps3_syscon_uart_script.py", line 169, in main
ps3 = PS3UART(argv[1], argv[2])
File "C:\Users\iamma\source\repos\ps3syscon\ps3_syscon_uart_script.py", line 34, in __init__
assert(False)
AssertionError

CXR needs to be uppercase.

 

[RIP-Felix]

This should be similar to last cok001 untouched board I've did . Rsx defective. Don't even bother to reball 90nm once dead.

Unless you consider to convert working sem001 rsx to cok001/002 like we fix it on stream.

Do you have the ohm test results on that RSX victor? I'd like to know which voltage line caused it?

I'd have to say I was suspecting the RSX might be dead. Pressure test has no effect and that could be why.

It would be cool if we could pin this BitTraining error or lone 3034 to a specific type of fault (BGA, dead VDDR, VDDQ...ETC)

I toredown another PS3 (PS3#13) yesterday described as a "no display," but it is working for me. It did have 3034 in the log, but that was many years ago according to the timestamp. It looks like a very professional reball, I can't tell anything work was done, except for the new thermal paste. IHS are still lidded.

The point is, I have a working A model to compare with PS3 #11's voltage line ohm tests on the MB. So I'm gonna record and compare those to see if any look different. Maybe this will be a way to quickly identify a bad RSX.

 

[vyktormvmpay25]

Just was 2.5 ohms on vdd measurements on board, took at that time and ram line reading like 110 ohms on rsx_fbvddq. I usually check that sides only . After I removed all caps so I can separate vdd line for core and got 1.8 on motherboard so I didn't carry to it. I just remove it and lost it in phile of rsx. Not sure if complete removal of rsx ram will increase vdd line as is not same power line but who knows, one day need to be tested but pretty much sure is core related and not ram.
I really didn't bother before but from now promise to test bit carefull to bring more data. I've seen that David did get exactly same temperature of melting point.
I say jovy TC is 210=230 for omega TC.
Exactly what I said before 2 same rework stations never will work same way.
It was 218 melted because board was kind bended (not sure), TC omega was 240 so it is kind of deviation but both can really work great, I do desolder with ihs around 232~235 (read by omega TC and 225 or bit less without ihs, so there are different ways to do it but best learn for beginning with ihs bounded always. Didn't work with Jovi TC for a while but I know for sure it is less always with 20 Celsius lower than TC omega . That side each technician must exercise on his machine and improve profiles by his board, jig level. I will refer more profiles to test in 4 or 5 stages, all that with time.
Each situation need to be explained when is faced. I'll help where I can and I have tested myself.
Edit
David next desoldering test try without fume extractor while running profile, running fume extraction given that 10 Celsius deviation. Run it after desolder is done while cooling down mobo.
I don't have fume extractor, nor that I've had when did practice profiles.
Both TC are right, you may get right on 212 or 232 perfect melted for pick rsx.
Edit 2
That costumer of David who took ps3 working and he is not getting images on screen, he did not reset image hdmi, hold 10 seconds on power until first beep or he is tested AV output wrong. This issue won't happen so fast. I would have doubts if was 3~6 months but so fast costumer does not have proper setup. I may be wrong but without testing we can't assume.

 

[RIP-Felix]

I've heard that multiple times, but that's not possible with the official version of the script (https://www.psdevwiki.com/ps3/Talk:..._squeasy_way_.28UART.29_.28CXR.2FCXRF.2FSW.29).
It'll always convert the input to the lower case before doing the comparison, so running "AUTH", "auth", "Auth", "AuTh" is all the same:

if(in_data.lower() == 'auth')

CXR needs to be uppercase.

I meant with internal accesse mode (CXRF). And I am probably using an older script. I think it was the version that required python v2. It still works so I never felt the need to update

 

[Cypha]

Further inspection the ps4 apu metal plate to stiffen it is actually glued on so this means i could either put it on the ps3 cpu or make one from scratch to fit the rsx and cpu

 

[vyktormvmpay25]

RIP-Felix can you please compare and add few cell vdd power line values? That wasn't inspect before and need to explain a low resistance in vdd line for cell, probably same situation as rsx.

 

[RIP-Felix]

COK-001 CHECHA01
This console was GLOD and I reballed the RSX and this is what I got. (thanks for the help RIP-FELIX <3)

[Version 10.0.19041.1415]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Razer\Desktop\syscon\ps3syscon-master>python ps3_syscon_uart_script.py COM3 CXRF
>$ AUTH
Auth successful
>$ 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:0x20e2
>$
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
>$ becount
becount
Bringup : 4377 times
Shutdown: 2604 times
Power-on: 284day 00hour 25min 51sec
[mullion]$
>$ errlog
errlog
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[  0]:err_code:0xa0403034, clock:0xffffffff
ofst[  4]:err_code:0xa0403034, clock:0xffffffff
ofst[  8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
[mullion]$

In case anyone missed it here is the livestream where we got these codes.

He balls an RSX, which is a good video of it being done for any would be reballers out there. We exchanged tips and common pitfalls in chat. So this is a great video to watch for that alone.

...But I also walked him through the process of gaining internal SYSCON access and interpriting the code. So this is a super useful one to watch.

 

[RIP-Felix]

RIP-Felix can you please compare and add few cell vdd power line values? That wasn't inspect before and need to explain a low resistance in vdd line for cell, probably same situation as rsx.

Yeah, tonight I'll take some pics and measurments. But besides BE_VDDC at the tokins, CPU shares FlexIO (YC_RC_VDDIO) with RSX, Has PLL, and VDDA (YC_RC_VDDA) also shared with RSX. But RSX_VDDA is filtered. Both are fused before VDDA enters the chip. There are 2x 4-resistor arrays under the CPU. I forget off the top of my head what the Light blue is (check schematic). clock refrence voltage i know. and Black is PLL. Should read 60ohm for blue caps and black should read 100. RSX has a 4x resistor array for its clock refrence voltage too, between cell/rsx. They should be 60 ohms too.

Like I said, I'll add pics and descriptions tonight.

 

[vyktormvmpay25]

All those lower resistance under 2.5 ohms out of board or on board can affect vdd line tend to short vdd line while units will be on games passing 68 Celsius.
Value will start from 2.7 on board, seen it often, this must be minimal threshold for our mostfets in order to run normal.
I've found one cok001 today with 2 ohms cell. Board will start, image on screen, original nec on it. Something wierd right after syscon is checking fan speed, it is going bit up with speed straight away after that few seconds check.
Problems with it is later in games will fail with 2031 and isn't related to rsx. Board is telling somehow it is but measuring around rsx I get all fine for 40nm, vdd is 2.7 ohms and isn't rsx. That abnormal temperature error will come from cell side.
Seen this before when cell is low and will tell rsx error, that was exchanged with 65nm.
So when cell is lower then 2.5 ohms that cell is going to fail and suddenly dead.
I will try my improvements and I'll see what resistance is out on both and on board.
That resistance is always going to affect direct vdd power line and behave later when it is fully assembled for testing.
Even in one fixed cok001 I've got 40nm rsx 2 ohms, but on board somehow that was increased after recap up to 2.8 ohms.
Some rsx will behave strange out but on board it is nominal valve 2.7.
Felix hope you can understand and write it with better explanation than me, I'm not good with teaching/explaining.

 

[RIP-Felix]

All those lower resistance under 2.5 ohms out of board or on board can affect vdd line tend to short vdd line while units will be on games passing 68 Celsius.
Value will start from 2.7 on board, seen it often, this must be minimal threshold for our mostfets in order to run normal.
I've found one cok001 today with 2 ohms cell. Board will start, image on screen, original nec on it. Something wierd right after syscon is checking fan speed, it is going bit up with speed straight away after that few seconds check.
Problems with it is later in games will fail with 2031 and isn't related to rsx. Board is telling somehow it is but measuring around rsx I get all fine for 40nm, vdd is 2.7 ohms and isn't rsx. That abnormal temperature error will come from cell side.
Seen this before when cell is low and will tell rsx error, that was exchanged with 65nm.
So when cell is lower then 2.5 ohms that cell is going to fail and suddenly dead.
I will try my improvements and I'll see what resistance is out on both and on board.
That resistance is always going to affect direct vdd power line and behave later when it is fully assembled for testing.
Even in one fixed cok001 I've got 40nm rsx 2 ohms, but on board somehow that was increased after recap up to 2.8 ohms.
Some rsx will behave strange out but on board it is nominal valve 2.7.
Felix hope you can understand and write it with better explanation than me, I'm not good with teaching/explaining.

2031 sounds like it could be thermal monitor related. Clear errlog, bringup, then trigger ylod with 2031. After that use command disp_err. Post results here.

 

[vyktormvmpay25]

I'll post results for sure ,first ill try tomorrow to start full reball and recap as this has to be done and run more further test .To be honest not confident but ill give it a go to see what is happening.

 

[Gus21]

2031 sounds like it could be thermal monitor related. Clear errlog, bringup, then trigger ylod with 2031. After that use command disp_err. Post results here.

Hello, I'm looking to buy the PS3 Tantalizer - Beta Release (v0.3b) but I would like to know if it works without problems, I would like to know.

I have a PS3 BC Cechb01 that I bought on ebay, the ps3 arrived with some external damage, I added 11 tantalum Cell and 11 on the RSX, and the ps3 was not able to turn on, I did reflow without success, so I took the PS3 BC Cechb01 to an assistance technique, for repair but the technician informed that it would be necessary to add more capacitance in the processors that would make the attempt, I was confused since I had added 11x470 in Cell and 11x470 in RSX, I authorized such an attempt, a few days later the technician informed that the device is bad and it could not do anything.
Is this technical support bad, since I had added 5147 capacitance in Cell and 5147 capacitance in RSX?
Or they don't want to do the reballing on the ps3?

 

[RIP-Felix]

Hello, I'm looking to buy the PS3 Tantalizer - Beta Release (v0.3b) but I would like to know if it works without problems, I would like to know.

I have a PS3 BC Cechb01 that I bought on ebay, the ps3 arrived with some external damage, I added 11 tantalum Cell and 11 on the RSX, and the ps3 was not able to turn on, I did reflow without success, so I took the PS3 BC Cechb01 to an assistance technique, for repair but the technician informed that it would be necessary to add more capacitance in the processors that would make the attempt, I was confused since I had added 11x470 in Cell and 11x470 in RSX, I authorized such an attempt, a few days later the technician informed that the device is bad and it could not do anything.
Is this technical support bad, since I had added 5147 capacitance in Cell and 5147 capacitance in RSX?
Or they don't want to do the reballing on the ps3?

They probably didnt want to reball it. Most techs don't consider reballs worth the investment of time. It would cost the customer alot for the attempt with no guarintee of a positive result. Leads to more complaints than satisfied customers, so they don't bother.

I don't blame them. Reballing is one of, if not the highest tier of rework skill. Takes supreme confidence in technique and equipment to have sucess. And it's never cheap!

 

[Computer Booter]

Heres another Internal SYSCON Log I pulled just now.

CHECH-A01 came in for YLOD, I believe I pulled some "possible voltage tokin" errors, forget which ones so I replaced topside tokins on both cell/rsx side. The console lasted for about 6 months and returned with another YLOD which this time I pulled 3034 so I put it on my shelf. Today I pulled this:

rosoft Windows [Version 10.0.19041.1415]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Razer\Desktop\syscon\ps3syscon-master>python ps3_sycscon_uart_script.py COM3 CXRF
python: can't open file 'C:\\Users\\Razer\\Desktop\\syscon\\ps3syscon-master\\ps3_sycscon_uart_script.py': [Errno 2] No such file or directory

C:\Users\Razer\Desktop\syscon\ps3syscon-master>python ps3_syscon_uart_script.py COM3 CXRF
>$ AUTH
scopen response invalid
>$ AUTH
Auth successful
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
sum:0x0100
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ w 39fe 38 0f
w 39fe 38 0f
w complete!
[mullion]$
>$ r 39fe 02
r 39fe 02
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
38 0F
[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ AUTH
Auth successful
>$ 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]: 0xa0093004
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
>$ becount
becount
Bringup : 2586 times
Shutdown: 2395 times
Power-on: 175day 21hour 20min 40sec
[mullion]$

errlog
ofst[ 56]:err_code:0xffffffff, clock:0x0be1f36d  2006/04/26 09:01:33
ofst[ 60]:err_code:0xa0801701, clock:0x0be1f394  2006/04/26 09:02:12
ofst[ 64]:err_code:0xa0801601, clock:0x0be1f394  2006/04/26 09:02:12
ofst[ 68]:err_code:0xa08014ff, clock:0x0c23aa97  2006/06/15 05:20:23
ofst[ 72]:err_code:0xa0801701, clock:0x0c23aa97  2006/06/15 05:20:23
ofst[ 76]:err_code:0xa0403034, clock:0x0c23ac5b  2006/06/15 05:27:55
ofst[ 80]:err_code:0xa0403034, clock:0x0c23b1d8  2006/06/15 05:51:20
ofst[ 84]:err_code:0xa0801001, clock:0x0c3c5b47  2006/07/03 22:48:39
ofst[ 88]:err_code:0xa0801001, clock:0x0b49e0ba  2006/01/01 00:37:14
ofst[ 92]:err_code:0xa0093003, clock:0x0b49e0cb  2006/01/01 00:37:31
ofst[ 96]:err_code:0xa0801701, clock:0x0b4b0c30  2006/01/01 21:54:56
ofst[100]:err_code:0xa08014ff, clock:0x0b4b0c30  2006/01/01 21:54:56
ofst[104]:err_code:0xa0801601, clock:0x0b4b0c30  2006/01/01 21:54:56
ofst[108]:err_code:0xa0801701, clock:0x0b4b0e85  2006/01/01 22:04:53
ofst[112]:err_code:0xa08014ff, clock:0x0b4b0e85  2006/01/01 22:04:53
ofst[116]:err_code:0xa0801601, clock:0x0b4b0e85  2006/01/01 22:04:53
ofst[120]:err_code:0xa0093004, clock:0xffffffff
ofst[124]:err_code:0xa0093004, clock:0xffffffff
ofst[  0]:err_code:0xa0093004, clock:0xffffffff
ofst[  4]:err_code:0xa0093004, clock:0xffffffff
ofst[  8]:err_code:0xa0093004, clock:0xffffffff
ofst[ 12]:err_code:0xa0093004, clock:0xffffffff
ofst[ 16]:err_code:0xa0093004, clock:0xffffffff
ofst[ 20]:err_code:0xa0093004, clock:0xffffffff
ofst[ 24]:err_code:0xa0093004, clock:0xffffffff
ofst[ 28]:err_code:0xa0093004, clock:0xffffffff
ofst[ 32]:err_code:0xa0093004, clock:0xffffffff
ofst[ 36]:err_code:0xa0093004, clock:0xffffffff
ofst[ 40]:err_code:0xa0093004, clock:0xffffffff
ofst[ 44]:err_code:0xa0093004, clock:0xffffffff
ofst[ 48]:err_code:0xa0093004, clock:0xffffffff
ofst[ 52]:err_code:0xa0093004, clock:0xffffffff
>$

EDIT: After further probing and help from the community we were able to ascertain that the RSX was dead. (.4 ohm rating after removing all tokins on RSX side, possible RSX replacement? we shall see)

 

[vyktormvmpay25]

Heres another Internal SYSCON Log I pulled just now.

CHECH-A01 came in for YLOD, I believe I pulled some "possible voltage tokin" errors, forget which ones so I replaced topside tokins on both cell/rsx side. The console lasted for about 6 months and returned with another YLOD which this time I pulled 3034 so I put it on my shelf. Today I pulled this:

rosoft Windows [Version 10.0.19041.1415]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Razer\Desktop\syscon\ps3syscon-master>python ps3_sycscon_uart_script.py COM3 CXRF
python: can't open file 'C:\\Users\\Razer\\Desktop\\syscon\\ps3syscon-master\\ps3_sycscon_uart_script.py': [Errno 2] No such file or directory

C:\Users\Razer\Desktop\syscon\ps3syscon-master>python ps3_syscon_uart_script.py COM3 CXRF
>$ AUTH
scopen response invalid
>$ AUTH
Auth successful
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
sum:0x0100
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ w 39fe 38 0f
w 39fe 38 0f
w complete!
[mullion]$
>$ r 39fe 02
r 39fe 02
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
38 0F
[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ AUTH
Auth successful
>$ 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]: 0xa0093004
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
>$ becount
becount
Bringup : 2586 times
Shutdown: 2395 times
Power-on: 175day 21hour 20min 40sec
[mullion]$
>$

This is something with cell area again. Can you test resistance for caps those on cell side? Also if you can "errlog " command should bring 32 errors.
Edit
Also do what Felix say.
It is 3004 not 3034 in rrac area for communication between cell and rsx.

 

[RIP-Felix]

Heres another Internal SYSCON Log I pulled just now.

CHECH-A01 came in for YLOD, I believe I pulled some "possible voltage tokin" errors, forget which ones so I replaced topside tokins on both cell/rsx side. The console lasted for about 6 months and returned with another YLOD which this time I pulled 3034 so I put it on my shelf. Today I pulled this:

rosoft Windows [Version 10.0.19041.1415]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Razer\Desktop\syscon\ps3syscon-master>python ps3_sycscon_uart_script.py COM3 CXRF
python: can't open file 'C:\\Users\\Razer\\Desktop\\syscon\\ps3syscon-master\\ps3_sycscon_uart_script.py': [Errno 2] No such file or directory

C:\Users\Razer\Desktop\syscon\ps3syscon-master>python ps3_syscon_uart_script.py COM3 CXRF
>$ AUTH
scopen response invalid
>$ AUTH
Auth successful
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
sum:0x0100
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ w 39fe 38 0f
w 39fe 38 0f
w complete!
[mullion]$
>$ r 39fe 02
r 39fe 02
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
38 0F
[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ AUTH
Auth successful
>$ 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]: 0xa0093004
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
>$ becount
becount
Bringup : 2586 times
Shutdown: 2395 times
Power-on: 175day 21hour 20min 40sec
[mullion]$
>$

Yeah, 3004 is what happens when there is a complete RSX VRM power failure. Usually when tokins completly fail, or it could be the caps you installed. Remove and replace all RSX tokins first. Let's see what that does.

 

[RIP-Felix]

This is something with cell area again. Can you test resistance for caps those on cell side? Also if you can "errlog " command should bring 32 errors.

CELL vrm failure is 3003, he has 3004. So it's on RSX side (currently).

 

[Computer Booter]

errlog edited into previous post for that checha01

about to go live and work on some stuff, might get to this ps3 in a bit and check those tokins

 

[Gus21]

Hello, I'm looking to buy the PS3 Tantalizer - Beta Release (v0.3b) but I would like to know if it works without problems, I would like to know.

 

[Gus21]

Can anyone tell me if after reballing the ps3 works perfectly or is there problems?
I want to send for reballing another ps3 bc is it worth it?
I don't care about the reballing value.