Wind River Glossary
Wind River Technical Glossary
Special | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | ALL
board support package (BSP)
A Board Support Package (BSP) consists primarily of the hardware-specific code for a particular target board. A BSP includes facilities for hardware initialization, interrupt handling and generation, hardware clock and timer management, mapping of local and bus memory space, and so on.
A branch node (or intermediate node) is a command node that exists hierarchically (on the command tree) between other nodes. A branch node is subordinate to another node (perhaps only the root node) and has nodes subordinate to it.
A network packet or frame is broadcast if it is addressed not to a particular address but to all machines on a subnet or network segment.
The browse path defines the path used to reach the DXConnection when browsing the DX Database. Branches within the browse path represent logical groupings of DXConnections. Clients are allowed to define more than one browse path for each DXConnection, thus enabling DXConnections to belong to more than one logical grouping.
Board Support Package
In several places within this document, there are references to file names that are based on the BSP. These filenames have the string bspname substituted. For example, if you are working on a BSP calledacmeBSP, change any reference bspname to acmeBSP. For example, bspname .h would become acmeBSP.h.
The type of project built: managed build by default (formerly flexible build); and also a deprecated but still available standard managed build (sometimes known as a standard build). There are also user-defined and disabled builds
A build flag variable is defined in the makefile and used to set various compiler options.
A build macro is a build flag