Archive for the ‘Flash Industry Info’ Category

Gearing Up for the Flash Memory Summit

 

Datalight Sponsoring and Presenting August 12-14 in Santa Clara

Every August, flash memory zealots converge on Santa Clara to trade war stories, find out what’s new, and debate the relative merits of a mind-boggling assortment of flash technologies. Now in its third year, the Flash Memory Summit is set to break attendance and sponsorship records yet again, and Datalight will be there waving the banner of fault-tolerance, flexible design and raw performance. Other sponsors include intel, Spansion, Samsung, Micron, Toshiba, Numonyx, Dell and many others.

We hope you can join us at the world’s only conference dedicated entirely to flash memory technology. This year we’re excited to present four tutorial sessions at the show, given by veteran Datalight engineers Keith Garvin and Bill Roman:

View Session Overviews

WorldWide Mobile phone sales increased 14% in 2008

My Nokia 5300 vs My Ex Motorola Rokr E1Image by daslive.blogspot.com via Flickr

Gartner just announced their latest research on mobile phone sales. Here are some of the highlights

  1. Q1 2008 worldwide sales – 294.3 Million
  2. Growth in emerging markets [Asia/Pacific, Latin America] and slowdown in mature ones [US, Europe, Japan]
  3. Nokia maintains market leadership with 39.1% market share
  4. Motorola woes continue – share drops from 18.4% to 10.2%
  5. LG and Samsung capitalize on Motorola’s challenges.

image

The entire press release is located here and is very informative. If you are in the mobile software/hardware business, I’d strongly recommend you check it out.

YAFFS – Linux Flash File System

Continuing the conversation started in Flash File Systems and JFFS2 blog posts, this post talks about a YAFFS, another Linux flash file system alternative. YAFFS (Yet Another Flash File System) was designed to solve some of the performance issues suffered by JFFS2 on NAND flash. Later, YAFFS was upgraded (to YAFFS2) to work with modern, high-density NAND flash. Like JFFS2, YAFFS2 is a log-structured flash file system. YAFFS2 is licensed under the GPL for use with Linux; it also can be ported to and licensed for non-GPL environments, if needed

Interesting facts about YAFFS

1. Reliability against data corruption – As a log-structured file system, YAFFS2 is intended to be power-fail safe, though there have been reports of data corruption during the garbage collection process and cases where YAFFS2 has lost directories.

2. Wear Leveling – YAFFS2 only implements dynamic wear leveling. Wear leveling is not performed for static data. This may cause a higher number of blocks to be rendered useless at a faster rate than if both static and dynamic wear-leveling scheme were available. [For more information on static and dynamic wear-leveling, see our whitepaper on the topic at www.Datalight.com/whitepapers].

3. Performance: According to the YAFFS development team, YAFFS2 will perform best on disks that are greater than 64MB, while JFFS2 is still preferred for smaller disks.

For a detailed look at YAFFS, there is a great presentation on YAFFS by Wookey at Embedded Linux Conference 2007.

Risks on relying on a single flash vendor

Interesting piece of news today – Digitimes is reporting that Samsung has informed its customers that it will be reducing supply of NAND Flash chips because of the huge order placed by Apple. This story is being picked up by several news outlet including Engadget. While this is good news for Apple and all those vying for the 3G iPhone, it underscores the challenges other OEMs that depended on Samsung Flash will be facing. NAND flash market is very volatile with demand – supply economics changing rapidly. Intricacies of flash memory force most OEMs to rely on a single vendor for supply, that way they do not have to implement support for several flash parts in their design. While this may seem the easier route, situations such as today’s causes production to come to halt or a significant redesign, both which are very expensive alternatives.

One of the ways to reduce such risk is to include support for multiple flash parts and use multi-sourcing to source flash parts from 3-4 flash vendors. If you are using an intelligent flash manager like FlashFX Pro , you are already covered since FlashFX pro supports 200+ flash parts from all top flash vendors. For others, it can still be done with some serious effort during planning and design time. Consider this work as an insurance against an event such as today’s.

Is General Embedded Ready for MLC NAND?

Adoption by Industrial & Mil-Aero Promises Some Rewards & Major Issues

MLC NAND is experiencing a high rate of adoption and within the consumer electronics sector – MP3 players, digital cameras, smart phones, flash cards and USB drives – it is everywhere you look. However, other embedded segments (industrial, automotive, military, aerospace, etc), are hesitating to take advantage of MLC’s low-cost, high-density attributes. There are good reasons behind the cautious stance; these applications are often mission critical, have a low tolerance for failure, and are expected to perform consistently over a much longer lifespan than their counterparts in the nearly-disposable consumer world. These requirements are in direct conflict with some of MLC’s known shortcomings: shorter lifespan, shorter data retention times, higher error rates, more complex (and consequently slower) error detection and correction.

On the topic of lifespan, traditional single-level NOR parts are typically expected to endure up to 100,000 cycles, which could translate to 20 years of use in a typical embedded application.  Most MLC NAND is rated for 10,000 cycles, rendering these parts unusable in 2 years under the same use case.  While 2 years is a long time for many consumer grade products, it is unacceptably short for the vast majority of industrial products. Similarly, data retention requirements differ.  Traditional flash data retention rates have been 20 years, but recently some flash parts are being introduced with only a 10 or 15 year rating. Applications involving products with life times in the 10 year range need to consider such limitations.

Lower erase cycle endurance is conceptually easy to manage: track high use areas and occasionally swap the data within those areas with a low use area. However, a major difficulty is brewing that involves how errors are introduced and the performance impact of detecting and correcting them.

When writing pages within an erase block, disturb errors may be introduced, causing some number of bits to be flipped in pages other than the one being written to. The time required to read and verify the contents of the entire erase block can cause unacceptable delays, leading programmers to defer the detection until the next read operation, which may occur infrequently. Consequently, bit errors can exist in these “not written to” pages for a long time before they are detected.

And the issues with MLC error rates will worsen, as each new generation of chips pushes the cell size down even further. Future generations of MLC NAND devices beyond the 35nm range may have to distinguish between only a few hundred electrons on each cell. With so few electrons, discerning among the multiple levels of charge in a cell will be a time-consuming, error-prone process.

The somewhat obvious solution is to put in place a process to read and verify areas in the vicinity of writes in an attempt to detect disturb errors earlier.  A solution like this must be carefully balanced with the system performance requirements.

MLC NAND has many compelling reasons for adoption, but until its challenges are successfully dealt with, it will not be broadly accepted by industrial, mil-aero, and automotive device designers as a viable replacement for tried and true technologies of SLC NAND and NOR.

At Datalight, we are focused on easing many of the problems of MLC NAND. For more information on our intelligent flash management solutions, please visit our resources page.

Welcome to “Data Matters”

Hi All:

Welcome to the Datalight blog on “Data Matters”.   It’s amazing to see the increase in size and value of data in devices over 25 years that Datalight has been in business.   In the old days, well the 80’s, Datalight worked with Flight Data recorders that held data on 3.5 inch floppies using the FAT file system and  similar non-reliable foundations.  Today, device data requirements are growing at a tremendous pace. These requirements include reliability, performance, size and flexibility in media, bootability and system field-update requirements.

Road Trip: San Francisco - Gadget list

Image by mr brown via Flickr

On the consumer front, the spectrum moves from the inexpensive GO Phone, up to the Feature phones (with multimedia capabilities) toward the Smartphones that can assume the role of a MP3 Player, a movie Player or an office management system for the road warrior.

The more demanding embedded devices hold data that is much more valuable, sensitive, and mission critical.  These devices succeed or fail based on how they handle, store and deliver the data to the final data consumer.

There many “Good Enough” solutions that, well, aren’t really “Good Enough”!     Datalight is committed to Risk Free Device Data, and that’s what this Blog is all about.   If you require more than “Good Enough” for your device data, then keep reading.

Thanks for joining us!

Roy Sherrill
President