It sounds good but not sure. What will the endurance numbers be if their chip is used? The article is a nice marketing piece with no information. I was hoping to see some numbers so that the improvement was understood and not just "better". Is this too early in the development cycle for any measurements to have been made or available?
This product is shipping in volume.
Endurance meets the customer/application needs.
In Smartphones, it is typically in the low thousands program/erase (P/E) cycles plus 1yr retention. Anobit has announced an enterprise SSD which meets endurance spec which is equivalent to 50,000 P/E cycles, using standard off-the-shelf MLC NAND, typically spec'd at 3,000 P/E cycles. I hope this helps. Dror Salee, Anobit
Wear leveling and FEC are nothing new in SD cards, thumb drives and SSDs. Otherwise, the FAT table (written every time you write to a file) wouldn't last long. A flash manager needs to remember sectors that go bad, provide wear leveling, and do forward error correction among other things. A press release wouldn't necessarily say "Ours is better than Theirs because...".
You are correct about wear leveling and error correction codes. This product has something else, which we call Memory Signal Processing. It is about applying signal processing methods to the analog voltage levels inside the memory array.
Poor endurance is just one aspect of newer NAND devices that is problemmatic. The other is increasing latency because of the much slower multi-level cells and the the increasing time neeeded for error correction before any of the retrieved data can be used. Cell latency used to be of the order of 20-30uS and 1-bit error correction added almost nothing to that. Now cell latency is 80uS or more and typical NAND controllers add far more.
Our application, which demands low random access latency, used to be practical with NAND but with present trends, may become impractical before we can deliver a product. Does the MSP controller help the latency issue?
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...