From: Andre Sebastien <sebastien.andre@sxb.bsf.alcatel.fr>
To: egcs@cygnus.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RedBoot RAM version problem
Date: Mon, 30 Jul 2001 01:38:00 -0000 [thread overview]
Message-ID: <3B651CEF.83619A08@sxb.bsf.alcatel.fr> (raw)
In-Reply-To: <XFMail.20010727085334.gthomas@redhat.com>
Hi everybody !!
So i try to increase a pause in this function : 'void flash_dev_query(void* data)'
into i make a pause at two differents points !!! each pause are around 1 sec (but i
had test it with 15 secs too :-) )
void flash_dev_query(void* data)
{
.....
HAL_FLASH_CACHES_OFF(d_cache, i_cache);
<=========== HERE
(*_flash_query)(data);
<=========== HERE
HAL_FLASH_CACHES_ON(d_cache, i_cache);
}
So this way don t work !!! i have always the same problem !!!!
Gary Thomas wrote:
> 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
next prev parent reply other threads:[~2001-07-30 1:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 7:27 [ECOS] Hardware Watchdog Doug Fraser
2001-07-26 7:51 ` Christoph Csebits
2001-07-26 8:50 ` Gary Thomas
2001-07-26 9:20 ` Christoph Csebits
2001-07-26 9:25 ` Gary Thomas
2001-07-26 11:30 ` Robin Farine
2001-07-26 23:26 ` Christoph Csebits
2001-07-26 23:57 ` Robin Farine
2001-07-27 1:28 ` Christoph Csebits
2001-07-27 1:50 ` Robin Farine
2001-07-27 2:50 ` [ECOS] RedBoot RAM version problem Andre Sebastien
2001-07-27 3:35 ` Jesper Skov
2001-07-27 5:20 ` Andre Sebastien
2001-07-27 6:20 ` Jesper Skov
2001-07-27 7:30 ` Andre Sebastien
2001-07-27 7:54 ` Gary Thomas
2001-07-30 1:38 ` Andre Sebastien [this message]
2001-07-30 1:57 ` Jesper Skov
2001-07-30 2:29 ` Andre Sebastien
2001-07-30 3:03 ` Jesper Skov
2001-07-30 3:07 ` Andre Sebastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B651CEF.83619A08@sxb.bsf.alcatel.fr \
--to=sebastien.andre@sxb.bsf.alcatel.fr \
--cc=ecos-discuss@sources.redhat.com \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).