This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Flash - the saga continues
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Matt Sartori <msartori at hanoverdisplays dot com>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 30 Aug 2005 16:29:06 +0200
- Subject: Re: [ECOS] Flash - the saga continues
- References: <F9885E669725F248A1F6DB9109FDD67905E4E6@Molly.hanover.local>
On Tue, Aug 30, 2005 at 02:19:47PM +0100, Matt Sartori wrote:
> Hi Andrew.
> I'm using my own flash drivers which I've placed in
> /packages/devs/flash/arm/myboard/current/src and, in the configtool
> packages window the packages used for my particular configuration are
> both the "generic FLASH memory support" and the "FLASH memory support
> for the ARM STR710FZ2" (which I've been referring to as my board in my
> postings). All the stuff I've not written myself came from a cvs
> snapshot from a month or so back.
>
> The CYGPKG_REDBOOT_FLASH is set to true.
> I know that Redboot is using (or at least calling the expected
> functions) because on reset it now displays the message;
> "FLASH: 0x00000000 - 0x0, 0 blocks of 0x00000000 bytes each."
> I have put a hang (while(1);) in the function that calls the
> flash_hwr_init (called flash_init in
> /packages/io/flash/current/src/flash.c) and it does hang, but putting
> the same in my flash_hwr_init doesn't hang it, ergo it must be calling
> some other flash_hwr_init. My suspicions were then confirmed when I
> renamed my flash_hwr_init and Redboot didn't bat an eyelid.
Try
XXX-elf-objdump --syms install/lib/libtarget.a | less
Then search for flash_hwr_init. You can then see which object file the
symbol is in. That should give you some clues.
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