ecosconfig only provides coarse-grained control over the configuration: the hardware, the template and the packages that should be built. Unlike the Configuration Tool, ecosconfig does not provide any facilities for manipulating finer-grained configuration options such as how many priority levels the scheduler should support. There are hundreds of these options, and manipulating them by means of command line arguments would not be sensible.
In the current system fine-grained configuration options may be manipulated by manual editing of the configuration file. When a file has been edited in this way, the ecosconfig tool should be used to check the configuration for any conflicts which may have been introduced:
$ ecosconfig check
The check command will list all conflicts and will also rewrite the configuration file, propagating any changes which affect other options. The user may choose to resolve the conflicts either by re-editing the configuration file manually or by invoking the inference engine using the resolve command:
$ ecosconfig resolve
The resolve command will list all conflicts which can be resolved and save the resulting changes to the configuration.
It is necessary to regenerate the build tree and header files following any changes to the configuration before rebuilding eCos:
$ ecosconfig tree
All the configuration options and their descriptions are listed in the eCos Reference Manual.