Using --size in the imx-imx-boot-bootpart.wks.in to set size of /boot
partition does not result in a 256MiB partition as expected but in a
~332MiB one. Indeed, --size ensures --extra-space (default 10MiB) is
added to actual data size and furthermore applies --overhead-factor
(default 1.3) to the wanted size. This is exactly the case here as 256
* 1.3 = 332.8.
Use --fixed-size instead to force the /boot partition to be exactly
256MiB just as it is indicated in the comments of this file.
Consequently, the `do_image_wic` task will also fail if data copied in
this partition are too large at creation.
Signed-off-by: Jonathan GUILLOT <jonathan@joggee.fr>
(cherry picked from commit 0ee7c736c7)
For i.MX 9 a typical kernel is 35 MB. With gcov, that increases to 75 MB
or more. Bump the /boot partition size accordingly.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Using the UUU-tagged bootloader image directly with UUU can cause UUU
to hang. The bootloader image is split on a certain transmit size, and
the hang occurs if the tag does not fit with the final bytes of the
bootloader image and must be split into a new transmit package.
The UUU tag is needed by UUU only in the SD Card image file itself so
that UUU can find the end of the boot partition.
Rework the design so the default bootloader and the default imx-boot
binaries are not tagged.
Also, extend the UUU tagging to fslc so it can gain the same benefit.
Fixes: https://github.com/Freescale/meta-freescale/pull/1762
Fixes: https://github.com/nxp-imx/mfgtools/issues/416
Co-authored-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
${IMAGE_LINK_NAME} already contains "rootfs" at the end, therefore it does not
need to be added explicitly. Otherwise the wic creation fails with:
wic.filemap.Error: cannot open image file '.../build/tmp-glibc/deploy/images/imx233-olinuxino-maxi/core-image-minimal-imx233-olinuxino-maxi.rootfs.rootfs.uboot-mxsboot-sdcard'
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Now that we have a symlink with constant name 'imx-boot' independent
on the use of the MACHINEOVERRIDE 'imx-boot-container', drop the
additonal imx-boot-container-bootpart file as imx-imx-boot-bootpart
does the same thing.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Recent version of U-Boot v2022.01 reverted boot container generation
mechanism to provide single boot container isntead of separate binaries
for SPL+DDR and U-Boot FIT. New approach provides packing of those
separate components inside the U-Boot binman, and is delivered as a
single 'flash.bin' file, which resembles the original behavior before
binman image packing was introduced.
Adapt our boot container class and WIC file to pick up this consolidated
binary instead of two separate pieces.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
Add new WKS template file, which uses the boot container provided by
mainline U-Boot.
Boot container built as a part of U-Boot packs binary components into
two separate files, namely 'flash.bin' and 'u-boot.itb'. First file
contains SPL, while second one represents the FIT image containing
U-Boot and ATF blob.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
The u-boot env offset in the imx-boot partition is 4MiB,
so set the boot partition alignment to 8MiB to fix the overlap.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
The layout comment was incorrect. It was missing the start of the
rootfs and what was there wasn't updated when the boot partition
was increased to 64MiB.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Some boards expects a specific binary name.
Example : Pico i.MX7D required the u-boot-dtb.img file (instead of u-boot.img).
Signed-off-by: Joris Offouga <offougajoris@gmail.com>
The i.MX8 / i.MX8X kernel's size is about 22MB.
Increase the boot partitions minimum size to have space for two kernel
images and have a constant partition size.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Some boards expects a specific binary name.
Example : WaRP7 required the u-boot-dtb.imx file (instead of u-boot.imx).
Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
Signed-off-by: Joris Offouga <offougajoris@gmail.com>
The i.MX 8QXP bootrom in B0 silicon reads the 1st image container at offset 32k
while tha A0 silicon started at 33k. The machine configurations already contain
the variable IMX_BOOT_SEEK to specify the needed offset.
Change the wks file accordingly.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
imx8 family boards use u-boot as boot loader in addition to some other
binaries. The final bootloader binary is gathered by mkimage into a file
called imx-boot.
Add the wks file to create the wic image tailored for imx8 family.
Set the wks file as default for all imx8.
Signed-off-by: Daiane Angolini <daiane.angolini@nxp.com>
The binary is generated as part of the image build so it should use
the same naming schema to provide consistency. This also fixes the wks
templates which use it.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Those are untested and anyone interested in supporting them (mainly
barebox) ought to send the support to OE-Core instead.
This also removes the corresponding code from the
image_types_fsl.bbclass as it is not going to be used from now on.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The image needs to use the U-Boot generated, for the uSD card, so a
dependency on that must be added to ensure the file is available prior
'wic' uses it.
Besides that, the fstype needs to be changed so it sets the partition
mark allowing the bootrom to find it.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This includes the wic templates which use a separated boot
partition. This allow for easier migration from the new deprecated
sdcard generation class.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Some old SoC has problems to read GPT partition tables so we use
'msdos' as default here and if some vendor wants to override it, it
can still be done in their wks files.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The wic looks for wks files in many places. The root layer directory
is one of those and makes much easier to find the wks files for
reference and use.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
