From: Andrey Volkov <avolkov@varma-el.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] BDI vs. Lauterbach
Date: Mon, 10 Apr 2006 20:17:25 +0400 [thread overview]
Message-ID: <1618325846.20060410201725@varma-el.com> (raw)
In-Reply-To: <20060410153222.A513C353B3C@atlas.denx.de>
On Monday, April 10, 2006, Wolfgang Denk wrote:
> In message <427722615.20060410170041@varma-el.com> you wrote:
>>
>> Pros:
> meaning: pro for Lauterbach, just to make it clear.
Yes
>> BDI - 10Mbit eth, Lauterbach - 100 Mbit.
> This does not mean anything. I haven't seen a single case where the
> network speed was the limiting factor. Shuffeling the data through
> the JTAG is usually much slower.
Not always. As ex.: allowable MPC5200 JTAG's clock is ... 25 MHz,
clock of 10 Mbit eth is ... + tcp stack overhead. And now we run
memory dump command and measure.
>> Lauterbach scalable and simply extendable, BDI - not.
> What would you want to extend or scale?
Lauterbach like Lego, constructing from modules: from dumb
LPT<->jtg upto monster-alike in-circuit emulator
(I didn't talk about how _much_ smb. will pay for it,
I talk about possibility).
>> Cons:
>> BDI support gnu toolchain natively (in GDB server mode),
> In other words: The BDI2000 fits seamlessly into a Linux based
> development environment. You can use exact the same tools and and
> user interface for low level stuff (boot loader, OS and drivers -
> using the BDI) and for application code (using gdbserver).
Yes.
>> Lauterbach - not (sometime it parsing elf/dwarf correctly,
>> sometime, usually in critical cases :), not).
> Question: does the Lauterbach reliably handle issues like relocating
> the symbol table as needed fur U-Boot?
I'm not sure, since I doesn't work with Lb approx. 3 years,
but probably it could.
>> And you are know, hmm, strange Lauterbach price policy:
>> price of BDI firmware for a new CPU target is approx. 1000 eur,
>> for the Lauterbach - price of new device.
> Another pro for the BDI: they have *excellent* support. I know a
> couple of vendors of hardware and tools etc. Some of them are really
> good, but Abatron beats them all.
Don't asking them for a help, since my BDI work as predicted,
so it may be pros also :).
> Best regards,
> Wolfgang Denk
--
Regards,
Andrey Volkov
next prev parent reply other threads:[~2006-04-10 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 12:38 [U-Boot-Users] BDI vs. Lauterbach David Snowdon
2006-04-10 13:00 ` Andrey Volkov
2006-04-10 15:32 ` Wolfgang Denk
2006-04-10 16:17 ` Andrey Volkov [this message]
2006-04-10 16:38 ` Wolfgang Denk
2006-04-10 18:04 ` Andrey Volkov
2006-04-11 6:06 ` [U-Boot-Users] " Wolfram Wadepohl
2006-04-10 16:35 ` [U-Boot-Users] " llandre
2006-04-10 17:58 ` Andrey Volkov
2006-04-10 19:48 ` Wolfgang Denk
2006-04-10 22:10 ` Andrey Volkov
2006-04-11 10:41 ` Andreas Schweigstill
2006-04-12 7:54 ` David Snowdon
2006-04-12 10:07 ` Wolfgang Denk
2006-04-13 6:17 ` David Snowdon
2006-04-13 6:43 ` Marco Cavallini
2006-04-10 17:00 ` Marco Cavallini
2006-04-10 18:20 ` Frank
2006-04-10 22:04 ` Andrey Volkov
-- strict thread matches above, loose matches on Subject: below --
2006-04-10 13:02 Woodruff, Richard
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=1618325846.20060410201725@varma-el.com \
--to=avolkov@varma-el.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