Board support package

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Purplefishies (talk | contribs) at 14:18, 5 October 2015 (Changed awkward word selection as well as incorrect subject verb agreement). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In embedded systems, a board support package (BSP) is an implementation of specific support code (software) for a given (device motherboard) board that conforms to a given operating system. It is commonly built with a bootloader that contains the minimal device support to load the operating system and device drivers for all the devices on the board.

Some suppliers also provide a root file system, a toolchain for building programs to run on the embedded system (which would be part of the architecture support package), and utilities to configure the device (while running).

History

This term has been in use since 1981 when Hunter & Ready, the developers of VRTX, first used the term to describe the hardware-dependent software needed to run VRTX on a specific hardware platform. The phrase is commonly associated with Wind River Systems for its VxWorks embedded operating system because of its extensive device driver offerings, but since the 1980's it has been in wide use throughout the industry. For example, QNX Software Systems also distributes BSPs, as does Microsoft (for its Windows CE operating system), NVIDIA and many others. In fact, virtually all RTOS providers will use the term BSP to describe the hardware support software modules available for their RTOS.

Example

The Wind River board support package for the ARM Integrator 920T board contains, among other things, the following elements:

  • A config.h file, which defines constants such as ROM_SIZE and RAM_HIGH_ADRS.
  • A Makefile, which defines binary versions of VxWorks ROM images for programming into flash memory.
  • A bootrom file, which defines the boot line parameters for the board.
  • A target.ref file, which describes board-specific information such as switch and jumper settings, interrupt levels, and offset bias.
  • A VxWorks image.
  • Various C files, including:
flashMem.c — the device driver for the board's flash memory
pciIomapShow.c — mapping file for the PCI bus
primeCellSio.c — TTY driver
sysLib.c — system-dependent routines specific to this board
romInit.s — ROM initialization module for the board; contains entry code for images that start running from ROM

Additionally the BSP is supposed to perform the following operations

  • Initialize the processor
  • Initialize the bus
  • Initialize the interrupt controller
  • Initialize the clock
  • Initialize the RAM settings
  • Configure the segments
  • Load and run bootloader from flash