eMMC Failure/Corruption Issue – SDINBDG4-8G-I1 – Request for Debug Guidance

Announcements, News, and Feedback Forum Feedback
1

Hello,

We are using the SDINBDG4-8G-I1 eMMC part in our devices. Recently we have experienced repeated failures/corruptions with the eMMC in multiple units. We would like to know whether there is any recommended procedure or diagnostic tool to help debug and identify the root cause of these failures.

In the meantime, we will share additional logs or updates as they become available.

Thank you for your help.

2

Additional Information:
Below is a comparison between a working device and a failing device.

Working Device:

sh-5.0# ls /dev/mmc*
/dev/mmcblk1       /dev/mmcblk1boot1  /dev/mmcblk1p2
/dev/mmcblk1boot0  /dev/mmcblk1p1     /dev/mmcblk1rpmb

sh-5.0# cat /sys/block/mmcblk1/size
15273600

sh-5.0# cat /sys/block/mmcblk1/queue/hw_sector_size
512

sh-5.0# mmc extcsd read /dev/mmcblk1
=============================================
  Extended CSD rev 1.8 (MMC 5.1)
=============================================
Card Supported Command sets [S_CMD_SET: 0x01]
HPI Features [HPI_FEATURE: 0x01]
Background operations support [BKOPS_SUPPORT: 0x01]
...

dmesg logs (working):

dmesg | grep mmc
[    4.108069] mmc0: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA
[    4.133089] mmc0: queuing unknown CIS tuple 0x80 (2 bytes)
[    4.139430] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
[    4.145525] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
[    4.150150] mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
[    4.159460] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
[    4.171690] mmc0: queuing unknown CIS tuple 0x80 (6 bytes)
[    4.259423] mmc0: new high speed SDIO card at address 0001
[    4.273654] mmc1: new DDR MMC card at address 0001
[    4.278602] mmcblk1: mmc1:0001 DG4008 7.28 GiB
[    4.282434] mmcblk1boot0: mmc1:0001 DG4008 partition 1 4.00 MiB
[    4.287857] mmcblk1boot1: mmc1:0001 DG4008 partition 2 4.00 MiB
[    4.293013] mmcblk1rpmb: mmc1:0001 DG4008 partition 3 4.00 MiB, chardev (245:0)
[    4.302141] mmcblk1: p1 p2

Failure Device:

sh-5.0# ls /dev/mmc*
/dev/mmcblk1

sh-5.0# cat /sys/block/mmcblk1/size
62688

sh-5.0# cat /sys/block/mmcblk1/queue/hw_sector_size
512

sh-5.0# mmc extcsd read /dev/mmcblk1
cmd error -110
ioctl: Connection timed out
Could not read EXT_CSD from /dev/mmcblk1

dmesg logs (failure):

sh-5.0# dmesg | grep mmc
[    4.108203] mmc0: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA
[    4.133312] mmc0: queuing unknown CIS tuple 0x80 (2 bytes)
[    4.139666] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
[    4.145758] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
[    4.150373] mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
[    4.159693] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
[    4.171954] mmc0: queuing unknown CIS tuple 0x80 (6 bytes)
[    4.225848] mmc1: new MMC card at address 0001
[    4.235224] mmcblk1: mmc1:0001 SDM032 30.6 MiB
[    4.267487] mmc0: new high speed SDIO card at address 0001

Observation:
The failing device reports a much smaller capacity (30 MB vs 7.28 GB), and reading the EXT_CSD fails with error -110.

3

We are using the SDINBDG4-8G-XI1 eMMC device in our design. We observed a failure in the eMMC following a voltage surge, after which the device was unable to boot. Upon replacing the eMMC, the system resumed normal operation.

We will share the failed eMMC device for your analysis. Kindly investigate the root cause of the eMMC failure and identify which pins or interfaces may have been affected.

Note: We did not observe any short (low impedance) on the power path of the failed eMMC device.