RE: debugging using BDI2000 on MPC860

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:<redacted>]
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" <redacted>
To: "Shen Rong" <redacted>
Cc: "Linuxppc-Embedded" <redacted>
Sent: Monday, June 16, 2003 7:28 PM
Subject: RE: debugging using BDI2000 on MPC860

quoted

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

quoted

-----Original Message-----
From: Shen Rong [mailto:<redacted>]
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" <redacted>
To: "Linuxppc-Embedded" <redacted>
Sent: Monday, June 16, 2003 6:56 PM
Subject: debugging using BDI2000 on MPC860

quoted

Hi,

I want to use our BDI2000 to debug my MPC860 board. Unfortunately it always stops with a machine check interrupt at

0x00000100.

quoted

quoted

quoted

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/