From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Flash write endurance (write cycle) test for AT91RM9200 boards
Date: Wed, 30 Jun 2010 16:17:46 +0200 [thread overview]
Message-ID: <201006301617.46700.marek.vasut@gmail.com> (raw)
In-Reply-To: <BAY134-W19D664FC2A596F0209D21FBDCA0@phx.gbl>
Dne Po 28. ?ervna 2010 22:39:07 Xiachen Dong napsal(a):
> Hi,
>
> We use AT91RM9200 MCU and made our own motherboard for it. We wish to know
> how many write cycles the flash (MicroSD and DataFlash) may survive under
> both OS and non-OS situation. We also wish to know the behavior of the
> flash when the flash becomes dead.
I believe the number of write cycles is unlimited, but at some point, you won't
be able to read the data back ;-) If the flash becomes dead, kernel will mark a
bad block and that's all (you'll be informed). Writes to this block will be
redirected to some healthy block. You'll probably have the flash partitioned and
run some FS on top of it, which will take care of load balancing the flash
blocks. You don't have to worry that the flash will die fast if you don't swap
on it.
Cheers
>
> After doing some searching on the web, we found the following information
> helpful:
>
> 1) Write Endurance in Flash Drives: Measurements and Analysis
> http://www.ccs.neu.edu/home/pjd/papers/fast10-flash.pdf
>
> 2) NAND Testing
> http://wiki.laptop.org/go/NAND_Testing
>
> 3) How Long Does a Flash Drive Last?
> http://www.bress.net/blog/archives/114-How-Long-Does-a-Flash-Drive-Last.htm
> l
>
> What we plan to do is to test the flash both under u-boot (raw, without
> JFFS2) and Linux OS (with ext2 fs). The test will be done with flash empty
> and flash full. We will also do the test under different room
> temperatures.
>
> We searched the archive of the list. It looks like no posts mentioned such
> tests. We wonder anyone on the list has done similar test before and are
> there any special attention need to pay while doing such tests. Are there
> any professional software (either open source or commercial) for such
> tests? Any suggestions and comments are welcomed.
>
> Thanks,
>
> Xiachen
>
>
> _________________________________________________________________
> Turn down-time into play-time with Messenger games
> http://go.microsoft.com/?linkid=9734385
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2010-06-30 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 20:39 Flash write endurance (write cycle) test for AT91RM9200 boards Xiachen Dong
2010-06-30 14:17 ` Marek Vasut [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201006301617.46700.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).