This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: RedBoot RAM version problem
- To: Andre Sebastien <sebastien dot andre at sxb dot bsf dot alcatel dot fr>
- Subject: Re: [ECOS] RedBoot RAM version problem
- From: Gary Thomas <gthomas at redhat dot com>
- Date: Fri, 27 Jul 2001 08:53:34 -0600 (MDT)
- Cc: ecos-discuss at sources dot redhat dot com
- Organization: Red Hat, Inc.
On 27-Jul-2001 Andre Sebastien wrote:
> Hi,
>
> I start to examine this file !! i make a little changment in the code for see th
> differents ID , build it and execute it !!!
>
> so MANUFACTURER ID that device return is 18 and the expected by redboot is 31
> FLASH device ID that device return is 0 and the expected by redboot is 164
>
> So What should i do ? bypass this test or not ?
It seems to me that the device is not responding to the inquiry - those are not
valid numbers AFAIK.
In most of the flash drivers, there is a pause after sending the "identify" command
before reading the data. Some devices take a really long time to go into that
mode and send back the correct information. Try increasing the pause and see
if it starts working.
>
> Jesper Skov wrote:
>
>> >>>>> "Andre" == Andre Sebastien <sebastien.andre@sxb.bsf.alcatel.fr> writes:
>>
>> Andre> Yes it s this flash device that i have (AT29C040A) !!!! What
>> Andre> does it wrong ?
>>
>> Dunno. I remember we had a similar problem with one of the boards in
>> our test farm, but I never got around to investigate.
>>
>> The problem is that the device ID returned by the device when queried
>> is not what the driver expects. See flash_hwr_init in
>> devs/flash/atmel/at29cxxxx/current/include/flash_at29cxxxx.inl.
>>
>> Jesper