This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Creating a file in JFFS2 within FIS
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Paul D. DeRocco" <pderocco at ix dot netcom dot com>
- Cc: 'ecos-discuss' <ecos-discuss at ecos dot sourceware dot org>
- Date: Mon, 23 Jul 2007 18:48:50 +0200
- Subject: Re: [ECOS] Creating a file in JFFS2 within FIS
- References: <000401c7cc1e$215d8250$6b00a8c0@PAULD>
On Sun, Jul 22, 2007 at 01:06:54AM -0400, Paul D. DeRocco wrote:
> System: Atmel EB40A, ARM7. Redboot has FIS, and there's a blank "image"
> called "jffs2". eCos application loaded over serial for now, includes Posix,
> flash, JFFS2, etc.
>
> My app is trying to create a file, using
>
> f = open("/dev/flash/fis/jffs2/cal.bin", O_WRONLY|O_CREAT|O_TRUNC);
>
> Down inside flashiodev_lookup, it's detecting the "fis/" part of the string,
> and trying to do the CYGNUM_CALL_IF_FLASH_FIS_GET_FLASH_BASE function on the
> name "jffs2/cal.bin", but the latter is returning -ENOENT. I'm under the
> impression that JFFS2 is supposed to be able to automatically initialize a
> blank flash area, but I also don't think it's getting that far. Am I missing
> something? Do I have to do an explicit mount? It seems like the system is
> designed so that "/dev/flash/fis" doesn't need mounting. Is the Redboot
> flash function somehow expecting a name like "jffs2" instead of
> "jffs2/cal.bin"? Any ideas?
You need to mount the filesystem. It is not automagically mounted.
There is a way to use FIS to indicate the location of the filesystem
in flash, however, im not sure how to use it. Take a look at
CYGNUM_IO_FLASH_BLOCK_CFG_FIS_1 in io/flash/current/
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss