From: Josh Karabin <gkarabin@vocollect.com>
To: linux-omap@vger.kernel.org
Subject: BDI3000 JTAG debug on OMAP3
Date: Wed, 09 Jul 2008 19:38:08 -0400 [thread overview]
Message-ID: <48754BE0.3070904@vocollect.com> (raw)
Is anyone using a BDI3000 JTAG debugger for kernel debug on an OMAP3
board? An engineer on my team is evaluating the hardware, but running
into some problems. A tip or two would be appreciated from anyone who's
got the hardware working. We've already got a separate evaluation of a
Lauterbach JTAG debugger working, but the BDI seems to be giving us some
trouble. Nothing in the docs or faqs seems relevant.
He can set breakpoints in the kernel and step through code at least
halfway through the power up printks sent to the console, but at some
point (he's still bisecting the debug) he can no longer interactively
halt the kernel, and his breakpoints stop getting hit. The kernel runs
just fine, GDB is able to talk to the BDI3000 just fine, but the BDI3000
seems like it's no longer talking to the OMAP (since halt requests timeout).
Any ideas?
Thanks,
- Josh
reply other threads:[~2008-07-10 0:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48754BE0.3070904@vocollect.com \
--to=gkarabin@vocollect.com \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox