From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] update u-boot BDM/JTAG debugger page?
Date: Fri, 15 Jul 2016 15:34:48 -0400 [thread overview]
Message-ID: <20160715193448.GU7260@bill-the-cat> (raw)
In-Reply-To: <alpine.LFD.2.20.1607151527570.32044@localhost.localdomain>
On Fri, Jul 15, 2016 at 03:29:54PM -0400, Robert P. J. Day wrote:
> On Fri, 15 Jul 2016, Tom Rini wrote:
>
> > On Fri, Jul 15, 2016 at 08:38:57AM -0400, Robert P. J. Day wrote:
> >
> > > i am in no way a BDM/JTAG authority, but i notice that on this
> > > u-boot page:
> > >
> > > http://www.denx.de/wiki/DULG/UBootInstallUsingBDM
> > >
> > > there is a recommendation for the BDI2000/BDI3000, but those are on
> > > their way out:
> > >
> > > http://www.abatron.ch/news/eol-bdi-products/
> > >
> > > so are there any other recommendations for debuggers? is anyone using
> > > the flyswatter debuggers successfully?
> >
> > In general I use one of the FTDI based products. I've got a Flyswatter
> > 2, some Olimex ones and and XDS...something low numbered or two as well.
>
> as i read it, the flyswatter3 is MIPS-only, is that correct? an
> up-to-date debugging page would be immensely handy.
Er, I don't see a Flyswatter 3, but I do see that Tin Can Tools has
adapters for MIPS for Flyswatter 2.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160715/c7860a68/attachment.sig>
next prev parent reply other threads:[~2016-07-15 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 12:38 [U-Boot] update u-boot BDM/JTAG debugger page? Robert P. J. Day
2016-07-15 15:17 ` Tom Rini
2016-07-15 19:29 ` Robert P. J. Day
2016-07-15 19:34 ` Tom Rini [this message]
2016-07-15 19:37 ` Robert P. J. Day
2016-07-15 19:41 ` Tom Rini
2016-07-15 20:18 ` Robert P. J. Day
2016-07-15 20:21 ` Tom Rini
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=20160715193448.GU7260@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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