linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Ross A. Osborn" <rosborn@GI.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Progress - new problem
Date: Mon, 12 Feb 2001 17:35:39 +0100	[thread overview]
Message-ID: <20010212163544.4458A281DA@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 12 Feb 2001 09:54:29 EST." <20010212095429.E8453@gi.com>


Hi Ross,

in message <20010212095429.E8453@gi.com> you wrote:
>
> I have been fighting with an old Nohau BDM debugger and was trying to
> get information together to talk my boss into ordering the BDI2000.  I
> could not find any price information on there web site.

Please understand that I cannot speak for the design and contents  of
Abatron's  web pages.

Speaking for us: we are a reseller for Abatron, and I  certainly  can
send  you a quote. But I'm pretty sure there is US based reseller for
Abatron, too. I have no idea if the US prices  are  highr  or  lower
than ours.

> So, the right thing to do is to send you a message to a quote?  Is it
> just me or is this an odd way to conduct business?

In such situations I'm biased when posting to the  mailing  list.  On
one  side,  I like to help, and give the best advice I am able to. On
the other  side,  this  _is_  commercial  advertising,  and  as  such
inappropriate for the list.

If we're talking directly to each other, we can talk clean business :-)

> This will certainly not make it any easier to convice my boss to buy
> this instead of (or in addition to) the EST products they are currently
> looking at.

Well, when comparing products, just ask a few questions:

* How much does the Linux version of the debugger cost? [And how much
  is the Windows version, and why is there a difference, if any?]

  Our price for  the  BDI2000  bundled  with  bdiGDB  software  which
  interfaces  to  GDB  is  2500  Euro, or about $ 2325 (including the
  power supply).

* Does the debugger support the MMU? Will you get  a  guarantee  that
  you  can  use  it to symbolically debug the LInux kernel, including
  automatic variables (on the stack)?

  Many debuggers fail here, and AFAIK the EST is one of them.  Lately
  I've heard that they provide some MMU support, but it sounded as it
  was  just  for  static  mappings,  so  it  would  fail  for dynamic
  situations like data on the stack.

* Is there any warranty? The BDI2000 comes with 3 years  of  warranty
  for the hardware.

* How good is there  support  if  you  have  any  problems,  or  need
  extensions, etc.?


OK, now I want to ask you a question: what hardware do you  have?  If
you  can  do  with  BDM,  are  you  aware  of  the BDM4GDB project at
sourceforge? You can built the parallel port adapter yourself, or get
it for less than $ 50.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Visit us at Embedded Systems: Feb 14-16 2001, Nuremberg, Halle 12/K01
(with TQ Components); our presentation "Starke Zwerge: Embedded Linux
auf PowerPC-Systemen" on Thursday, Feb 15 2001, 13:30 Forum Halle 11.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-02-12 16:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010212083954.A768@dyn-52-73.matrox.com>
2001-02-12 13:52 ` Progress - new problem Wolfgang Denk
2001-02-12 14:54   ` Ross A. Osborn
2001-02-12 14:33     ` Marius Groeger
2001-02-12 16:35     ` Wolfgang Denk
2001-02-12 16:35     ` Wolfgang Denk [this message]
2001-02-12 14:55   ` Sébastien Côté
2001-02-12 14:35     ` Marius Groeger
2001-02-12 14:41       ` Matt Porter
2001-02-12 18:37         ` Sébastien Côté
2001-02-09 16:24 hints on read() - EFAULT problem Conor O'Gorman
2001-02-09 21:19 ` Progress - new problem Sébastien Côté
2001-02-09 22:11   ` 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=20010212163544.4458A281DA@denx.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rosborn@GI.com \
    /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).