Hi Mitsus,
Testing the fconfig throws the following error and the issue is due to RedBoot config size.
root@OpenWrt:/# fconfig -w -v -d /dev/mtd3 -n bootp -x TRUE
Low verbosity messages are printed.
Normal verbosity messages are printed.
Failed to open device or file /dev/mtd3!
Could not get a config data handle!
root@OpenWrt:/#
also can't unlock Redboot Config mtd3
root@OpenWrt:/# mtd unlock mtd3
Unlocking mtd3 ...
Could not open mtd device: mtd3
whereas unlock other mtd's
root@OpenWrt:/# mtd unlock mtd4
Unlocking mtd4 ...
root@OpenWrt:/#
root@OpenWrt:/# cat /proc/mtd and dmesg shows that the erase size of RedBoot config size is 0x1000 and not 0x20000
dev: size erasesize name
mtd0: 00060000 00020000 "RedBoot"
mtd1: 00100000 00020000 "kernel1"
mtd2: 00300000 00020000 "rootfs1"
mtd3: 00001000 00020000 "RedBoot config"
mtd4: 00020000 00020000 "FIS directory"
5 RedBoot partitions found on MTD device IXP4XX-Flash.0
Creating 5 MTD partitions on "IXP4XX-Flash.0":
0x00000000-0x00060000 : "RedBoot"
0x00060000-0x00160000 : "kernel1"
0x00160000-0x00460000 : "rootfs1"
0x00fc0000-0x00fc1000 : "RedBoot config"
mtd: partition "RedBoot config" doesn't end on an erase block -- force read-only
0x00fe0000-0x01000000 : "FIS directory"
Can you please tell me, should I need to update the Redboot bootloader ( resize to 0x20000) or modify
the linux mtd driver ?
Sara