This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Redboot _do_flash_init() too late for initialization of "/dev/flash1"?
- From: Andrew Lunn <andrew at lunn dot ch>
- To: wang cui <iucgnaw at msn dot com>
- Cc: ecos-discuss at sourceware dot org
- Date: Fri, 15 Dec 2006 19:52:15 +0100
- Subject: Re: [ECOS] Redboot _do_flash_init() too late for initialization of "/dev/flash1"?
- References: <BAY110-F10BC3C5D94A7A2C167CBDBA5D40@phx.gbl>
On Fri, Dec 15, 2006 at 05:02:41AM +0000, wang cui wrote:
> I added JFFS2 package into my platform. For the default configuration, it
> works well.
>
> Since I don't want to locate the JFFS2 image at a static location(set by
> "CYGNUM_IO_FLASH_BLOCK_CFG_STATIC_1"), I switch to
> "CYGNUM_IO_FLASH_BLOCK_CFG_FIS_1" to let "/dev/flash1" device get its block
> infomation from FIS.
>
> But when cyg_io_init() call "/dev/flash1"'s init function, all FIS
> information are not intialized yet, and the device init fails.
> Until Redboot's cyg_start() call _do_flash_init(), the FIS get initialized.
>
> So the "/dev/flash1" device was not available when I mount the JFFS2
> filesystem. However the mount action still pass(the mount only try to
> lookup the device, but not check whether the device is available), but I
> can't write any files because the "/dev/flash1"'s block infomation is
> invalid(all zero).
>
> So I wander how to get "CYGNUM_IO_FLASH_BLOCK_CFG_FIS_1" work?
This was discussed about a month ago. I asked the reporter of the
problem to try a different versions of eCos from CVS, but i never got
a reply. Please could you read:
http://sourceware.org/ml/ecos-discuss/2006-11/msg00176.html
Thanks
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