EZ NAND compared to eMMC

Posted by: Thom Denholm

A recent article by Doug Wong compared performance characteristics of eMMC and ONFI specification EZ-NAND, specifically Toshiba's SmartNAND here: http://www.eetimes.com/design/memory-design/4218886 One consideration I would add to this quite excellent summary is about the availability of drivers. Raw NAND has been around for quite a while and the market supplies a large range of drivers. Many of these will utilize the basic functionality of SmartNAND and other EZ NAND chips with only small modifications. Drivers for eMMC, on the other hand, are much harder to find. Only Linux has a freely available driver, which Google's Android has taken advantage of in recent releases. At Datalight, we continue to be excited by both of these new technologies. From the JEDEC eMMC parts, the cool features such as Secure Delete and Replay Protected Memory Block are very exciting. On the other hand, the sheer performance of Toshiba's SmartNAND and other EZ NAND solutions is very much in demand.

Comments (2)

  1. Jose George:
    Dec 01, 2011 at 04:14 PM

    Interested in pros/cons of each type of NAND

  2. Peter:
    Jan 08, 2012 at 06:35 AM

    Thanks for your excellent introduction and summary. Lookiong to me, "wear leveling, bad block management, ECC, and logical-to-physical address translation" are the key factors. In fact, all of these can be implemented in pure NAND flash controller as well. After all, eMMC solution is most likely like the gasket/brdige converting between SDHC interface and NAND flash interface, not better than pure NAND controller solution. I understand, eMMC standard is very mature and widly used,just want to think from technical point of view. And with ONFI spec development (3.0, up to 400MB/s), can eMMC solution be still suitable ? And I feel it's tend to put above work (ECC,etc) into nand-flash to off-load controller and achive better performance. Please share your point, thanks! Best regards, Peter

Add a Comment

Allowed tags: <b><i><br>Add a new comment: