Ian Pangilinan <[email protected]> writes: > The device comes in two variants depending on where the bootloader > loads the kernel. One variant where the bootloader loads at 0xbc140000 > (mtd4), and another at 0xbe800000 (mtd5). This patch is for the latter. > I haven't found a way to change this behavior, so I'm making a > distinction between the two. > > This is the MTD partitions from the stock firmware: > > 0x000000000000-0x000007f80000 : "ALL" > 0x000000000000-0x000000080000 : "Bootloader" > 0x000000080000-0x000000100000 : "Config" > 0x000000100000-0x000000140000 : "Factory" > 0x000000140000-0x000002800000 : "firmware1" > 0x000002800000-0x000004ec0000 : "firmware2" > 0x000002996dfc-0x000004ec0000 : "rootfs" > 0x000003180000-0x000004ec0000 : "rootfs_data" > 0x000004ec0000-0x000007f00000 : "ota" > 0x000007f00000-0x000007f80000 : "Configbak" > > This is how it looks when flashed to OpenWrt with this patch: > > 0x000000000000-0x000000080000 : "u-boot" > 0x000000080000-0x0000000a0000 : "u-boot-env" > 0x000000100000-0x000000140000 : "factory" > 0x000000140000-0x000002800000 : "ubiconcat0" > 0x000002800000-0x000002c00000 : "kernel" > 0x000002c00000-0x000007f00000 : "ubiconcat1" > 0x000007f00000-0x000007f80000 : "configbak" > 0x000000000000-0x0000079c0000 : "ubi"
This sounds strange. The above looks like a pretty common dual partition scheme, where one or more variables in the "Config"/"u-boot-env" partition decides which system partition is booted by default. Could you please dump the contents of "Config"/"u-boot-env"? Are you 100% sure there isn't anything there telling U-Boot which partition is active? Bjørn _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
