PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

Cypha said:
Kid… im 27 your mad that we fixed the issue before you and hmmm you wanna know why it's because my friends friend knows ken and he admitted its the rsx reason why he left sony as he couldnt cope with the issue but since hes been working on robots hes been kindly enought to give us documents of what the e3 2005 ps3 and how the old cooling was going to be like as as u saw in e3 as there was only one vent and that was on the side and disk tray was at the top rather on the bottom, he literally gave us the full documents and how everything was made a processed and most of all we been able to have the concept design and its incredibly better than the 60gb
Click to expand...

LOL. Weren't you going to post pictures?
 
images
 
i mean, it does sound interesting… the rsx is a modified nvidia gt70, and that (Im guessing?) well known. You'd have to trick the syscon into accepting the replacement, but that too has been done. Next you have to get it to talk to cell and do the proper calibrations we've learning about recently. And last but not least, you'd have to deal with api compatibility. I'm sure others can think of additional obstacles to be overcome.

So… is this GO a g70 with some kind of in between to replace missing rsx functionality? This has definitely made us curious.
 
marciolsf said:
i mean, it does sound interesting… the rsx is a modified nvidia gt70, and that (Im guessing?) well known. You'd have to trick the syscon into accepting the replacement, but that too has been done. Next you have to get it to talk to cell and do the proper calibrations we've learning about recently. And last but not least, you'd have to deal with api compatibility. I'm sure others can think of additional obstacles to be overcome.

So… is this GO a g70 with some kind of in between to replace missing rsx functionality? This has definitely made us curious.
Click to expand...

He showed zero proof of even a fraction of what he has written here so far.
 
I was on his steam hes a legend im cypha im sure youve seen me aha anyways ive got the photos waiting for approval as ive posted them

Thats why hes done something similar to the einstien mod to get the rsx to see it etc thats why hes annoncing it after all these years as he gave up and left it for what better stuff comes out in the future as back then it was harder but since this einstein mod has came out hes fingured it out
 
Last edited by a moderator:
Cypha said:
Thats why hes done something similar to the einstien mod to get the rsx to see it etc thats why hes annoncing it after all these years as he gave up and left it for what better stuff comes out in the future as back then it was harder but since this einstein mod has came out hes fingured it out
Click to expand...

Pictures are coming this week?
 
There is no way anyone is able to do this. RSX is a black box. No publically available datasheets or hardware installation guides. No techical documentation besides similar G70 designs. The fact it's based on those GPU's actually makes researching the RSX harder because of the trash heap of Video card marketing, testing, and comparisons. There is much more available information about the CELL.

The nail in the coffin is the fact you can't reverse engineer it without having priveleged NDA protected information. You would have to copy the RSX FW, because the SB/CELL/SYSCON are expecting it to respond exactly the same. You cant RE this programming in a way that would mimic the same functions, not in a way that the chipset is expecting. Certainly not with a "clean room" design. In other words, it's illegal to make and sell. If anyone tried, Nvidia/SONY would take it down.

And we're talking about the highest complexitey of electronig design - actual silicon dies. The wafer costs alone preclude this type of "mod". This only makes sense for large companies doing large production runs.
 
vyktormvmpay25 said:
atm im helping here live stream
Yup fixed!
Click to expand...
I didn't have a chance to check out much of that stream yesterday. I popped in for a minute or two, but had to run. Before I rip into him, let me just say it's one thing to keyboard warrior the guy with hindsight being 20/20, and completly anopther thing to host a 14-hour live stream and performing in the moment. So mad respect for him and victor working it out in real time!!!

Anyway, I decided to throw it on tonight and crack open a 6-pack. Let the ripping commence...

1-brew in:
Didn't know you could isolate the MOSFET by removing shunt resistors 1-by-1. Makes sense tho. Good trick! Super useful, I'm going to have to remember that! But I'm going to have to agree with one of the commentators who suggested injecting 12V from the start and seeing what get's hot on a thermal cam. Would've save a lot of time. But I'm acytually glad he didn't do that. This way people get to see what the alternative method is. Isolating the short by one circuit at a time by removing caps, resistors, and fuses. Checking voltages, resistances and basic troubleshooting with a multimeter. That's more accessible for the average Joe.

2-brew's in:
Never seen the issue he had with the standby LED taking a long time to go solid red. Sometimes it would go to a blinking Standby LED. Issues with standby shouldn't be caused by the tokins, but it stopped after he removed them. Of course went to a instant YLOD, but didn't give issues with standby anymore. We do know that the CPU filter is more of an enigma, that 1001 errors are associated with many issues. In this case they did "appear" to be tokin related, but he also messes with that buck converter which didn't appear to be seated correctly after replacing it the first time. I suspect that had more to do with it. Now if the Buck Converter shorts 12V to the Tokins, they'll act as a fuse and burn out because they're only rated for 2.5v. I don't know if they will fail short or open, but the resistance was fine when he checked them, so it didn't look like there was anything wrong with them. But the NEC/TOKINs have a reputation and he changed them a bit prematurely IMO. Which is why he got the same result after installing the tantalums - that buck converter wasn't seated correctly.

Now failing tokins could cause the buck converters to work harder to supply voltage, and perhaps cause this issue. But I doubt that's actually what was going on here. I'd need to see the initial errorlog before he started all of these tests. The error history would tell the real story. But we didn't see that in the video. IDK if he dumped them earlier or not. Anybody know what handle he goes by on the forum, I'm curious if he saved the logs before starting work?

3-brews in:
Installs the tantalums. I's suggest a chissel tip exacto knife for those topside tokins. And he's definitely going to want to put better caps on that console long term. Those yellow AVX caps have too high an ESR. If he wants a repeat of what happened before that's a good way to get it! Low ESR processor decoupling caps are more efficient. Console won't have to work so hard, or hot.

4-brews in:
Finally gets back to that buck converter. Tests and...it works! Pretty sure that's what it was. I can't rule out the possability that the tokions were bad and caused the buck to go bad. Congratz... to both computerbooter and Victor for figuring it out real time. I'd consider 3 hours on this a win. That's not bad at all.

BTW: $250 for a Reball, tokin recap, and delid is a pretty good price. I'd consider that! Man it's a LOT of work...lol! I can commiserate! I don't think

5-bruisin:
Never mind, I found his thread here.

He mentioned in passing he'd like to buy a "shit ton" of the Orbis mod and offer them for sale in the US. I think that's a great idea!!! And I think $25-30 a piece is more than fair price for 1. I bought 5x for $100 shipped to the US after the gal On Fiverr took her cut ($20 ea.). I'm sure @botakompong would be willing to do a wholesale deal with someone who's willing to buy a medium run. He should totally make this happen! We gotta get the word out about this mod!!! It's effin AWESOME!

6-bruz-in :
Well, looks like it's all Amiga from here on out, so I think I'm gonna finish my sixer while winding the weekend down. Then call it a night...

PS: this guy earned my like and sub!
 
LOL that was super enjoyable to read, I don't think i've ever been "critiqued" before, thank you for that haha.

I am going to have to invest in some chisel tip exacto's for the NEC removal, also do you think that these caps are better than the AVX ones, or at least good enough to install in the PS3's?

I went ahead and ordered x100 Orbis chips today, lets hope they arrive LOL, I've been referred by vyktor to another user to make the purchase and have already completed payment.

Thanks for the sub and the watch, I greatly appreciate the support and I hope to be of service to the community in any way I can!
 
It is fine to have all people support. I was confident he was done a good reball. It was kind same situation with my first reball Frankenstein after many years, after few days I had to recap totally. Well for further tests and improvement he has to take and practice all around informations around here. Didn't really want to go on all over so I've focused on that issue. Just a test even if I don't like those yellow caps. As for install he may get one of that paint knife utility set and for better quality and design he will check
https://oshpark.com/profiles/RIP-Felix
For tantal caps new Panasonic are quite expensive, slim ps3 scrap boards have best tantal caps, ps4 ar s**t.
All 24 caps need to be tested before installation, if any less than 472 uF don't use, a internal resistance of each is also key to understand things.
 
Last edited:
Yeah, Victor is right. Phat PS3's have a few Panasonic's that are good. Slim models have more. So that's the cheapest route, if u have the donors just take those.

Otherwise, I recommend Panasonic decoupling caps in my Tantalizer release post. I linked to digikey or mouser, but you can check prices at other vendors. But I don't reccomend ali express or e-bay. Those are a crap shoot. Either they weren't good enough to be sold to the reputable distributors, they were left over from production runs, or they're counterfit. You never know.
 
@SkaziChris @RIP-Felix
Hello, I have a Ver-001 console with GLOD(removed hdd, eject button works, power button doesnt respond after turning it on (fans don't ramp up, doenst shut down) with A0802024 (ERR 00-ERR 09) but seems to have had at some point A0112124 (ERR10-ERR19) some kind of error in power up sequence. What do you recommend I do, I see you are dealing with a similar issue, also for hdmi chip and av chip, Aliexpress/eBay any luck or full of fakes and overpriced and only chance donor boards? Thank you
 
Kostaslgr7 said:
@SkaziChris @RIP-Felix
Hello, I have a Ver-001 console with GLOD(removed hdd, eject button works, power button doesnt respond after turning it on (fans don't ramp up, doenst shut down) with A0802024 (ERR 00-ERR 09) but seems to have had at some point A0112124 (ERR10-ERR19) some kind of error in power up sequence. What do you recommend I do, I see you are dealing with a similar issue, also for hdmi chip and av chip, Aliexpress/eBay any luck or full of fakes and overpriced and only chance donor boards? Thank you
Click to expand...
Please post the full errorlog and the info the SYSCON spits out during a bringup cmd (hint, press enter after the string stops and it'll spit out more).

The GLOD makes me suspect the RSX VRAM. @Computer Booter , you may be interested in this too, since this is how you can tell if an RSX is good or not (I noticed you're only ohm testing VDDC, but it's often the PLL or FBVDDQ voltage lines that die). Measure resistance all 7 RSX voltages...

RSX Pinout RSX View.jpg


When the RSX is off the board use these test points (just to keep them comparable)...
RSX Ohm Test Points.jpg
RSX Ohm Test Results (40nm vs 90nm).JPG

When installed on the MB you can test these too...
COK-001_MB_Ohm_Test_points.jpg

The SMD's on the MB around the outside of the RSX may be different, but there should be spot you can measure from since the RSX pinout are the same for 90/65/40nm. You'll have to use some deductive reasoning to find the right spot to measure the voltage line.

My guess is that FBVDDQ is low (Should be ~166 ohms for a 65nm RSX). Alternatively, the PLL could be low (should be ~400KOhms for 65nm).

@Computer Booter I saw in one of your recent streams that you have a 65nm RSX ready to be installed. I only have measurements for one 65nm RSX (the one used to fill in the chart above). If you could measure those and post to the forum that would help confirm those measurements. You can do this for all RSX's before installing, to be sure it's good. This is how you vet RSX's purchased on ali express or e-bay BTW.

Also, if you have any working 90nm, 65nm, & 40nm motherboards, we need the same measurements, but when the RSX is installed on the MB. This way we know what they are supposed to measure (on the board) and can easily identify when one of those voltages are bad. It'll make diagnosing much easier.
 
Last edited:
RIP-Felix said:
Please post the full errorlog and the info the SYSCON spits out during a bringup cmd (hint, press enter after the string stops and it'll spit out more).

The GLOD makes me suspect the RSX VRAM. @David Rainer, you may be interested in this too, since this is how you can tell if an RSX is good or not (I noticed you're only ohm testing VDDC, but it's often the PLL or FBVDDQ voltage lines that die). Measure resistance all 7 RSX voltages...

View attachment 36137

When the RSX is off the board use these test points (just to keep them comparable)...
View attachment 36136View attachment 36139

When installed on the MB you can test these too...
View attachment 36141
The SMD's on the MB around the outside of the RSX may be different, but there should be spot you can measure from since the RSX pinout are the same for 90/65/40nm. You'll have to use some deductive reasoning to find the right spot to measure the voltage line.

My guess is that FBVDDQ is low (Should be ~166 ohms for a 65nm RSX). Alternatively, the PLL could be low (should be ~400KOhms for 65nm).

@David Rainer I saw in one of your recent streams that you have a 65nm RSX ready to be installed. I only have measurements for one 65nm RSX (the one used to fill in the chart above). If you could measure those and post to the forum that would help confirm those measurements. You can do this for all RSX's before installing, to be sure it's good. This is how you vet RSX's purchased on ali express or e-bay BTW.

Also, if you have any working 90nm, 65nm, & 40nm motherboards, we need the same measurements, but when the RSX is installed on the MB. This way we know what they are supposed to measure (on the board) and can easily identify when one of those voltages are bad. It'll make diagnosing much easier.
Click to expand...
Hello, thanks for replying, this is the full errlog
===================================
ERR 00: 00000000 A0802024 0B721311
ERR 01: 00000000 A0802024 0B721310
ERR 02: 00000000 A0802024 0B72130C
ERR 03: 00000000 A0802024 0B72130B
ERR 04: 00000000 A0802124 0B72130B
ERR 05: 00000000 A0802124 0B72130A
ERR 06: 00000000 A0802124 0B72130A
ERR 07: 00000000 A0802024 0B721309
ERR 08: 00000000 A0802124 0B721309
ERR 09: 00000000 A0802024 0B721308
ERR 10: 00000000 A0112024 0B721305
ERR 11: 00000000 A0112024 0B721304
ERR 12: 00000000 A0112024 0B721304
ERR 13: 00000000 A0112124 0B721303
ERR 14: 00000000 A0112024 0B721303
ERR 15: 00000000 A0112124 0B721302
ERR 16: 00000000 A0112124 0B721302
ERR 17: 00000000 A0112124 0B721301
ERR 18: 00000000 A0112124 0B721301
ERR 19: 00000000 A0112124 0B721300
===================================
I haven't tested any resistances yet as I will remove rsx as a last resort. Also, where is the diag point so I can ground it to go internal mode for bringup? I can't find it, thanks.
EDIT: Here is the bringup errorlog
python ps3_syscon_uart_script.py COM5 SW

>$ auth
Auth successful
>$ bringup
00000000
# [SSM] Bringup Start.

>$
F0000003
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.5.0
#!(Build ID: 3318,35708,
#!Build Date: 2008-10-11_00:31:58)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] Unknown command.

>$
F0000003
# [UCMD] Unknown command.

>$
F0000003
# [UCMD] Unknown command.

>$ shutdown
00000000
# [SSM] Shutdown Start.

>$
F0000003
# [SSM] Shutdown ok.
# (PowerOff State)
OK 00000000
# [UCMD] Unknown command.

>$
Also, is there a picture like the one you sent to measure voltages for when RSX is installed for VER-001? Thank you for your help
 
Last edited:
Kostaslgr7 said:
Hello, thanks for replying, this is the full errlog
===================================
ERR 00: 00000000 A0802024 0B721311
ERR 01: 00000000 A0802024 0B721310
ERR 02: 00000000 A0802024 0B72130C
ERR 03: 00000000 A0802024 0B72130B
ERR 04: 00000000 A0802124 0B72130B
ERR 05: 00000000 A0802124 0B72130A
ERR 06: 00000000 A0802124 0B72130A
ERR 07: 00000000 A0802024 0B721309
ERR 08: 00000000 A0802124 0B721309
ERR 09: 00000000 A0802024 0B721308
ERR 10: 00000000 A0112024 0B721305
ERR 11: 00000000 A0112024 0B721304
ERR 12: 00000000 A0112024 0B721304
ERR 13: 00000000 A0112124 0B721303
ERR 14: 00000000 A0112024 0B721303
ERR 15: 00000000 A0112124 0B721302
ERR 16: 00000000 A0112124 0B721302
ERR 17: 00000000 A0112124 0B721301
ERR 18: 00000000 A0112124 0B721301
ERR 19: 00000000 A0112124 0B721300
===================================
I haven't tested any resistances yet as I will remove rsx as a last resort. Also, where is the diag point so I can ground it to go internal mode for bringup? I can't find it, thanks.
EDIT: Here is the bringup errorlog
python ps3_syscon_uart_script.py COM5 SW

>$ auth
Auth successful
>$ bringup
00000000
# [SSM] Bringup Start.

>$
F0000003
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.5.0
#!(Build ID: 3318,35708,
#!Build Date: 2008-10-11_00:31:58)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] Unknown command.

>$
F0000003
# [UCMD] Unknown command.

>$
F0000003
# [UCMD] Unknown command.

>$ shutdown
00000000
# [SSM] Shutdown Start.

>$
F0000003
# [SSM] Shutdown ok.
# (PowerOff State)
OK 00000000
# [UCMD] Unknown command.

>$
Also, is there a picture like the one you sent to measure voltages for when RSX is installed for VER-001? Thank you for your help
Click to expand...
Nope, there should be 32 errors in the errorlog. Type errlog and it'll show all of them. Do a becount while you're at it.

Get those resistance measurements when you get a chance. I want to rule out a dead RSX before we waste too much time on shiz that's fine.

Looking at the bringup log, Power on reset and power on sequencing went fine (it made POST). The bootloader starts and then...
Code: 
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] Unknown command.
Continues on like that. This is very possibly dead RSX VRAM, so we need to get those measurements.

Did you attempt to connect to the SB UART? @vyktormvmpay25 have you seen that? I wonder if he should try connecting to the SB UART to see more info. Maybe you can help him with that part, I haven't messed with SB UART yet.
 
You must log in or register to reply here.

Similar threads

Back
Top