Imported Objects

The following objects are predefined and can be used within the board-specific configuration files. They can be used to specify conditions that enable different configurations to be set up for different situations, for example you can set up two different configurations for the two deployment schemes, that would depend on the object BOOT_MODE:

• SYSTEM specifies the kind of ChorusOS operating system currently built and is an enumeration. The possible values of SYSTEM are:

  • kernonly: the system image will contain the microkernel, built-in drivers and possibly built-in application actors

  • chorus: the system image will contain the microkernel, built-in drivers, the POSIX personality and possibly built-in application actors

  • uartTest or flashTest: the system image will contain the corresponding device driver (UART or flash memory) test program

  • kts or ktu: the system image will contain the general purpose microkernel test suite to be run in the supervisor (kts) or the user (ktu) mode

  • benchs or benchu: the system image will contain the microkernel benchmark program to be run in the supervisor (benchs) or the user (benchu) mode

• BOOT_MODE specifies how the generated system image will be deployed on the target board, and is an enumeration. The possible values for BOOT_MODE are:

  • ROM: the system image will be deployed (burned, flashed) in ROM or Flash

  • RAM: the system image will be downloaded in RAM from a local device or the network

• BUILD_DIR is a string specifying the build directory prepared by the configure utility during the ChorusOS operating system installation.

• BSP_DIR is a string specifying the installation directory of the BSP configuration and bootstrap package.

• DRV_DIR is a string specifying the installation directory of the family-specific and generic drivers package.