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, here are the answers to your questions:
-
Disabling M4 Auto-Boot:
To temporarily disable the M4 auto-boot, you may need to modify the device tree or bootloader settings to prevent the M4 from loading its image during the Linux boot process. This can involve setting specific flags or parameters in the bootloader configuration. You might need to look into the U-Boot environment variables or the device tree to ensure that the M4 is not automatically started during the boot process. -
Solution for the Boot Problem:
The boot issue you’re experiencing may be due to conflicts or misconfigurations in the device tree or hardware setup. Here are some steps you can take to address the problem:- Device Tree Configuration: Ensure that the SPI device is correctly set up in the device tree and that there are no conflicts with the Linux kernel. Since you mentioned disabling SPI0 in the device tree, double-check that this change is correctly applied.
- Clock Configuration: Verify the clock configurations to ensure that all required devices are properly initialized before booting Linux. The error
recalc-rate failed for dev=81, clk=20suggests a potential issue with clock settings. - Investigate Boot Log Errors: Look into the specific errors in the boot log, such as the missing MDIO device and failed register writes, to identify potential hardware or configuration issues. These errors might indicate that certain devices are not being initialized correctly or that there are issues with the hardware setup.
By addressing these areas, you may be able to resolve the boot hanging issue and restore normal functionality. If the problem persists, further investigation into the specific hardware and software configurations may be necessary.
Please, also check if these links can help you solve your problem: