You’re absolutely correct - this is clearly a module-specific issue rather than a USB drive problem. The fact that you get “MMC: no card present” and “** Unrecognized filesystem type **” without any USB device connected confirms this is an internal eMMC issue.
Where to Check for Batch-Specific Issues
You can check for known hardware issues and product change notifications in several places:
1. Product Change Notifications (PCNs)
The Colibri iMX6DL 512MB V1.1A revision history shows several PCNs that document known issues(1). Your serial number 12897713 corresponds to a specific production batch that may have documented issues.
2. Revision History Documentation
According to the documentation, the Colibri iMX6DL 512MB has had multiple revisions addressing various issues(1):
- V1.1A addressed eMMC-related changes including “Changed internal eMMC voltage from 3.3V to 1.8V”
- There were also “Resolved start-up issue when VBATT is supplied and the module was shut-down by software”
3. Community Reports
There are documented cases of similar eMMC issues. One community report shows modules experiencing eMMC corruption with error messages like “Failed to load OS image from SD,'FNC” and “MMC corruption is mentioned”(2). Another report documents “mmcblk0: error -110 sending stop command” issues affecting multiple Colibri iMX6S modules(3).
Root Cause Analysis
Your boot log shows:
MMC: no card present
switch to partitions #0, OK
mmc0(part 0) is current device
** Unrecognized filesystem type **
This indicates the module is detecting the eMMC hardware (mmc0) but cannot read the filesystem, suggesting either:
- eMMC corruption in the boot partition
- Hardware failure in the eMMC interface
- Factory firmware corruption
Recommended Actions
- Contact Toradex Support with your serial numbers to check if there are known issues with this production batch
- Check Product Change Notifications for your specific module revision at the developer portal
- Consider RMA if multiple modules from the same batch show identical symptoms
- Use Recovery Mode to attempt reflashing the factory firmware if the eMMC is still functional
The pattern you’re seeing across multiple modules with similar serial numbers strongly suggests a batch-specific issue that should be escalated to Toradex support for investigation.
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.