From: Simon Kallweit <simon.kallweit@intefo.ch>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Cc: Ross Younger <wry@ecoscentric.com>
Subject: [ECOS] NAND for STM32, YAFFS and UFFS
Date: Wed, 01 Jul 2009 14:43:00 -0000 [thread overview]
Message-ID: <4A4B771F.1060804@intefo.ch> (raw)
Hello
I added NAND support for the STM3210E-EVAL board today. I currently use
Ross's framework as I think it's a bit more lightweight than Rutgers,
which is rather important for me at the moment. The port consists of the
HAL part as well as a new ST NANDxxxx3A NAND driver. Both were started
as copies of Ross's code. What is still missing is interrupt mode and
the usage of STM32's onboard ECC computation unit.
I wanted to do some quick tests with YAFFS, as my initial port of the
UFFS filesystem is not yet done, and I wanted to get some rough numbers
of what resources are needed to run YAFFS. Unfortunately it turned out
that the YAFFS port does not handle small page NANDs, as one is found on
the STM32 evalboard. Further investigation showed that YAFFS1 was using
small page NANDs and YAFFS2 is used on 1k++ page NANDs. The eCos port is
based on YAFFS2 I guess, so I think this should be renamed properly. Or
was there a plan to support both YAFFS1 and YAFFS2?
After some first investigation of the UFFS source code it seems that it
needs quite a bit of work to make it work properly with eCos and not
have hacks all over the place. But it seems that YAFFS does still use
too much resources for our usage, so I think I need to work on a simpler
one and UFFS still looks like a good start ...
Simon
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2009-07-01 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 14:43 Simon Kallweit [this message]
2009-07-01 18:05 ` Ross Younger
2009-07-02 10:07 ` Simon Kallweit
2009-07-29 14:26 ` Ross Younger
2009-07-29 15:21 ` Simon Kallweit
2009-07-03 14:30 ` [ECOS] YAFFS memory usage Ross Younger
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=4A4B771F.1060804@intefo.ch \
--to=simon.kallweit@intefo.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=wry@ecoscentric.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).