[ECOS] question on Redboot and CDL template

Bart Veer bartv@ecoscentric.com
Thu Apr 22 14:58:00 GMT 2004


>>>>> "kneep" == kneep  <caozhiyuan@hotmail.com> writes:

    kneep> Dear Bart Veer,
    kneep> 	Thank you for your explanation.
    kneep> 	Then I have some more questions.
    kneep> 	If I define a target in ecos.db as below,

    kneep> 	target ixdp425 {
    kneep> 	alias { "IXDP425 board" ixdp425 }
    kneep> 	packages { CYGPKG_HAL_ARM
    kneep>                    	            CYGPKG_HAL_ARM_XSCALE_CORE
    kneep> 	                        CYGPKG_HAL_ARM_XSCALE_IXP425
    kneep>                                            CYGPKG_HAL_ARM_XSCALE_IXDP425
    kneep> 		      CYGPKG_IO_PCI
    kneep> 		      ..............
    kneep> 		      }
    kneep> 	}

    kneep> 	However, for initial porting, I need not compile the
    kneep> PCI package into the .bin image. So, how to temporarily
    kneep> remove this package? Should I remove it from the target
    kneep> definition lines as shown above? Or I need to remove it
    kneep> from the redboot_xxx.ecm file? Or both?

It depends on exactly what you are doing.

If you are porting to a new target, similar but not identical to an
idxp425, create a new target entry in ecos.db which does not list
CYGPKG_IO_PCI. You'll also want to use modified .ecm files to prevent
the import from re-adding the package.

If you just want to suppress the PCI support for now, and assuming the
rest of the system will work happily if the PCI hardware is not
properly initialized etc., then you can just remove the package from
your configuration. This can be done using either "ecosconfig remove
CYGPKG_IO_PCI" or via equivalent functionality in the configtool.

    kneep> 	BTW, where can I find information about the syntax of
    kneep> 	.ecm file? The online manual seems not provide any so
    kneep> 	far. Thank you.

A .ecm file uses the same syntax as a .ecc savefile, which is
described in the Manual Configuration section of the User's Guide:
http://ecos.sourceware.org/docs-latest/user-guide/manual-configuration.html
.ecm files are just a cut-down version, with all the comments stripped
out and with entries only for configuration options with a non-default
value. 

In practise people don't usually create or edit .ecm files. Instead
you create a full configuration, editing various options as required,
and then use "ecosconfig export" or the equivalent functionality in
the graphical configtool to generate the .ecm file.

Bart

-- 
Bart Veer                       eCos Configuration Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



More information about the Ecos-discuss mailing list