Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Example: embedded Linux system equipped with an e.MMC
Regardless of the file system used, e.MMC devices provide some functionalities conceived to monitor their health status while operating. As these functionalities are defined by [https://www.jedec.org/sites/default/files/docs/JESD84-B51.pdf JEDEC standards], all the vendors implement them.
In practice, e.MMC's integrates some registers — namely, <code>DEVICE_LIFE_TIME_EST_TYP_B</code>, <code>DEVICE_LIFE_TIME_EST_TYP_B</code>, and <code>PRE_EOL_INFO</code> — providing information about the health status of the device. These registers can be accessed with the <code>mmc-utils</code>, which are documented [https://www.kernel.org/doc/html/latest/driver-api/mmc/mmc-tools.html here]. Following is a dump of such registers of an e.MMC mounted on a [[MITO_8M_SOM|Mito8M SoM]].
TBD
Interestingly, JEDEC standard also defines a set of registers (<code>VENDOR_PROPRIETARY_HEALTH_REPORT</code>) that vendors are free to use for providing further, fine-grained information about the device's health status. Engineers and system integrators are supposed to contact the e.MMC manufacturer to have more details.
= References =
