im using apalis imx8qm and flashed the my image (torizon 6.7) using tezi, this is what im getting
do i need to enable the CONFIG_LEGACY_IMAGE_FORMAT ??? im using signed FIT format and im not closing the device so secure boot is not the problem
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
I’d be glad to help troubleshoot this U-Boot issue with your Apalis iMX8QM! To provide you with the most accurate guidance, could you let me know which exact version of Torizon OS you are running? You can use the tdx-info command to get detailed information about your system configuration - more details at this link.
Initial Analysis
Based on your description, you’re using a signed FIT format on Torizon 6.7 with an Apalis iMX8QM. The U-Boot security hardening features in Torizon include command whitelisting and bootm protection that could affect how images are loaded(1).
Common Platforms to Consider
When troubleshooting U-Boot issues, it’s helpful to confirm:
- Hardware: Apalis iMX8QM (which you’ve specified)
- OS Version: Exact Torizon OS version (please confirm)
- Implementation: Whether you’re using Docker containers, specific device tree configurations, or custom kernel parameters
Regarding CONFIG_LEGACY_IMAGE_FORMAT
The security hardening modifications in U-Boot include exclusive signed software execution where the bootm command is restricted to only boot FIT images signed with proper keys when hardening is enabled(1). This protection ensures that alternative notations that don’t mandate signature checks are denied(1).
Once you provide the exact Torizon OS version, I can give you more specific guidance on whether CONFIG_LEGACY_IMAGE_FORMAT is relevant to your setup and how the security hardening features might be affecting your boot process.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
im not using u boot hardening and im not closing the device so its not secure boot problem , im using torizon os 6.7
FIT Image Loading Issue on Apalis iMX8QM
Thank you for the clarification about Torizon OS 6.7 and confirming that secure boot hardening isn’t enabled. Based on the available documentation, I don’t have specific information about CONFIG_LEGACY_IMAGE_FORMAT configuration for your exact scenario.
Potential Considerations
Even without secure boot hardening enabled, U-Boot on Torizon OS includes various protections and configurations that could affect image loading(1). The bootm command behavior can vary depending on the U-Boot configuration and the format of the image being loaded(1).
Bootloader Version Compatibility
Since you’re using Torizon OS 6.7, you might want to verify if your bootloader version is compatible with your custom image. Bootloader updates are sometimes required when specific features or compatibility with certain image formats is needed(2).
Next Steps
Without being able to see the specific error message in your image clearly, and given the complexity of U-Boot configuration on iMX8QM platforms, I’d recommend:
- Checking if there are any specific error messages in the U-Boot console output
- Verifying that your FIT image is properly formatted for the Apalis iMX8QM platform
- Considering whether a bootloader update might be needed for your use case
For more detailed troubleshooting of this specific configuration issue, you may find relevant discussions on the Toradex Community by searching for “Apalis iMX8QM FIT image” or “CONFIG_LEGACY_IMAGE_FORMAT”.
Best regards, Toradex AI Assistant.
Did you like my answer?
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
Greetings @anmsn44,
Did you perhaps customize/change our standard default U-Boot configuration? This issue isn’t present in our default images. Unless something was changed on your setup it wouldn’t make sense as to way you’re seeing this issue occur.
Also I would generally highly recommend you to use a newer version of our OS that is still being supported. Like 6.8.8. at least for example. Torizon 6.7 was released almost 2 years ago at this point.
Best Regards,
Jeremias