Freescale Semiconductor SEC2SWUG Header Files, Source Files, Interrupt Service Routine

Page 42

Porting

Only a few of the files in the driver's source distribution contain specific dependencies on operating system components; this is intentional. Those specific files are:

•Sec2Driver.h

•sec2_init.c

•sec2_io.c

8.1 Header Files

Sec2Driver.h

This header file is meant to be local (private) to the driver itself, and as such, is responsible for including all needed operating system header files, and casts a series of macros for specific system calls

Of particular interest, this header casts local equivalents macros for:

malloc

Allocate a block of system memory with the operating system's heap allocation mechanism.

free

Return a block of memory to the system heap

semGive

Release a mutex semaphore

semTake

Capture and hold a mutex semaphore

__vpa

Translate a logical address to a physical address for hardware DMA (if both are equivalent, does nothing).

8.2 C Source Files

sec2_init.c performs the basic initialization of the device and the driver. It is responsible for finding the base address of the hardware and saving it in IOBaseAddress for later reference.

For Linux, this file also contains references to register/unregister the driver as a kernel module, and to manage it's usage/link count.

sec2_io.c contains functions to establish:

•Channel interlock semaphores (IOInitSemaphores)

•The ISR message queue (IOInitQs)

•Driver service function registration with the operating system (IORegisterDriver)

•ISR connection/disconnection (IOConnectInterrupt)

8.3 Interrupt Service Routine

The ISR will queue processing completion result messages onto the IsrMsgQId queue. ProcessingComplete() pends on this message queue. When a message is received, the completion task will execute the appropriate callback routine based on the result of the processing. When the end-user application prepares the request to be executed, callback functions can be defined for nominal processing as well as error case processing. If the callback function was set to NULL when the request was prepared then no callback function will be executed. These routines will be executed as part of the device driver so any constraints placed on the device driver will also be placed on the callback routines.

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

42

PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE

Freescale Semiconductor

Page 41 Page 43
Image 42
Page 41 Page 43
Contents Overview Freescale SemiconductorTerm Meaning Acronyms and AbbreviationsOverview SEC 2.0 Reference Device Driver User’s Guide, RevDevice Driver Components Device Driver ComponentsDevice Driver Structure End-User ApplicationRequest Dispatch Routine Interrupt Service RoutineDriver Initialization Routine Process Request RoutineApplication Interface Deferred Service RoutineUser Interface User InterfaceError Handling = DpdaesacbcencryptcryptChannel Definitions Global Definitions1 I/O Control Codes Second and Third Arguments in the ioctl FunctionReturn Codes Callback Error Status Return CodeOperation ID opId Masks Channel DefinesSEC2PARITYSYSTEMERROR SEC2ADDRESSPROBLEMSEC2CHAERROR SEC2TEAERRORSEC2INVALIDADDRESS SEC2CANCELLEDREQUESTMiscellaneous Request Structures Define DescriptionProcess Request Structures StatusreqNotifyonerror Scatter-Gather Buffer ManagementDirect Scatter-Gather Usage Example DES Requests Individual Request Type DescriptionsRandom Number Requests Rngreq1 ARC4LOADCTXCRYPTREQ ARC4 RequestsDescryptreq Descbccryptreq Valid Descriptors opId2 ARC4LOADKEYCRYPTUNLOADCTXREQ ARC4LOADCTXCRYPTREQ Valid Descriptor opIdARC4LOADKEYCRYPTUNLOADCTXREQ Valid Descriptor opId Hash Requests HashreqHashreq Valid Descriptors 0x4400 opId Hmac Requests HmacpadreqHashreq Valid Descriptors 0x4500 opId AES Requests AesacryptreqHmacpadreq Valid Descriptors opId Aesacryptreq Valid Descriptors opId Integer Public Key RequestsModexpreq Modexpreq Valid Descriptor opIdModssexpreq Valid Descriptor opId ModssexpreqMODR2MODNREQ DpdmmssrsaexpModrrmodpreq Valid Descriptor opId Modrrmodpreq5 MOD2OPREQ 0x5300MOD2OPREQ Valid Descriptors opId Value Function Description ECC Public Key Requests EccpointreqMOD2OPREQ Valid Descriptors opId 2 ECC2OPREQ Eccpointreq Valid Descriptors opIdEccspkbuildreq Valid Descriptor opId EccspkbuildreqECC2OPREQ Valid Descriptors opId DpdecspkbuildulctxIpseccbcreq IPSec RequestsEccptadddblreq Eccptadddblreq Valid Descriptor opIdIpseccbcreq Valid Descriptors opId Descriptors Ipsececbreq Ipsececbreq Valid Descriptors opIdIpsecaescbcreq Ipsecaescbcreq Valid Descriptors opIdIpsecaesecbreq Ipsecespreq Ipsecaesecbreq Valid Descriptors opIdIpsecespreq Valid Descriptors opId Dpdipsecespouttdescbccrptshapad DpdipsecespinsdescbcdcrptshapadDPDIPSECESPOUTTDESCBCCRPTMD5PAD DPDIPSECESPINTDESCBCDCRPTMD5PADCcmpreq 10 802.11 Protocol RequestsSrtp Protocol Requests SrtpreqSample Code DES SampleSrtpreq Valid Descriptors opId Ipsec Sample PRELIMINARY-SUBJECT to Change Without Notice Installation Linux EnvironmentOperation Driver Module License Macro Driver Operation in User ModeVxWorks Environment VxWorks EnvironmentBSP Integration PortingBuilding the Interface Modules VxWorks Interface Module VariablesInterrupt Service Routine Header FilesSource Files Conditional Compilation Debug MessagingDistribution 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