From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: "Shen Rong" <rshen@udtech.com.cn>
Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: debugging using BDI2000 on MPC860
Date: Mon, 16 Jun 2003 14:21:59 +0200 [thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJOEKDDCAA.Stephan.Linke@epygi.de> (raw)
In-Reply-To: <077601c333fe$92722610$e600a8c0@udtech.net>
I found the reason. The is no default boot addres defined. So I have to start the board with "go <bootaddress>" :-(
Thanks, Stephan
> -----Original Message-----
> From: Shen Rong [mailto:rshen@udtech.com.cn]
> Sent: Montag, 16. Juni 2003 13:58
> To: Stephan Linke
> Subject: Re: debugging using BDI2000 on MPC860
>
>
> Maybe a machine check occured and leaded to a reset.
> ME bit in MSR can be set to let machine check lead to a exception.
>
> Normally, BDI will stop at reset vector address after it catches the CPU,
> so you can use "go" to start from reset vector. Anyway, your can use
> "go [address]" to start from another address.
>
>
> ----- Original Message -----
> From: "Stephan Linke" <Stephan.Linke@epygi.de>
> To: "Shen Rong" <rshen@udtech.com.cn>
> Cc: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
> Sent: Monday, June 16, 2003 7:28 PM
> Subject: RE: debugging using BDI2000 on MPC860
>
>
> >
> > Hi Shen,
> >
> > Thanks for your response,
> >
> > I don't know how to interprete this but it always stops with the following status:
> >
> > Target state : debug mode
> > Debug entry cause : machine check interrupt
> > Current PC : 0x00000100
> > Data address : 0x00000000
> > DSISR value : 0x00000000
> >
> > Regards, Stephan
> >
> > > -----Original Message-----
> > > From: Shen Rong [mailto:rshen@udtech.com.cn]
> > > Sent: Montag, 16. Juni 2003 13:03
> > > To: Stephan Linke
> > > Subject: Re: debugging using BDI2000 on MPC860
> > >
> > >
> > > Machine check exception vector is located at 0x200.
> > > 0x100 is reset vector, and it is ok.
> > >
> > > ----- Original Message -----
> > > From: "Stephan Linke" <Stephan.Linke@epygi.de>
> > > To: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
> > > Sent: Monday, June 16, 2003 6:56 PM
> > > Subject: debugging using BDI2000 on MPC860
> > >
> > >
> > > >
> > > > Hi,
> > > >
> > > > I want to use our BDI2000 to debug my MPC860 board. Unfortunately it always stops with a machine check interrupt at
> 0x00000100.
> > > > Flashing works fine.
> > > > Our flash is at 0xff000000, IMMR at f0000000...
> > > >
> > > > Any ideas? How do I define the boot address in MPC860 config files.
> > > >
> > > > Thanks, Stephan
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-06-16 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <077601c333fe$92722610$e600a8c0@udtech.net>
2003-06-16 12:21 ` Stephan Linke [this message]
[not found] <075c01c333f6$ce1c2bf0$e600a8c0@udtech.net>
2003-06-16 11:28 ` debugging using BDI2000 on MPC860 Stephan Linke
2003-06-16 15:27 ` Peter Barada
2003-06-16 10:56 Stephan Linke
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=FCEAKDJJAPHPLJFINDAJOEKDDCAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rshen@udtech.com.cn \
/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 NNTP newsgroup(s).