Jtag Nand Error!

ruddyrum

Inactive User
Joined
Sep 1, 2007
Messages
676
Reaction score
30
Ok, so this is what i get... Each line takes aprox 5 secs

left it on for a few min, and got to 80, then i gave up! What could be causing this - I read the troubleshooting, but nothing seems to shed any light on the situation!!!

Code:
You don't have permission to view the code content. Log in or register now.
 
same happend to me was down to bad soldering plus i did not use a diode switch..

so i just soldered it again and added a diode switch and every thing was perfect..
 
Read that long cables may cause problems, - mine was 1.2m... chopped it down to 60cm and seems to be working fine!!!
 
I had the same trouble getting the right FlashConfig

in the end i shortend the cable and got the correct FlashConfig


For Xenon/Zephyr/Opus/Falcon
FlashConfig: 01198010
For Jasper (16MB)
FlashConfig: 00023010
For Jasper (256MB)
FlashConfig: 008A3020
256MB NAND Detected
For Jasper (512MB)
FlashConfig: 00AA3020
512MB NAND Detected
 
That is a common problem, the recommended is between 8-8 inches.

Jama
 
Well, just for shits and giggles (and have nothing else constructive to do this afternoon/evening) I decided to dump my NAND at various cable lengths to see what happens. I cut 10cm off after every 2 or 3 dumps, thats if it even read the NAND at all...

Results are as follows:

1.2M - nothing!
1.1M - nothing!
1.0M - nothing!
0.9M - Dump, but loads of errors
0.8M - Dump with few errors
0.7M - Dump was not the same as my original.bin - had to do multiple reads from the NAND, and then compare various dumps (so dumps without errors, but apparently not that well)
0.6M - Was a Good dump and all dumps were consistent!
0.5M - Again, same as before, good consistent dumps
0.4M - I think we've already established that any cable less than 0.6M will work fine!!!
0.3M - Can't test any less than 38cm as thats how far my lpt port is from the top of my chasis where the xbox sits!!!

I only did this as i had nothing better to do, I'm sure other systems/rigs may varey! I'm pretty sure its safe to say that any cable around 0.6/0.5 m (thats pretty much anything below 2 foot) will work just fine!

P.S. Only reason i've done this is because the console which is jtag exploitable has the 3 red ring o' death! only thing i can do is j'tag it, until my x-clamp kit arrives :proud:
 
Well, just for shits and giggles (and have nothing else constructive to do this afternoon/evening) I decided to dump my NAND at various cable lengths to see what happens. I cut 10cm off after every 2 or 3 dumps, thats if it even read the NAND at all...

Results are as follows:

1.2M - nothing!
1.1M - nothing!
1.0M - nothing!
0.9M - Dump, but loads of errors
0.8M - Dump with few errors
0.7M - Dump was not the same as my original.bin - had to do multiple reads from the NAND, and then compare various dumps (so dumps without errors, but apparently not that well)
0.6M - Was a Good dump and all dumps were consistent!
0.5M - Again, same as before, good consistent dumps
0.4M - I think we've already established that any cable less than 0.6M will work fine!!!
0.3M - Can't test any less than 38cm as thats how far my lpt port is from the top of my chasis where the xbox sits!!!

I only did this as i had nothing better to do, I'm sure other systems/rigs may varey! I'm pretty sure its safe to say that any cable around 0.6/0.5 m (thats pretty much anything below 2 foot) will work just fine!

P.S. Only reason i've done this is because the console which is jtag exploitable has the 3 red ring o' death! only thing i can do is j'tag it, until my x-clamp kit arrives :proud:
That is possibly one of the most useful posts i've seen anywhere in a while :)

+1 INTERNET FOR YOU

Jama
 
Back
Top