Configuration Files

The ChorusOS operating system configuration is expressed in ECML, an XML based language. Further information on ECML is available from "ECML Syntax" in ChorusOS 5.0 Source Delivery Guide. There are several levels of configuration files, all located in the conf directory used to build the system image. They are available to be edited from the conf directory once the system image is built.

Configuration files named in the format xxx.xml can be associated with those in the format xxx_action.xml: the xxx_action.xml usually contains the production rules.

• ChorusOS.xml is the top level configuration file. The entire ChorusOS operating system configuration is accessible through this file, which contains references to all other configuration files.

• typedef.xml contains a definition of generic types. This is not visible from Ews. For more information on Ews, see "The Embedded Workshop Graphical Configuration Tool".

• mkconfig is the directory containing the configuration information for each system component. Most of the information it contains relates to feature options and tunable parameters. For example:

  • mkconfig/kern.xml contains the microkernel feature definitions and dependencies, and contains the tunables for the microkernel. This file also contains default values for the standard configuration.

  • mkconfig/kern_action.xml contains specific configuration actions, including the production rules used internally for the configuration.

  • mkconfig/kern_f.xml and mkconfig/kern_action_f.xml are additional configuration files identified by _f.xml that can be used to manage family-specific configuration options.

  • mkconfig/typedef.xml contains a definition of types for configuration. This is not visible from Ews. For more information on Ews, see "The Embedded Workshop Graphical Configuration Tool".

  • mkconfig/nucleus.xml contains microkernel features and tunables. This file refers to other XML files such as kern.xml, pmm.xml or sysdump.xml.

  • mkconfig/debug.xml contains the debug features and tunables. This file refers to other XML files such as dbgAgent.xml.

  • mkconfig/dbgAgent.xml contains the tunables for System Debug (DEBUG_SYSTEM) feature. Specifies the behavior of the DebugAgent.

  • mkconfig/dbgAgent_action.xml contains associated specific actions related to the DebugAgent.

  • mkconfig/dbgDrv.xml contains tunables to configure the serial line for debugging purposes.

  • mkconfig/dbgDrv_action.xml contains associated actions for debugging purposes.

  • mkconfig/pmm.xml contains persistent memory management tunables.

  • mkconfig/pmm_action.xml contains associated actions.

  • mkconfig/sysdump.xml contains SYSTEM_DUMP tunables.

  • mkconfig/sysdump_action.xml contains SYSTEM_DUMP associated actions.

  • mkconfig/drv.xml defines the DRV_MERGE feature to merge a set of drivers into one (to reduce the image size).

  • mkconfig/os.xml contains the OS features and tunables. This file refers to others files such as cinit.xml or hrCtrl.xml.

  • mkconfig/sys_rule.xml contains Input/Output Management features and tunables.

  • mkconfig/sys_action.xml contains the production rules used internally for Input/Output Manager configuration.

  • mkconfig/cinit.xml contains the command interpreter features such as LOCAL_CONSOLE and rsh.

  • mkconfig/cinit_action.xml contains associated production rules.

  • mkconfig/hrCtrl.xml contains the HOT_RESTART support feature and related tunables, such as maximum number of restart groups and hot restart actors.

  • mkconfig/hrCtrl_action.xml contains associated production rules.

  • mkconfig/monitor.xml contains the monitoring agent feature and related tunables, such as EBD_MONITOR.

• mkimage is the directory containing all the information related to the system image build:

  • mkimage/action.xml contains the production rules for creating the image.

  • mkimage/mkimage.xml contains two configurable declarations:

    • BOOT_MODE is set to ram to build an image for RAM, or rom to build an image for ROM.

    • SYSTEM is set to chorus to build a default system image, or kernonly to build a microkernel-only system image. Other system images are also available.

  • mkimage/family.xml contains the family dependent definitions.

  • mkimage/model.xml contains the binary models for the executable files.

  • mkimage/target.xml contains all configuration options related to the board support package, (BSP), and also the list of drivers. It describes the target specific elements required to build the system image. This is one of the only ChorusOS operating system configuration files that should not be edited. For more information, see the ChorusOS 5.0 Board Support Package Developer's Guide.

  • mkimage/target_action.xml contains actions to produce the system image.

  • mkimage/system.xml contains all system binaries and the configuration of the system image.

  • mkimage/applications.xml describes the applications to be included in the chorus or kernonly system image.

  • mkimage/benchmarks.xml contains a list of the ChorusOS operating system benchmarks to include in the image.

  • mkimage/testsuites.xml contains a list of test suites to include in the image.

  • mkimage/typedef.xml contains generic type definitions for the image (not visible from Ews).

  • mkimage/mkdrv.xml refers to drvlist.xml and mkdrv_action.xml.

  • mkimage/mkdrv_action.xml contains drivers actions.

  • mkimage/drivers.xml contains the list of drivers.

• basic and extended are the two configuration profiles.