public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "eCos Discuss" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Configuring EB40A for JFFS2
Date: Wed, 13 Jun 2007 13:36:00 -0000	[thread overview]
Message-ID: <000901c7ad49$a6a57e70$887ba8c0@PAULD> (raw)

I have an old EB40A (ARM7) board, and am having trouble figuring out how to
partition its 2MB flash memory. I already have Redboot burned into the
flash, and FIS set up. The bootable version of Redboot is represented by an
FIS image called "Redboot", covering the first 128K of flash. Not sure if
that was necessary, but it seemed like a Good Idea.

I have a boot script which currently just consists of "fis list"; I'll add
an "fis load" command later. It doesn't appear as an image in "fis list",
but I assume that that's because it's short, and there's some magic that
allows short boot scripts to be stored directly in the FIS directory,
instead of in an image. (Did I read that somewhere, or did I just make that
up?)

Anyway, what I want to do next is create an eCos app that uses JFFS2. The
rest of my flash, then, must be divided between the area where I store the
app, and the area used for JFFS2 file storage. I don't want to store the app
inside a JFFS2 file, as I'm content to use Redboot to write each new version
of the app into flash manually.

I have a vague memory of reading somewhere that there's a way to get JFFS2
to use a named FIS image, rather than having to hard code a start address
and length in my eCos app. Is this true? If so, do I first use Redboot to
manually create an empty image of the appropriate name, using "fis create -n
...", and then later let Redboot create an image for my app using the rest
of the space? Or should I first create an image for my app, possibly padding
it for future growth, and then create an empty image for JFFS2 to use out of
the remaining space?

Next question: with only 2M flash, and with my app written in C++, I don't
have a lot of room to spare. I'd like to store my app as GZIPped binary, but
my current version of Redboot doesn't have support for that. Among the
available packages, I see something called "Zlib compress/decompress". Is
that the same thing as GZIP? If I include that, will it automatically add
support for the "fis load" command -d option, or do I have to do something
else?

(I do have a working RAM version of Redboot, which I can use to burn a new
ROM version into flash, by the way.)

-- 

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com 


--
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:[~2007-06-12 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 13:36 Paul D. DeRocco [this message]
2007-06-13 14:19 ` Jürgen Lambrecht
2007-06-15  6:25   ` Paul D. DeRocco

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='000901c7ad49$a6a57e70$887ba8c0@PAULD' \
    --to=pderocco@ix.netcom.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).