Error: 250/210 reading block ?

[Neddy990]

This might be a silly question, Just wanted to make sure before going any further, First time using nand-x

I am following this guide:

http://team-xecuter.com/forums/showthread.php?t=75749

I am getting these errors when dumping the nand, using a nand-x, Its a 256 Jasper.

Looking for usb interface device
Flash Config: 0x008A3020
Block Size: 128KB Block Limits: 0x000000..0x000FFF
File: nanddump.bin
Reading
Error: 250 reading block D58
Error: 210 reading block D59
Error: 210 reading block D5A
Error: 210 reading block D5B
Error: 210 reading block D5C
Error: 210 reading block D5D
Error: 210 reading block D5E
Error: 210 reading block D5F
0FFF

This is the command I am using to dump it

NandPro.exe usb: -r64 nanddump.bin

Is this command right and are these errors anything to worry about ?

I have dumped it several times and the errors come up every time but the dumps do match using the FC command in the guide.

Thanks

 

[smalltylynch]

i would suggest to check you soldering and make sure you have a good connection where you have soldered if you post pictures that will really help

 

[Neddy990]

Hi

I thought dumps that don't match were a wiring/connection fault?

All my dumps are the same.. I have checked the connections and all appear good, but I am using pin headers so is quite difficult to tell..

 

[seanr28]

You are correct, just remap them.....

 

[Martin C]

Just open in 360 Flash Dump Tool. If the bad block at 0xD58 has been remapped, then you're good to go.

---------- Post added at 17:45 ---------- Previous post was at 17:44 ----------

You are correct, just remap them.....

No - don't touch them. There's absolutely no need.

Once you're ready to build the RGH image, use multi_builder and it will do it all for you.

 

[Neddy990]

Just open in 360 Flash Dump Tool. If the bad block at 0xD58 has been remapped, then you're good to go.

How do I tell if it has been remapped in 360 Flash Tool ?

not sure if this is any help but this is what the 360 flash tool says and the bad block tab..



The 6bl & 7bl are blank (unlike the guide im following) is that right for a jasper?

Thank you all for the help, It is very much appreciated

 

[Pazoozoo]

Opss forgot to refresh my browser.

 

[Neddy990]

I figured I would flash it anyway, soldered the coolrunner wires, they are tiny points, but found it fairly easy.

All went well but it wouldn't glitch (or I just wasn't leaving it long enough?..) so I added the cap that came with the coolrunner to A and Ground on the coolrunner.. I didn't realise one came with the coolrunner before ordering it, thought I might have to hunt one down.. anyway that worked and it glitched first time

So I did all the xell stuff, made the new nand image and flashed that and it froze every time on the boot up animation, read some where to try without the dashlaunch patches, but that was the same, so I tried moving the bottom wires, I separated the green and blue as they were quite close making sure to avoid them 2 coils again.

It has now booted a few times perfectly

Need to work out how to hold the power to the pin headers.. The few tests I have done I am holding the wire against the pin, which isn't exactly ideal :facepalm:

Also need to make another image with the dashlaunch patches and flash it, although not sure what they do ?

Thanks everyone for you help :smile:

Next one will use the qsb's I think

 

[Martin C]

Dashlaunch is pretty essential. Rebuild and flash again with it.

What do you mean about hold power to pin headers? You have me baffled on this.

 

[Neddy990]

I will flash it again with them patches then

I put pin headers in J2B1, for the nand-x, but I didn't realise at the time the coolrunner power goes to one of them pins..

Like this

http://www.team-xecuter.com/forums/showpost.php?p=472475&postcount=28

That's what I was planning on doing but I have not found an end for the red wire yet..

The qsb's would have been easier, which I have got, but didn't want to de-solder these pin headers. Next one will use them