User guide

74 MPC184/MPC185 Security Co-Processor Software User’s Guide MOTOROLA

PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE

VxWorks Environment VxWorks Environment

7.4 BSP Integration

Once the modules are built, they should be linked directly with the user’s board support package, to become

integral part of the board image.

In VxWorks, the file sysLib.c contains the initialization functions, the memory/address space functions, and

the bus interrupt functions. It is recommended to call the function MPC18xDriverInit directly from

sysLib.c.

The security processor will be initialized at board start-up, with all the other devices present on the board.

The same technique can be used in other operating systems.

7.5 Distribution Archive

For this release, the distribution archive consists of the source files listed in this section. Note that the file

paths are relative to installDir/target/.

h/drv/crypto/dpd_Table.h —Data packet descriptor table

h/drv/crypto/MPC18x.h —User request defines and structures

h/drv/crypto/MPC18x_Descriptors.h

h/drv/crypto/MPC18xDriver.h

h/drv/crypto/MPC18xNotify.h

src/drv/crypto/Makefile

src/drv/crypto/cha.c

src/drv/crypto/dpd.c

src/drv/crypto/init.c

src/drv/crypto/io.c

src/drv/crypto/ioctl.c

src/drv/crypto/isr.c —interrupt service routine

src/drv/crypto/request.c