U-Boot: saveenv fails because can't erase bad block

farrah

Hi,

I'm using u-boot.bin 1.2.0 that came with the dvsdk 2.0. I used serial flash loader to program UBL and U-Boot. However saveenv fails because u-boot can't erase a bad block. So I downloaded u-boot tarball from DVSDK 3.10. UBL jump to entry point and hangs. CCS can no longer connect. How do I erase nand and how do I deal with a bad block in the environment?

Farrah

over 15 years ago

0 farrah over 15 years ago

Prodigy 220 points

I was able to restore u-boot 1.2.0, however, I still don't know how to deal with a bad block in the environment. Is there an updated version of u-boot for the DM6467?

0 Sekhar Nori over 15 years ago in reply to farrah

TI__Expert 6385 points

Hello,

Typically, U-Boot stores environment at a fixed location in NAND. Can you please check the value of CONFIG_ENV_OFFSET in the configuration file (present in include/configs within U-Boot source).

Most NAND devices guarantee block 0 to be good for 1000 erase cycles. You can set this value to 0 to use this for U-Boot environment. UBL is stored in block 1.

Thanks,

Sekhar

0 farrah over 15 years ago in reply to Sekhar Nori

Prodigy 220 points

Hi,

Solved the problem with following two fixes:

#1: Fixed bug in drivers/nand/nand_base.c:

Changed

mtd->oobsize = (8 << (extid & 0x03)) * (mtd->oobblock / 512);

mtd->oobsize = (8 << (extid & 0x01)) * (mtd->oobblock / 512);

#2: Applied patch to common/env_nand.c

http://git.denx.de/?p=u-boot.git;a=commitdiff;h=cc49cadeeb8bb2f0ae3fdc13af7051ae59f083bc;hp=8155efbd7ae9c65564ca98affe94631d612ae088

Farrah

Processors

Processors forum

U-Boot: saveenv fails because can't erase bad block