This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: FIS problem
- From: Jesper Skov <jskov at redhat dot com>
- To: Jing Luo <Jing at vicom dot com>
- Cc: 'Jonathan Larmour' <jlarmour at redhat dot com>,eCos Discuss <ecos-discuss at sources dot redhat dot com>
- Date: 25 Apr 2002 08:43:12 +0200
- Subject: RE: [ECOS] FIS problem
- References: <B26EACBBAF91D411BD8500508BF7D695051E2A@earth.vicom.com>
On Wed, 2002-04-24 at 17:57, Jing Luo wrote:
> When I try to create ROM-start Redboot version to FLASH block 0 using
> fis create RedBoot -b 0xc1200000 -s 0x1b880 ( 0xc1200000 is the ROM-start
> Redboot image address in SRAM, image size is 0x1b880),
> erasing block 0 and block 1 works, but hang on program flash block 0 start
> on address 0x0.
> The flash chip I have is TE28F016B3TA90, 2MB 8-bit flash.
> But the same command for creating RedBoot[backup] works. The only difference
> is RedBoot[backup] programs FLASH block 3 & 4 from address 0x20000 to
> 0x40000.
By any chance, is there a gap in the flash used for board magic? I know
on some platforms, the range 0x10-0x20 contain board identification
stuff, overriding flash memory in that range.
Obviously, any attempt to program that range is going to fail. In
particular, if the flash driver loops waiting for a status update on the
programmed address, it may hang.
Jesper
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss