Yocto build TorizonOS doesn't recognize lockbox

[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 the issue with the Lockbox not being recognized as an update by Aktualizr is likely related to the custom TorizonOS image you created using Yocto. Since the offline update mechanism works correctly with pre-built images, the problem might be in the custom build process or the specific configurations applied during the build.

Here are a few suggestions to investigate and potentially resolve the issue:

1. Verify Metadata Consistency: Ensure that the metadata file generated for the offline update is consistent with what Aktualizr expects. Any discrepancies in the metadata, such as incorrect signatures or missing fields, could cause the update to be unrecognized.

2. Compare with Pre-built Images: Since the offline update works with pre-built images, compare the metadata and configuration files of the custom image with those of a pre-built image. Look for any differences that might affect the recognition of the Lockbox.

3. Check Yocto Build Configuration: Review the Yocto build configuration, especially the local.conf and any other configuration files that might affect the build process. Ensure that the addition of chrony does not inadvertently alter other aspects of the build that could impact the update mechanism.

4. Rebuild and Test: Try rebuilding the custom image with minimal changes to isolate the issue. Start with a basic custom image and gradually add modifications, testing the offline update mechanism at each step to identify when the issue arises.

5. Consult Documentation and Support: If the issue persists, consult the Toradex documentation for any additional guidance on building custom TorizonOS images and using offline updates. You may also consider reaching out to Toradex support for further assistance.

If these steps do not resolve the issue, it may require a deeper investigation into the specific build process and configurations used in your custom image.

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

Offline updates not searching for lockbox

Hello, we want to use a custom TorizonOS with offline updates managed by the Torizon Cloud. To test the offline update functionality I built a vanilla torizon-minimal (BSP6.6.0) with Yocto and flash it with TEZI. The device isn’t connected to the internet. After bootup I deactivated the aktualizr-daemon with sudo systemctl stop aktualizr sudo systemctl disable aktualizr to trigger and observe the update process manually. After that I provisioned and configured my device for offline updates…

TorizonCore Builder 6.1.0 support

Hi I’m new to TorizonCore Builder, but I have some fundamental problems. I try to follow the the guide to customize and image: TorizonCore Builder Tool - Customizing TorizonCore Images | Toradex Developer Center I selected the Latest Monthly Release for iMX8MP with PREEMT_RT as an input image. I could add a kernel module, but I’m quite sure it uses gcc-9.3 to compile it and it should be gcc version 11.3 which is used by BSP 6. The image works to deploy on the platform nonetheless. But when…

[aktualizr, offline updates] Found in archive a file with bad file type: 40960.