eMMC health status

Dear Toradex,
Is there a way to find out about the wear / health status of the eMMC? e.g. S.M.A.R.T. data or similar?
I have tried installing mmc-utils but the parameter DEVICE_LIFE_TIME_EST_TYP is not supported by the hardware.
Kind regards

Is there a way to find out about the wear / health status of the eMMC? e.g. S.M.A.R.T. data or similar? I have tried installing mmc-utils but the parameter DEVICE_LIFE_TIME_EST_TYP is not supported by the hardware.

I’m not sure why you claim that this is not supported. Any of our BSPs of late should allow you to easily get such information e.g. as follows:

root@colibri-t30:~# mmc extcsd read /dev/mmcblk0
=============================================
  Extended CSD rev 1.7 (MMC 5.0)
=============================================

...
Device life time estimation type B [DEVICE_LIFE_TIME_EST_TYP_B: 0x01]
 i.e. 0% - 10% device life time used
Device life time estimation type A [DEVICE_LIFE_TIME_EST_TYP_A: 0x04]
 i.e. 30% - 40% device life time used
Pre EOL information [PRE_EOL_INFO: 0x01]
 i.e. Normal
...

Dear Mr. Ziswiler,

We have our own image based on core-image AND a mainline kernel (4.19). I do have other versions of the software (see below).
What is the easiest way to find the BSP version? I thought I installed v2.8.
Would an update of the BSP work with “repo sync” or not?

kind regards.

:~# mmc extcsd read /dev/mmcblk0
=============================================
  Extended CSD rev 1.6 (MMC 4.5)
=============================================

And you are absolutely sure we are talking about a Colibri T30 1GB V1.1F module? This looks more like one of them previous module versions with Hynix resp. SKHynix eMMC parts.

Dear Mr. Ziswiler,
You were right, I was testing with an E module. Testing with an F module now, I have the same version numbers as you do, BUT still no parameter with the char string LIFE or life…
please find attached the output of

mmc extcsd read /dev/mmcblk0 > log

the Kernel this time is 3.1.10-2.7.3+ga24d47d56d9f
LINK TO TXT FILE OF OUTPUT

that was the solution. thank you.

Most possibly you are using mmc-utils from openembedded-core rather than mmc-utils-cos from meta-toradex-demos.

You are very welcome.

Is there a documentation about the specific mmc used in F revision what the vendor specific fields describe?
We are asking ourselves if
VENDOR_PROPRIETARY_HEALTH_REPORT
may contain interesting information?

Is there a documentation about the specific mmc used in F revision

Yes, it’s the Micron MTFC4GACAJCN-1M WT as you can see from the Colibri T30 revision history.

what the vendor specific fields describe? We are asking ourselves if VENDOR_PROPRIETARY_HEALTH_REPORT may contain interesting information?

Unfortunately, we are not aware of any such document. However, there is a Micron specific emmcparm tool available which may or may not show any more information.