This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Port to Accelent IDP StrongARM SA1110



Hi all,

I'm working on porting eCos to this platform. This is a StrongARM SA1110
based platform sold by Accelent systems (http://www.accelent.com). The
board has some similarities with Assabet and consequently I'm using the
Assabet port as a template for the porting.

This board has a OS Loader which reads an image file from the Compact
Flash Interface (if there is a card attached in), copy this file to SDRAM
and transfer the execution to a predefined memory position (defined
when the image is created by their development tool).

As far as I understand, I have two options: create a GDB Stubs application
that can be copied to the CF card and then booted into the SDRAM memory or
port RedBoot and do the same thing. Re this, which option is better? (I'm
going with the GDB stubs so far but as I've just started I still have
time to change...)

Re the port, first of all I've copied the Assabet HAL directory and I'm
working on modifying this directory. As stated in the porting guide I've
modified the CDL files (renaming stuff), the memory mapping (which is
0x80000000 for SDRAM (size: 32MB) and 0x90000000 for FLASH (size: 16MB))
and added the necessary packages to the ecos.db file (I basically
replicated all the Assabet packages and renamed them). 

I know that I've got more thing to do to starting testing the port but
anyway I think that the modifications I've done so far should be enough
to generate a ecos stubs tree with the following command (I named the new 
platform as accelent):

ecosconfig new accelent stubs

this commands outputs the following messages:



ecos.db, package CYGPKG_NET_AUTOTEST: warning
    This package is not present in the component repository.
    There is no directory `/opt/cvsecos/packages/net/autotest'.
U CYG_HAL_STARTUP, new inferred value ROM
U CYGSEM_HAL_ROM_MONITOR, new inferred value 1
U CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM, new inferred value 0
U CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT, new inferred value 0
U CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS, new inferred value 1
U CYGBLD_BUILD_COMMON_GDB_STUBS, new inferred value 1



If I try to change the options as also stated in the porting guide:

ecosconfig remove CYGPKG_IO
ecosconfig remove CYGPKG_IO_SERIAL
ecosconfig remove CYGPKG_ERROR

and disable the options CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT,
CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT and
CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT and set CYG_HAL_STARTUP option to RAM
and issue the command:

ecosconfig tree

I get the following messages:



ecos.db, package CYGPKG_NET_AUTOTEST: warning
    This package is not present in the component repository.
    There is no directory `/opt/cvsecos/packages/net/autotest'.
U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
C CYGBLD_BUILD_GDB_STUBS, "requires" constraint not
satisfied:  CYG_HAL_STARTUP == "ROM" 
C CYGBLD_BUILD_GDB_STUBS, "requires" constraint not
satisfied: CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT
C CYGBLD_BUILD_GDB_STUBS, "requires" constraint not
satisfied: CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT
C CYGSEM_HAL_ROM_MONITOR, "requires" constraint not
satisfied:  CYG_HAL_STARTUP == "ROM" 

Unable to generate build tree, this configuration still contains
conflicts.
Either resolve the conflicts or use --ignore-errors



In short these options seem to conflit and I'm not clear why and how to
fix it. Any one could please give me a hand?

Thanks,
Cristiano.

------------------------------------------------------------
Cristiano Ligieri Pereira - http://www.ics.uci.edu/~cpereira



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]