RAM 6.0 BUX II Series Guia do Utilizador descarregar pdf (Página 12)

VxWorks

BSP Developer’s Guide, 6.0

developer. However, a typical development process is more likely to take several

months.

Once the minimal kernel is running, additional drivers may be required for the

intended application. In most cases, these drivers can be added at a later date,

concurrent with application development.

For more information on developing and using drivers with your BSP, see the

VxWorks Device Driver Developer’s Guide.

1.4 Terminology

The following terminology is used in this document:

■

installDir—Within this document, file paths are typically expressed relative to

the top of an installation directory, which is referred to as installDir in all

documentation. All file and directory paths in this manual are relative to the

VxWorks installation directory. For installations based on VxWorks 5.x, this

corresponds to installDir. For installations based on VxWorks 6.0, this

corresponds to installDir/vxworks-6.0/.

■

bspname—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 called acmeBSP, change

any reference to bspname to acmeBSP. For example, bspname.h would become

acmeBSP.h.

■

dev—Where this document refers to devices that the BSP might support, these

devices are generically referred to as dev. In such cases, substitute the name of

each device or device type for dev. For example, if your BSP supports both ATA

and SCSI devices, change sysDev.c to the pair of files sysAta.c and sysScsi.c.

■

projName—Each project must be given a name. When the project is created,

several files are created based on the name given to the newly created project.

These files are referred to as projName.

1 2 ... 7 8 9 10 11 12 13 14 15 16 17 ... 188 189

Sem comentários

RAM 6.0 BUX II Series Guia do Utilizador Página 12