Guest blog: What Tesla taught us about eMMC

Paul Norbury

Paul Norbury, CEO of Cardwave, asks how we can all learn from Tesla’s experience of the small but mighty eMMC

EMMC memory might be small, but it is mighty. Get the specification right and a product will hum along, with end-users taking advantage of what the eMMC does for them, but not aware of its central role, and certainly unconcerned about the specification of the memory itself.

Get the specification wrong and none of the above applies, and the end result could be expensive and reputationally damaging.

 

Tesla recall

Memory is very complex and anyone specifying it for a product has to take an awful lot into consideration. Many of the factors are pretty technical such as workload, predicted lifetime and how often data need to be written to or read from the NAND, and the consequences of making a less than optimal choice might not be apparent till it’s too late.

Let’s consider the recent recall of more than 130,000 Model S and Model X cars by Tesla. This happened because the driver’s screen-based information centre, the media control unit (MCU), stopped working. In a letter to Tesla, the US National Highway Traffic Safety Administration noted that the loss of the MCU meant drivers did not have access to safety features including the rearview camera and defogging and defrosting controls, and there were also adverse impacts on other safety features such as the autopilot advanced driver assistance system.

In information relating to the recall Tesla said the culprit was wear and tear on the 8Gbyte eMMC memory. In essence, it seems the eMMC was written to every time a car was started, and over time its storage capacity was reached. With no way to erase data, eMMC’s NAND cell hardware failed, causing the MCU to fail in turn. The recall allows 64Gbyte eMMC units to be used to replace those 8Gbyte units, which hopefully will provide the required future-proofing.

 

Learning points

It is pointless bashing Tesla for this issue. But it is worth using its experience as an example to learn from, and there are four key points in particular that are worth stressing for any organisation working with flash memory. They are relevant across the whole of the vehicle electronics sector.

Sweat the small stuff. We can’t know how or why the eMMC used was specified in Tesla’s case. Sometimes parts are specified with a particular workload in mind and tolerance is absolutely fine, then more workload is placed on them as a device develops and tolerance can struggle. The part can be upgraded – but only if it appears in the right schedule, in front of the right eyes, at the right times. A tiny eMMC card might be easily overlooked.

Don’t let that happen. Memory cannot be an afterthought in the design process. It may be small and hidden away, but it is a core component and needs to be treated as such.

Don’t cut corners. Sometimes lower cost or lower quality parts are specified to cut production costs, and every single fraction of a penny in the bill of materials really does count. But the flash memory components in a device are there for vital reasons. Nobody would suggest deliberately over-specifying the memory – remember that bill of materials has to be kept under control – but there is a fine line between over-specifying for the sake of it and building in capacity for future upgrades. Erring on the generous side rather than scrimping and just getting by can be a very good strategy.

Be aware of different grades of memory. Cars are complex products, increasingly reliant on electronics components for core functionality, and they’re not cheap to build or to buy. While private owners might think of their car as a consumer good, it is a highly specialised, precisely engineered device, and building it requires a level of attention to detail in component selection that approaches or equals that required for industrial processes or manufacturing rather than the production of consumer goods.

That is true as much for the smallest, most hidden of components such as flash memory as it is for the parts users see and interact with. Flash memory comes in many grades of quality for different use cases. Car manufacturers really need to use automotive and industrial grade flash as these products have health monitoring features that will enable the manufacturer to predict failure and plan maintenance.

Work with trusted third parties. Not every maker of complex devices has detailed knowledge about every single component. There will be specialists in many fields that can advise on getting the specification right as well as help with sourcing from the most appropriate suppliers.

In the end, no company wants the cost, hassle or reputational problems that are caused by having to recall a product. Flash memory such as eMMC is a component that is small in both size and cost relative to the overall product, but it is vital to functionality. Ignore it at your peril, for it is truly small but mighty.

www.cardwave.com

 

Recommend to Colleagues: