BSP Developer's Guide

B
Upgrading a BSP for Tornado 2.2
■
■
Makefile update. This step is required for all users. Use the bspCnvtT2_2 script
to update the BSP makefile. This script comments out unnecessary include
lines and any existing HEX_FLAGS value.
TFFS support. This step is required for BSPs with TFFS support. Remove the
inclusion of sysTffs.c from the syslib.c file.
B.2.2 68K/CPU32
All Wind River-supplied BSPs for the 68K/CPU32 architecture released with the
Tornado 2.2 product have been upgraded for use with VxWorks 5.5. Custom
VxWorks 5.4-based BSPs require only the modifications described in
B.2.1 Migration Changes Common to All Architectures, p.214 to upgrade to VxWorks
5.5. No architecture-specific modifications are required.
For more information on using VxWorks with 68K/CPU32 targets, see the
VxWorks for 68K/CPU32 Architecture Supplement.
B
B.2.3 ARM
NOTE: This section describes BSP migration from Tornado 2.1\VxWorks 5.4 to
Tornado 2.2\VxWorks 5.5. For information on migrating a BSP from Tornado 2.0.x
to Tornado 2.1, see the Tornado for ARM Release Notes and Architecture Supplement
manual available on WindSurf.
In addition to the steps described in B.2.1 Migration Changes Common to All
Architectures, p.214, the following ARM-specific migration changes are required:
■
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 ARM targets, see the VxWorks for
ARM Architecture Supplement.
215