Embedded Flash MemorySponsored by: RENESAS TECHNOLOGY CORP.

March 15, 2004
Flash Memory And MCUs: A Match Made in Heaven

Embedded flash-memory-based MCUs are dominating new system designs. This is true even in high-volume production because of flash memory’s flexibility and reprogrammability. Improved performance, life, and reliability have been pivotal to flash MCU’s success. ROM-based solutions will continue to be useful for products shipped in very large quantities. But embedded flash is replacing ROM and one-time-programming (OTP) solutions by meeting the long-term stability and cost goals set by these well established technologies.

A wide range of processor architectures, from 8-bit MCUs to 64-bit processors, use embedded flash memory. This diversity of architectures and system requirements prevents one flash architecture from meeting the needs of all systems. It also differentiates the requirements for embedded flash memory and bulk flash storage found in products that range from digital cameras to solid-state hard-disk drives. Fast access, high reliability, and a wide temperature operating range distinguish embedded flash from bulk flash solutions.

Different Flash-Memory Technologies All flash-memory architectures use a form of floating gate. The approach employs Fowler-Nordheim tunneling to move electrons to or from the floating gate (see "How Flash Memory Works"). Some options for embedded flash memory include the use of a single or double transistor architecture and the use of an n- or p-type substrate. MCU developers rarely get down to this level to determine what type of product to choose. Instead, vendor per-formance, cycle, and lifetime specifications provide a developer with the kind of information needed to differentiate one approach versus another. One big factor that arises when considering a particular flash-based MCU is programming methods (see "Choosing a Flash Memory MCU"). Most flash-memory MCUs have multiple programming methods (see "Programming Embedded Flash 101"). Consider this issue only after an application is developed because it can affect production efficiency. For example, an application that uses a large amount of flash memory will need high programming speeds. Otherwise, the assembly line will have to be slowed down to accommodate the MCU’s limitations.

Click here to download the PDF version of this entire article.

About the Author

William G. Wong | Senior Content Director - Electronic Design and Microwaves & RF

I am Editor of Electronic Design focusing on embedded, software, and systems. As Senior Content Director, I also manage Microwaves & RF and I work with a great team of editors to provide engineers, programmers, developers and technical managers with interesting and useful articles and videos on a regular basis. Check out our free newsletters to see the latest content.

You can send press releases for new products for possible coverage on the website. I am also interested in receiving contributed articles for publishing on our website. Use our template and send to me along with a signed release form. 

Check out my blog, AltEmbedded on Electronic Design, as well as his latest articles on this site that are listed below. 

You can visit my social media via these links:

I earned a Bachelor of Electrical Engineering at the Georgia Institute of Technology and a Masters in Computer Science from Rutgers University. I still do a bit of programming using everything from C and C++ to Rust and Ada/SPARK. I do a bit of PHP programming for Drupal websites. I have posted a few Drupal modules.  

I still get a hand on software and electronic hardware. Some of this can be found on our Kit Close-Up video series. You can also see me on many of our TechXchange Talk videos. I am interested in a range of projects from robotics to artificial intelligence. 

Sponsored Recommendations

Comments

To join the conversation, and become an exclusive member of Electronic Design, create an account today!