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

2 Overview of a BSP

2.4 The Development Environment

linked with the boot ROM image. For more information, see the memory controller

section of the VxWorks Device Driver Developer’s Guide.

2.4 The Development Environment

The development environment consists of a mechanism to build an object module,

a method to download the image to the target, and a mechanism for testing the

downloaded code. It includes several items: a hardware debugger (if you use one),

the IDE installation, a compiler and other development tools, and a means of

downloading VxWorks images for debugging.

When porting a BSP, it is usually best to start with a debugging method that

includes some simple test code rather than a full-blown VxWorks image. For

example, if your board has LEDs, the first code you write may be the code to turn

the LEDs on and off. By starting with this simple kind of code, you can verify the

development environment in addition to creating a routine that is useful later in

the BSP development process.

The development environment also includes compilers, linkers, and OS library

files. The BSP provides board-specific functionality, and the BSP routines often

depend on OS routines that are not normally provided by Wind River in source

form. Object modules for these routines are provided in a library file in the

VxWorks installation. The old VxWorks library naming convention was that

libraries were named libCPUTOOLvx.a, where CPU is the CPU architecture of

your board, and TOOL is the toolchain you are using to build your BSP. An

example of an older library is libPPC860gnuvx.a.

Starting with VxWorks 5.5, the library files are split up into several different files.

The libCPUTOOLvx.a files are still present as of VxWorks 5.5, but they are stubs

only. The new files are kept in subdirectories under the target/lib directory, named

target/lib/ARCH/CPU/TOOL and target/lib/ARCH/CPU/common, where CPU and

TOOL are as described above, and ARCH is the abbreviation for the processor

architecture family. For example, PowerPC libraries for use with the Diab C/C++

Compiler toolchain with the 860 processor are in target/lib/ppc/PPC860/diab and

target/lib/ppc/PPC860/common. Several library files are kept in these two

NOTE: A hardware debugger, such as an on-chip debugging (OCD) system, is a

good investment and is generally considered a requirement for efficient BSP

development.

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

Keine Kommentare

RAM 6.0 BUX II Series Betriebsanweisung Seite 51