Yocto/OSTree OTA Update Testing Issues (QualComm Linux, QEMU Boot Loop, Image Corruption)

[CipherWielder1104]

I'm working on implementing OTA (Over-The-Air) updates for a Qualcomm Linux device using Yocto Project and OSTree. I'm encountering several issues during the build and testing phases, particularly when trying to validate the update process using admin deploy command.

My goal is to reliably build an OSTree-enabled image, serve updates from an OSTree repository, and then perform an ostree admin deploy update.

My questions are:
1)How do I test ostree admin deploy command?

• I tried creating a mount for my system.img and then doing admin deploy but it is giving errors.
• I am not able to run virtual environment(qemu) inside my yocto build.
  2)My work directory also has less space, so is that causing my image to become corrupted and eventually causing all the errors.How do I verify that the build is correctly generating everything?

Using mount of system.img, I tested the pull command which is working and pulling the latest commit from the server repo but when i run admin deploy its not working.

Please Guide.

[ricardosalveti]

I'm working on implementing OTA (Over-The-Air) updates for a Qualcomm Linux device using Yocto Project and OSTree. I'm encountering several issues during the build and testing phases, particularly when trying to validate the update process using admin deploy command.

What is the device you are using here? We do support ostree and sota via meta-updater in both qualcomm linux 1.x (manually deploying and updating the device) and via foundries factory (managed system with device registration and aktualizr-lite support). I work for qualcomm / foundries btw.

Some pointers:

• https://docs.qualcomm.com/bundle/publicresource/topics/80-70018-27/qualcomm_linux_software_components.html#ota-update-for-qualcomm-linux
• https://github.com/foundriesio/meta-partner/tree/qualcomm