The DM firmware is required in the SDK for toplevel makefile build of u-boot for am62xx. The flow is to add it to deploy and then to prebuilt-images folder of SDK. Sent a new patch for the same as per

The DM firmware is required in the SDK for toplevel makefile build of u-boot for am62xx. The flow is to add it to deploy and then to prebuilt-images folder of SDK. Sent a new patch for the same as per

The DM firmware binary is required for building uboot binaries for am62xx-evm using toplevel makefile in SDK. Add this file to deploy directory so it can be included in prebuilt-images directory of SD

Add DM firmware ipc_echo_testb_mcu1_0_release_strip.xer5f to deploy directory for am62xx-evm. This is required for building tispl.bin. Signed-off-by: Aparna M <a-m1@...> --- recipes-bsp/ti-sci-fw/t

On 19:17-20220301, Denys Dmytriyenko wrote: Hi Denys, Yes, the wic image was tested on the HS platform and the boot works. This should give you an idea about the boot flow : https://software-dl.ti.com

The wic image generated for HS platforms do not contain all required boot files. This happens because the IMAGE_BOOT_FILES variable that contains boot binaries to be included in the wic image is not s

Hi, I looked into wic images generated for am64xx HS, am65xx HS, j7 HS and j7200 HS - the issue seems to be similar. The boot partition contains u-boot.img_HS file but other boot binaries are missing.

The wic file generation scripts that pick up files for the boot partition from the IMAGE_BOOT_FILES variable is unable to find u-boot.img. As a result, the generated wic image does not package the ubo

All the HS platforms generate the u-boot binary as u-boot.img_HS but the bootloader expects the binary to be named as u-boot.img Due to this mismatch, script cannot find the required image to be added

The sysfw.itb to be packaged by the installer is copied to the prebuilt-images directory from the deploy directory. This change installs the sysfw.itb in the deploy directory. Signed-off-by: Aparna M