public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "M.Eugenia G.Valdecasas" <valdecasas@isar-tec.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: Re:[ECOS] Flash detection
Date: Tue, 11 Nov 2003 12:51:00 -0000	[thread overview]
Message-ID: <1068555105.9906.321.camel@hermes> (raw)
In-Reply-To: <20031111100754.GE325@kavik.isar-tec.com>

On Tue, 2003-11-11 at 03:07, M.Eugenia G.Valdecasas wrote:
> > > The configuration lines are:
> > >
> > > in altair_strataflash.inl->
> > >
> > > #define CYGNUM_FLASH_DEVICES     (2)
> > > #define CYGNUM_FLASH_BASE        (0x00000000u)
> > > #define CYGNUM_FLASH_BASE_MASK   (0xFE000000u) // 2 * 16Mb devices
> > > > #define CYGNUM_FLASH_WIDTH       (16)
> > > > #define CYGNUM_FLASH_BLANK       (1)
> > > >
> > > > #define FLASH_P2V(x) ((volatile flash_t *)(((unsigned)(x) <
> > 0x1000) ? \
> > > >                              ((unsigned)(x) | 0xa0000000) : \
> > > >                              (unsigned)(x)))
> > > >
> > >
> 
> > Why do you have this code?  I think it was only necessary on the
> > IQ80321
> > and definitely *not* on the PXA25x
> 
> If I substitude this code for
> #define FLASH_P2V(x) (unsigned)(x)
> 
> The exit on the console would be:
> 
> +$T0a0f:08f0efa3;0d:d8ca00a0;#a7
> 
> and would repeat the same line every time I press a key.

First of all, this is RedBoot falling into GDB mode, indicating that
you are accessing invalid memory.  I think you have other configuration
or setup issues here.

On most ARM platforms, PXA25x based ones included, the hardware has
FLASH at 0x00000000 (as you write above), but eCos immediately uses
the MMU to remap this to some other address.  

For example,  on the uE250 (PXA250) the FLASH is at *logical* address 
0x50000000 and this is the address used by the FLASH drivers.  You'll
have to figure out the appropriate address to use, based on how memory
is being remapped.

> 
> Also I tried to apply the patch for strataflash:
> 2003-05-02 	Jani Monoses
> 
> but it gave me this answer as well:
> +$T0a0f:08f0efa3;0d:d8ca00a0;#a7
> 
> Do I have to apply other patches?
> 
> I know I take ok the data of the flash (manufacturer code, qry etc...) 
> but somehow somewhere between the cache enable and cache disable, this 
> data is lost... does it make anysense what I am saying???
> 
> Why would it jump out of this condition
>   if ( (qp->manuf_code == FLASH_Intel_code) &&
> 	(strncmp(qp->id, "QRY", 3) == 0))
> 
> if the data that the flash sends is correct???? 
> I am out of ideas....
-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      parent reply	other threads:[~2003-11-11 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000b01c3a7d0$49ead9f0$030aa8c0@kavik>
2003-11-11 10:08 ` M.Eugenia G.Valdecasas
2003-11-11 11:22   ` [ECOS] " Jani Monoses
2003-11-11 12:51   ` Gary Thomas [this message]

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=1068555105.9906.321.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=valdecasas@isar-tec.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).