This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Trying to get ecosconfig to work with a definitive xxxx.ecc
- From: Bart Veer <bartv at ecoscentric dot com>
- To: erik at dd dot nec dot com dot au
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 22 Mar 2005 10:49:39 +0000 (GMT)
- Subject: Re: [ECOS] Trying to get ecosconfig to work with a definitive xxxx.ecc
- References: <20050322045153.GB917@dd.nec.com.au>
>>>>> "Erik" == Erik Christiansen <erik@dd.nec.com.au> writes:
Erik> While trying to configure a small non-preemptive eCos
Erik> scheduler, unaware of hardware, without I/O, just to run on
Erik> top of existing board initialisation, we've hit the
Erik> following snag.
Erik> o configtool segfaults when attempting to resolve the
Erik> second of 2 conflicts after "omit hardware" and deleting
Erik> serial packages from the Adder template, so ecosconfig
Erik> begins to look very attractive. (Happens both with Adder
Erik> and fads templates.)
If you have an exact sequence of steps which can reproduce this
reliably, please consider filling in a bugzilla report.
http://ecos.sourceware.org/problemreport.html
Erik> o ecosconfig has apparently suitable templates, like
Erik> "kernel", that I haven't found in the gui, but generates
Erik> only 42 lines of top level .ecc, providing no scheduling
Erik> options, etc.
Erik> o Trying
Erik> ecosconfig new adder850
This gives you a file ecos.ecc with full details of all the
configuration options, i.e. the 14K or so lines. ecos.ecc is the file
you should edit for fine-grained configuration.
Erik> ecosconfig export xxxx.ecc
Erik> still only gives 141 lines of .ecc, as opposed to 14126
Erik> from the gui. (Even after importing the detailed .ecc,
Erik> ecosconfig exports only the version devoid of fine
Erik> options.)
"ecosconfig export" is used to generate a minimal configuration save
file, with all the comments removed, all options with default settings
stripped out, etc. Typically this results in a file of some dozens to
hundreds of lines, i.e. a couple of order of magnitudes smaller than
ecos.ecc. It still contains the exact information needed to reproduce
a full ecos.ecc configuration, but is not intended for editing.
Exporting is very useful if you need to share a configuration with
another user. For example when submitting a bug report you can supply
a small exported file rather than a massive ecos.ecc file without
losing any important information.
So just skip the export step and edit the ecos.ecc file generated by
"ecosconfig new".
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