Freescale Semiconductor SEC2SWUG Conditional Compilation, Debug Messaging, Distribution Archive

Page 43

Porting

8.4 Conditional Compilation

See the makefile for specifics on the default build of the driver

8.5 Debug Messaging

The driver includes a DBG define that allows for debug message output to the developer's console. If defined in the driver build, debug messages will be sent from various components in the driver to the console.

Messages come from various sections of the driver, and a bitmask is kept in a driver global variable so that the developer can turn message sources on or off as required. This global is named SEC2DebugLevel, and contains an ORed combination of any of the following bits:

DBGTXT_SETRQ

Messages from request setup operations (new requests inbound from the application).

DBGTXT_SVCRQ

Messages from servicing device responses (ISR/deferred service routine handlers)

 

outbound to the application.

DBGTXT_INITDEV

Messages from the device/driver initialization process.

DBGTXT_DPDSHOW

Shows the content of a constructed DPD before it is handed to the security core.

DBGTXT_INFO

Shows a short banner at device initialization describing the driver and hardware version.

In normal driver operation (not in a development setting), the DBG definition should be left undefined for best performance.

8.6 Distribution Archive

For this release, the distribution archive consists of the source files listed in this section. Note that the user may wish to reorganize header file locations consistent with the file location conventions appropriate for their system configuration.

Header

 

Description

 

Sec2.h

 

Primary public header file for all users of the driver

 

Sec2Driver.h

Driver/Hardware interfaces, private to the driver itself

 

Sec2Descriptors.h

DPD type definitions

 

Sec2Notify.h

Structures for ISR/main thread communication

 

sec2_dpd_Table.h

DPD construction constants

 

sec2_cha.c

CHA mapping and management

 

sec2_dpd.c

DPD construction functionality

 

sec2_init.c

Device/driver initialization code

 

sec2_io.c

 

Basic register I/O primitives

 

sec2_ioctl.c

Operating system interfaces

 

sec2_request.c

Request/response management

 

sec2_sctrMap.c

Scatter buffer identification and mapping

 

sec2isr.c

 

Interrupt service routine

 

 

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

 

 

 

 

Freescale Semiconductor

PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE

43

Page 42 Page 44
Image 43
Page 42 Page 44
Contents Freescale Semiconductor OverviewSEC 2.0 Reference Device Driver User’s Guide, Rev Acronyms and AbbreviationsOverview Term MeaningEnd-User Application Device Driver ComponentsDevice Driver Structure Device Driver ComponentsProcess Request Routine Interrupt Service RoutineDriver Initialization Routine Request Dispatch RoutineUser Interface Deferred Service RoutineUser Interface Application Interface= Dpdaesacbcencryptcrypt Error HandlingSecond and Third Arguments in the ioctl Function Global Definitions1 I/O Control Codes Channel DefinitionsChannel Defines Callback Error Status Return CodeOperation ID opId Masks Return CodesSEC2TEAERROR SEC2ADDRESSPROBLEMSEC2CHAERROR SEC2PARITYSYSTEMERRORDefine Description SEC2CANCELLEDREQUESTMiscellaneous Request Structures SEC2INVALIDADDRESSStatusreq Process Request StructuresScatter-Gather Buffer Management NotifyonerrorDirect Scatter-Gather Usage Example Rngreq Individual Request Type DescriptionsRandom Number Requests DES RequestsDescbccryptreq Valid Descriptors opId ARC4 RequestsDescryptreq 1 ARC4LOADCTXCRYPTREQARC4LOADCTXCRYPTREQ Valid Descriptor opId 2 ARC4LOADKEYCRYPTUNLOADCTXREQARC4LOADKEYCRYPTUNLOADCTXREQ Valid Descriptor opId Hashreq Hash RequestsHashreq Valid Descriptors 0x4400 opId Hmacpadreq Hmac RequestsHashreq Valid Descriptors 0x4500 opId Aesacryptreq AES RequestsHmacpadreq Valid Descriptors opId Modexpreq Valid Descriptor opId Integer Public Key RequestsModexpreq Aesacryptreq Valid Descriptors opIdDpdmmssrsaexp ModssexpreqMODR2MODNREQ Modssexpreq Valid Descriptor opId0x5300 Modrrmodpreq5 MOD2OPREQ Modrrmodpreq Valid Descriptor opIdMOD2OPREQ Valid Descriptors opId Value Function Description Eccpointreq ECC Public Key RequestsMOD2OPREQ Valid Descriptors opId Eccpointreq Valid Descriptors opId 2 ECC2OPREQDpdecspkbuildulctx EccspkbuildreqECC2OPREQ Valid Descriptors opId Eccspkbuildreq Valid Descriptor opIdEccptadddblreq Valid Descriptor opId IPSec RequestsEccptadddblreq IpseccbcreqIpseccbcreq Valid Descriptors opId Descriptors Ipsececbreq Valid Descriptors opId IpsececbreqIpsecaescbcreq Valid Descriptors opId IpsecaescbcreqIpsecaesecbreq Ipsecaesecbreq Valid Descriptors opId IpsecespreqIpsecespreq Valid Descriptors opId DPDIPSECESPINTDESCBCDCRPTMD5PAD DpdipsecespinsdescbcdcrptshapadDPDIPSECESPOUTTDESCBCCRPTMD5PAD DpdipsecespouttdescbccrptshapadSrtpreq 10 802.11 Protocol RequestsSrtp Protocol Requests CcmpreqDES Sample Sample CodeSrtpreq Valid Descriptors opId Ipsec Sample PRELIMINARY-SUBJECT to Change Without Notice Linux Environment InstallationOperation VxWorks Environment Driver Operation in User ModeVxWorks Environment Driver Module License MacroVxWorks Interface Module Variables PortingBuilding the Interface Modules BSP IntegrationHeader Files Interrupt Service RoutineSource Files Debug Messaging Conditional CompilationDistribution Archive 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