Per Stuart @ Toradex, I am posting here to get some documentation on flashing buildroot images to the Apalis i.MX6. I understand that Toradex prefers Yocto, but for many embedded systems, Buildroot is a better choice.
Their documentation is quite good for the Apalis i.MX6 actually, but falls short on flashing to the Apalis. The do reference a Toradex document, but it is not a direct map and I’m not finding my way.
Apalis configuration is already in the long-term support release of Buildroot.
Yet I still can’t seem to combine their tips and the referenced Toradex document into something that actually works as far as flashing the device.
Please invest a few minutes to provide this information. It’s quite simple and will help many people beside myself. We’re not asking you to support buildroot–it’s fine to leave that up to the user. Just asking for the very basic recipe of device-specific flashing commands to get from their “output/images” directory onto the SD card and onto the Toradex module. I think this is quite minimal on your end and quite useful for many people. I’m sure it’s just a few commands.
I will even promise to add your instructions to their README file via a pull request.
For flashing the parts of the Image created by Buildroot to the Toradex module, you can integrate these parts to Legacy Image or Toradex Easy Installer Image. Afterwards, you install the new customised image using the Legacy Procedure or using Toradex Easy Installer. Feel free to ask if you have any other questions.
I could do it successfully. I also noticed that it works well with Apalis-iMX6_LXDE-Image_2.7-20180104.tar.bz2 but not with Apalis-iMX6_LXDE-Image_2.8b5.156-20181228.tar.bz2.
One more thing is that if I copy the zImage to apalis-imx6_bin/ folder, the system will use the same kernel provided in the tarball. If I enable the uImage in Buildroot then use it instead of the zImage, the expected kernel (in Buildroot) will be loaded correctly.