Hi, I'm interested in Flash energy consumption to complete a fair comparison between different technologies (particularly in NOR and NAND Flash, SRAM). This parameter is normally disregarded in books and so on. Please could you give any clue on orders of magnitude of the static consumption (specified as current/power leakage) and dynamic consumption during random read operation. Best regards, Leonardo
NAND array architecture is fundamentally more efficient (bits/area) than NOR at a given process node. This array efficiency advantage outweighs NOR's smaller peripheral area as densities increase. From a silicon cost perspective NAND will always be less expensive at the highest densities, NOR will always be less expensive at the lowest densities. So from a cost perspective both NOR and NAND will continue to be viable for the foreseeable future.
From a performance perspective both technologies have characteristics that are essential in different applications. (NOR - low latency reads, NAND - fast program/erase rates)
I think the major flaw in that argument is that NAND and NOR are typically used for very different purposes and there are very few typical user scenarios for both beyond holding boot code/data.
Trying to compare them is like trying to compare a Ford F250 with a Porche.
NAND is prefered for general r/w file system usage - for which NOR is pretty terrible.
NOR is prefered for boot code and data, but many systems are dropping the NOR and using NAND to reduce costs. That slows boot, but is a compromise.
I tried to use a typical usage case scenarios. As tb1 mentions x16 NAND is getting hard to find and commands a significant price premium. Note that even if the NAND transfer time were eliminated altogether the NOR:NAND comparision would be 50:1.
One significant NOR usage change is the continuing proliferation of high density SPI. As a NVM product catagory, NOR revenue is more than adequate to fund next generation process development and new product catagories.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.