This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Re: What is the reason to...
>>>>> "Oliver" == oliver munz @ s p e a g <munz@speag.ch> writes:
Oliver> In this case templates like:
Oliver> target at91sam7sek {
Oliver> alias { "Atmel AT91SAM7SEK evaluation board" at91_at91sam7sek }
Oliver> packages { CYGPKG_HAL_ARM
Oliver> CYGPKG_HAL_ARM_AT91
Oliver> CYGPKG_HAL_ARM_AT91SAM7
Oliver> CYGPKG_HAL_ARM_AT91SAM7SEK
Oliver> CYGPKG_IO_SERIAL_ARM_AT91
Oliver> CYGPKG_DEVS_FLASH_AT91
Oliver> CYGPKG_DEVS_SPI_ARM_AT91
Oliver> CYGPKG_DEVICES_WATCHDOG_ARM_AT91WDTC
Oliver> CYGPKG_DEVS_USB_AT91
Oliver> }
Oliver> description "
Oliver> The at91sam7sek target provides the packages needed to run eCos
Oliver> on an
Oliver> Atmel AT91SAM7S-EK evaluation board."
Oliver> }
Oliver> should be changed?
Oliver> They are missing the CYGPKG_IO_SPI and so on...
As per http://ecos.sourceware.org/ml/ecos-devel/2008-11/msg00012.html,
yes. However it looks like other changes are needed. If you just add
CYGPKG_IO_SPI to the target definition (not template, that is
something else) then you end up with SPI driver code even in
executables that do not use SPI. Just build the default config, then
do an objdump of install/tests/kernel/current/tm_basic, and you'll see
the spi functions.
Changing spi_at91.cdl, removing the -library=libextras.a from the
compile spi_at91_init.cxx, sorts out that problem. However I don't
have a suitable board handy right now so I cannot check that
everything still works.
So somebody needs to do some experimenting and provide a patch.
Bart
--
Bart Veer eCos Configuration Architect
eCosCentric Limited The eCos experts http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.