From: Craig Verbeck <CVerbeck@ClarityVisual.com>
To: "'crossgcc@sourceware.cygnus.com'" <crossgcc@sourceware.cygnus.com>
Subject: RE: General embedded development kits using gcc/gdb.
Date: Fri, 07 Jul 2000 09:21:00 -0000 [thread overview]
Message-ID: <7E404755D206D411869900D0B7474D0F06B38A@blackhole.clarityvisual.com> (raw)
My reply may be considered off topic -- but I think it's a cool idea....
| I would like to make some single board embedded development
| kits with some
| simple tools. Firstly I would like to use a board that has a
| more general
| (i.e. non DSP) type processor, something like a MIPS, ARM, PowerPC, or
| Pentium, or anything else that is deemed suitable. The
| programme for a board
| will be programmed using gcc on any type of host computer
| with target output
| for the embedded system processor, and I would like to have
| the facility to
| use gdb as the debugger. Such a system has many advantages.
One not-so-implied requirement is to lower the entry cost to develop on such
a system. IMO this is the key to making this type of system work. I have
been drawn to gcc/gdb/eCos for the same reasons: extremely high quality
tools, exceptionally low cost of entry (in $).
However, there is cost. In many cases you must converge the tools to your
system. To expand on your idea, wouldn't it be great if there were a "kits"
for not just this board (which BTW is an excellent combination) but for a
large number of development boards/eval kits.
I am approached by distributors/factory reps every week. They want to
"give" me an eval board. In almost all cases the development tool-chain
cost is extreme ($5k-$25k+). They will give you an eval license for the
development tools that lasts 30 days. This is not enough time. Also, all
of these compilers are different -- I have no desire to learn a new tool
chain each time I have to develop a project with a new processor.
There are development boards for all of these systems. The ultimate would
be to download a zip (windows) or tar-ball (Linux) that had binary versions
of the compiler, debugger, eCos, and maybe uC/Linux with a BSP for a
specific development board. Based on how much processor you have available
(MIPS, memory size, etc.) other excellent additions would be a portable GUI
and a TCP/IP stack. All ready to go. Download, install and you are ready
to develop in a familiar environment that has been pre-converged to this
target system.
Here's a list of processors that I'd love to see a binary distribution of
this "development kit" for both windows and Linux:
8bit: 8051/Atmel AVR
16bit: x86
32bit: PPC/CPU32(68k)/ARM/MIPS/Pentium
I'm sure there are more. These are the processors that I use (or would like
to use) on a regular basis.
I know a lot of people have developed parts and pieces of this. All of the
source code is available. But, there does not appear to be any _overall_
organization.
Sorry for the rant,
A.C. Verbeck
Principal Software Engineer
Clarity Visual Systems
email: cverbeck@clarityvisual.com
vox: (503) 570-0319
fax: (503) 682-9441
web: www.ClarityVisual.com
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-07-07 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 9:21 Craig Verbeck [this message]
2000-07-07 10:40 ` Daris Nevil
2000-07-07 10:44 ` Joel Sherrill
-- strict thread matches above, loose matches on Subject: below --
2000-07-10 9:23 dwglessn
2000-07-10 11:04 ` Curt Mills, WE7U
2000-07-09 10:51 Andrew Tuckey
2000-07-07 4:27 tuckey
2000-07-07 6:36 ` Andre Rodrigues da Silva
2000-07-07 7:53 ` Frank Przybylski
2000-07-07 11:19 ` norwood sisson
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=7E404755D206D411869900D0B7474D0F06B38A@blackhole.clarityvisual.com \
--to=cverbeck@clarityvisual.com \
--cc=crossgcc@sourceware.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).