Freescale-semiconductor SEC2SWUG Manual do Utilizador Página 41
- Página / 44
- Índice
- MARCADORES
Avaliado. / 5. Com base em avaliações de clientes
SEC 2.0 Reference Device Driver User’s Guide, Rev. 0
Freescale Semiconductor PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE 41
Porting
Once the modules are installed, the driver image may be built per the following instructions.
7.2 Building the Interface Modules
Throughout the remainder of the installation instructions, the variables provided below are used:
The following steps are used to build drivers and/or the driver test and exercise code:
1. Go to the command prompt or shell
2. Execute
torVars to set up the Tornado command line build environment.
3. Run make in the driver or test installation directory by use of the following command:
make CPU=cpuFamily TOOL=toolChain SP=securityProcessor
example: make CPU=PPC85XX TOOL=gnu SP=SEC2)
7.3 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 SEC2DriverInit directly from sysLib.c.
In the process of initialization, the driver calls a specialized function name
sysGetPeripheralBase(), which
returns a pointer to the base location of the peripheral device block in the processor (often defined by the CCSBAR
register in some PowerQUICC III processors). The driver uses this address and an offset to locate the SEC2 core on
the system bus. This is not a standard BSP function, the integrator will need to provide it, or a substitute method for
locating CCSBAR.
The security processor will be initialized at board start-up, with all the other devices present on the board.
8 Porting
This section describes probable areas of developer concern with respect to porting the driver to other operating
systems or environments.
At this time, this driver has been ported to function on both VxWorks and Linux operating systems. Most of the
internal functionality is independent of the constructs of a specific operating system, but there necessarily are
interface boundaries between them where things must be addressed.
Driver: $(WIND_BASE)/target/src/drv/crypto
Tes ts:
$(WIND_BASE)/target/src/drv/crypto/test
Table 31. VxWorks Interface Module Variables
Variable Definition
CpuFamily Specifies the target CPU family, such as PPC85XX
ToolChain Specifies the tools, such as
gnu
SecurityProcessor Specifies the target security processor, should be
SEC2 for this driver
- User’s Guide 1
- 2 Device Driver Components 3
- 2.1.3 Process Request Routine 4
- 3 User Interface 5
- 3.2 Error Handling 6
- 3.3 Global Definitions 7
- 3.3.4 Return Codes 8
- 3.3.5.1 STATUS_REQ Structure 10
- 4.1 Random Number Requests 14
- 4.2 DES Requests 14
- 4.3 ARC4 Requests 15
- 4.4 Hash Requests 17
- 4.5 HMAC Requests 18
- 4.6 AES Requests 19
- 4.7.1 MOD_EXP_REQ 20
- 4.7.2 MOD_SS_EXP_REQ 21
- 4.7.3 MOD_R2MODN_REQ 21
- 4.7.4 MOD_RRMODP_REQ 22
- 4.7.5 MOD_2OP_REQ 22
- 4.8 ECC Public Key Requests 24
- 4.8.2 ECC_2OP_REQ 25
- 4.8.3 ECC_SPKBUILD_REQ 26
- 4.9 IPSec Requests 27
- 4.9.2 IPSEC_ECB_REQ 29
- 4.9.3 IPSEC_AES_CBC_REQ 30
- 4.9.4 IPSEC_AES_ECB_REQ 31
- 4.9.5 IPSEC_ESP_REQ 32
- 4.10 802.11 Protocol Requests 35
- 4.11 SRTP Protocol Requests 35
- 5 Sample Code 36
- 5.2 IPSEC Sample 37
- 6Linux Environment 39
- 7 VxWorks Environment 40
- 8 Porting 41
- 8.1 Header Files 42
- 8.2 C Source Files 42
- 8.3 Interrupt Service Routine 42
- 8.4 Conditional Compilation 43
- 8.5 Debug Messaging 43
- 8.6 Distribution Archive 43
- How to Reach Us: 44
Manuais e produtos relacionados com Hardware Freescale-semiconductor SEC2SWUG
(166 páginas)Panasonic HMTA1GC manuels
Manuels d'utilisation et guides de l'utilisateur pour Caméscopes Panasonic HMTA1GC.
Nous fournissons des manuels en pdf 1 Panasonic HMTA1GC à télécharger gratuitement par type de document : Instructions d'exploitation
Comentários a estes Manuais