Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] MMC filesystem speed

2005-11-21 by Bertrik Sikken

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

donhamilton2002 wrote:
> I will leave the discussion about the legalities alone.
> 
> I would like to know, those whom have used this code.
> 
> What is the speed of writing a file to the media?
> 
> Whether using an AVR or an ARM chip.
> 
> Just how fast can I (we) write to the media?
> 
> There is a lot of code here to run through, latency is my interest.

I'm wondering about this too.

Tom, do you have a general idea about how long the card
responds with a busy condition after issuing the WRITE_BLOCK
command?

And have you tried the WRITE_MULTIPLE_BLOCK command?
- From what I've read in some of the sandisk documents,
their flash products internally use blocks much larger
than a single 512-byte sector, so using the WRITE_MULTIPLE_BLOCK
command may help to write more efficiently (faster, smoothly) and
probably also reduce wear of the flash medium.

I'm looking into this for my hobby project, a digital bat
detector. It records ultrasonic bat audio at around 250 kS/s
and writes it directly onto a flash disk. This recording can
then be slowed by 16 times to make it audible to humans or be
read in on a PC for frequency analysis.
Since the data is coming in at a steady rate and there's not a lot
of RAM to buffer incoming samples, I think I have to be careful
to avoid delays when writing to the flash.

I expect to receive the hardware (LPC2148) this week, so I hope
I can help to answer some of these questions myself in a few weeks.

Kind regards,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDgkIBETD6mlrWxPURAgw6AKCdZRN0kj35a05QsfkBppHePOy1IwCfap3Y
LYi3H36Tj/rez8XbjniIjBY=
=ir/I
-----END PGP SIGNATURE-----

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.