public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Barada <peterb@logicpd.com>
To: "Syed Mohammed, Khasim" <khasim@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: JTAG debugging of the kernel
Date: Fri, 15 Aug 2008 13:58:16 -0400	[thread overview]
Message-ID: <1218823096.24975.108.camel@blackhole> (raw)
In-Reply-To: <0680EC522D0CC943BC586913CF3768C00208C16544@dbde02.ent.ti.com>

On Fri, 2008-08-15 at 23:04 +0530, Syed Mohammed, Khasim wrote:
> 
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Peter
> > Barada
> > Sent: Friday, August 15, 2008 8:34 PM
> > To: linux-omap@vger.kernel.org
> > 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

  reply	other threads:[~2008-08-15 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15 15:03 JTAG debugging of the kernel Peter Barada
2008-08-15 17:34 ` Syed Mohammed, Khasim
2008-08-15 17:58   ` Peter Barada [this message]
2008-08-15 18:57     ` Josh Karabin
2008-08-18 18:47       ` Peter Barada

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=1218823096.24975.108.camel@blackhole \
    --to=peterb@logicpd.com \
    --cc=khasim@ti.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