Bad eraseblock - Save to flash U-Boot

Hi all,

I am looking at upgrading the ootb U-Boot of my NSA325 to the latest release from this forum. Howver when I check for bad eraseblocks in dmesg, I get following result:

[    2.047146] nand: Samsung NAND 128MiB 3,3V 8-bit
[    2.052016] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    2.059648] Scanning device for bad blocks
[    2.110339] Bad eraseblock 454 at 0x0000038c0000
[    2.173313] 9 fixed-partitions partitions found on MTD device orion_nand
[    2.180054] Creating 9 MTD partitions on "orion_nand":
[    2.185215] 0x000000000000-0x000000100000 : "uboot"
[    2.190423] 0x000000100000-0x000000180000 : "uboot_env"
[    2.195919] 0x000000180000-0x000000200000 : "key_store"
[    2.201438] 0x000000200000-0x000000280000 : "info"
[    2.206496] 0x000000280000-0x000000c80000 : "etc"
[    2.211516] 0x000000c80000-0x000001680000 : "kernel_1"
[    2.216941] 0x000001680000-0x000004640000 : "rootfs1"
[    2.222481] 0x000004640000-0x000005040000 : "kernel_2"
[    2.227914] 0x000005040000-0x000008000000 : "rootfs2"

I would read it that way, that the bad eraseblock is in 'kernel_1'. Am I correct and is it save to flash the U-Boot?

Regards
Ruediger

Ruediger,


> [ 2.059648] Scanning device for bad blocks
> [ 2.110339] Bad eraseblock 454 at
> 0x0000038c0000

Yes, it is safe to flash u-boot. The bad block is far away from block 0 to 7 (where u-boot will be flashed).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)