Lets keep things consistent by providing two possibilities for platforms to pick from - legacy boot and multi-certificate boot. In legacy boot, the base bootloader and system firmware are maintained a

We use the default IMAGE_BOOT_FILES configuration which matches up with legacy boot configuration. Document the same to allow folks to understand by just looking at the SoC include file. Signed-off-by

Switch to using all of multi-certificate boot images. This allows us to create bootable images - in this case, we are missing tiboot3.bin Signed-off-by: Nishanth Menon <nm@...> Reviewed-by: Denys D

IMAGE type and dependencies can easily be centralized to SoC include file. This is necessary to make sure that we don't do the duplication and having multiple places to fix up. Signed-off-by: Nishanth

Lets generate bmap files for bmaptool to use as well as default to use with wic files. NOTE: bmaptool can speed up flashing SD cards by 2x-3x by skipping empty blocks of the image. https://www.yoctopr

We use the default IMAGE_BOOT_FILES configuration which matches up with legacy boot configuration. Document the same to allow folks to understand by just looking at the SoC include file. Signed-off-by

Hi, V2 of the series. lets help cleanup the wic files generated for K3 platforms. This includes setting up a reusable boot image pattern that we can use, also generates the bmap file that bmaptool can

Switch to using all of multi-certificate boot images. This allows us to create bootable images - in this case, we are missing tiboot3.bin Signed-off-by: Nishanth Menon <nm@...> --- Changes since V1

Updated in the upcoming V2 of this series.

yup. the merge of sk and evm is still TBD - I have heard of it internally, though was'nt clear as to how it will be done since the DDR is so different.. hopefully in some follow on series, I suppose..

Done in the upcoming V2.

Aaah.. thanks. Reviewed-by: Nishanth Menon <nm@...>

Switch to using all of multi-certificate boot images. This allows us to create bootable images - in this case, we are missing tiboot3.bin Signed-off-by: Nishanth Menon <nm@...> --- conf/machine/inc

Lets keep things consistent by providing two possibilities for platforms to pick from - legacy boot and multi-certificate boot. In legacy boot, the base bootloader and system firmware are maintained a

We use the default IMAGE_BOOT_FILES configuration which matches up with legacy boot configuration. Document the same to allow folks to understand by just looking at the SoC include file. Signed-off-by

Hi, lets help cleanup the wic files generated for K3 platforms. This includes setting up a reusable boot image pattern that we can use, also generates the bmap file that bmaptool can use and while at

IMAGE type and dependencies can easily be centralized to SoC include file. This is necessary to make sure that we don't do the duplication and having multiple places to fix up. Signed-off-by: Nishanth

Lets generate bmap files for bmaptool to use as well as default to use with wic files. https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#flashing-images-using-bmaptool Signed-off-

We use the default IMAGE_BOOT_FILES configuration which matches up with legacy boot configuration. Document the same to allow folks to understand by just looking at the SoC include file. Signed-off-by

Switch to using all of multi-certificate boot images. This allows us to create bootable images - in this case, we are missing tiboot3.bin Signed-off-by: Nishanth Menon <nm@...> --- conf/machine/j72