OTA update by our own built imx-boot

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Based on the context provided, it seems that you are experiencing an issue with the OTA update process for the bootloader using Torizon Cloud’s “INITIATE SETUP” feature. The logs indicate that the bootloader update failed, even though the U-Boot was successfully updated and the OS booted normally.

Here are a few suggestions to troubleshoot and resolve the issue:

1. Check the bl_actions.sh Script: The log message indicates that the failure is related to the bl_actions.sh script. Verify that this script is correctly handling the bootloader update process. Ensure that all necessary steps and error handling are implemented in the script.

2. SSL Certificate Issues: The logs show multiple curl error 58 messages, indicating a problem with the local SSL certificate. Ensure that the SSL certificates used by the device are correctly configured and valid. This might be affecting the communication with the Torizon Cloud.

3. Metadata and SQL Storage: The log mentions “No valid metadata found in storage.” Ensure that the metadata required for the update process is correctly stored and accessible. Check the SQL storage paths mentioned in the logs to ensure they are correctly set up and contain the necessary data.

4. Update Package Verification: Double-check the integrity and authenticity of the update package. Ensure that the package is correctly signed and that the device can verify it.

5. Consult Torizon Documentation: Review the Torizon Remote Updates documentation for any specific requirements or steps related to bootloader updates. There might be additional configuration or setup steps needed for custom-built images.

If these steps do not resolve the issue, consider reaching out to Toradex support for further assistance, providing them with the detailed logs and any additional information about your setup.

Please, also check if these links can help you solve your problem:

"Current versions in storage and reported by OSTree do not match"

Hi there, I’m having difficulty progressing with a problem in upgrading the base os of our fleet. As it stands, there are approximately 50 units which continuously and stubbornly return “not_affected_running_assignment” after a PostUpdate request. To start with, here are the details for just one of the devices. Using app.torizon.io, the upgrade is logged as successful on 23/05/2024: [image] However, the update status is listed as “in progress”: [image] Upon clicking on “More info”, the u…

Updating U-Boot on iMX8 without Toradex Easy Installer

The TorizonCore Yocto build generates a U-Boot image (/workdir/torizon/build-torizon-rt/deploy/images/apalis-imx8/u-boot-sd-2020.04-r0.bin). I would like to update U-Boot on the eMMC using this build artifact. Furthermore, I would like to do so via either U-Boot commands (e.g., mmc write) or Linux commands (e.g., dd), rather than Toradex Easy Installer. My use case is OTA updates of the bootloader and I’m not aware of a straightforward path to do this with Easy Installer. I got the impression f…

Bootloader Updates in Torizon OS | Toradex Developer Center.