This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
ecosconfig generic ARM target
- From: Scott Dattalo <scott at dattalo dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Fri, 14 Jun 2002 11:40:48 -0700 (PDT)
- Subject: [ECOS] ecosconfig generic ARM target
Does anyone have recommendations on how I can target a generic ARM core
for simulation purposes?
Ultimately I intend to port an application to an AT91xxxx. At the moment,
I have the AT91EB40 and AT91EB40A eval boards. But prior to porting to
real hardware, I need to assess my application's resource requirements
(RAM requirements, CPU performance, etc) so that I can make some
fundamental design decisions about the final product.
As a test, I successful built and simulated the hello.c application (which
is in the old ecos-1.3.1 distribution, but not in CVS). For my ecosconfig
target, I've selected the at91/eb40. For my gdb target, I selected the
simulator. Now when I simulate, the application hangs deep in the bowels
of eCos waiting for some hardware related thing that doesn't exist. I know
I could painstakingly "#ifdef SIMULATE" the at91 source, but it'd be more
convenient to use a generic ARM core already configured for simulation.
Any recommendations?
Thanks,
Scott
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss