On Fri, 2008-08-15 at 23:04 +0530, Syed Mohammed, Khasim wrote: > > > -----Original Message----- > > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Peter > > Barada > > Sent: Friday, August 15, 2008 8:34 PM > > To: linux-omap@xxxxxxxxxxxxxxx > > Subject: JTAG debugging of the kernel > > > > I've been trying to use JTAG (and an Abatron BDI-2000) to debug the ALSA > > driver to determine why madplay can't keep up when pulling .mp3 from an > > SD card, and have not had any luck trying to halt via JTAG and set/stop > > at breakpoints within the kernelthe kernel. I've found that JTAG works > > for a while on kernel startup, but stops working at a non-reproducible > > point in the startup code. > > > > Have people had success using a BDI-2000 to debug the kernel after it > > has completed startup? > > > > Any suggestions on what can cause the JTAG to stop working after the > > kernel starts? > > > > I think you should disable Power Management. Which kernel are you using now? 2.6.22.18. I'm planning to move to 2.6.26 after the dust settles... I'll try w/o power management, but any idea why power management might affect JTAG? > Regards, > Khasim -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
