This isnt my first rgh but in coolshrimps every time I dump nand two errors pop up 250 reading 68 and 250 reading 260. this isn't a problem as I know its the first 50 for ecc but coolshrimps cant find two matching dumps 1 non matching block 260 yet dumps are the same . I tried a ecc build after remapping just to see system powers up green flashing light coolrunner every 5 secs no xell coolrunner programed to falcon timings as per board. the cb is 5771 and board v3. I even tried to power boot normally as this sometimes helps with ecc on falcon v3 but nothing . Two probs how can I get dumps to match read the same but states non matching . Any tips on coolrunner I heard try different timings Might try jasper The main problem is this nand dump they dump the same and always state the two errors but coolshrimps states non matching:facepalm:
bad blocks and coolshrimps not matching
- Thread starter tonyjandc
- Start date
BL4K3Y
VIP Member
Goldensavage
VIP Member
will give that a try instead of using coolshrimps will use nandpro Thanks for tips guys will get back to you and let you know how it gets on
Martin C
VIP Member
Guys - stop.
Unfortunately this is the downfall of using FC with images that have bad blocks.
It's possible the reason you have differences in 0x260 is because on read, the SPI is throwing different values for this block due it's state (Bad). Open any of your NANDs in 360 Flash Dump Tool and provided these bad blocks are being remapped, you are good to go.
If you want to confirm they match, ERASE the block from the dump and try to compare afterwards. They're bad anyway so the data in them is irrelevent.
i.e
nandpro nand1.bin: -e16 68 1
nandpro nand1.bin: -e16 260 1
nandpro nand2.bin: -e16 68 1
nandpro nand2.bin: -e16 260 1
fc /b nand1.bin nand2.bin
Otherwise you'll be forever trying to get matching dumps.
Unfortunately this is the downfall of using FC with images that have bad blocks.
It's possible the reason you have differences in 0x260 is because on read, the SPI is throwing different values for this block due it's state (Bad). Open any of your NANDs in 360 Flash Dump Tool and provided these bad blocks are being remapped, you are good to go.
If you want to confirm they match, ERASE the block from the dump and try to compare afterwards. They're bad anyway so the data in them is irrelevent.
i.e
nandpro nand1.bin: -e16 68 1
nandpro nand1.bin: -e16 260 1
nandpro nand2.bin: -e16 68 1
nandpro nand2.bin: -e16 260 1
fc /b nand1.bin nand2.bin
Otherwise you'll be forever trying to get matching dumps.
Thanks Martin knew about remapping never thought about erasing you have made my day I have 18 dumps to play with so shouldn't be a problem now to get this fekker to ecc I need dvd key lol
Martin C
VIP Member
Martin C
VIP Member
I was going to suggest this to him, but figured it's only 2 bad blocks and probably clearer to show that you can erase them for checking purposes.
This post is mainly for Martin looked at your pics of taping wires to board realised one of mine was to near a mosfet on the back of board got the wife to slap me hard retapped the wire and guess what xell booted got keys now to ggbuild and usb the new nand just to confirm xell will remap the bad blocks for me Martin your a saint as the wife said walk away and then come back to it
Martin C
VIP Member
If you use Multi_builder, you'll get a log file created and you'll see that these two blocks are being remapped 
Thanks did put post up Martin I had a look at your tapings moved one slightly to left and guess what xell popped up got keys now to confirm will xell remap bad blocks if I use ggbuild to get new dash ? saves all that hassle If this is unadvisable will remap nands
Martin C
VIP Member