From: Mike Wellington <wellington@lucent.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re[1]: BDI2000 vs Vision-ICE
Date: Fri, 09 Jan 2004 08:32:02 -0700 [thread overview]
Message-ID: <3FFEC972.8090207@lucent.com> (raw)
Dear Wolfgang -
I agree. However my superiors seem to want to spend the
money. Good debugging skills and an easy-to-debug architecture
matter more. I just didn't want us to spend USD$7500 on something
that we could buy for USD$2500 - especially not when the traffic
on the list says the BDI2000 is better. But they seem hell-bent
on spending the money.
Mike Wellington
wellington at lucent.com
-------- Original Message --------
Subject: Re: [U-Boot-Users] BDI2000 vs Vision-ICE
Date: Fri, 09 Jan 2004 00:04:38 +0100
From: Wolfgang Denk <wd@denx.de>
In my experience, this is marketing babble. For the low level stuff
("simple problems"), a good logic analyzer is at least as capable,
and for the highlevel ("complicated") problems it doesn't work
anyway, and a plain BDM/JTAG debugger plus a little brain and a lot
of experience gives beter results.
Just my $ 0.02 - ymmv.
next reply other threads:[~2004-01-09 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 15:32 Mike Wellington [this message]
2004-01-09 19:31 ` [U-Boot-Users] Re[1]: BDI2000 vs Vision-ICE Ed Okerson
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=3FFEC972.8090207@lucent.com \
--to=wellington@lucent.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