topic How to update u-boot by swupdate in i.MX Processors

How to update u-boot by swupdate

wang12zhe — Thu, 06 Jul 2023 08:34:08 GMT

HW: IMX8QXP EVK

I had update rootfs/Kernel image and dtb successfully,

Rootfs/kernel Image and dtb are store in fat32 or ext4 partition,I can add information to sw-description to update them.

But u-boot store a raw data area, how to update u-boot by swupdate?

Any help will very useful for me thanks very much

Re: How to update u-boot by swupdate

Dhruvit — Fri, 07 Jul 2023 07:09:51 GMT

Hi @wang12zhe,

I hope you are doing well.

Please find the information related to SWUpdate OTA over IMX8QXP from the below documents.

SWUpdate OTA i.MX8MM EVK / i.MX8QXP MEK

Thanks & regards,
Dhruvit Vasavada

Re: How to update u-boot by swupdate

wang12zhe — Mon, 10 Jul 2023 08:41:08 GMT

@Dhruvit

Thank you very much.

Refer the sw-description file in

upgrage_image_build_source_file.zip (i.MX8QXP\imx8qxpmek_doublecopy_slotb_full_LF_v5.10.9_1.0.0）

Add below information to my sw-description

images: (

{

filename = "imx-boot-imx8qxpmek-sd.bin-flash_spl";

device = "/dev/mmcblk0boot0";

}

);

after update by swupdate and reset the system output nothing from console(uboot not start).

My start command:

swupdate -l TRACE -i imx8qxpevk.swu -e "stable,mmcblk0p2" or

swupdate -l TRACE -i imx8qxpevk.swu -e "stable,mmcblk0p4"

I had added my sw-description as attachment, please check it where the error is, thank very much.

Re: How to update u-boot by swupdate

wang12zhe — Mon, 10 Jul 2023 08:57:24 GMT

@Dhruvit

If Run "reboot" after update by swupdate, will show below from console

U-Boot SPL 2021.04-lf_v2021.04+g1c0116f3da (Sep 06 2021 - 08:48:23 +0000)
Normal Boot
Trying to boot from MMC1
Primary set selected
Parse seco container failed -14
Load image from MMC/SD 0x0

Any suggestion about this? Thanks very much.

Re: How to update u-boot by swupdate

Dhruvit — Fri, 14 Jul 2023 11:28:48 GMT

Hi @wang12zhe

I hope you are doing well

It seems that the error 'Parse seco container failed -14' occurs because of the Wrong container header.

Please share the steps you followed to further debug the issue.

Thanks & Regards

Dhruvit Vasavada