public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Gary Thomas <gthomas@cambridge.redhat.com>
Cc: ecos-discuss@sources.redhat.com,
	"Dennis Ehlin (ECS)" <Dennis.Ehlin@ecs.ericsson.se>
Subject: RE: [ECOS] Bug in PPC 405 target.
Date: Fri, 04 May 2001 08:44:00 -0000	[thread overview]
Message-ID: <XFMail.20010504094446.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <XFMail.20010504093024.gthomas@cambridge.redhat.com>

On 04-May-2001 Gary Thomas wrote:
>  
> On 04-May-2001 Dennis Ehlin (ECS) wrote:
>> Hi,
>>  
>> The option "CYGHWR_HAL_POWERPC_VECTOR_BASE  (0xfff00000 or 0x00000000)" 
>> doesn't work as intended on the PPC405GP and (i think also the PPC403).
>>  
>> Because the MSR_IP bit is not valid for changing the exception vector offset (The IP_BIT is
>> actually marked as reserved in the MSR register).
>> Instead the EVPR register should be used.
>>  
>> It would be great if I could fix this, but I'm not sure how to tackle the problem, because if I
>> change something in the
>> "powerpc/arch/current/src/vectors.S" file the changes will affect all PPC targets, and that is
>> not what I want, and
>> also the cdl file for the PPC arch needs to be changed to allow setting of other exception
>> vector
>> offsets than 0x00000000 and 0xfff00000 for the PPC40x targets.
>>  
>> "User's Manual page 95"
>>  
>> 23:25 Reserved
>>  
>> "User's Manual page 884"
>> EVPR
>> 
>> Exception Vector Prefix Register
>> 
>> SPR 0x3D6
>> 
>> See "Exception Vector Prefix Register (EVPR)" on page 10-30.
>> 
>> Figure 25-13. Exception Vector Prefix Register (EVPR)
>> 
>> 0:15 EVP Exception Vector Prefix 16:31 Reserved
>> 
>> //Dennis
> 
> All of what you point out is true.  However, the code currently only
> works with the exception vectors set to 0x00000000.  See the setup
> in hal/powerpc/ppc40x/current/include/variant.S.  This code would be
                                        variant.inc  (sorry)

> the place to change things around if you really wanted the vectors
> to be somewhere else.  Also, the exception decode would be affected.
> 
> Is there some reason that you want the vectors somewhere other than 0x0?
> Don't forget that eCos is set up to "create" the vector handling space
> by copying the appropriate vector code (VSR) to the interrupt vector
> table.

  reply	other threads:[~2001-05-04  8:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-04  8:06 Dennis Ehlin (ECS)
2001-05-04  8:30 ` Gary Thomas
2001-05-04  8:44   ` Gary Thomas [this message]
2001-05-04  8:38 Sergio Nunes
2001-05-04  8:44 ` Gary Thomas
2001-05-04  8:56 Sergio Nunes
2001-05-04  9:02 ` Gary Thomas

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=XFMail.20010504094446.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=Dennis.Ehlin@ecs.ericsson.se \
    --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).