A.3   Interface Variations

This section describes particular routines and tools that are specific to 68K targets in any of the following ways:

For complete documentation, see the reference entries for the libraries, subroutines, and tools discussed below.

CPU-Specific Interfaces

Because of specific characteristics of the MC68040 or MC68060, certain VxWorks features are not useful on these targets. Conversely, other VxWorks features are particular to one or both of these processors, to exploit specific characteristics.

Note that discussion of the MC68040 also applies to the MC68LC040 unless otherwise noted. The MC68LC040 is a derivative of the MC68040 and differs only in that it has no floating-point unit.

Table A-1 lists such CPU-specific VxWorks interfaces. Section A.4 Architecture Considerations discusses these interfaces in the context of CPU architecture. For more complete documentation on these routines, see the associated reference entries.

Table A-1:  VxWorks Interface Variations for MC68040/MC68060  


Routine or Macro Name
CPU
Change
Detailed Discussion

checkStack( )  
060
Interrupt stack display meaningless 
vxSSEnable( )
vxSSDisable( )  
060
Only for this architecture 
cacheLock( )
cacheUnlock( )  
040
Always return ERROR 
cacheStoreBufEnable( )
cacheStoreBufDisable( )  
060
Only for this architecture 
USER_B_CACHE_ENABLE  
060
Architecture-specific configuration 
BRANCH_CACHE  
060
Architecture-specific cache 
VM_STATE  
both
Architecture-specific MMU states 

a.out-Specific Tools

The following tools are specific to the a.out format. For more information, see the reference entries for each tool.

hex
converts an a.out-format object file into Motorola hex records. The syntax is:

hex [-a adrs] [-l] [-v] [-p PC] [-s SP] file 
aoutToBin
extracts text and data segments from an a.out file and writes it to standard output as a simple binary image. The syntax is:

aoutToBin < inFile > outfile 
xsym
extracts the symbol table from an a.out file. The syntax is:

xsym < objMod > symTbl