From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "eCos Discuss" <ecos-discuss@ecos.sourceware.org>
Cc: "'Jürgen Lambrecht'" <J.Lambrecht@televic.com>
Subject: RE: [ECOS] Configuring EB40A for JFFS2
Date: Fri, 15 Jun 2007 06:25:00 -0000 [thread overview]
Message-ID: <009201c7aecf$a38d2cb0$887ba8c0@PAULD> (raw)
In-Reply-To: <466F94FA.4070902@televic.com>
> From: Jürgen Lambrecht
>
> My flash of 64MB is partitioned this way:
> 1. 0x1000_0000, 0x0004_0000 ( 256KB): RedBoot
> 2. 0x1004_0000, 0x0008_0000 ( 512KB): application
> 3. 0x100C_0000, 0x0002_0000 ( 128KB): spare
> 4. 0x100E_0000, 0x03F0_0000 ( 63MB): jffs2 partition (63MB)
> 5. 0x13FE_0000, 0x0002_0000 ( 128KB): FIS directory and
> RedBoot config
>
> In redboot, I create a jffs2 partition this way:
> fis create -f 0x100E0000 -l 0x03F00000 -n jffs2
>
> application code:
> #include <pkgconf/fs_jffs2.h> // Address of JFFS2
> mount ("/dev/flash1", JFFS2DIR, "jffs2"); // Initialize
> File system (this mounts the "jffs2" partition to the mount
> point (a directory) JFFS2DIR, "/" in my case (root))
Thanks for your help. I decided to manually divide the 32 erasable 64K
blocks into 2 for Redboot, 14 for my app, 14 for JFFS2, and 2 left over at
the top for the flash directory, configuration data and boot script. (I
suppose one would have been enough.)
I'm merely assuming that the top of the flash is where the FIS directory is
stored, because that's where it says it's reading from when I do "fis list".
I'm a little confused, though, because "fis free" shows that space to be
free. (This is an EB40A ARM7 board.)
--
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
prev parent reply other threads:[~2007-06-14 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 13:36 Paul D. DeRocco
2007-06-13 14:19 ` Jürgen Lambrecht
2007-06-15 6:25 ` Paul D. DeRocco [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='009201c7aecf$a38d2cb0$887ba8c0@PAULD' \
--to=pderocco@ix.netcom.com \
--cc=J.Lambrecht@televic.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).