This console has been bugging me for ages. I built it for someone ages ago with XBR and I remember having to remap the bad blocks for it and its been fine, I got it back to update to freeboot and so far have not been able to get it to work, during boot it starts the swirl then goes to E71. Putting the original image back in there works fine.
Its a 64M image Jasper.
Flashtool reports a little bit of weirdness:
It reports bad blocks at 4 locations but then only finds 2 of those bad blocks relocated
Note: Bad Block ID0x00AE [offset 0x166E000]
Note: Bad Block ID0x00AF [offset 0x168F000]
Note: Bad Block ID0x016A [offset 0x2EAA000]
Note: Bad Block ID0x016B [offset 0x2ECB000]
Block ID 0X016B found @ 0x1FC [Offset: 0x0417C000]
Block ID 0X016A found @ 0x1FD [Offset: 0x0419C000]
I have tried unmapping the extracted nand then using a tool (peanuts tried pig too) to produce freeboot then remapping and writing back into the nand, the result is always the same, the box boots xell no problem, but locks up i imagine on the second kernel
I tryed using xellous and updflash.bin to write the unmapped freeboot and allowing it to use its own remapping to remapp the blocks on both a unmapped and mapped image, neither worked. This thing is driving me nuts
What I do notice is the bad blocks were found at 1FC and 1FD does that imply there is data in 1FF and 1FE that flash tool has not picked up? I tried mapping the data from 0AE and 0AF into 1FF and 1FE (both ways because thinking about which way they go in does my head in)but that did not work either.
During the read process I get a whole bunch of read errors, when I write back I only get two locations I can't write too (which I assume is the two flash tool found)
the read errors are as follows using a USB reader:
Error: 250 reading block 578
Error: 210 reading block 579
Error: 210 reading block 57A
Error: 210 reading block 57B
Error: 210 reading block 57C
Error: 210 reading block 57D
Error: 210 reading block 57E
Error: 210 reading block 57F
Error: 250 reading block B58
Error: 210 reading block B59
Error: 210 reading block B5A
Error: 210 reading block B5B
Error: 210 reading block B5C
Error: 210 reading block B5D
Error: 210 reading block B5E
Error: 210 reading block B5F
I have been looking for a way of translating what flash tool reports as bad locations into these locations. But at least knowing if any of the above blocks are actually important ones would be a start.
Apologize in advance if this answer is staring me in the face, I have done the appropriate searching and spend enormous amount of time trying to fix this thing, I am a hardware guy and this looks like a software problem