RAM 6.0 BUX II Series Guía de usuario descargar pdf (Pagina 31)

2 Overview of a BSP

2.3 Components of a BSP

vtsLogs

Starting with VxWorks 6.0, Wind River recommends, but does not require, that

VxWorks validation test suite (VTS) test logs for the most recent BSP revision be

shipped with the BSP. The VTS test log files are kept in the BSP directory in a

vtsLogs subdirectory. In addition to the automatic log files, it is also appropriate to

keep the console output from any test runs and any supporting, BSP-specific test

information (for example, .T1 files).

The console output is also kept in the vtsLogs directory, in a file named

vtsConsole.txt. A README file listing what tests were run on what dates, and

identifying the responsible test engineer, is also encouraged.

For more information on the VTS, see the VxWorks Hardware Interface Validation

Guide.

Makefile

This file controls the build of the VxWorks image. You must set several variables

within this makefile. The required variables are listed and described in the

2.3.5 Required Macros, p.39.

config.h

This header file contains all #include and #define macros specific to configuring

the CPU and board architectures. It also contains any necessary overrides to the

macro definitions in configAll.h, which you must include using #include. You

must also include the bspname.h header in this file.

bspname.h

This header file contains all the header information for the BSP that is not related

to OS configuration. The information in this header file is required under all

configurations of VxWorks using this BSP. This file includes any headers for device

drivers.

Use bspname.h to set all non-optional, board-specific information, as defined in this

file; including definitions for the serial interface, timer, and I/O devices.

1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 188 189

Sin comentarios

RAM 6.0 BUX II Series Guía de usuario Pagina 31