RAM 6.0 BUX II Series Betriebsanweisung PDF herunterladen (Seite 52)

VxWorks

BSP Developer’s Guide, 6.0

directories; each library file contains object modules for individual components. In

VxWorks 6.0, processor variants have been eliminated. For example, all PowerPC

processors are now indicated using PPC32. For more information, see the

appropriate VxWorks Architecture Supplement.

2.4.1 BSP Debugging Methods

Part of setting up your development environment is choosing a BSP debugging

method. This section provides an overview of the hardware debugging options

available to a BSP developer. For more detailed information, see 4. Debugging Your

BSP.

Primitive Tools

For most of the early work of porting a BSP, the system is not initialized enough to

use a host-based debugger, a target-based debugger, logMsg( ), or printf( ) to

obtain debugging information. Therefore, some method of low-level debugging

must be selected.

A BSP developer can begin porting a BSP with no more debugging information

than what is provided by an LED that can be turned on or off under software

control. Later in the development process, a polled-mode serial output routine,

possibly called kprintf( ), can be created to print complex diagnostic information

to the serial console.

Another debugging method consists of writing information to non-volatile RAM

(NVRAM). This information can be displayed using another computer at a later

time and can be used to obtain information about the state of the target processor.

Both of the above methods are considered primitive. Other methods are generally

available to make the port easier and faster.

1 2 ... 47 48 49 50 51 52 53 54 55 56 57 ... 188 189

Keine Kommentare

RAM 6.0 BUX II Series Betriebsanweisung Seite 52