Need Urgent Help With My Slim - Constant Green Light

Repoman 108

BANNED
Sep 22, 2011
184
28
Sydney, Australia
Hey guys, well I've had a slim RGH box for about a week now, and opened it up today to try to fix the wire length problem. I've already flashed the coolrunner with the trinity.xsvf file using nandpro 3.0a, a nand-x and a nand-x to coolrunner cable, with no problems. After fiddling with the wire for a bit, my CPU_RST wire came desoldered (annoyingly) so I had to open the whole board up to get to the alt point resistor under the heatsink to resolder. For the sake of testing boot times after resoldering, I plugged it back in to test etc: I get a constant green and red light on the coolrunner (not blinking, constant) while booting, the console only seems capable of booting retail images, and when i try to program the coolrunner, I get programming error 0x0002. The soldering is pretty much all neat, and I have gone over every single connection with a multimeter and found nothing wrong, and have gone ahead and resoldered most of them anyway to be safe. Does anyone know if this is a coolrunner problem, I can't think of what else it might be. If it's likely a soldering problem can somebody specify which of the wires from the Coolrunner the problem likely pertains to? Thanks in advance
 

Repoman 108

BANNED
Sep 22, 2011
184
28
Sydney, Australia
Well the track of the original CPU_RST point was torn up very easily when I moved around the wire to optimise the boot time, so I bridged the track to that solder point (otherwise the xbox didnt boot) and soldered the CPU_RST wire instead to the R4D4 resistor under the heatsink, on the side closest to the CPU/GPU chip
 

Repoman 108

BANNED
Sep 22, 2011
184
28
Sydney, Australia
I appreciate the thought guys, but unfortunately this broken track is not my problem, since I was able to simply bridge from where the track ended to the solder point FT4R2 where it should have been all along, and then simply used the alternate point since I didn't want to fiddle with the already-temperamental solder point. As I said, the xbox boots retail images so there's nothing wrong with the xbox joints, only something to do with the coolrunner's soldering or its programming etc.

EDIT:
In fact, I'm almost 100% that the CPU_RST wire isn't the problem at all, since I've gone to the trouble of soldering it from the Coolrunner side to the R4D4 resistor alt point and then testing the connection between the coolrunner CPU_RST point and then C5R11 pad on the bottom with a multimeter, and the result was that both were connected i.e. the join at the resistor must be A-OK.

EDIT 2:
Well at this point I'm fairly well convinced that the Coolrunner has at some stage shorted itself out in some fatal manner, since the list of reasons for a 0x0002 programming error seem very limited, and it HAS been programmed successfully in the past. I suspect that the Coolrunner is just fried, so I'll go about replacing it with an old SEEED Coolrunner chip I had lying about the place and let you know how it goes (though it'll take several days since I'm terrible at soldering and my soldering-muscle friend won't be over till after Xmas). Until then, if anyone has any other suggestions, I'm open.

EDIT 3 (considered double posting to get attention):
I decided to just resolder the Coolrunner ends of the install to the SEEED chip, and what do you know it boots perfectly. So therefore the culprit was indeed a broken Team-Xecuter Coolrunner. Incase it's useful for feedback/troubleshooting purposes, the main symptoms of the Coolrunner failure were: Constant green light while Xbox was in standby mode or powered on; No boot up except retail images; and when attempting to program with functional Nand-X to Coolrunner cable, I received programming error 0x0002 (an error I know was related to the broken Coolrunner since I did program it myself with the same cable earlier, successfully).

I would send the Coolrunner off to TX for diagnostics if it would help, but I live in Australia so I'm guessing it's more trouble than it's worth. Hopefully I helped anybody else with similar problems. Thanks, you can close the thread now if you deem it necessary.
 
Last edited: