Hi Toradex, support and community,
We are developping a system based on Colibri T30 modules. Our software environnent is based on:
Toradex Linux kernel from BSP
- U-Boot 2011.06 of “Toradex Colibri T30 Linux BSP V2.3 Beta 1” built from sources
- Rootfs generated with Buildroot (https://buildroot.org/)
We still use nvflash to flash our boards since we need a standalone USB tool to program the SoM at manufacturing. New scheme with U-Boot only is not possible right now.
In our continuous integration system, we noticed that flashing the Colibri started to sometimes fail in the middle of a flashing operation with nvflash (stucked in the middle of the process) with no alternative to restart a flashing (including config block which gets lost in these situations).
The error condition occurred more and more often up to the point where we could hardly ever succeed to program the whole module.
We suspect an eMMC wear-out which could explain why we saw the fail ratio increase over the time.
I couldn’t find any information on the number of erase/write cycles of the Hynix eMMC mounted on Colibri T30.
Toradex Knowledge Base on Flash gives some numbers for raw flash (SLC and MLC) but nothing for the eMMC. Do you have some specification on the possible number of writes on your eMMC ?
Do you know if the eMMC will internally perform wear-levelling on the whole flash area or if the same blocks get written if we always flash at the same linearr address with nvflash ? In other words, does the flashing at always the same address/offset always hit the same blocks/pages or do these low-level writes benefit from wear-leveling done at the eMMC layer.
Thanks for any help helping us to track down our issues.