ANSWERED RGH- RROD 0022 problem

[hodgie]

I just had this exact same problem on a big block jasper last night. I had to re-route the green wire. I ran it around the board by where the fans are. It took a lot of trial and error. But now in runs perfect. Boots instantly too. Maybe that will work for you.
I read what MartinC wrote about pll_bypass interference, so that's what I thought would help.

 

[Martin C]

OP- how long are you leaving it to glitch?

 

[werewolfman]

almost 5 min

 

[Martin C]

So remembering that this wouldn't boot with the retail NAND and coolrunner on NOR (0022), it's your wiring/soldering. This is why I advise people not to program until this is happening.

Just confirm that by writing the first 50 blocks back

(nandpro usb: -w16 nanddump.bin 0 50)

and setting the CR to NOR that it still boots?

 

[Hackerjac]

maybe a crazy thought, but have you programmed the cr board with the right timing file ?

 

[werewolfman]

So remembering that this wouldn't boot with the retail NAND and coolrunner on NOR (0022), it's your wiring/soldering. This is why I advise people not to program until this is happening.

Just confirm that by writing the first 50 blocks back

(nandpro usb: -w16 nanddump.bin 0 50)

and setting the CR to NOR that it still boots?

just to be sure:
u are saying to write the first 50 blocks of my original nand...right ?
what should happen/indicate then ?


and does it look like a cold solder ?

 

[Martin C]

Yes, you're overwriting the XeLL file you flashed over. It should boot normally with the CR set to PRG.

 

[werewolfman]

maybe a crazy thought, but have you programmed the cr board with the right timing file ?

yes i programmed with impact---> no go
then erased & programmed with 360gcprog--> no go
then back to impact and succesfully programmed it and verfied by 360gcprog as gligli timing 1.1

 

[werewolfman]

here is a screenshot from 360gcprog

 

[werewolfman]

ok martin i will try and give a feed back

 

[werewolfman]

Yes, you're overwriting the XeLL file you flashed over. It should boot normally with the CR set to PRG.

just as u said Martin C
ecc with CR normal--> no glitch
flashed original nand (0 50) with CR prog---> boots te original dash normally
when on Normal mood--> RROD

so it's wiring/solder problem ...right ?
but how ? pulling my hair out :facepalm:
any tips to test connections/voltages ?
it seems i will do the soldering again with the spare slim cables ...would probably the alt points

 

[Martin C]

0022 is because the CR isn't getting the signal needed to release the CPU.

Wire positioning and soldering is paramount. Just confirm you flashed the right timing file for your board?

 

[werewolfman]

0022 is because the CR isn't getting the signal needed to release the CPU.

Wire positioning and soldering is paramount. Just confirm you flashed the right timing file for your board?

should this be enough ? or do i have to verify using something else?

 

[Martin C]

No, that looks fine.

Therefore it's either your wiring position or the soldering. Remember that Jaspers can be very tricky.

Flash the ECC file back and boot it 10 times, each time leave it for 2 mins to see if anything happens.

 

[werewolfman]

another update for this endless task:
i did as the pic...removed wires ..cleaned...resoldered both to xbox & CR
soldered the orange wire to the alt point underside the board (i used a blue wire)
routed the cpu reset wire (originally blue but i replaced it with an orange utp wire) from above the board not the bottom to separate as shown
re-routed all the wires as shown
tried...> xell from the first boot..got the cpu key...

soo much joy...i hot glued to fix with the same working routes (on empty spots) with some tape...soldered the points to protect efuses --->fix in the board in the chasis---> power...no *@#$% glitch
removed the short for these 2 points...still no boot
tried all routing and it was 5 AM so i called it for a day (as i think u say)
i am getting mad at this jasper

any advices ?

another important question i tried to build the freeboot dash with the cpu key and it worked but i have these parts from the multibuilder 7 log...i highlighted the parts i am concerned with...please tell me if this is the normal
---------------------------------------------------------------

------ Checking .\my360\nanddump.bin ------
Loading NAND dump (0x22ee70 bytes)...done!
NAND dump is from a small block machine
NAND dump uses big block controller
parsing dump into user and spare...
done!
decrypting KeyVault at address 0x4000 of size 0x4000
keyvault decrypted OK, will use if no kv.bin is provided
decrypting SMC at address 0x1000 of size 0x3000
SMC decrypted OK, will use if no external smc.bin is provided

------ Loading bootloaders and required security files ------
reading .\my360\smc.bin failed, using smc.bin from nand dump
reading .\my360\kv.bin failed, using kv.bin from nand dump
reading .\14699\cb_6750.bin (0x9a40 bytes)
reading .\14699\cd_8453.bin (0x5780 bytes)
reading .\14699\ce_1888.bin (0x5606a b pad 0x56070 b)
reading .\my360\xell-gggggg.bin (0x40000 bytes)
reading .\14699\cf_14699.bin (0x4450 bytes)
reading .\14699\cg_14699.bin (0x67168 b pad 0x67170 b)
reading .\14699\bin\patches_fat.bin (0x6f0 bytes)
reading .\my360\smc_config.bin failed, using smc_config.bin from nand dump
-------------------

------ adding 4 security files ------
reading .\my360\crl.bin (0xa00 bytes)
writing as crl.bin to flash
crl appears crypted, attempting to decrypt with CPU key...failed! Trying alternate key...success!
reading .\my360\dae.bin (0xad30 bytes)
writing as dae.bin to flash
dae appears encrypted, attempting to decrypt with CPU key...failed! Attempting to decrypt with alternate key...
success!
reading .\my360\extended.bin (0x4000 bytes)
writing as extended.bin to flash
reading .\my360\secdata.bin (0x400 bytes)
writing as secdata.bin to flash

 

[Martin C]

Load your 16MB original dump into 360 Flash Dump Tool.

Go to edit config and post a screenshot.

 

[werewolfman]

here we go
thanx for the great support martin

 

[Martin C]

ok - so wiring is good as you booted to XeLL.

log is good - you def have a 16MB Jasper.

Try the 68nF cap between GND and A to help with consistent boot.

EDIT: get 360 Flash Dump Tool 0.97 as your version is outdated.

 

[werewolfman]

ok..thanx man..i will play with it again later this night hopefully

 

[werewolfman]

well...lost again
here is what i did
since i had the cpu key i made the hacked dash with multi_builder7 as stated b4 but since xell didn't start again..i decided to write the 1st 50 blocks of the original nand to be sure nothing is shorted...and it worked as usual when CR is in prog mode and after some tries it even started the original dash with CR in normal mode twice (from 20 tries)...so i decided to write the hacked dash with nandpro (-w16) and start from there
but it won't start at all....
the green led just keep flashing (half a sec) every 5 sec .
sometimes when i try diff. cpu_rst cable length the green led stays on for longer period (almost 2 sec)

I tried a capacitor (supplied with CR)
i did many rewiring...
i even tried a shielded cable for cpu_rst
nothing ...i have no idea what to do now
completely lost

and i have another confusing thing...
as i said b4 i dumped my nand as a 16 jasper since the flash config was 23010
and the new flash tool gave me the pic attached 16-1, 16-2 (jasper 4.0)
but since i didn't want to take any chances i also dumped 64 just in case but when i open it in flash tool it gave me pic 64-1, 64-2 (jasper 4.1)
is that normal ?
ad any advices ?
i don't quit easily but this is tiresome
thanx in advance