Freescale Semiconductor SEC2SWUG specifications Process Request Structures, Statusreq

Page 11

User Interface

STATUS_REQ

driverstatus; // Detailed information as to the state of the

//hardware and the driver at the time of an error

3.3.6Process Request Structures

All process request structures contain the a copy of the same request header information, which is defined by the COMMON_REQ_PREAMBLE macro. The members of this header must be filled in as needed by the user prior to the issue of the user's request.

unsigned long

 

opId;

unsigned char

 

scatterBufs;

unsigned char

 

notifyFlags;

unsigned char

 

reserved;

unsigned char

 

channel;

PSEC2_NOTIFY_ROUTINE

 

notify;

PSEC2_NOTIFY_CTX

 

pNotifyCtx;

PSEC2_NOTIFY_ON_ERROR_ROUTINE

notify_on_error;

SEC2_NOTIFY_ON_ERROR_CTX

ctxNotifyOnErr;

int

 

status;

void

 

*nextReq;

opId

operation Id which identifies what type of request this is. It is normally associated with

 

a specific type of cryptographic operation, see Section 4, “Individual Request Type

 

Descriptions” for all supported request types.

scatterBufs

A bitmask that specifies which of the argued buffers are mapped through a

 

scatter-gather list. The mask is filled out via the driver's helper function

 

MarkScatterBuffer(), described in Section 3.3.7, “Scatter-Gather Buffer

 

Management.”

notifyFlags

If a POSIX-style signal handler will be responsible for request completion notification,

 

then it can contain ORed bits of NOTIFY_IS_PID and/or

 

NOTIFY_ERROR_IS_PID, signifying that the notify or notify_on_error

 

pointers are instead the process ID's (i.e. getpid()) of the task requesting a signal

 

upon request completion.

channel

identifies the channel to be used for the request. It exists for legacy compatibility

 

reasons, and is no longer useful for SEC2.

notify

pointer to a notification callback routine that will be called when the request has

 

completed successfully. May instead be a process ID if a user-state signal handler will

 

flag completion. Refer back to notifyFlags for more info.

pNotifyCtx

pointer to context area to be passed back through the notification routine.

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

Freescale Semiconductor

PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE

11

Page 10 Page 12
Image 11
Page 10 Page 12
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 ARC4LOADCTXCRYPTREQARC4LOADKEYCRYPTUNLOADCTXREQ 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 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 MOD2OPREQ Valid Descriptors opId ECC Public Key RequestsEccpointreq 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 CcmpreqSrtpreq Valid Descriptors opId Sample CodeDES Sample Ipsec Sample PRELIMINARY-SUBJECT to Change Without Notice Operation InstallationLinux Environment VxWorks Environment Driver Operation in User ModeVxWorks Environment Driver Module License MacroVxWorks Interface Module Variables PortingBuilding the Interface Modules BSP IntegrationSource 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