Freescale Semiconductor SEC2SWUG Porting, Building the Interface Modules, BSP Integration

Page 41

Porting

Driver: $(WIND_BASE)/target/src/drv/crypto

Tests: $(WIND_BASE)/target/src/drv/crypto/test

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:

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

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.3BSP 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.

SEC 2.0 Reference Device Driver User’s Guide, Rev. 0

Freescale Semiconductor

PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE

41

Page 40 Page 42
Image 41
Page 40 Page 42
Contents Freescale Semiconductor OverviewOverview Acronyms and AbbreviationsTerm Meaning SEC 2.0 Reference Device Driver User’s Guide, RevDevice Driver Structure Device Driver ComponentsDevice Driver Components End-User ApplicationDriver Initialization Routine Interrupt Service RoutineRequest Dispatch Routine Process Request RoutineUser Interface Deferred Service RoutineApplication Interface User Interface= Dpdaesacbcencryptcrypt Error Handling1 I/O Control Codes Global DefinitionsChannel Definitions Second and Third Arguments in the ioctl FunctionOperation ID opId Masks Callback Error Status Return CodeReturn Codes Channel DefinesSEC2CHAERROR SEC2ADDRESSPROBLEMSEC2PARITYSYSTEMERROR SEC2TEAERRORMiscellaneous Request Structures SEC2CANCELLEDREQUESTSEC2INVALIDADDRESS Define DescriptionStatusreq Process Request StructuresScatter-Gather Buffer Management NotifyonerrorDirect Scatter-Gather Usage Example Random Number Requests Individual Request Type DescriptionsDES Requests RngreqDescryptreq ARC4 Requests1 ARC4LOADCTXCRYPTREQ Descbccryptreq Valid Descriptors opIdARC4LOADKEYCRYPTUNLOADCTXREQ Valid Descriptor opId 2 ARC4LOADKEYCRYPTUNLOADCTXREQARC4LOADCTXCRYPTREQ Valid Descriptor opId Hashreq Valid Descriptors 0x4400 opId Hash RequestsHashreq Hashreq Valid Descriptors 0x4500 opId Hmac RequestsHmacpadreq Hmacpadreq Valid Descriptors opId AES RequestsAesacryptreq Modexpreq Integer Public Key RequestsAesacryptreq Valid Descriptors opId Modexpreq Valid Descriptor opIdMODR2MODNREQ ModssexpreqModssexpreq Valid Descriptor opId Dpdmmssrsaexp5 MOD2OPREQ ModrrmodpreqModrrmodpreq Valid Descriptor opId 0x5300MOD2OPREQ Valid Descriptors opId Value Function Description MOD2OPREQ Valid Descriptors opId ECC Public Key RequestsEccpointreq Eccpointreq Valid Descriptors opId 2 ECC2OPREQECC2OPREQ Valid Descriptors opId EccspkbuildreqEccspkbuildreq Valid Descriptor opId DpdecspkbuildulctxEccptadddblreq IPSec RequestsIpseccbcreq Eccptadddblreq Valid Descriptor opIdIpseccbcreq Valid Descriptors opId Descriptors Ipsececbreq Valid Descriptors opId IpsececbreqIpsecaescbcreq Valid Descriptors opId IpsecaescbcreqIpsecaesecbreq Ipsecaesecbreq Valid Descriptors opId IpsecespreqIpsecespreq Valid Descriptors opId DPDIPSECESPOUTTDESCBCCRPTMD5PAD DpdipsecespinsdescbcdcrptshapadDpdipsecespouttdescbccrptshapad DPDIPSECESPINTDESCBCDCRPTMD5PADSrtp Protocol Requests 10 802.11 Protocol RequestsCcmpreq SrtpreqSrtpreq Valid Descriptors opId Sample CodeDES Sample Ipsec Sample PRELIMINARY-SUBJECT to Change Without Notice Operation InstallationLinux Environment VxWorks Environment Driver Operation in User ModeDriver Module License Macro VxWorks EnvironmentBuilding the Interface Modules PortingBSP Integration VxWorks Interface Module VariablesSource Files Interrupt Service RoutineHeader Files Distribution Archive Conditional CompilationDebug Messaging How to Reach Us

SEC2SWUG specifications

Freescale Semiconductor, a prominent player in the semiconductor industry, has made significant strides in developing robust solutions tailored for the automotive and industrial sectors. One such innovation is the SEC2SWUG (Security Configuration to Software User Guide), a comprehensive framework designed to enhance security protocols across various applications.

The SEC2SWUG is particularly vital in an era where cybersecurity threats are increasingly sophisticated. This tool is built to help developers implement security measures seamlessly during the software design phase, ensuring products are resilient against potential vulnerabilities. One of the main features of the SEC2SWUG is its versatility; it can be applied across a wide range of microcontrollers and processors offered by Freescale. This is particularly advantageous for engineers who require a consistent security approach across different platforms.

In terms of technology, the SEC2SWUG incorporates advanced cryptographic algorithms, allowing for data encryption, decryption, and authentication processes. This ensures that sensitive information remains secure, particularly in automotive applications where vehicle-to-everything (V2X) communication is becoming paramount. Moreover, the guide details the implementation of secure boot processes, which verify the integrity of firmware before it executes, bolstering overall system security.

Another key characteristic of SEC2SWUG is its user-friendliness. Freescale has focused on creating a resource that not only provides theoretical knowledge but also practical guidelines, making it easier for developers to integrate security protocols into their projects. The guide features clear annotations, example code snippets, and troubleshooting tips, which enhance the developer experience and facilitate a smoother transition from concept to execution.

Additionally, SEC2SWUG is designed to be scalable. As industries evolve, the demand for security measures will only grow, and this framework ensures that developers can adapt their solutions accordingly. Whether working on embedded systems, IoT applications, or complex automotive networks, the SEC2SWUG offers a robust security foundation.

In conclusion, Freescale Semiconductor's SEC2SWUG is a vital tool for engineers and developers looking to embed security into their applications. With its focus on advanced technologies and user-centric design, the SEC2SWUG stands at the forefront of secure software development, addressing the critical need for safety in interconnected systems.
Top Page Image Contents