U-Boot: dmesg | grep -i 'bad' --> Bad eraseblock 72 at 0x000000900000 August 29, 2021 01:00AM |
Registered: 7 years ago Posts: 13 |
/tmp/tools # dmesg | grep -i 'bad' <6>[ 0.960000] Scanning device for bad blocks <4>[ 0.970000] Bad eraseblock 72 at 0x000000900000 <5>[ 1.340000] UBI: number of bad PEBs: 0 <5>[ 1.370000] UBI: number of PEBs reserved for bad PEB handling: 8
Re: U-Boot: dmesg | grep -i 'bad' --> Bad eraseblock 72 at 0x000000900000 August 29, 2021 01:26AM |
Admin Registered: 14 years ago Posts: 19,558 |
Quote
4. Be sure there is no bad block in the first 1M of your NAND (check dmesg). This is very important, if there is bad block in the first 1M (8 blocks), don't flash u-boot, because you will almost certainly brick your box. Please post your question here (there is a work around for it).
Example of bad block in mtd0:
dmesg | grep -i 'bad'
[ 2.413231] Scanning device for bad blocks
[ 2.417731] Bad eraseblock 3 at 0x000000060000
This bad block is the 4th block which resides within mtd0 (block 0 to block 7). So u-boot should not be flashed.