Overview

You cannot use the graphical configuration tools, ews, to define the system image configuration for a new target board. Instead, create the configuration files using a text editor. Once the files have been created, you can view them using ews, and build the system image. You can also use the mkimage tool to build the system image.

The board-specific configurations must be stored in the directory src/nucleus/bsp/family/board. For example, the board-specific configuration files for the SBC8260 board are stored in src/nucleus/bsp/powerpc/sbc8260, and those for the PC/AT are stored in src/nucleus/bsp/x86/i386at.

There are two configuration files:

• target.xml specifies the main board-specific configuration.

• target_action.xml specifies the board-specific system image reshaping procedure.

Most of the examples in this chapter use the SBC8260 board. To understand the examples, the following information about the SBC8260 board is useful:

• CPU: EC603e

• Physical memory map: The powerup initialization code programs the chipset memory map decoder registers in such a way that in the processor's physical address space all available RAM is contiguously mapped to (physical) address 0x0, and at least 1M of NOR flash memory is contiguously mapped to the end of the physical address space (that is, to the physical address 0xfff00000).

• Deployment: The ChorusOS configuration supports two deployment schemes:

  • Boot from ROM

    Write the ChorusOS operating image to flash memory and then boot the ChorusOS operating system from flash memory, by resetting the board.

  • Boot from RAM

    Write the ChorusOS Boot Monitor to flash memory and then download the ChorusOS operating system image from the network to RAM.