From: John Dallaway <john@dallaway.org.uk>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: eCos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Advice on hardware choice
Date: Tue, 14 Jul 2009 07:56:00 -0000 [thread overview]
Message-ID: <4A5C3A25.4030209@dallaway.org.uk> (raw)
In-Reply-To: <PGEAIGBPLOMOJDAPCOJHKEBONFAB.pderocco@ix.netcom.com>
Hi Paul
Paul D. DeRocco wrote:
> I'm starting a "hobby" project based on eCos, so I have to use the free
> version, but I'm not wedded to any particular hardware platform yet. Before
> I go through the excruciating process of investigating all the hardware for
> which free eCos includes board support packages for, I thought I'd just ask
> for advice. My hardware requirements are:
>
> Roughly the horsepower of a 200MHz ARM
> At least 4MB RAM on a 32-bit bus, preferably single SDRAM chip
> Don't want NOR flash on board (boot from internal or SPI flash)
> 100mb/s Ethernet interface
> Full speed USB slave interface
> SD card interface
>
> If the support is for some off-the-shelf eval board, I'll basically use it
> as the basis for my own hardware design, so the BSP should work pretty much
> as-is.
Evgeniy Dushistov has some eCos patches for AT91SAM9263:
http://ecos.sourceware.org/ml/ecos-discuss/2009-06/msg00136.html
Another possibility is the EP93xx board support from Cirrus Logic:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739
However, it looks like the EP93xx processors do not provide USB slave.
You might also wish to look at some of the more powerful PowerPC boards.
John Dallaway
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-07-14 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 22:58 [ECOS] " Paul D. DeRocco
2009-07-14 7:25 ` Andrew Lunn
2009-07-14 16:19 ` Paul D. DeRocco
2009-07-14 7:56 ` John Dallaway [this message]
2009-07-14 16:21 ` [ECOS] " Paul D. DeRocco
2009-07-14 16:35 ` Tim michals
2009-07-14 17:20 ` H Hartley Sweeten
2009-07-15 6:52 ` John Dallaway
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=4A5C3A25.4030209@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=pderocco@ix.netcom.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).