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

Hello i have one question
i have some errorslogs that say A0802124, A0112024 and A0112124
I saw that can be the AV or HDMI encoders (i think), my question is, if i only use HDMI, can the problem be also in the AV encoder?
 
The DVE (digital video encoder) compresses the raw video bitstream into an HDMI compatible signal (encoding) and Analog AV, depending on which is being used. Then the encoded HDMI signal is sent to the HDMI transmitter, for transmitting to the TV.

An HDMI encoder is a term for 1 Chip that combines the encoding and transmitting functions. Since PS3 has to output both hdmi and analog AV, it has 2.

To answer your question, yes. It can be caused by either, or neither.

Post your full log.
 
Last edited:
Here is the errorlog, and thank you to reply, it helped a lot


>$ errlog
00000000
# CODE CLOCK
# A0802124 0B49D808
# A0801002 0B49D808
# A0802124 0B49D823
# A0801002 0B49D822
# A0802124 0B49D809
# A0802124 0B49D808
# A0801002 0B49D808
# A0802124 0B49D80A
# A0801002 0B49D809
# A0802124 0B4A1C59
# A0801002 0B4A1C59
# A0112024 0B4A0741
# A0112124 0B4A0740
# A0112124 0B4A0740
# A0112124 0B4A073F
# A0112124 0B4A073F
# A0112124 0B4A073E
# A0112124 0B4A073E
# A0112024 0B4A073D
# A0112124 0B4A073D
# A0112124 0B4A073C
# A0112124 0B4A073C
# A0112124 0B4A073B
# A0112124 0B4A073B
# A0112024 0B4A073A
# A0112124 0B4A073A
# A0112124 0B4A0739
# A0112124 0B4A0739
# A0112124 0B4A0738
# A0112124 0B4A0738
# A0112124 0B4A0737

>$ shutdown
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

RIP-Felix said:
The DVI (digital video encoder) compresses the raw video bitstream into an HDMI compatible signal (encoding) and Analog AV, depending on which is being used. Then the encoded HDMI signal is sent to the HDMI transmitter, for transmitting to the TV.

An HDMI encoder is a term for 1 Chip that combines the encoding and transmitting functions. Since PS3 has to output both hdmi and analog AV, it has 2.

To answer your question, yes. It can be caused by either, or neither.

Post your full log.
Click to expand...
 
saseca said:
Here is the errorlog, and thank you to reply, it helped a lot


>$ errlog
00000000
# CODE CLOCK
# A0802124 0B49D808
# A0801002 0B49D808
# A0802124 0B49D823
# A0801002 0B49D822
# A0802124 0B49D809
# A0802124 0B49D808
# A0801002 0B49D808
# A0802124 0B49D80A
# A0801002 0B49D809
# A0802124 0B4A1C59
# A0801002 0B4A1C59
# A0112024 0B4A0741
# A0112124 0B4A0740
# A0112124 0B4A0740
# A0112124 0B4A073F
# A0112124 0B4A073F
# A0112124 0B4A073E
# A0112124 0B4A073E
# A0112024 0B4A073D
# A0112124 0B4A073D
# A0112124 0B4A073C
# A0112124 0B4A073C
# A0112124 0B4A073B
# A0112124 0B4A073B
# A0112024 0B4A073A
# A0112124 0B4A073A
# A0112124 0B4A0739
# A0112124 0B4A0739
# A0112124 0B4A0738
# A0112124 0B4A0738
# A0112124 0B4A0737

>$ shutdown
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
Click to expand...

Focus on the 1002 error for now, the 2124 is likely associative, a by product of the 1002 (RSX filter, likely tokins).
joe musashi said:
hello what is the newest version of your RIP-FELIX Tantalizers
Click to expand...
Bookmark this or follow the link in my signature. I keep that post updated.
 
Good afternoon, I'm having difficulty after using the crxf command and confirming the auth successfully, when typing the eepcsum command I'm getting this message, what should I do?
upload_2024-7-6_14-6-33.png

C:\Python27\Scripts>PYTHON C:\Python27\Scripts\PS3_Syscon_(Mullion_Sherwood)_script.py COM4 CXRF
> AUTH
Auth successful
> eepcsum
Traceback (most recent call last):
File "C:\Python27\Scripts\PS3_Syscon_(Mullion_Sherwood)_script.py", line 190, in <module>
main(len(sys.argv), sys.argv)
File "C:\Python27\Scripts\PS3_Syscon_(Mullion_Sherwood)_script.py", line 187, in main
print(ret[1][0].decode('ascii'))
^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'decode'. Did you mean: 'encode'?
C:\Python27\Scripts>
upload_2024-7-6_14-6-33.png
upload_2024-7-6_14-6-33.png
 
try installing pycryptodome (without the x). I see you're using python2.7 and the current tutorial suggests installing pycryptodomex, but with 2.7 you need the other version.
 
RIP-Felix said:
try installing pycryptodome (without the x). I see you're using python2.7 and the current tutorial suggests installing pycryptodomex, but with 2.7 you need the other version.
Click to expand...
I have the latest version of Python installed, only now that you mentioned it did I realize it's running on 2.7, I'll try what you said tomorrow and get back to you if it works.

RIP-Felix said:
try installing pycryptodome (without the x). I see you're using python2.7 and the current tutorial suggests installing pycryptodomex, but with 2.7 you need the other version.
Click to expand...

I redid the process using python version 3.12, and installed the following:

pip install pyserial
pip install pycryptodomex
pip install pycryptodome

I'm still getting this error, what else can I do?

C:\Python312\Scripts>python C:\Python312\Scripts\PS3_Syscon_(Mullion_Sherwood)_script.py COM4 CXRF
>AUTH
scopen response invalid
>AUTH
Auth successful
>eepcsum
Traceback (most recent call last):
File "C:\Python312\Scripts\PS3_Syscon_(Mullion_Sherwood)_script.py", line 190, in <module>
main(len(sys.argv), sys.argv)
File "C:\Python312\Scripts\PS3_Syscon_(Mullion_Sherwood)_script.py", line 187, in main
print(ret[1][0].decode('ascii'))
^^^^^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'decode'. Did you mean: 'encode'?
 
Last edited by a moderator:
is that the only command that causes that traceback error? Because it looks like you are auth'd into internal mode and it's ready for the commands. I can't see how that one command could cause a traceback and nothing else would.
 
RIP-Felix said:
is that the only command that causes that traceback error? Because it looks like you are auth'd into internal mode and it's ready for the commands. I can't see how that one command could cause a traceback and nothing else would.
Click to expand...

all subsequent commands do not work, in external mode yes, in internal mode I managed to get to the point where it emits 3 beeps due to the incorrect sum. Using the ps3uart gui I managed to work the first time, and I got these errlogs, based on my experience with the 3034, it would be a BGA defect on the RSX, but I'm selling a 2120 there related to HDMI, but from what I've read, this error is also related to the lack of rsx communication with the correct hdmi c.i.? What I think?

ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xa0202120, clock:0xffffffff
ofst[124]:err_code:0xa0202120, clock:0xffffffff
ofst[ 0]:err_code:0xa0202120, clock:0xffffffff
ofst[ 4]:err_code:0xa0202120, clock:0xffffffff
ofst[ 8]:err_code:0xa0202120, clock:0xffffffff
ofst[ 12]:err_code:0xa0404402, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0202120, clock:0xffffffff
ofst[ 24]:err_code:0xa0202120, clock:0xffffffff
ofst[ 28]:err_code:0xa0202120, clock:0xffffffff
ofst[ 32]:err_code:0xa0202120, clock:0xffffffff
ofst[ 36]:err_code:0xa0202120, clock:0xffffffff
ofst[ 40]:err_code:0xa0202120, clock:0xffffffff
ofst[ 44]:err_code:0xa0202120, clock:0xffffffff
ofst[ 48]:err_code:0xa0202120, clock:0xffffffff
ofst[ 52]:err_code:0xa0202120, clock:0xffffffff
ofst[ 56]:err_code:0xa0202120, clock:0xffffffff
ofst[ 60]:err_code:0xa0404402, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0202120, clock:0xffffffff
ofst[ 72]:err_code:0xa0202120, clock:0xffffffff
ofst[ 76]:err_code:0xa0202120, clock:0xffffffff
ofst[ 80]:err_code:0xa0202120, clock:0xffffffff
ofst[ 84]:err_code:0xa0202120, clock:0xffffffff
ofst[ 88]:err_code:0xa0202120, clock:0xffffffff
ofst[ 92]:err_code:0xa0202120, clock:0xffffffff
ofst[ 96]:err_code:0xa0202120, clock:0xffffffff
ofst[100]:err_code:0xa0202120, clock:0xffffffff
ofst[104]:err_code:0xa0202120, clock:0xffffffff
ofst[108]:err_code:0xa0404402, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff

before I forget that there is some command responsible for showing the current version of the system?
 
Last edited by a moderator:
Do not use the gui.

  1. turn off and unplug
  2. connect rx/tx.
  3. connect the GND on your UART adaper to the GND on the PS3 (not diag)
  4. power into standby
  5. Attempt to auth back into external mode.
  6. double check that the internal access byte is enabled while your here. I'm sure it is, but you know...dotting i's and crossing t's.
  7. power off. unplug power. close the script.
  8. connect diag to ground. Keep your uart adaper grounded to the ps3 gnd. Just also ground diag.
  9. power into standby.
  10. open the uart script and attempt to auth into internal mode.
  11. profit
about your questions. 2120/2124 are red-herrings. Associatve, also occur codes, can accompany more diagnostic ones. The 3034 is the diagnostic code here and the 2120's is likely incidental to it.

I don't remember what model ps3 you have, but if it's a 90nm RSX it's likely bumps, not BGA. Unless you have evidence of a BGA defect, such has positive pressure test (responds to light flexing or pressure). If you see drop damage it could be BGA. If it was delided damage it could be trace damage.

If you have to reball, you may as well replace with a 65 or 40nm model that doesn't have this sort of defect. It's not much more work.

If you can't do this sort of rework then this is the end of the line.
 
This ps3 is a cechc04, tomorrow I'm going to do the pressure test, to see if the device works. when you refer to bumps and not bga what exactly does it mean? Sorry, I use the translator to communicate, maybe I didn't understand.
 
The controlled collapse chip connection, the tiny balls connecting the die to the interposer. The underfill used (namics 8439-1) to protect this bond was poorly chosen for the brittle solder type used (high lead).
 
RIP-Felix said:
The controlled collapse chip connection, the tiny balls connecting the die to the interposer. The underfill used (namics 8439-1) to protect this bond was poorly chosen for the brittle solder type used (high lead).
Click to expand...

good afternoon,
I managed to connect to the syscon using your YouTube video.
The errlog obtained is the same as what I obtained through the GUI, I observed that the sequence of errors is the same 3034/4402 and 10x 2120, as you said this 2120 are false clues, but I saw through ps3devwiki that 10 combinations of error A0202120 may be related to VDDIO.
Anyway, I'm looking for a 40nm RSX to replace, it's difficult to find here in Brazil.
 
birigui said:
...10x 2120, as you said this 2120 are false clues, but I saw through ps3devwiki that 10 combinations of error A0202120 may be related to VDDIO.
Click to expand...
look for a coresponding diagnostic code with the 10x 2120. That's what makes it a combo. Something like 3013. If the number is always 10x and there's an associated code, then it cound be something else, or still the GPU. VDDIO is just the RSX I/O voltage, one of its dependent sub systems. VRAM and other things can cause it.

But IIRC I counted 11x 2120's in your log. So it's not the 10x combo. I reccomended following that 3034 1st because it's the most diagnostic code and the GPU ossue is the most common cause.

So fix the GPU 1st and you'll probably find it fixes everything. If not, then you trank down the next issue.
Anyway, I'm looking for a 40nm RSX to replace, it's difficult to find here in Brazil.
Click to expand...
You have to harvest them from slims. Allmost all the loose ones have been bought up. And if they are availavle, they are piss poor pulls and likely destroyed in the process. So find yourself a slim to harvest from, preferrable one with issues that make you feel better about stealing it's GPU.
 
3000s and 4000s might be good donors - IIRC a few of the 1st generation superslims still had 40nm chips (MSX and MPX mainboards specifically). I figure 2500s and 2100s have already been bought up, while usually 3000 and early 4000s are usually left aside due to being HEN/HFW capable only, as opposed to CFW.
 
Last edited:
I don't reccomend harvesting from slims before 30xx model, since they can be jailbroken. Especially not the 21xx, which is the most reliable model.
 
That's why I pointed to the 3000s and 4000s. Since people avoid those due to them not being able to do full CFW (only HEN), they're more easier to find than 2100 and 2500 stocks, which might have already been depleted.

I suppose the early 4000 RSX (CXD5302) having no IHS... is a plus?
 
Last edited:
There's no shortage of 25xx slims. There haven't been people harvesting GPU for long enough and even if every single backwards compatible model did have it's GPU replaced, it would hardly make a dent in the shear numbers of slims made.
 
You must log in or register to reply here.

Similar threads

Back
Top