Trinity - Red Light constant

[estaga]

Hi,

I'm a newbie to this forum, I read what I could to address my issue but not getting anywhere, try and not be too harsh :smile:

I'm one of those who probably should not be soldering but figured I should have a go on a Slim after doing a JTAG and a Zephyr RGH recently...

For this slim I have..

- Dumped the nand, and verified they are same
- Checked the CB, ensured it's as expected
- Programmed the Coolrunner with the Trinity file with my Nand-X V3
- Generated ECC, MultiBuilder 0.3 and 0.4 produces the same ECC file (md5's match)
- Wrote (+w16 ecc...) the Nand for Xell to grab the CPU keys
- Coolrunner is set to 'NOR' and 'SLIM' of course

Symptoms at this stage:
- Coolrunner shows a red light that stays on constantly when the power is plugged in and continues to stay red when booting
- The Xbox's green light flickers constantly when switching on with no DVDRom attached
- The Xbox's green light is on constantly when switching on with a DVDRom attached
- The fan activity appears normal, no faster than before and no clicking sounds that some have mentioned
- I can flash my stock Nand back and everything works again
- Of course no glitching, tried moving the blue one around in ten's of boots

My sins:
- I have checked and resoldered several times now to try and see what the problems are, apologies for the mess ):
- I have checked for shorts, all points on the QSB at least seems to go where they need to when I check with a multimeter on the back of the board, including the resistor point.
- I am sure I messed up my CPU_RST point, however I read on the forums that if I messed that up that the Xbox will no longer boot? I assume I read the context wrong as it is of course booting with the stock NAND ok (and of course even when the CPU_RST wire is disconnected).

So in short, is a Coolrunner showing only a RED light a indicator for CPU_RST being bad? Or is there something else I should check? I'm not too confident with the alternate points for CPU_RST and would best like to avoid that as I will no doubt have to send that to one of the professionals here!

Thanks!

 

[diaboliq20]

the coolrunner shold always be red when powered.......you obviously got xell to boot to obtain your cpu key to build the ecc.....so your wiring is ok, and the coolrunner is working.
I would guess your ecc image is bad.....multibuilder should have no issues, but try another program like jtag tool or bestpigs and flash that file to your nand

 

[estaga]

the coolrunner shold always be red when powered.......you obviously got xell to boot to obtain your cpu key to build the ecc.....so your wiring is ok, and the coolrunner is working.

diaboliq, just to confirm, I have not managed to boot Xell yet, I have generated the first image to boot into Xell which will not boot so I can retrieve the CPU keys which I am stuck at, hence me being concerned about wiring ):

Thanks!

Sent from my HTC Vision using Tapatalk

 

[Martin C]

Your blue and yellow wires are the wrong way round!!!

Blue - CPU_RST (D)
Yellow - POST_OUT1 (C)

 

[diaboliq20]

PMSL -= I didn't even look at the pictures lol

blue should be to FT4R2

 

[Martin C]

ok - if you don't have the cpu key yet - you can't have built the ECC correctly using multibuilder (I think this requires the cpukey to be present)

does the coolrunner flash green when you try to boot?
try using bestpigs to generate the ecc and flash that to your NAND and retry

Multi_Builder will build an ECC by default when no cpukey.txt is present.

also read my post. It's a wiring problem. From the first pic, the yellow wire should be soldered where the blue wire is and vice versa.

 

[diaboliq20]

yeah - I edited my post - I completely overlooked the pics lol.....wow.....

 

[estaga]

Heh, thanks for catching that stupid move!

Will give it a go and report back.

Sent from my HTC Vision using Tapatalk

 

[quicks2k]

if you mess the cpu_rst point, the slim will beep on power but nothing else will happen, no light at all. so if you have a light then it's not ruined.

 

[estaga]

Thanks all!

Once I resoldered it as per the manual (d'oh!) I glitched on the first attempt , on average within about 20 seconds up to a maximum of a minute.

Seems like I did not mess up CPU_RST too badly - thanks everybody for your help on this ridiculous one!

 

[quicks2k]

Congratz. !!