Originally Posted by 3absiso
What is the second "new_nand.bin"? i do not get it.
so this script is done after patching the original dump and separate it it into top and bottom dumps? ad it is done for both top and bottom dumps?
top and bottom should be treated separately. this is not related to whether you patched the NAND or not. you can call this script - "NAND copy". it overcomes the problem of bad blocks which are found (during manufacture or later) in the NAND.
What the script does is:
1. strip all the bad blocks from src_nand. (again - it can be either patched or not).
2. find all the bad blocks in tgt_nand - that is why i need new_nand.bin
3. remap data we have in (1) to the tgt_nand using what we found in (2).
************* [ - Post Merged - ] *************
Originally Posted by zoom33
ok i'm back with bad news, it doesn't work ...
the script is deleting the bad block so the output file is 135036 Kb
was before 135168 Kb
here is what I'm doing manually with an hex editor:
$5FA6000 is beginning of bad block
$5FC6FFF is end of bad block
$5FC7000 is beginning of next block
$83FFFFF is the last byte of the last block
copy data from $5FC7000 <--> $83FFFFF to $5FA6000
it means that block 1023 is the same as block 1022
am i right or wrong ?
My question now is does the dump have some kind of ECC or checksum ?
first of all, I fixed the script - so you can take it from the hjudges/NORway repository and retry.
what you did seems right to me (all the calculations). the only thing that is a) in case you have several bad blocks, and b)missing is the remapping to the new NAND.
If the new NAND doesn't have any bad blocks - you are fine. otherwise you have to remap