On 8/21/15, 6:43 AM, "openwrt-devel on behalf of Jonas Gorski" <[email protected] on behalf of [email protected]> wrote:
> On 21.08.2015 13:39, John Crispin wrote: >> >> >> On 21/08/2015 13:28, Jonas Gorski wrote: >>> On 21.08.2015 13:24, John Crispin wrote: >>>> >>>> >>>> On 21/08/2015 13:17, Jonas Gorski wrote: >>>>> The stock QSDK expects the ubi to be wrapped in an itb image, so >>>>> provide one for easy sysupgrade from QSDK. >>>>> >>>>> FIXME: currently does not work? Seems to flash fine, but ubi cannot >>>>> be mounted by OpenWrt and needs to be flashed a second time. >>>> >>>> how do you flash it the second time ? using the same process ? >>> >>> Booted a ramdisk OpenWrt kernel, then flashed the ubi with ubiformat. Which >>> didn't seem to differ from what the preinstalled QSDK did, but somehow >>> works. >>> >>> Jonas >>> >> >> does sysupgrade work from owrt->owrt ? > > Yes, even without the last two patches. The last two are only for "easy" > sysupgrade from QSDK (in theory). Therefore also as RFC. The following patch is somehow causing the issue: target/linux/generic/patches-3.18/494-mtd-ubi-add-EOF-marker-support.patch Still investigating further. [ 3.295677] UBI: auto-attach mtd11 [ 3.295698] UBI: attaching mtd11 to ubi0 [ 3.334563] UBI: EOF marker found, PEBs from 29 will be erased [ 3.334725] UBI: scanning is finished [ 3.339293] UBI error: ubi_read_volume_table: the layout volume was not found [ 3.343386] UBI error: ubi_attach_mtd_dev: failed to attach mtd11, error -22 [ 3.350150] UBI error: ubi_auto_attach: cannot attach mtd11 But with the above patch removed the board will boot when flashed from u-boot. -M _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
