public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Max Seidenstücker" <max.seidenstuecker@googlemail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] JFFS2 on NOR flash with ECC
Date: Wed, 15 May 2013 15:49:00 -0000	[thread overview]
Message-ID: <CAASVbFE8AOs_xpQmJWsot+3veRXQ9RxR9XYibLaDBfdjNUr9Zw@mail.gmail.com> (raw)

Hi folks,

we are using a µC that has ECC calculation on an 8 Byte boundary in
its NOR flash storage. After taking a glance at the JFFS2 eCos port
and the most recent Linux version I am a little lost on how to get the
fastest solution to solve this.

The problem with ECC'd NOR is that the obsolete-flag cannot be
written. ECC is calculated after the initial write, so even this one
bit flip results in an ECC error.

Unfortunately the eCos port of JFFS2 doesn't support NAND flash and
Linux MTD, where the NOR ECC patches
(http://mhonarc.axis.se/jffs-dev/msg01398.html) would be easily ported
to.

So I see two possible approaches:
1. Add JFFS2 NAND support to eCos by updating JFFS2 to the newest
version, which also incorporates adaption of the Linux MTD stuff
2. Increment the obsolete marker to 8 Byte and align it on an 8 Byte
boundary so a obsolete marker will write to a formerly unwritten 8
Byte sector and make sure the flash writes are 8 Byte aligned.

I would like to go with the second approach as it looks faster, but
don't know if this easy to achieve.

Any ideas or help on how to do that, is highly appreciated.

Cheers Max

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2013-05-15 15:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAASVbFE8AOs_xpQmJWsot+3veRXQ9RxR9XYibLaDBfdjNUr9Zw@mail.gmail.com \
    --to=max.seidenstuecker@googlemail.com \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).