This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Questions about dual flash
- From: "Tom Deconinck" <t dot deconinck at gmail dot com>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Mon, 3 Dec 2007 13:31:35 +0100
- Subject: [ECOS] Questions about dual flash
- References: <31213.213.15.68.47.1196669035.squirrel@webmail.chalmers.se> <e37cb5250712030430v4e71799ase1c40bc57889a1fc@mail.gmail.com>
On Dec 3, 2007 9:03 AM, Per-Erik Johansson <perka@dtek.chalmers.se> wrote:
> Hello again
>
> Found some posts from 2004 about merging flash_v2 and trunk..
> http://sources.redhat.com/ml/ecos-discuss/2004-10/msg00119.html
> will this still work?
> Also I have a home-cooked driver for the internal flash, do I have to
> change this driver or will it work with v2 as it is?
>
> Cheers
> Per-Erik
>
>
>
> >> Hello
> >>
> >> I'm working on a redboot port for a PhyCore MPC5554 board.
> >> Our eval board has flash on it and the MPC5554 also has flash, but on
> >> startup the redboot prompt only displays one flash segment. Could it be
> >> made to show both?
> >> We added so redboot displays both our ram segments but cant understand
> >> how
> >> we could do it for flash since _flash_info() doesn't use a list.
> >> Also, just by using both flash drivers, with corresponding cdl and
> >> c-files, will redboot initiate both our flashes?
> >
> > The trunk of anoncvs has no support for discontinuous flash. Look at
> > the flash_v2 branch, which can have multiple flash devices.
> >
> > 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
>
>
Hi,
Yes, the merging will work.
I've done it a couple of weeks ago in light of porting eCos on the
AT91SAM7SE family.
Just start from the trunk tree and then replace the following
directories with their flash_v2 branch counter parts:
io/flash
dev/flash
redboot
fs/jffs2
You will probably have to make some small changes to your ecos.db too,
but those are pretty straight-forward.
If you enable the flash legacy api (CYGHWR_IO_FLASH_DEVICE_LEGACY cdl
option), I guess your home-cooked driver should still work.
Tom
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss