BSP Developer's Guide

B
Upgrading a BSP for Tornado 2.2
■
The preferred replacements for this routine are vxImmrIsbGet( ) and
vxImmrDevGet( ), which are implemented in vxALib.s and should not be
overridden by the BSP. Standard Wind River drivers use the new interface.
Some early MPC74xx/AltiVec support included a routine, typically
vmxExcLoad( ), to initialize the AltiVec exception vectors. For example:
{
bcopy ((char*)(LOCAL_MEM_LOCAL_ADRS + 0x0100),
(char*)(LOCAL_MEM_LOCAL_ADRS + _EXC_VMX_UNAVAIL),
SIZEOF_EXCEPTION);
bcopy ((char*)(LOCAL_MEM_LOCAL_ADRS + 0x0100),
(char*)(LOCAL_MEM_LOCAL_ADRS + _EXC_VMX_ASSIST),
SIZEOF_EXCEPTION);
}
Such code must be removed. AltiVec exception vectors are initialized by
altivecInit( ).
The following change is optional for PowerPC BSPs:
■
Assembly files can be converted to use the Wind River standard macros
defined in installDir/target/h/arch/ppc/toolsPpc.h:
B
FUNC_EXPORT
FUNC_IMPORT
_WRS_TEXT_SEG_START
FUNC_BEGIN
FUNC_LABEL
FUNC_END
Converting assembly files in this way is not generally required. However,
conversion (especially to _WRS_TEXT_SEG_START) occasionally fixes a silent
bug.
For more information on using VxWorks with PowerPC targets, see the VxWorks
for PowerPC Architecture Supplement.
B.2.8 XScale/StrongARM
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 StrongARM/XScale Release Notes and Architecture
Supplement manual available on WindSurf.
219