From: "Joshua Horvath" <Josh_Horvath-AJH051@email•mot.com>
To: linuxppc-embedded <linuxppc-embedded@lists•linuxppc.org>
Subject: Abatron BDI2000
Date: Fri, 02 Nov 2001 09:55:07 -0600 [thread overview]
Message-ID: <3BE2C1DB.8B975906@labs.mot.com> (raw)
In my lab, we are currently using EST VisionICE boxes to develop custom
PowerPC 8xx based boards. I recently got a BDI2000 evaluation unit and am
trying to decide if it makes sense to purchase a few of these units and dump
the EST boxes.
>From playing around with the Abatron unit, it seems the two biggest advantages
are
1) MMU support
2) Can be used with a Linux based development pc
Since we haven't had a problem bringing the kernel up on our boards, 1) isn't
(currently) a big deal. What we really need is to be able to debug loadable
modules, which from what I've gathered is only possible with kgdb. Is this
assumption correct?
We can flash our boards, download code, etc. and as I said, we've got the
kernel running successfully. So other than point 2) above, is there anything
else I've missed that would provide a compelling reason to purchase these
units?
Thanks,
-Josh
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-11-02 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 15:55 Joshua Horvath [this message]
2001-11-02 18:10 ` Abatron BDI2000 Scott Anderson
2001-11-02 21:03 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 18:04 Williams, Kevin M.
2001-11-20 18:54 ` Wolfgang Denk
2001-11-20 16:36 Williams, Kevin M.
2001-11-20 17:13 ` Wolfgang Denk
[not found] ` <3BFA8C23.465CD6B1@cambridgebroadband.com>
2001-11-21 1:07 ` Michael Habermann
2001-01-31 0:37 Brian Kuschak
2001-01-30 22:42 Brian Kuschak
2001-01-31 0:13 ` 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=3BE2C1DB.8B975906@labs.mot.com \
--to=josh_horvath-ajh051@email$(echo .)mot.com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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