We have integrated dragonboard 410c into our product and have deployed them. Several of them became defective after 1-2 years and they were unable to boot with its internal eMMC.
Environment of Defective dragonboards:
- Android OS
- Boot using eMMC
We have analyzed a few of the defective dragonboard 410c using Debian Linux bootable microSD card. So far, we found that all of them have one of these eMMC issues:
- The eMMC couldn’t even be detected. In dmesg, I found
mmc0: tuning execution failed: -5
andmmc0: error -5 whilst initialising MMC card
. - Reading the eMMC would generate errors on dmesg.
cat /sys/class/mmc_host/mmc0/mmc0\:0001/life_time
returned0x0b 0x0b
- The eMMC can be read. But it couldn’t be written. Its content is corrupted.
cat /sys/class/mmc_host/mmc1/mmc1\:0001/life_time
returned0x09 0x0b
I’m surprised that I couldn’t find any related issue in this forum. I wonder if we’re actually alone.
Here’s our questions:
- We wonder if it’s a known issue of dragonboard 410c
- Please advise if replacing the eMMC would fix the issue
Thank you!