public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@chez-thomas.org>
To: Barton Meeks <bartonm2002@yahoo.com>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] MPC860 and IMMR location
Date: Thu, 18 Jul 2002 08:59:00 -0000	[thread overview]
Message-ID: <1027007960.27397.204.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20020718155449.5312.qmail@web21207.mail.yahoo.com>

On Thu, 2002-07-18 at 09:54, Barton Meeks wrote:
> As I stared writing this, I was thinking there was a
> problem with the viper HAL, but it may just be a
> matter of me being confused by the comments.  In the
> code below, I believe 0xff000000 is indeed the MCP
> registers for just a brief period, until viper.S gets
> going.  Then the internal memory is moved to
> 0xfa020000, which is listed in the comments below as
> "Control/Status+LEDs."
> 

The comments are stale, sorry.  In fact, I don't think the
0xFF000000 space is used anymore at all.

The MCP registers were moved to 0xFA020000 to be more compatible
with the Motorola MBX series of boards.

> This is from viper/current/src/hal_aux.c:
> 
> CYGARC_MEMDESC_TABLE CYGBLD_ATTRIB_WEAK = {
>     // Mapping for the Viper 855/860 development
> boards
>     CYGARC_MEMDESC_CACHE(   0xfe000000, 0x00800000 ),
> // ROM region
>     CYGARC_MEMDESC_NOCACHE( 0xff000000, 0x00100000 ),
> // MCP registers
>     CYGARC_MEMDESC_NOCACHE( 0xfa000000, 0x00400000 ),
> // Control/Status+LEDs
>     CYGARC_MEMDESC_CACHE(   CYGMEM_REGION_ram,
> CYGMEM_REGION_ram_SIZE ), // Main memory
> 
>     CYGARC_MEMDESC_TABLE_END
> };
> 
> 
> 
> 
> Background information:
> 
> At reset time, the 860 family has a configuration (via
> device pins) as to the location of the internal memory
> space. This controls the initialization of the IMMR
> register, which can be later changed by software.
> 
> This setting of the IMMR is changed by ecos based on
> the setting here:
> 
> mpc8xx/current/include/var_regs.h:
>     #define CYGARC_REG_IMM_BASE 0xfa200000
> 
> I'm guessing that the initial (at reset) value doesn't
> really matter, since the value listed above is written
> to the IMMR first thing in hal_hardware_init (such as
> in the files mbx.S or viper.S.)
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Autos - Get free new car price quotes
> http://autos.yahoo.com
> 
> -- 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss



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

      reply	other threads:[~2002-07-18 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  8:54 Barton Meeks
2002-07-18  8:59 ` 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=1027007960.27397.204.camel@hermes.chez-thomas.org \
    --to=gary@chez-thomas.org \
    --cc=bartonm2002@yahoo.com \
    --cc=ecos-discuss@sources.redhat.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).