BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
In addition to the steps described in B.2.1 Migration Changes Common to All
Architectures, p.214, the following XScale/StrongARM-specific changes are
required to migrate your custom BSP to Tornado 2.2/VxWorks 5.5:
■
For assembly files only: the new macros GTEXT, GDATA, FUNC, and
FUNC_LABEL have been added to assist in porting assembly files. The leading
underscores in global assembly label names should be removed. Using these
macros allows source compatibility between Tornado 2.1.x and Tornado 2.2.
■
Diab support. Due to differences in assembler syntax between the GNU and
Diab toolchains, you need to change any GNU assembly macros to Diab
syntax. For more information on Diab assembly syntax, see the Diab C/C++
Compiler for ARM User’s Guide.
For more information on using VxWorks with XScale/StrongARM targets, see the
VxWorks for Intel XScale/StrongARM Architecture Supplement.
B.2.9 SuperH
In addition to the steps described in B.2.1 Migration Changes Common to All
Architectures, p.214, the following SuperH-specific changes are required to migrate
your custom BSP to Tornado 2.2/VxWorks 5.5:
■
■
■
Power management setup. This step is required for BSPs where processor
power management is enabled. In the sysHwInit( ) routine in sysLib.c.
initialize the vxPowerModeRegs structure depending on the SuperH
processor used.
Diab support. This step is only required if the BSP will be built with the Diab
toolchain. Assembler files should be updated to use the .short directive instead
of the .word directive.
Use of NULL. In previous releases, NULL was defined as integer zero. This
definition has been changed to match the C standard to a void pointer. To
avoid compiler warnings, make sure NULL is only used for pointer
assignments.
For more information on using VxWorks with SuperH targets, see the VxWorks for
Hitachi SuperH Architecture Supplement.
220