This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
ecos porting question
- From: Brian Smith <briansmith777 at sky dot com>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 13 Oct 2010 13:41:19 +0100
- Subject: [ECOS] ecos porting question
Hi,
I'm trying to port ecos to a coldfire mcf5235 chip and using the
mcf5272c3 target as a starting point.
I've copied a template for the 5272c3 and have modified it to reflect
my new template 5235c3 development board.
I've modified the proc_io.h file to include the required definitions
such as HAL_MCFXXXX_HAS_MCF5282... and removed any specific m5272
definitions and commented out the HAL_CLOCK_INITIALISE .
HAL_CLOCK_RESET and HAL_CLOCK_READ from proc_intr.h.
I thought that this would build with the variant definitions for
HAL_CLOCK _....( which are more akin to the mcf5235 architecture.).
However ?I get the following errors
var_intr.h 473:3 #error Processor or platform hal Should have provided
HAL_CLOCK_INITIALIZE macro
HAL_CLOCK_RESET
HAL_CLOCK_READ
does this mean I need to define the variant macros again in the
proc_intr.h file?
Regards and thanks in advance.
Brian Smith
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss