Quote:
Originally Posted by arrrghhh
Ran mtty task28... Here's the output:
Code:
Cmd>task 28
Format start
Fill RSVD information for block 351 to 384
Storage start sector=0x1A900, total sector=0x1F700
Storage start block=1733, total block=2012
Total Bad Block in CE: 1
Erase physical block from 2087 to 3944
formatstorage Bad block found: 2555
formatstorage Bad block found: 3022
si backup: Erase physical block from 4080 to 4096
Format end
I thought this was normal, to have bad blocks shipped with NAND devices...
Nate, actually found that thread on my own - thanks for the post tho. I didn't see any commands about searching for bad blocks, task28 is correct... no? Task29 I know is to wipe the device, which I certainly can do again, but have already tried... The thread didn't seem to address this.
Edit - did a task29 just for fun. Output is below, appears I do have a couple of bad blocks... but again, I thought this was expected:
Code:
Cmd>task 29
Format BINFS start
CE start start block=384, total block=3712
ERASE block 2204 FAIL !!!
ERASE block 2671 FAIL !!!
Write 0xFF start page=0x6000, total page=0x3A000
Format BINFS end
|
hmm.. yes and no. I run thos bad boys too with no bad blocks. But we should be able to handle them since they can happen.
Now its hard for me to see where these blocks are in terms of tinboot. We may need to change your offset around to skip those parts.
Edit: may need to reach out to the godfather dzo and see how vogue handles bad blocks