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

I have a JSD-001 and have hooked up the RX/TX/GRD. I'd like to wire up the diagnostics wire now but I can't find a diagram of where it is located on a JSD-001 board.


https://imgur.com/a/gkLTBhL <- my system right now
There is no diag wire needed for that model (See my tutorial). It has a Sherwood SYSCON, which doesn't have internal and external modes like mullion SYSCON's do. So you don't have to do anything special.

I would caution you against attaching cables as you have there. The pins are too ridged and can easily tear a pad off. It's better to cut off the pin connector and attach the wire directly. Just a warning.
 
There is no diag wire needed for that model (See my tutorial). It has a Sherwood SYSCON, which doesn't have internal and external modes like mullion SYSCON's do. So you don't have to do anything special.

I would caution you against attaching cables as you have there. The pins are too ridged and can easily tear a pad off. It's better to cut off the pin connector and attach the wire directly. Just a warning.

Many thanks for the advice! Will follow!!

So does that mean that commands like that show the total system uptime are not available on this model?

Also, what should I check for in the A0022110 error code. MK I2C ERROR (OR OTHER CLOCK's ERRORS)
 
So here's the bad tokin wave forms you are looking for.
LNit0tL.png
The sharp spikes is noise. The rectified sin wave is the ripple. We're mainly concerned with voltage ripple. That's what the tokins are tasked with attenuating (reducing). MLCC caps can be used to help reduce the noise spikes, but they aren't the major concern.
Nl4sfTu.png
CPU is in yellow and RSX is in Blue
8-png.28660

Pay attention to the axis. Horizontal needs to be near 1-5us and vertical axis needs to be about 50mV/div. If you set the scope to AC coupling, you won't have to adjust the DC voltage offset to get the graph in view. Or you can start zoomed out and start triggering in on it.

The further in you are zoomed the more accurate the measurement. So the reason you had so much noise, is partly because of the ground clip and partly because you are zoomed out so far.

FYI
You were right. This digital oscope is crap - I had to return it and order another analog one.
Will be back into this subject when I receive it.
 
FYI
You were right. This digital oscope is crap - I had to return it and order another analog one.
Will be back into this subject when I receive it.
My friend have one tektronix 100mhz 2 channels. Still quite good enough. I did not had time to ask for tests on nec as not really required. On my daily basis I find 4 simple measurements, resistance, capacity, diode, voltage. Rest it can be debugging to pc uart.
I've done enough porting parts from mobos to understand enough, not say I know everything but 95 percent of defects are repaired if less than 30 percent of damage on product. Really won't worth more than that.
 
So does that mean that commands like that show the total system uptime are not available on this model?

Also, what should I check for in the A0022110 error code. MK I2C ERROR (OR OTHER CLOCK's ERRORS)

Sherwood SYSCONs have many of the same commands as the internal access mode of mullion chips, but not all. bringup, powerstate, errlog, and becount should work (I think?). I'm not sure. I don't work on newer models. But victor does.

02 2110 is a clock generator error (IC5001, or it's equivalent on the JSD-001). A step number of 02 suggests a blown fuse or short that is preventing PWR from reaching the IC. That's pretty early. Or it could be the crystal. For this sort of thing an oscilloscope comes in handy. You can check to see if you're getting the correct clock frequencies. Assuming you have schematics for them or a working board to use as reference. You could try replacing it wholesale and hope for the best, but I suspect something caused it to fail, if it actually is bad. So be thorough troubleshooting the circuit's leading to it before you replace it or the new one could get destroyed too.
 
FYI
You were right. This digital oscope is crap - I had to return it and order another analog one.
Will be back into this subject when I receive it.

My friend have one tektronix 100mhz 2 channels. Still quite good enough. I did not had time to ask for tests on nec as not really required. On my daily basis I find 4 simple measurements, resistance, capacity, diode, voltage. Rest it can be debugging to pc uart.
I've done enough porting parts from mobos to understand enough, not say I know everything but 95 percent of defects are repaired if less than 30 percent of damage on product. Really won't worth more than that.
Victor is correct. You don't need an oscilloscope to diagnose bad tokins. It can confirm they are bad and show your tantalum array is an adequate substitute, but it's not strictly needed. A 1002 error is what you're looking for. Resistance at VDDC is useful.

Oscilloscope is useful in checking clock signals are present and correct, PWM signals, laser calibration, ripple/noise attenuation, checking proper SYCN levels and etc. Any application where the voltage regularly changes frequency. Certainly a useful tool to have (a decient one anyway). Especially if you get into designing electronics. Real world measurements often differ from theoretical calculations due to parasitics on real hardware. Theory only get's you so far. A scope allow you to dial the design in. I recommend the RIGOL DS1054z. It's the best bang for your buck. Very capable 4-channel scope!
 
@Michael Crump about your error in syscon can you report more data of bringup command. Running twice one after another will get a bit of more data, în SW version is quite wired how it works but I tend to believe cpu is fried, never sorted any errors of clock generator on any ps3 when cpu VDDC is lower then 2.4 ohms. Also reply with some measurements. As example see photos attached.
398a70b3af350fae4b7e174bc6711c78.jpg
edf2747ab197be415b448529d47a36d8.jpg
218963c40a1a2f3b90515fe9d68f2985.jpg
Also I often find jsd001 with glod (dead rsx), found 2 in a month, didn't bother to desolder it as got pretty much about 4 before, after reball same thing with SB debugging started and no errors in syscon and still glod.
I will say reply with both values of cpu and rsx for VDDC and much more around cpu and rsx. Just resistance values.
 
Last edited:
Hello everyone,
I have this PS3 that had some random YLOD's some time ago, it's working fine now apparently, so those are the errors I got:
01: A0901001 Wed May 17 02:49:58 2006
02: A0801002 Mon Apr 24 21:39:15 2006
03: A0801103 Sat Apr 15 02:05:08 2006
04: A0901001 Sat Apr 15 01:28:23 2006
05: A0801002 Tue Apr 11 00:47:51 2006
06: A0801002 Mon Apr 10 22:51:36 2006
07: A0801002 Mon Apr 10 22:51:04 2006
08: A0901001 Thu Apr 6 22:26:34 2006
09: A0901001 Thu Apr 6 21:45:02 2006
10: A0801002 Tue Apr 4 03:28:24 2006
11: A0802203 Sun Apr 2 21:20:27 2006
12: A0901001 Sat Mar 18 23:43:01 2006
13: A0801002 Sat Mar 18 21:46:25 2006
14: A0801002 Sat Mar 18 21:46:05 2006
15: A0801002 Fri Mar 17 23:04:14 2006
16: A0801002 Tue Mar 7 21:56:37 2006
17: A0801002 Sat Mar 4 21:38:02 2006
18: A0801002 Sat Mar 4 15:54:10 2006
19: A0901001 Sat Mar 4 14:55:45 2006
20: A0901001 Sat Mar 4 02:47:13 2006
21: A0801002 Fri Mar 3 22:23:31 2006
22: A0801002 Fri Mar 3 22:23:08 2006
23: A0801002 Thu Mar 2 22:20:42 2006
24: A0901001 Fri Feb 10 16:32:42 2006
25: A0901001 Fri Feb 10 16:32:00 2006
26: A0801002 Sun Jan 29 18:45:10 2006
27: A0801601 Sat Jan 14 01:56:09 2006
28: A0801701 Sat Jan 14 01:56:09 2006
29: A0801001 Fri Oct 2 04:01:35 2020
30: A0801002 Mon Sep 28 16:34:27 2020
31: A0901001 Mon Sep 28 16:19:08 2020
32: FFFFFFFF Sat Sep 26 22:12:45 2020
 
Hello everyone,
I have this PS3 that had some random YLOD's some time ago, it's working fine now apparently, so those are the errors I got:
01: A0901001 Wed May 17 02:49:58 2006
02: A0801002 Mon Apr 24 21:39:15 2006
03: A0801103 Sat Apr 15 02:05:08 2006
04: A0901001 Sat Apr 15 01:28:23 2006
05: A0801002 Tue Apr 11 00:47:51 2006
06: A0801002 Mon Apr 10 22:51:36 2006
07: A0801002 Mon Apr 10 22:51:04 2006
08: A0901001 Thu Apr 6 22:26:34 2006
09: A0901001 Thu Apr 6 21:45:02 2006
10: A0801002 Tue Apr 4 03:28:24 2006
11: A0802203 Sun Apr 2 21:20:27 2006
12: A0901001 Sat Mar 18 23:43:01 2006
13: A0801002 Sat Mar 18 21:46:25 2006
14: A0801002 Sat Mar 18 21:46:05 2006
15: A0801002 Fri Mar 17 23:04:14 2006
16: A0801002 Tue Mar 7 21:56:37 2006
17: A0801002 Sat Mar 4 21:38:02 2006
18: A0801002 Sat Mar 4 15:54:10 2006
19: A0901001 Sat Mar 4 14:55:45 2006
20: A0901001 Sat Mar 4 02:47:13 2006
21: A0801002 Fri Mar 3 22:23:31 2006
22: A0801002 Fri Mar 3 22:23:08 2006
23: A0801002 Thu Mar 2 22:20:42 2006
24: A0901001 Fri Feb 10 16:32:42 2006
25: A0901001 Fri Feb 10 16:32:00 2006
26: A0801002 Sun Jan 29 18:45:10 2006
27: A0801601 Sat Jan 14 01:56:09 2006
28: A0801701 Sat Jan 14 01:56:09 2006
29: A0801001 Fri Oct 2 04:01:35 2020
30: A0801002 Mon Sep 28 16:34:27 2020
31: A0901001 Mon Sep 28 16:19:08 2020
32: FFFFFFFF Sat Sep 26 22:12:45 2020
Nec caps on both sides for cpu and rsx may need exchange.
Model of ps3? It should be phat with 90nm rsx I'm assuming.
Also have you delid both?
 
I will suggest on next fail just save this rsx and delid both, exchange caps. If not able to do find nearest service to do it.

I use this PS3 for PS2 games only, so I suppose the RSX is not really used much, only the CELL is used in the emulation in this model, or am I wrong?
 
I can't remember the way this ps2 is working, în your model should have Cok002 motherboard and is kind of emulator more, this model may use rsx, cok001 is that may not use it because it have entire ps2 system on same board. That was explained few times but not been very focused on that.
 
I use this PS3 for PS2 games only, so I suppose the RSX is not really used much, only the CELL is used in the emulation in this model, or am I wrong?
The PS2 GPU is present but the CPU is emulated by the Cell. So it's partial emulation or about 80ish % compatible. Your, errorlog is consistent with bad tokins. This tutorial should fix the issue, if you are handy with a soldering iron and patient enough to learn.
 
With the reball, what kind of bga machine is needed?
I started a repair shop recently and I need something that can help me with reballing pc/laptop Mobos, PS3/4, Xbox etc at lowest cost. Any suggestions would be appreciated.
 
The PS2 GPU is present but the CPU is emulated by the Cell. So it's partial emulation or about 80ish % compatible. Your, errorlog is consistent with bad tokins. This tutorial should fix the issue, if you are handy with a soldering iron and patient enough to learn.

Thanks for the info, this PS3 seems to be working fine now, no more YLOD's lately, so it will be a future project.
But now there is this CECHA01 that doesn't even turn on, not after several attempts, then turn off when starting a game, here are the codes:
01: A0801002 Sun Feb 5 03:31:42 2006
02: A0801002 Sun Feb 5 03:31:36 2006
03: A0801002 Sun Feb 5 03:31:29 2006
04: A0801002 Sun Feb 5 03:31:22 2006
05: A0801002 Sun Feb 5 03:31:15 2006
06: A0801002 Sun Feb 5 03:31:08 2006
07: A0801002 Sun Feb 5 03:31:01 2006
08: A0801002 Sun Feb 5 03:30:54 2006
09: A0801002 Sun Feb 5 03:30:43 2006
10: A0801002 Sun Feb 5 03:30:34 2006
11: A0801002 Mon Jan 16 04:13:41 2006
12: A0801002 Mon Jan 16 04:13:34 2006
13: A0801002 Mon Jan 16 04:13:23 2006
14: A0801002 Tue Jan 10 03:28:26 2006
15: A0801002 Tue Jan 10 03:28:16 2006
16: A0801002 Tue Jan 10 03:28:05 2006
17: A0801002 Tue Jan 10 02:50:35 2006
18: A0801002 Tue Jan 10 02:01:40 2006
19: A0801002 Tue Jan 10 02:00:07 2006
20: A0801002 Tue Jan 10 01:57:57 2006
21: A0801002 Tue Jan 10 01:46:21 2006
22: A0801002 Tue Jan 10 01:21:31 2006
23: A0801002 Tue Jan 10 01:17:26 2006
24: A0801002 Tue Jan 10 01:13:23 2006
25: A0901001 Tue Jan 10 01:07:57 2006
26: A0801002 Tue Jan 10 01:07:44 2006
27: A0801002 Tue Jan 10 01:07:34 2006
28: A0901001 Tue Jan 10 01:07:24 2006
29: A0801002 Tue Jan 10 01:07:12 2006
30: A0801002 Tue Jan 10 01:07:02 2006
31: A0901001 Tue Jan 10 01:06:51 2006
32: FFFFFFFF Tue Jan 10 01:06:39 2006

Looks like bad tokins too.
And could the bad tokins affect the PS2 hardware?
Because trying PS1 and PS3 games give me YLOD, but a PS2 games doesn't show the Playstation 2 boot screen, just a black screen, I can still access the menu with the PS button and quit, so it's not stuck, just the game doesn't seems to boot.
 
Thanks for the info, this PS3 seems to be working fine now, no more YLOD's lately, so it will be a future project.
But now there is this CECHA01 that doesn't even turn on, not after several attempts, then turn off when starting a game, here are the codes:
01: A0801002 Sun Feb 5 03:31:42 2006
02: A0801002 Sun Feb 5 03:31:36 2006
03: A0801002 Sun Feb 5 03:31:29 2006
04: A0801002 Sun Feb 5 03:31:22 2006
05: A0801002 Sun Feb 5 03:31:15 2006
06: A0801002 Sun Feb 5 03:31:08 2006
07: A0801002 Sun Feb 5 03:31:01 2006
08: A0801002 Sun Feb 5 03:30:54 2006
09: A0801002 Sun Feb 5 03:30:43 2006
10: A0801002 Sun Feb 5 03:30:34 2006
11: A0801002 Mon Jan 16 04:13:41 2006
12: A0801002 Mon Jan 16 04:13:34 2006
13: A0801002 Mon Jan 16 04:13:23 2006
14: A0801002 Tue Jan 10 03:28:26 2006
15: A0801002 Tue Jan 10 03:28:16 2006
16: A0801002 Tue Jan 10 03:28:05 2006
17: A0801002 Tue Jan 10 02:50:35 2006
18: A0801002 Tue Jan 10 02:01:40 2006
19: A0801002 Tue Jan 10 02:00:07 2006
20: A0801002 Tue Jan 10 01:57:57 2006
21: A0801002 Tue Jan 10 01:46:21 2006
22: A0801002 Tue Jan 10 01:21:31 2006
23: A0801002 Tue Jan 10 01:17:26 2006
24: A0801002 Tue Jan 10 01:13:23 2006
25: A0901001 Tue Jan 10 01:07:57 2006
26: A0801002 Tue Jan 10 01:07:44 2006
27: A0801002 Tue Jan 10 01:07:34 2006
28: A0901001 Tue Jan 10 01:07:24 2006
29: A0801002 Tue Jan 10 01:07:12 2006
30: A0801002 Tue Jan 10 01:07:02 2006
31: A0901001 Tue Jan 10 01:06:51 2006
32: FFFFFFFF Tue Jan 10 01:06:39 2006

Looks like bad tokins too.
And could the bad tokins affect the PS2 hardware?
Because trying PS1 and PS3 games give me YLOD, but a PS2 games doesn't show the Playstation 2 boot screen, just a black screen, I can still access the menu with the PS button and quit, so it's not stuck, just the game doesn't seems to boot.
Yes, 80 1002 indicates bad tokins. Wow, you had 2 of them?! The odds of that is VERY remote, but hey anything is possible. Do you do go though a lot of consoles or just lucky.

About the black screen in PS2 games, I get that too and so far have not been able to resolve it. I have been putting off troubleshooting the PS2 hardware. It's just sitting in a pile of other busted consoles waiting for me to muster the desire to troubleshoot. They will have to wait. I have reached my frustration limit and am in a cooling off period.
 
With the reball, what kind of bga machine is needed?
I started a repair shop recently and I need something that can help me with reballing pc/laptop Mobos, PS3/4, Xbox etc at lowest cost. Any suggestions would be appreciated.

The variety of bga machines is wide. please help me out with this or if my question is wrong correct me. Thank you.
 
I don't own one, but I had my eye on the IR6500. Only because it's cheap, but I've seen one on Louis Rossman's counter in the background of his videos. Not that he endorsed it or anything. He also has a much more expensive one, which could mean he got tired of the crappy one and bought the expensive one to solve the issue once and for all. @vyktormvmpay25 may have a better idea.
 
Yes from what I have Jovi RE8500 is not on production so I will suggest like minimum 2000 bottom watts with top minimum 400 w ir . Also top air seems more faster but need well calibration. All depends on technician that works with that rework station. He must operate with that. Some people have even better suggestion to create/modify later this station. I will say to do it from scratch but take time, it took 6 months to complete one single setup for one dual station with top hot air gun and bottom plate. I still have one ir6000, had ir6500, it took me few months to create a profile to desolder in good condition rsx but I couldn't keep board as nearly in factory and always burst when heat. 800w on bottom isn't enough to desolder lead free alloy in old ps3. Ir6500 and ir6000 can do ps4, probably ps5, less copper probably inside boards on slims ps3 , but phats don't even think to try. Just a note for starting this maximum time to desolder lead free is 8 minutes. If you don't manage to reach that you will burn board or blow rsx for sure.
If you find any Jovi RE8500 or new models will be better. Oh and none of YouTube profiles help, learn to use it manually and working with that in stages. You need to test few boards before you can start, need to understand well this process otherwise is a big loss.
 

Similar threads

Back
Top