public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Jaap-Jan Boor <jjboor@lucent•com>
To: linuxppc-embedded@lists•linuxppc.org, r&d@wawnet•biz
Subject: Re: Lauterbach ICD In-Circuit Debugger
Date: Wed, 22 Jan 2003 15:43:53 +0100 (MET)	[thread overview]
Message-ID: <200301221443.PAA15378@hzsms01.nl.lucent.com> (raw)


>
> A lot of people suggest to use the Abatron BDI2000 as debug system. I used
> the Lauterbach TRACE32-ICD system with ARM processors without MMU (no
> Linux) and it works extremely well.
> The manufacturer claims it fully supports both the MMU and the Linux kernel
> (see here for more details
> http://www.lauterbach.com/cgi-bin/docloc.pl?file=rtoslinux.pdf). Can
> anybody who used it confirm this point?

I can. You can debug the kernel and e.g. interrupts using virtual
addresses very well, you just have to specify the mapping
(e.g. for ppc map phys 0x00000000 to 0xc0000000)

I've not looked in detail yet to debug user processes.

Jaap-Jan

>
> Many thanks in advance.
>
>
> llandre
>
>
>

---
J.G.J. Boor
Lucent Technologies Nederland b.v.	Room:  BE-525
Optical Networking Group TMS Data 	Phone: +31 (0)35 687 4721
Larenseweg 50, P.O. Box 1168, 		Fax:   +31 (0)35 687 5976
1200 BD, Hilversum, The Netherlands	mailto:jjboor@lucent•com


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

             reply	other threads:[~2003-01-22 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22 14:43 Jaap-Jan Boor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-22 14:43 Lauterbach ICD In-Circuit Debugger llandre

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=200301221443.PAA15378@hzsms01.nl.lucent.com \
    --to=jjboor@lucent$(echo .)com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=r&d@wawnet$(echo .)biz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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