[Buildroot] [PATCH] configs/toradex_apalis_imx6: bump to U-Boot 2016.11 and kernel 4.1.41.

Sergio Prado sergio.prado at e-labworks.com
Tue Aug 15 23:19:28 UTC 2017


Hello Arnout,

2017-08-15 13:01 GMT-03:00 Arnout Vandecappelle <arnout at mind.be>:
>
>  Hi Sergio,
>
> On 13-08-17 18:01, Sergio Prado wrote:
> [snip]
> > -BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
> > -BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME="u-boot.imx"
> > +BR2_TARGET_UBOOT_FORMAT_IMG=y
>
>  Did the image really change from u-boot.imx to u-boot.img? Or was there a
> mistake here and didn't you test properly?

Yes, It has changed. Since Toradex V2.7 SDK, they changed u-boot image from
u-boot.imx to SPL + u-boot.img, as you can see from the link below.

http://developer.toradex.com/knowledge-base/build-u-boot-and-linux-kernel-from-source-code#imx-6-based-modules-apaliscolibri-imx6

>  BTW, I tried to get this information by looking at the readme.txt, which
refers
> to the website [1], but after looking at all this I still have no idea
how to
> flash the U-Boot image generated by Buildroot...

There is a undocumented step. In the "Preparation" step in the link below,
after downloading the Toradex BSP binary image, we should update it with
the images generated by Buildroot (SPL, u-boot.img, zImage, rootfs). Do you
think documenting that in the readme.txt file is enough? It is really a
mess the way they implemented the process to update eMMC.

http://developer.toradex.com/knowledge-base/flashing-linux-on-imx6-modules

Best regards,

Sergio Prado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170815/3d84e6ef/attachment-0002.html>


More information about the buildroot mailing list