Detailed Description

AESGCM driver implementation for the Low Power F3 family.

============================================================================

This file should only be included in the board file to fill the AESGCM_config struct.

Hardware Accelerator

The Low Power F3 family of devices has a dedicated AES hardware that can perform AES encryption operations with 128-bit keys. Only one operation can be carried out on the accelerator at a time. Mutual exclusion is implemented at the driver level and coordinated between all drivers relying on the accelerator. It is transparent to the application and only noted to ensure sensible access timeouts are set. The GHASH computation for GCM has optimizations using Shoup's 4-bit tables that are precomputed for each hash key H.

Implementation Limitations

Only plaintext CryptoKeys are supported by this implementation.
Callback return behavior is not supported by this implementation.
Blocking return behavior operates the same as polling return behavior and does not block the calling thread.

Runtime Parameter Validation

The driver implementation does not perform runtime checks for most input parameters. Only values that are likely to have a stochastic element to them are checked (such as whether a driver is already open). Higher input parameter validation coverage is achieved by turning on assertions when compiling the driver.

#include <stdbool.h>
#include <stddef.h>
#include <stdint.h>
#include <ti/drivers/AESGCM.h>
#include <ti/drivers/cryptoutils/aes/AESCommonLPF3.h>
#include <ti/devices/DeviceFamily.h>
#include <DeviceFamily_constructPath(driverlib/aes.h)>

Include dependency graph for AESGCMLPF3.h:

Go to the source code of this file.

Data Structures
struct	AESGCMLPF3_Object
	AESGCMLPF3 Object. More...

Typedefs
typedef AESCommonLPF3_HWAttrs	AESGCMLPF3_HWAttrs
	AESCCMLPF3 Hardware Attributes. More...

Typedef Documentation

§ AESGCMLPF3_HWAttrs

typedef AESCommonLPF3_HWAttrs AESGCMLPF3_HWAttrs

AESCCMLPF3 Hardware Attributes.

AESCCMLPF3 hardware attributes should be included in the board file and pointed to by the AESCCM_config struct.