Do stock MTD values matter?
[root@Pogoplug ~]# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "root" ## guide says this should be rootfs, but root is my default, should I change?
mtd3: 05b00000 00020000 "data"
How do I save this nand dump after I run the following command?
nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0
Can I be sure I don’t have a bad block in the first 8 blocks of MTD0?
[root@Pogoplug dev]# dmesg | grep -i 'bad'
[ 1.050000] Scanning device for bad blocks
[ 1.070000] Bad eraseblock 250 at 0x01f40000
[ 1.080000] Bad eraseblock 513 at 0x04020000
I don’t have anything for mtdparts when I try to print envs, what should I restore here if anything?
fw_setenv mtdparts 'xxxxxxxxx'
Thanks for any clarifications.
[root@Pogoplug ~]# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "root" ## guide says this should be rootfs, but root is my default, should I change?
mtd3: 05b00000 00020000 "data"
How do I save this nand dump after I run the following command?
nanddump --noecc --omitoob -l 0x80000 -f mtd0 /dev/mtd0
Can I be sure I don’t have a bad block in the first 8 blocks of MTD0?
[root@Pogoplug dev]# dmesg | grep -i 'bad'
[ 1.050000] Scanning device for bad blocks
[ 1.070000] Bad eraseblock 250 at 0x01f40000
[ 1.080000] Bad eraseblock 513 at 0x04020000
I don’t have anything for mtdparts when I try to print envs, what should I restore here if anything?
fw_setenv mtdparts 'xxxxxxxxx'
Thanks for any clarifications.