konza
Member
Hello, I'll keep it as to-the-point as I can. I got a J model fat PS3 (DIA-002 board) untested and with a broken power button. The power button was broken because the contact pads rusted, but the button itself worked, and as I expected there was a YLOD, but luckily, the RSX seemed fine as the console only YLOD-ed after ~10 seconds and the display was fine via AV (the HDMI port is broken/damaged).
I hooked it up to syscon, and this is what I initially got:
Seeing how the 1001 errors were pretty old and spaced apart, and also the fact that they didn't occur to me a single time I put them aside and focused on the 1002 error. I gave the console a very good clean and applied new thermal paste. Booting the console, just before the XMB was displayed, the YLOD occurred again.
I restarted the console (I usually try twice for whatever reason), and this time, the console got into the XMB and didn't crash at all. It was unmodded, so I reset the system, formatted the HDD and patched the flash memory to allow for CFW. The wi-fi worked, and so did the BD drive, but I didn't check the bluetooth, and that was my mistake, as the console now faced an update boot-loop (error 8002F1F9). The total runtime went up by 2 hours during this whole thing. I left it alone for an hour before trying to attempt a fix, but to my dismay, the YLOD reappeared as suddenly as it disappeared.
Once again, the error was 1002, yet the bringup didn't cause the console to YLOD (in internal mode):
And so, a day later, I replaced 3 of the RSX NEC/Tokins (0E0108 - note that these are 1000uf each, totaling 4000uf) with 9x 470uf (4230uf) 6.3v tantalum capacitors (I don't know about the ESR, but these are the only ones that were available to me) and left 1 Tokin on the RSX side to serve as a bridge. Feeling proud of myself, I hastily reassembled the unit and tried booting it, but to my dismay, the YLOD was still there, and this time - it was instant. Thinking it was a fluke, I tried again, but it happened again.
I immediately took it back apart, and inspected the board; two capacitors on the backside were missing. How I didn't notice is beyond me. These are the error logs I got after that:
I was confused, wondering how 22 new errors occurred with 2 boots, so I checked the wiki out; it said that this was common with this error, but I noticed a discrepancy: it said error 0213010 on the wiki, but what I got was 0203010.
I used a donor SEM-001 board to get 2x 1uf capacitors and replaced the missing ones using those hoping that would fix it. I also replaced the "blown" F6302 fuse (I regret not checking it before I threw it away, but I'm almost completely sure it wasn't blown).
But the YLOD still remained, so I examined the board and the components around the replaced Tokins under the microscope. And sure enough, one capacitor next to it had been damaged. Same as the other, I replaced it with a 1uf capacitor from the SEM-001 board.
Here is the most recent syscon:
Here are the pictures of the caps I knocked off (both on the B side), as well as the damaged one (on A side):
I have almost zero knowledge of electronic engineering nor how to read schematics, but I managed to figure several things out:
- One of the caps I knocked off (the one on the bottom, close to the letter B) is used by the VCC line by the power buck controller on the other side of the board (I'll get back to that controller in a second),
- The other one, right next to the tokin (also on B side), I identified as a C6057 using the SEM-001 service manual (take this with a grain of salt, I'm not really sure if it's 100% the same cap).
Next, my research led me to the aforementioned pwm buck controller - ISL6568. I checked for shorts, but with my knowledge, even with the schematics and service manual made available, I could only do so much. In the picture below, the green pins weren't shorted to GND, and the red ones were shorted to GND:
I checked all the caps around the pwm buck controller, as well as the mosfets and inductors in the area, and none were shorted. The voltage coming out of the IREF pin was ~1.3v which I found odd, because in the manual, it said that IREF should be VDIFF + 1v, and the voltage that reached the tokins (both RSX and CELL) was around ~1.7v, which I also found to be odd (both were measured in the instant before the console shut-off because of the YLOD).
I checked the resistance on RSX and CELL as well, which were good, as well as at least 10 of the tiny CELL caps on the back, which were also within an acceptable range. The rest I inspected visually, as I think there's no reason the short could've spread there.
This is where I'm currently stuck and need help. I'm pretty happy with what I've been able to diagnose with my very limited knowledge and experience, so I'm looking forward to your replies.
Also, here's the pictures of the tantalum replacement, if it helps (it may very well be as simple as a bad tantalum install):
I hooked it up to syscon, and this is what I initially got:
Code:
errlog
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0801001, clock:0xffffffff
ofst[ 4]:err_code:0xa0801001, clock:0xffffffff
ofst[ 8]:err_code:0xa0801001, clock:0x180aafc5 2012/10/12 10:39:01
ofst[ 12]:err_code:0xa0801001, clock:0xffffffff
ofst[ 16]:err_code:0xa0003001, clock:0x1873a45b 2012/12/31 01:18:19
ofst[ 20]:err_code:0xa0801001, clock:0x18b263b4 2013/02/16 15:35:16
ofst[ 24]:err_code:0xa0801001, clock:0xffffffff
ofst[ 28]:err_code:0xa0801001, clock:0xffffffff
ofst[ 32]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 36]:err_code:0xa0801002, clock:0x0b4886a1 2005/12/31 00:00:33
(tried booting, held on for a good while)
ofst[ 40]:err_code:0xa0801002, clock:0x0b4886a0 2005/12/31 00:00:32
ofst[ 44]:err_code:0xa0801002, clock:0xffffffff
becount
Bringup : 4260 times
Shutdown: 3433 times
Power-on: 217day 00hour 39min 15sec
[mullion]$
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:0x20e7
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 2.3.5 (Build ID: 3034,32025, Build Data: 2008-05-12_15:29:27)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)Seeing how the 1001 errors were pretty old and spaced apart, and also the fact that they didn't occur to me a single time I put them aside and focused on the 1002 error. I gave the console a very good clean and applied new thermal paste. Booting the console, just before the XMB was displayed, the YLOD occurred again.
I restarted the console (I usually try twice for whatever reason), and this time, the console got into the XMB and didn't crash at all. It was unmodded, so I reset the system, formatted the HDD and patched the flash memory to allow for CFW. The wi-fi worked, and so did the BD drive, but I didn't check the bluetooth, and that was my mistake, as the console now faced an update boot-loop (error 8002F1F9). The total runtime went up by 2 hours during this whole thing. I left it alone for an hour before trying to attempt a fix, but to my dismay, the YLOD reappeared as suddenly as it disappeared.
Once again, the error was 1002, yet the bringup didn't cause the console to YLOD (in internal mode):
Code:
errlog
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0801001, clock:0xffffffff
ofst[ 4]:err_code:0xa0801001, clock:0xffffffff
ofst[ 8]:err_code:0xa0801001, clock:0x180aafc5 2012/10/12 10:39:01
ofst[ 12]:err_code:0xa0801001, clock:0xffffffff
ofst[ 16]:err_code:0xa0003001, clock:0x1873a45b 2012/12/31 01:18:19
ofst[ 20]:err_code:0xa0801001, clock:0x18b263b4 2013/02/16 15:35:16
ofst[ 24]:err_code:0xa0801001, clock:0xffffffff
ofst[ 28]:err_code:0xa0801001, clock:0xffffffff
ofst[ 32]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 36]:err_code:0xa0801002, clock:0x0b4886a1 2005/12/31 00:00:33
ofst[ 40]:err_code:0xa0801002, clock:0x0b4886a0 2005/12/31 00:00:32
ofst[ 44]:err_code:0xa0801002, clock:0xffffffff
ofst[ 48]:err_code:0xa0801002, clock:0x0b48868d 2005/12/31 00:00:13
ofst[ 52]:err_code:0xa0801002, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 56]:err_code:0xa0801002, clock:0x0b4886de 2005/12/31 00:01:34
ofst[ 60]:err_code:0xa0022110, clock:0xffffffff (these two 2110s occurred because I tried using a G model wifi/bt board, and it obviously didn't work)
ofst[ 64]:err_code:0xa0022110, clock:0xffffffff
ofst[ 68]:err_code:0xa0801002, clock:0xffffffff
ofst[ 72]:err_code:0xa0801002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0xffffffff
ofst[ 80]:err_code:0xa0801002, clock:0xffffffff
ofst[ 84]:err_code:0xa0801002, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, clock:0xffffffff
becount
Bringup : 4291 times
Shutdown: 3462 times
Power-on: 217day 02hour 33min 21sec
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:0x20e7
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 2.3.5 (Build ID: 3034,32025, Build Data: 2008-05-12_15:29:27)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV NVS] READ CMD
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)And so, a day later, I replaced 3 of the RSX NEC/Tokins (0E0108 - note that these are 1000uf each, totaling 4000uf) with 9x 470uf (4230uf) 6.3v tantalum capacitors (I don't know about the ESR, but these are the only ones that were available to me) and left 1 Tokin on the RSX side to serve as a bridge. Feeling proud of myself, I hastily reassembled the unit and tried booting it, but to my dismay, the YLOD was still there, and this time - it was instant. Thinking it was a fluke, I tried again, but it happened again.
I immediately took it back apart, and inspected the board; two capacitors on the backside were missing. How I didn't notice is beyond me. These are the error logs I got after that:
Code:
ofst[ 52]:err_code:0xffffffff, clock:0x0b488680 2005/12/31 00:00:00
ofst[ 56]:err_code:0xa0801002, clock:0x0b4886de 2005/12/31 00:01:34
ofst[ 60]:err_code:0xa0022110, clock:0xffffffff
ofst[ 64]:err_code:0xa0022110, clock:0xffffffff
ofst[ 68]:err_code:0xa0801002, clock:0xffffffff
ofst[ 72]:err_code:0xa0801002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0xffffffff
ofst[ 80]:err_code:0xa0801002, clock:0xffffffff
ofst[ 84]:err_code:0xa0801002, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, 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:0xa0202120, clock:0xffffffff
ofst[112]:err_code:0xa0202120, clock:0xffffffff
ofst[116]:err_code:0xa0202120, 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:0xa0203010, clock:0xffffffff
ofst[ 8]:err_code:0xa0202120, clock:0xffffffff
ofst[ 12]:err_code:0xa0202120, clock:0xffffffff
ofst[ 16]:err_code:0xa0202120, 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:0xa0203010, clock:0xffffffff
[mullion]$I was confused, wondering how 22 new errors occurred with 2 boots, so I checked the wiki out; it said that this was common with this error, but I noticed a discrepancy: it said error 0213010 on the wiki, but what I got was 0203010.
I used a donor SEM-001 board to get 2x 1uf capacitors and replaced the missing ones using those hoping that would fix it. I also replaced the "blown" F6302 fuse (I regret not checking it before I threw it away, but I'm almost completely sure it wasn't blown).
But the YLOD still remained, so I examined the board and the components around the replaced Tokins under the microscope. And sure enough, one capacitor next to it had been damaged. Same as the other, I replaced it with a 1uf capacitor from the SEM-001 board.
Here is the most recent syscon:
Code:
errlog
ofst[ 24]:err_code:0xffffffff, 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:0xa0203010, clock:0xffffffff
ofst[ 64]:err_code:0xa0202120, 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:0xa0203010, clock:0xffffffff
ofst[108]:err_code:0xa0202120, clock:0xffffffff
ofst[112]:err_code:0xa0202120, clock:0xffffffff
ofst[116]:err_code:0xa0202120, 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:0xa0202120, clock:0xffffffff
ofst[ 16]:err_code:0xa0202120, clock:0xffffffff
ofst[ 20]:err_code:0xa0203010, clock:0xffffffff
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
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
Press Ctrl+C to exit
>$
[POWERSEQ] Error : wait attention timeout.(SEQ1)
[SSM] state: 0102 -> 0302
[SSM] PowSeq Fail : Detected !
[SSM] state: 0302 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0203010
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)Here are the pictures of the caps I knocked off (both on the B side), as well as the damaged one (on A side):
I have almost zero knowledge of electronic engineering nor how to read schematics, but I managed to figure several things out:
- One of the caps I knocked off (the one on the bottom, close to the letter B) is used by the VCC line by the power buck controller on the other side of the board (I'll get back to that controller in a second),
- The other one, right next to the tokin (also on B side), I identified as a C6057 using the SEM-001 service manual (take this with a grain of salt, I'm not really sure if it's 100% the same cap).
Next, my research led me to the aforementioned pwm buck controller - ISL6568. I checked for shorts, but with my knowledge, even with the schematics and service manual made available, I could only do so much. In the picture below, the green pins weren't shorted to GND, and the red ones were shorted to GND:
I checked all the caps around the pwm buck controller, as well as the mosfets and inductors in the area, and none were shorted. The voltage coming out of the IREF pin was ~1.3v which I found odd, because in the manual, it said that IREF should be VDIFF + 1v, and the voltage that reached the tokins (both RSX and CELL) was around ~1.7v, which I also found to be odd (both were measured in the instant before the console shut-off because of the YLOD).
I checked the resistance on RSX and CELL as well, which were good, as well as at least 10 of the tiny CELL caps on the back, which were also within an acceptable range. The rest I inspected visually, as I think there's no reason the short could've spread there.
This is where I'm currently stuck and need help. I'm pretty happy with what I've been able to diagnose with my very limited knowledge and experience, so I'm looking forward to your replies.
Also, here's the pictures of the tantalum replacement, if it helps (it may very well be as simple as a bad tantalum install):
Last edited:
