All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded@ozlabs.org
Subject: Debugging tools
Date: Thu, 08 Jun 2006 19:08:32 -0400	[thread overview]
Message-ID: <4488ADF0.2030003@dlasys.net> (raw)
In-Reply-To: <200606011700.k51H0WJw014425@www-webmail1.magma.ca>


    I have encountered one of the rare instances where I need/want more
debugging resources than an LED on an IO port.

    I am looking for some recommendations as well as understanding of
the lighter weight debugging tools that are available.
    I am dealing with a Xilinx V4 PPC405  FPGA. It is hosted in a
computer running Windows XP. Aparently there is a JTAG port
    on the device that emulates a JTAG parallel port on LPT3 on the host
side.

    I was hoping to be able to bring up gdb, download an elf file to the
target and step through a program to see where it is going off the rails.

    A bit of research suggests that there are gdbservers that bridge
between gdb and JTAG. But all the links I have found to rproxy seem to
be broken, and those for gdbproxy seem to be
    for other processors.

  

  parent reply	other threads:[~2006-06-08 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 17:00 memset hangs part way through; called from early_init Chris Dumoulin
2006-06-01 20:32 ` Wolfgang Denk
2006-06-08 23:08 ` David H. Lynch Jr. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-09  0:11 Debugging tools Martin, Tim
2001-10-05 13:01 debugging tools Westerman, Mark
2001-10-05 16:23 ` Conan Callen
2001-10-04 12:58 Compiling for SuSE 7.2 James Bishop
2001-10-04 17:05 ` debugging tools Conan Callen
2001-10-04 18:08   ` Stephen Smalley
2001-10-04 19:01   ` Jose Nazario

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=4488ADF0.2030003@dlasys.net \
    --to=dhlii@dlasys.net \
    --cc=dhlii@comcast.net \
    --cc=linuxppc-embedded@ozlabs.org \
    /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.