I cannot find specific information about AM62 boot source fallback behavior in the available Toradex documentation. The sources I have access to primarily cover iMX6 modules and their eMMC boot configurations(1), but don’t provide detailed boot source priority information for the AM62 platform.
However, I can provide some general guidance based on the available information:
Boot Source Behavior
The available documentation shows that for other Toradex modules, boot source selection typically involves hardware configuration and fuse settings(1). For the AM62, the ROM code behavior regarding boot source fallback when eMMC boot partitions are corrupted is not explicitly documented in my sources.
What We Know from Similar Cases
From the community discussions, there have been cases where modules get stuck at the ROM DFU stage when boot partitions are corrupted(2)(3)(4), suggesting limited fallback options once the primary boot path fails.
Recommendation
Since this is a critical technical question about AM62 ROM behavior and boot source priority that could determine whether your module is recoverable, I’d recommend checking these potentially helpful sources:
- Custom Carrier Board Verdin AM62 - No UART3/UART4 Output During Boot from SD
- USB device not accepting new address (error=80000000) in uboot
- AM62 SPI on cortex M4 stuck in boot
Would you like me to try to provide a general answer based on my knowledge of embedded systems boot behavior instead?
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.