petecarlson
02-18-2008, 03:54 PM
When using mkfwimage to create an image for the LS2, there is no linux filr to re-write when doing an upgrade.
root@OpenWrt:/tmp# cat /proc/mtd
dev: size erasesize name
mtd0: 00030000 00010000 "RedBoot"
mtd1: 000b0000 00010000 "kernel"
mtd2: 002e0000 00010000 "rootfs"
mtd3: 00020000 00010000 "cfg"
mtd4: 0000f000 00010000 "FIS directory"
mtd5: 00001000 00010000 "RedBoot config"
How would one go about a reflash without having to tftp the default LS2 firmware and then use the web page on the LS2 to upgrade to the new 3rd party firmware. Obviously it is possible as the LS2 default firmware has the capabilities to do so. Which files should I re-flash? Does fwsplit split the bin into the correct files? If so does anyone have an example of usage? The docs are a little light.
It would seem that kernel is openwrt-atheros-vmlinux.lzma
and rootfs is openwrt-atheros-root.jffs2-64k
root@OpenWrt:/tmp# cat /proc/mtd
dev: size erasesize name
mtd0: 00030000 00010000 "RedBoot"
mtd1: 000b0000 00010000 "kernel"
mtd2: 002e0000 00010000 "rootfs"
mtd3: 00020000 00010000 "cfg"
mtd4: 0000f000 00010000 "FIS directory"
mtd5: 00001000 00010000 "RedBoot config"
How would one go about a reflash without having to tftp the default LS2 firmware and then use the web page on the LS2 to upgrade to the new 3rd party firmware. Obviously it is possible as the LS2 default firmware has the capabilities to do so. Which files should I re-flash? Does fwsplit split the bin into the correct files? If so does anyone have an example of usage? The docs are a little light.
It would seem that kernel is openwrt-atheros-vmlinux.lzma
and rootfs is openwrt-atheros-root.jffs2-64k