kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: chris@basementcode.com (Christopher Harvey)
To: kernelnewbies@lists.kernelnewbies.org
Subject: picking an ARM board with jtag for debugging
Date: Wed, 01 Jun 2011 09:11:52 -0500	[thread overview]
Message-ID: <1429bc2cc7af63be845fbb4281d85c2d@basementcode.com> (raw)
In-Reply-To: <4DE5E46C.2090308@gmail.com>

 On Wed, 01 Jun 2011 09:04:12 +0200, luca ellero <lroluk@gmail.com> 
 wrote:
> On 31/05/2011 16.39, Christopher Harvey wrote:
>>   I'm looking for an ARM board with a cortex a9 mpcore with a good
>>   solution for jtag debugging under linux.
>>
>>   I have a beagle and a pandaboard sitting in front of me, but the 
>> beagle
>>   only has cortex a8 and the pandboard jtag situation looks pretty 
>> dismal.
>>   (You need to buy and download a lot of software). Cost really 
>> isn't an
>>   issue, (under 1000$) but good gdb support is critical.
>>
>>   I need jtag specifically because kgdb doesn't start up soon enough 
>> for
>>   me.
>>
>>   Anybody here doing ARM linux development with jtag?
>>
>>   thanks,
>>   -Chris
>>
>
> Hi Christopher,
> why not give a look at OpenOCD? Some guys (me included) have sent 
> some
> patches to support Cortex A9 and Panda. Development version has now
> (basic) support for Pandaboard.
> Anyway you have to use development version (git clone
> git://repo.or.cz/openocd.git) since 0.4.0 stable release hasn't good
> support for Cortex A8/A9.
> Furthermore, if you use git version you can also contribute to 
> improve
> cortex-A* support, which is always very welcome ;-)
> I'm just about to write an HowTo to explain how to use OpenOCD on 
> Panda.
> I will publish it on my site soon.
>
> regards
> Luca Ellero
>

 Thanks Luca,
 I find it funny that of all the expensive jtag solutions out there, 
 OpenOCD seems to be the most convenient. I will probably try that 
 direction out. Hopefully I will find the time to learn and help out with 
 OpenOCD if I happen to need features that it doesn't already support.

 -C

      reply	other threads:[~2011-06-01 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 14:39 picking an ARM board with jtag for debugging Christopher Harvey
2011-06-01  7:04 ` luca ellero
2011-06-01 14:11   ` Christopher Harvey [this message]

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=1429bc2cc7af63be845fbb4281d85c2d@basementcode.com \
    --to=chris@basementcode.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).