Colibri IMX6DL 512MB v1.1b
OS Version: CE 7.0
BSP Version: 1.3b4
Serial: 00151101-14964289
Custom Carrier Board
We manufacture a biometric device based on the colibri imx6dl module. This device uses WinCE7 and runs an app developed in C#.
they have been working well since 2019, without any major setbacks, however, for the past month we have had reports of 15 devices that do not start.
In our app, a software restart is implemented every day at 0 hours. After this restart, the 15 mentioned devices do not boot.
The image shows how the boot screen remains, if nothing is done the device remains like that.
Something to mention is that, on our custom carrier board we had a button connected to the SODDIM 26, for an external reset.
When the equipment is in the fault state, if we press the reset button mentioned above, the device does not recover, that is, the screen goes black for a moment but it still does not boot.
I attach a video
The error only goes away when you disconnect and reconnect the power.
What could be the error? Could it be the state of the eMCC memory?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
I’m sorry to hear about the boot issues you’re experiencing with your Colibri iMX6DL modules. Based on your description, the problem might be related to a known issue with certain batches of Macronix eMMC memory, which can enter a “Forced Read Only Mode.” This condition can prevent the system from booting properly after a software restart.
To address this, you can use the MMCTool provided by Toradex to check if your modules are affected and, if necessary, perform a repair. Here’s how you can proceed:
Check for the Issue:
Use the MMCTool to verify if your module is affected by the “Forced Read Only Mode” issue. This tool will automatically check the eMMC and determine if a fix is needed.
Repair the eMMC:
If the tool indicates that a repair is necessary, it will guide you through the process. The repair involves running a sequence of commands to restore the eMMC to its normal state.
The tool will display progress on the device screen and log the process, ensuring you can track the repair.
Post-Repair:
Once the repair is complete, the eMMC should function correctly, and your modules should boot normally after a software restart.
If your modules are not affected by this specific issue, or if the problem persists after following these steps, further investigation into other potential causes, such as software configurations, may be necessary. However, addressing the eMMC issue is a critical first step given the symptoms you’ve described.
I hope this helps resolve the issue. Please proceed with caution and ensure you have the necessary setup to run the MMCTool.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
Unfortunately, it is not possible to debug this issue without logs from the Serial Debug UART. Does your system have the relevant port accessible? If so, please connect it to a development machine and collect the logs using any preferred terminal program, such as PuTTY, Tera Term, HyperTerminal, Minicom, etc. Additionally, please enable extended debug output as described here:
