From: Scott Anderson <scott_anderson@mvista.com>
To: Mark Pilon <mark.pilon@minolta-qms.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: how to dump other regs via abatron-bdi / gdb ?
Date: Tue, 28 Aug 2001 08:32:59 -0700 [thread overview]
Message-ID: <3B8BB9AB.570AE813@mvista.com> (raw)
In-Reply-To: 3B8AB925.D2DB3E90@minolta-qms.com
Mark Pilon wrote:
>
> I'm accustomed to printing general purpose registers: print $r0
> and the like --
>
> bringing up a board (before establishing an exception vector table)
> I'm getting some unknown exception -- how do I print the ESR (and
> other SPRs for that matter ) ??
If all is configured correctly, you can just do:
BDI>rd esr
esr : 0x00000000 0
If not, but you know the SPR number, you can just do:
BDI>rdspr 0x3d4
SPR 980 : 0x00000000 0
> I suspect the problem is an incomplete bdi board config file,
> but it'd help to be able to figure out what's missing ...
The BDI came with a file called reg405gp.def. This file contains the
mappings from names to spr/dcr numbers. Make sure it is in your tftp
directory and then make sure you have something like:
[REGS]
IDCR1 0x010 0x011 ;MEMCFGADR and MEMCFGDATA
IDCR2 0x012 0x013 ;EBCCFGADR and EBCCFGDATA
IDCR3 0x014 0x015 ;KIAR and KIDR
FILE reg405gp.def
in your config file. BOOT your BDI and you should then be set.
Scott Anderson
scott_anderson@mvista.com MontaVista Software Inc.
(408)328-9214 1237 East Arques Ave.
http://www.mvista.com Sunnyvale, CA 94085
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-08-28 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 21:18 how to dump other regs via abatron-bdi / gdb ? Mark Pilon
2001-08-28 15:32 ` Scott Anderson [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=3B8BB9AB.570AE813@mvista.com \
--to=scott_anderson@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mark.pilon@minolta-qms.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.