Last week, one of our customer faced to 3 Colibri SOM broken in same week-end.
After, first analysis, we identified an error when bootloader try to extract OS image.
Following message is display by the console.
. . Error extracting data B9ffOOOO - 39171 - 80760000.
ERROR: Failed to load OS image from SD,'FNC.
INFO: OEMRe ortError Reason Oxfffffffa
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
The error message you’re encountering suggests that the bootloader on your Colibri iMX6S V1.1Y modules is having trouble extracting the OS image from the SD card. Here are some potential causes and steps you can take to resolve the issue:
Corrupted OS Image: Verify that the OS image on the SD card is not corrupted. You can do this by checking the checksum of the image file and comparing it with the original.
Faulty SD Card: The SD card might be faulty. Try using a different SD card to see if the problem persists.
Incompatible OS Image: Ensure that the OS image is compatible with your Colibri iMX6S V1.1Y module. Different hardware revisions may require specific images.
Bootloader Configuration: Check the bootloader configuration to ensure it is correctly set up to load the OS image from the SD card. Incorrect settings can prevent the bootloader from accessing the image.
Software Updates: Make sure both the bootloader and the OS image are up to date. Updates can sometimes resolve compatibility issues or bugs that might cause such errors.
By systematically checking these areas, you should be able to identify the root cause of the problem. If the issue persists, further investigation into the specific error codes and logs during the boot process might be necessary.
I hope this helps you resolve the issue.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
Can you provide the complete Serial Log including the Bootloader version?
Is the log exactly the same on all 3 modules?
It looks like the output is somehow corrupted… maybe not captured properly from serial port? Or is it really like that?
From the little i can see it looks like a Error while reading from the internal eMMC, but it would be very very strange if it’s the same address on all 3 modules.