Re: use bdi on board with ppcbug

Re: use bdi on board with ppcbug

[于婧]

hi!
    Thanks a lot! I know the where the entry of ppcbug is,but by testing not regular operation.My board's ppcbug entry is 0xfff04000,is it strange?
     And another question:when I use bdi2000 to debug the kernel,if I use 'next'command, the kernel will run until the end of the kernel(that is the whole start procedure).But the normal situation should be excuting a single instruction!Can anybody tell me Why?
     Thanks in advance

>  I want to debug the kernel on the motorola lopec p011 board with bdi
>tools. And the first thing I must solve is to let the ppcbug "go" under
>the bdi control. But I don't know where the entry of ppcbug is,so I
>can't "go" the ppcbug. Has anybody know that?Or,the ppcbug can not be
>run under this circumstances?

                                                     yujing
                                                     yuj@mail.ndsc.com.cn

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: use bdi on board with ppcbug

[Steven Blakeslee]

Good point.

-----Original Message-----
From: Wolfgang Denk [mailto:wd@denx.de]
Sent: Friday, December 20, 2002 12:11 PM
To: Steven Blakeslee
Cc: ??; linuxppc-embedded@lists.linuxppc.org
Subject: Re: use bdi on board with ppcbug


In message <D73A25AA6E54D511AD74009027B1110F3C050D@ORION> you wrote:
> Also, wouldn't the INIT section of the config script have to be empty?

This depends on the hardware. On many boards a minimal initialization
MUST be performed (like switching off the watchdog timer :-)

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"Wish not to seem, but to be, the best."                  - Aeschylus

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: use bdi on board with ppcbug

[Wolfgang Denk]

In message <D73A25AA6E54D511AD74009027B1110F3C050D@ORION> you wrote:
> Also, wouldn't the INIT section of the config script have to be empty?

This depends on the hardware. On many boards a minimal initialization
MUST be performed (like switching off the watchdog timer :-)

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"Wish not to seem, but to be, the best."                  - Aeschylus

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

use bdi on board with ppcbug

[于婧]

hi!
  I want to debug the kernel on the motorola lopec p011 board with bdi tools.
And the first thing I must solve is to let the ppcbug "go" under the bdi control.But  I don't know where the entry of ppcbug is,so I can't "go" the ppcbug.Has anybody know that?Or,the ppcbug can not be run under this circumstances?

  Wait for your reply?
  Thanks in advance!


                                                               yujing
                                                        yuj@mail.ndsc.com.cn

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: use bdi on board with ppcbug

[Wolfgang Denk]

In message <200212200829.CAA05221@lists.linuxppc.org> you wrote:
>
>   I want to debug the kernel on the motorola lopec p011 board with bdi tools.
> And the first thing I must solve is to let the ppcbug "go" under the bdi control.But  I don't know where the entry of ppcbug is,so I can't "go" the ppcbug.Has anybody know that?Or,the ppcbug can not be run under this circumstances?

Just type "reset", followed by "go".

Like any other boot loader, ppcbug will strat right  from  the  reset
vector.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Eschew obfuscation.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: use bdi on board with ppcbug

[Dave Wilhardt]

Wouldn't it be the PowerPC reset address - 0xFFF00100?

ÓÚæº wrote:

> hi!
>   I want to debug the kernel on the motorola lopec p011 board with bdi tools.
> And the first thing I must solve is to let the ppcbug "go" under the bdi control.But  I don't know where the entry of ppcbug is,so I can't "go" the ppcbug.Has anybody know that?Or,the ppcbug can not be run under this circumstances?
>
>   Wait for your reply?
>   Thanks in advance!
>
>                                                                yujing
>                                                         yuj@mail.ndsc.com.cn
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: use bdi on board with ppcbug

[Wolfgang Denk]

In message <3E03565A.49119F4@synergymicro.com> you wrote:
>
> Wouldn't it be the PowerPC reset address - 0xFFF00100?

0xFFF00100 is just one out of several possibilities, depending on CPU
type and system configuration.


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
In the bathtub of history the truth is harder to hold than the  soap,
and much more difficult to find ...     - Terry Pratchett, _Sourcery_

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: use bdi on board with ppcbug

[pat_etc]

to see where your boot code starts:

at the BDI prompt the command:
reset halt  <enter>
followed by the command
info  <enter>

BDI responds with:

    Target state      : debug mode
    Debug entry cause : debug port nonm
    maskable breakpoint
   Current PC        : 0xfff00100

current pc is where your boot code starts
hope this helps
pat

----- Original Message -----
From: "Wolfgang Denk" <wd@denx.de>
Sent: Friday, December 20, 2002 1:09 PM
Subject: Re: use bdi on board with ppcbug


> In message <3E03565A.49119F4@synergymicro.com> you wrote:
> >
> > Wouldn't it be the PowerPC reset address - 0xFFF00100?
>
> 0xFFF00100 is just one out of several possibilities, depending on CPU
> type and system configuration.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/