Hi, On 27.1.2019 1.13, Hauke Mehrtens wrote: > On 1/14/19 6:54 PM, Oskari Lemmela wrote: >> Use LZMA compressed fit image to load kernel and dtb. >> Fit image can be used load kernel and dtb from SPI flash. >> >> Signed-off-by: Oskari Lemmela <osk...@lemmela.net> >> --- >> package/boot/uboot-sunxi/uEnv-a64.txt | 5 ++- >> package/boot/uboot-sunxi/uEnv-default.txt | 5 ++- >> package/boot/uboot-sunxi/uEnv-pangolin.txt | 5 ++- >> target/linux/sunxi/Makefile | 2 +- >> target/linux/sunxi/cortexa53/target.mk | 1 - >> target/linux/sunxi/image/Makefile | 17 +++++++--- >> target/linux/sunxi/image/cortex-a53.mk | 25 ++++----------- >> target/linux/sunxi/image/cortex-a7.mk | 36 +++++++++++----------- >> target/linux/sunxi/image/cortex-a8.mk | 11 ++++--- >> 9 files changed, 49 insertions(+), 58 deletions(-) >> > My H3 Xunlong Orange Pi R1 does not boot fit images, CONFIG_FIT is not > set in my U-Boot configuration. > > I am getting this error: > ------------------------------------------------------------------- > Scanning mmc 0:1... > Found U-Boot script /boot.scr > 301 bytes read in 1 ms (293.9 KiB/s) > ## Executing script at 43100000 > 2770296 bytes read in 125 ms (21.1 MiB/s) > Wrong Image Format for bootm command > ERROR: can't get kernel image! > SCRIPT FAILED: continuing... > > Device 0: device type unknown > ... is now current device > ethernet@1c30000 Waiting for PHY auto negotiation to complete.. done > BOOTP broadcast 1 > ------------------------------------------------------------------- > > I activated these U-Boot configuration options: > CONFIG_FIT=y > CONFIG_LZMA=y > and now I am hitting the next problem: > ------------------------------------------------------------------- > Found U-Boot script /boot.scr > 301 bytes read in 2 ms (146.5 KiB/s) > ## Executing script at 43100000 > 2772324 bytes read in 126 ms (21 MiB/s) > ## Loading kernel from FIT Image at 43300000 ... > Using 'config@1' configuration > Trying 'kernel@1' kernel subimage > Description: ARM OpenWrt Linux-4.14.95 > Type: Kernel Image > Compression: lzma compressed > Data Start: 0x433000e4 > Data Size: 2755114 Bytes = 2.6 MiB > Architecture: ARM > OS: Linux > Load Address: 0x42000000 > Entry Point: 0x42000000 > Hash algo: crc32 > Hash value: 62b0495d > Hash algo: sha1 > Hash value: ca607078b06de248018641320577e910a1967dab > Verifying Hash Integrity ... crc32+ sha1+ OK > ## Loading fdt from FIT Image at 43300000 ... > Using 'config@1' configuration > Trying 'fdt@1' fdt subimage > Description: ARM OpenWrt sun8i-h2-plus-orangepi-r1 device tree blob > Type: Flat Device Tree > Compression: uncompressed > Data Start: 0x435a0c54 > Data Size: 15325 Bytes = 15 KiB > Architecture: ARM > Hash algo: crc32 > Hash value: c9c29924 > Hash algo: sha1 > Hash value: 6f4bee23444eb246cc8287c40ebb240cdf45aa9d > Verifying Hash Integrity ... crc32+ sha1+ OK > Booting using the fdt blob at 0x435a0c54 > EHCI failed to shut down host controller. > EHCI failed to shut down host controller. > Uncompressing Kernel Image ... Image too large: increase > CONFIG_SYS_BOOTM_LEN > Must RESET board to recover > resetting ... > ------------------------------------------------------------------- > > My H5 Xunlong Orange Pi Zero Plus works fine. > > Hauke Thanks for testing. I did not expect that some of targets does not have CONFIG_FIT enabled. I'll modify patch so that only cortex-a53 platforms use this lzma and fit image boot.
U-boot is not currently updated while running sysupgrade. That has to implemented before FIT boot can be enabled to other sunxi targets. Thanks, Oskari _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
