Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello Richard,
Thank you for reaching out with your question. It sounds like you’ve made significant progress in building and deploying a secure boot image for your Verdin AM62 module. However, I understand you’re encountering some runtime errors and issues with password persistence.
The use of the “torizon-signed” bbclass indeed results in a volatile /etc directory, which means changes like password updates won’t persist after a reboot. To address this, you can utilize the systemd-tmpfiles service to create persistent configurations. This service allows you to define files and directories that should be created or modified at boot time, ensuring your configurations are retained across reboots.
Regarding the runtime errors, here are a few steps you can take to troubleshoot:
-
Examine Boot Logs: Carefully review the boot logs for any specific error messages that might indicate the source of the problem. This can provide clues about what might be going wrong.
-
Verify Secure Boot Configuration: Double-check all configurations related to secure boot, including key management and signing processes, to ensure they are correctly set up.
-
Test Without Secure Boot: If feasible, try booting the module without secure boot enabled to determine if the errors are related to the secure boot setup.
By following these steps, you should be able to identify and resolve the issues you’re experiencing. If you have further questions or need additional assistance, feel free to reach out.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem: