From: bennett78 <bennett78@digis.net>
To: Wolfgang Denk <wd@denx.de>
Cc: atul.sabharwal@exgate.tek.com, linuxppc-embedded@ozlabs.org
Subject: Re: u-boot debugging
Date: Fri, 20 Jan 2006 13:40:46 -0700 [thread overview]
Message-ID: <43D14ACE.8090204@digis.net> (raw)
In-Reply-To: <20060120194815.654AD353A3F@atlas.denx.de>
[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]
Wolfgang Denk wrote:
>In message <4A062D477D842B4C8FC48EA5AF2D41F201AC2CC8@us-bv-m23.global.tektronix.net> you wrote:
>
>
>>Besides, the BDI has only a 10Mbps Ethernet interface. It might be
>>enough for simple debug operation but they should
>>Have put a 100Mbps link to put it on a shared network. For an isolated
>>network configuration, it should suffice...
>>
>>
>
>
>
Yeah this thread is covering a broad range of JTAG debug. There
are debuggers that range form $50 to $50k with no JTAG standard.
$50 wigglers that are painfully slow because they bit-bang the parallel
port and $50k Gigabit interface with GBs of fast memory that can "capture
bugs" in realtime (that is if you can define/setup the trigger condition to
capture "the bug", but for a 400MHz processor that may only mean 1-2
seconds of data). The BDI is a nice product for $2k, wish I would of
thought of designing it. You can either communicate with it directly for
single step, breakpointing, etc, but the coolness is the capability to run
remote gdb, then there is insight which is a gui that runs ontop of gdb....
works great debugging u-boot and kernel/user code later....but the best
part is no need for windose and with DENX you don't have to pay big
$ to metrowerks, greenhills or the like and wait while they develop or
if they will ever develop debugger software for your target!
>You should really get a clue. Or can you please explain what is the
>maximum transfer rate you can get over the BDM / JTAG interface, and
>how is this limited by the 10Mbps Ethernet interface?
>
>
>Best regards,
>
>Wolfgang Denk
>
>
>
--
*/Frank Bennett
Technical Contractor/*
/Triad Systems Engineering
200 West Mountain Avenue, Suite 103C
Ft. Collins, CO 80521
/http://www.traidsyseng.com <http://www.triadsyseng.com>
frank.bennett@triadsyseng.com <mailto:frank.bennett@triadsyseng.com>/
/office: 970-493-7586
cell: 970-402-9269
[-- Attachment #2: Type: text/html, Size: 3142 bytes --]
next prev parent reply other threads:[~2006-01-20 20:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 18:06 u-boot debugging atul.sabharwal
2006-01-20 19:48 ` Wolfgang Denk
2006-01-20 20:40 ` bennett78 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 18:42 sri.dharmasanam
2006-01-23 7:48 Paula Saameño
2006-01-22 10:10 Albert David
2006-01-23 14:10 ` Atul Sabharwal
[not found] <mailman.3.1137805202.13229.linuxppc-embedded@ozlabs.org>
2006-01-21 14:20 ` Glenn Burkhardt
2006-01-22 8:28 ` Frank
2006-01-20 21:13 atul.sabharwal
2006-01-23 9:25 ` Alexandre BASTOS
2006-01-20 18:13 atul.sabharwal
2006-01-20 18:00 atul.sabharwal
2006-01-20 17:56 atul.sabharwal
2006-01-20 19:46 ` Wolfgang Denk
2006-01-21 6:34 ` Atul Sabharwal
2006-01-23 9:32 ` David Jander
2006-01-23 13:44 ` Atul Sabharwal
2006-01-23 22:32 ` Wolfgang Denk
2006-01-20 6:51 Mustafa Çayır
2006-01-20 13:40 ` Wolfgang Denk
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=43D14ACE.8090204@digis.net \
--to=bennett78@digis.net \
--cc=atul.sabharwal@exgate.tek.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@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;
as well as URLs for NNTP newsgroup(s).