* BDI3000 JTAG debug on OMAP3
@ 2008-07-09 23:38 Josh Karabin
0 siblings, 0 replies; only message in thread
From: Josh Karabin @ 2008-07-09 23:38 UTC (permalink / raw)
To: linux-omap
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-07-10 0:14 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-09 23:38 BDI3000 JTAG debug on OMAP3 Josh Karabin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox