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, it seems that the Verdin iMX8MP boards are experiencing WiFi driver timeouts and unresponsiveness, which could be related to background scanning operations and firmware loading issues. Here are some suggestions to address the problem:
-
Firmware Compatibility: Ensure that the firmware used with the proprietary driver is compatible with your current kernel version and hardware configuration. The logs indicate failures in downloading firmware, which might be a critical factor in the WiFi module’s failure to respond.
-
Driver Updates: Check for any updates or patches for the WiFi driver that might address the timeout issues, especially those related to background scanning. This could involve checking both the kernel-included driver and the proprietary driver for any recent updates.
-
Alternative Drivers: If the proprietary driver continues to exhibit issues, consider testing with alternative drivers or configurations to see if the problem persists. This might involve using a different version of the driver or a different driver altogether if available.
-
Monitor Logs: Continue to monitor
dmesg
logs for any additional error messages that might provide further insight into the underlying cause of the driver timeouts. This can help in identifying any patterns or specific triggers for the issue. -
Testing on Reference Hardware: Although you mentioned that you are not in a position to try this with a reference image on a reference carrier board, it is still a recommended step to isolate whether the issue is specific to your custom carrier board or a broader compatibility issue.
-
Background Scanning: Since the issue might be related to background scanning, consider disabling or modifying the scanning behavior to see if it affects the frequency of the timeouts.
These steps should help in diagnosing and potentially resolving the WiFi driver issues on your Verdin iMX8MP boards. If the problem persists, further investigation into the specific interactions between the driver, firmware, and hardware might be necessary.
Please, also check if these links can help you solve your problem: