Or a bad BGA on RSX, see my early posts in this thread.
PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
When I changed NEC to tantalum I don't touched the RSX too and I got error 3034
db260179
Member
Before putting the tantalum caps on, you need to check what rating they give out. Remember that NEC tokins when new give a 2000uf rating per tokin or there abouts, these cheap chinese tantalums barely give 330uf if rated at 470uf. So given this issue, get a new nec tokins and put them back. A simple test if you can is get some 1000uf caps and put them on too see if it fixes this issue.
An oscilliscope will show you how bad they are at filtering.
An oscilliscope will show you how bad they are at filtering.
Anyway i'm waiting for flux, i think tomorrow or tuesday will arrive. So i need a reflow on boot chip or just a check on nec/tokin? Because to delid i used an heat gun to soften the adhesive maybe the tokin gone bad? Or i dried the solder under the chip and then using force i broke some balls (i didn't use too much heat so maybe not)? I know that when heat is used the situation get tricky
Andre Cesar
Member
Senhores estou com meu PS3 sem energia o mesmo não está ligando a luz vermelha se alguém tiver material para fazer os testes primários vai ser de grande ajuda estou desmontado ele não tenho ferramentas de medição de energia sou leigo em manutenção desde já agradeço pela ajuda
ENGLISH
Gentlemen, I have my PS3 without power, it is not turning on the red light if someone has material to do the primary tests, it will be of great help. I am disassembled. I do not have energy measurement tools.
ENGLISH
Gentlemen, I have my PS3 without power, it is not turning on the red light if someone has material to do the primary tests, it will be of great help. I am disassembled. I do not have energy measurement tools.
Last edited by a moderator:
por favor, escreva em inglês
db260179
Member
OK, good luck, take your time and re trace your steps back, make sure to do some voltage checking on the nec tokins.
db260179
Member
You will need a multimeter ESR preferably, no way around this?
Do a simple short to ground test on the +12v and GND pins, you didnt mention what PS3 you have.
And also this thread is not for this kind of discussion. Post a new thread in the main forum!
Do a simple short to ground test on the +12v and GND pins, you didnt mention what PS3 you have.
And also this thread is not for this kind of discussion. Post a new thread in the main forum!
Whatever happens to the caps can only be measured under load in circuit. Every one I've pulled, including the ones that I verified with scope to be bad then changed out and verified a fix, all tested fine out of circuit. No loss of capacitance or changed ESR. So, you just kinda have to cross your fingers that your new caps are good. Remember I had one batch of name brand bought new from Mouser that were bad.
Last edited:
No mínimo você deve ter um voltímetro/multímetro, porém é alta a probabilidade de ser a fonte.
You need a voltmeter at minimum. It could be the power supply.
CodeKiller
Member
Well, sad to report the PS3 resurrected a while back died again, even with more aggressive fantables 
These were the errors saved while dyeing (clock bad, dont know why not synced from inet):
then the usual BitTraining error:
These were the errors saved while dyeing (clock bad, dont know why not synced from inet):
Code:
ofst[ 96]:err_code:0xa0801701, clock:0x0b939523 2006/02/25 22:22:27
ofst[100]:err_code:0xa0801601, clock:0x0b939523 2006/02/25 22:22:27
ofst[104]:err_code:0xa0801802, clock:0x0b939546 2006/02/25 22:23:02then the usual BitTraining error:
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
> version
[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]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
version
v1.1.3_k1
[mullion]$CodeKiller
Member
If the caps are bad they would produce different errors in the errorlog, as that would cause the regulator(s) to send power_fail signal to the syscon causing it to also shutdown all power.
db260179
Member
Looking at the comment from LSL, it appears there is an issue with CELL.
So in this case your correct. Most likely damaged an area near the CELL chip.
So in this case your correct. Most likely damaged an area near the CELL chip.
db260179
Member
These errors you are getting are related to data errors on the bus.
The reflow from a preheater usually fixes this on the RSX chip.
Its also possible the RSX chip is dieing slowly, if you are getting a 1.5 or below ohms reading, its on its way out.
The reflow from a preheater usually fixes this on the RSX chip.
Its also possible the RSX chip is dieing slowly, if you are getting a 1.5 or below ohms reading, its on its way out.
Well, sad to report the PS3 resurrected a while back died again, even with more aggressive fantables
These were the errors saved while dyeing (clock bad, dont know why not synced from inet):
Code:ofst[ 96]:err_code:0xa0801701, clock:0x0b939523 2006/02/25 22:22:27 ofst[100]:err_code:0xa0801601, clock:0x0b939523 2006/02/25 22:22:27 ofst[104]:err_code:0xa0801802, clock:0x0b939546 2006/02/25 22:23:02
then the usual BitTraining error:
Code:> [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS [ERROR]: 0xa0404402 [ERROR]: 0xa0403034 [POWSEQ] PowerSeq_Letup called. [SSM] state: 0700 -> 0600 (PowerOff State) (Fatal) version v1.1.3_k1 [mullion]$
chiefhunnablunts
Member
Hello, I'm pretty new to all of this. Python, Ubuntu, soldering, pretty much everything.
I've had two successful repairs with tantalum cap replacements. However, I have a CECHE that's proving to be quite problematic. I was told from a Reddit thread that I should follow this thread and diagnose my problem before replacing components. In hindsight, they were right, and it seems that I was just lucky with my previous two repairs. I digress.
On this particular unit, I replaced the capacitors, and was able to get it to boot to the XMB to see that the previous owner installed CFW before it promptly YLOD again. I replaced the last two caps and bridged it, all to no avail. Now, I've dual booted Ubuntu on my beater laptop and was able to talk to my PS3 and fortunately pulled the error logs. There's only two that showed up, neither have dates attached to it.
Now, I have no idea what the 0202120 error is, but from what I've read through this thread, 0213013 indicates a dead cell, correct? Initially it wasn't on the table of error logs.
Now, I have the service manual and power point diagram pulled up, and if I'm being 100% completely honest here, I have no idea how to accurately read voltage on a PCB. I apologize if this seems so incredibly basic, however, I was a cook before all of this. I can work a hot line, yet can't accurately read voltage lmao. Could anyone possibly tell me what I'm doing wrong? Or to more accurately put it, tell me what I need to be doing here?
I've had two successful repairs with tantalum cap replacements. However, I have a CECHE that's proving to be quite problematic. I was told from a Reddit thread that I should follow this thread and diagnose my problem before replacing components. In hindsight, they were right, and it seems that I was just lucky with my previous two repairs. I digress.
On this particular unit, I replaced the capacitors, and was able to get it to boot to the XMB to see that the previous owner installed CFW before it promptly YLOD again. I replaced the last two caps and bridged it, all to no avail. Now, I've dual booted Ubuntu on my beater laptop and was able to talk to my PS3 and fortunately pulled the error logs. There's only two that showed up, neither have dates attached to it.
Now, I have no idea what the 0202120 error is, but from what I've read through this thread, 0213013 indicates a dead cell, correct? Initially it wasn't on the table of error logs.
Now, I have the service manual and power point diagram pulled up, and if I'm being 100% completely honest here, I have no idea how to accurately read voltage on a PCB. I apologize if this seems so incredibly basic, however, I was a cook before all of this. I can work a hot line, yet can't accurately read voltage lmao. Could anyone possibly tell me what I'm doing wrong? Or to more accurately put it, tell me what I need to be doing here?
db260179
Member
Hi and welcome to the ps3 syscon revival group!
Dont worry about being a pro, you have passed the first few tasks, and used common sense and logic so far.
Like everything in life, you gain experience over time.
So on the first page of this thread there is my github rep (https://github.com/db260179/ps3syscon), that has the 'syscon error codes.pdf'
This has near or matching areas to look at based on the error.
So your first error is 'hdmi error' and second is the 'Cell issues'
Based on your model, it should be a COK-002 board. - In that same github repo, there is testpoints pics for that model of motherboard.
You will need to have a multimeter - this is essential tool for any budding electronics repairer
It slow and labories, but you will need to check every voltage test point to see what is showing wrong values.
A pro tip on determining if the cell is completely dead, measure the resistance on the nec tokins next to the cell - GND and Positive
Resistance usually reads about 1.8 ohms and above, anything lower or really low like 0.2, means a short or dead cell. Also one more place under the board - the capacitors grouped around the cell
https://imgur.com/a/ZGua2Ef
Make sure they are reading other than 0.2 - 0.4 ohms, usually 2K or more
Caps and resistors are notorious for going short and when touching things by mistake will make them go boom.
Hope this helps? and come back if u have anymore info? - voltage outputs etc
Dont worry about being a pro, you have passed the first few tasks, and used common sense and logic so far.
Like everything in life, you gain experience over time.
So on the first page of this thread there is my github rep (https://github.com/db260179/ps3syscon), that has the 'syscon error codes.pdf'
This has near or matching areas to look at based on the error.
So your first error is 'hdmi error' and second is the 'Cell issues'
Based on your model, it should be a COK-002 board. - In that same github repo, there is testpoints pics for that model of motherboard.
You will need to have a multimeter - this is essential tool for any budding electronics repairer
It slow and labories, but you will need to check every voltage test point to see what is showing wrong values.
A pro tip on determining if the cell is completely dead, measure the resistance on the nec tokins next to the cell - GND and Positive
Resistance usually reads about 1.8 ohms and above, anything lower or really low like 0.2, means a short or dead cell. Also one more place under the board - the capacitors grouped around the cell
https://imgur.com/a/ZGua2Ef
Make sure they are reading other than 0.2 - 0.4 ohms, usually 2K or more
Caps and resistors are notorious for going short and when touching things by mistake will make them go boom.
Hope this helps? and come back if u have anymore info? - voltage outputs etc
Last edited:
chiefhunnablunts
Member
Hello, thanks db for the info.
Pardon the late response. I've been tinkering around with a little garbo build of a PC for the past few days and switched over to a new system Now, I've set that particular board aside for another time. It's a little frustrating and time consuming so I've gotta be in the right head space for it.
Now, I fully repaired a board recently. The NEC TOKINS and BR laser assembly was replaced and it's back to it's former glory; CECHE. I'm now working on another CECHE, however this particular one is the MG. It was giving me a hard time when replacing the BR laser assembly and YLOD during boot. I got into it, authorized myself into internal. However, when I go and run the CXRF, I keep getting various ascii errors regularly, and if I'm lucky, I'll get "scopen response invalid". The python error usually looks something like this:
Now, like I've said, I've verified that I am in fact in internal. I've run the "EEP GET 3961 01" and the response is all zeros. The RxD, TxD and GND are all in their proper respective places on the board. The ascii error has variations, but usually look something like that, aside from the "byte 0xeXX" line.
For reference I'm running Ubuntu 20.04, using python 2.7 with crpyto and serial modules, both verified for proper installation.
Any sort of help would be much appreciated. I'm very, very close to having this unit fully repaired. Just at this last little hiccup.
Pardon the late response. I've been tinkering around with a little garbo build of a PC for the past few days and switched over to a new system Now, I've set that particular board aside for another time. It's a little frustrating and time consuming so I've gotta be in the right head space for it.
Now, I fully repaired a board recently. The NEC TOKINS and BR laser assembly was replaced and it's back to it's former glory; CECHE. I'm now working on another CECHE, however this particular one is the MG. It was giving me a hard time when replacing the BR laser assembly and YLOD during boot. I got into it, authorized myself into internal. However, when I go and run the CXRF, I keep getting various ascii errors regularly, and if I'm lucky, I'll get "scopen response invalid". The python error usually looks something like this:
Now, like I've said, I've verified that I am in fact in internal. I've run the "EEP GET 3961 01" and the response is all zeros. The RxD, TxD and GND are all in their proper respective places on the board. The ascii error has variations, but usually look something like that, aside from the "byte 0xeXX" line.
For reference I'm running Ubuntu 20.04, using python 2.7 with crpyto and serial modules, both verified for proper installation.
Any sort of help would be much appreciated. I'm very, very close to having this unit fully repaired. Just at this last little hiccup.
db260179
Member
Np, yes you need a clear head for this kind of stuff.
So regards your issue, not sure if you have missed a step? but the diag pin needs to be connected to the gnd lead for internal mode to work. also this type of issue occurs randomly, so just make sure the leads are connected well.
main thing is to have the diag pin on the gnd lead. switch off ps3, connect diag to gnd turn on give it a minute, then run python script, auth
So regards your issue, not sure if you have missed a step? but the diag pin needs to be connected to the gnd lead for internal mode to work. also this type of issue occurs randomly, so just make sure the leads are connected well.
main thing is to have the diag pin on the gnd lead. switch off ps3, connect diag to gnd turn on give it a minute, then run python script, auth
chiefhunnablunts
Member
So, my process goes as follows:
- Solder RxD, TxD to respective pins, cover with kapton tape and then electrical tape
- Attach GND to ground point. In this instance, I used the exposed edge of the PCB
- Power board
- Run Python script in CXR
- auth -> auth successful
- EEP GET 3961 01 -> 00000000 FF
- EEP SET 3961 01 00
- EEP GET 3961 01 -> 00000000 00
- Power off
- Solder GND to DIAG
- Power board
- No flicker, just RLOD with three beeps (even on the first time. This didn't happen on the last board I diagnosed, flickered as per usual)
- Run Python script in CXRF
- I either get "scopen response invalid" or various "ascii...decode bye 0xXX" error
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
-