CryptoCC26XX Hardware Attributes. More...

#include <CryptoCC26XX.h>

Data Fields
uint32_t	baseAddr

int	powerMngrId

int	intNum

uint8_t	intPriority
	Crypto Peripheral's interrupt priority. More...

Detailed Description

CryptoCC26XX Hardware Attributes.

These fields, with the exception of intPriority, are used by driverlib APIs and therefore must be populated by driverlib macro definitions. For CC26XXWare these definitions are found in:

inc/hw_memmap.h
inc/hw_ints.h

intPriority is the Crypto peripheral's interrupt priority, as defined by the underlying OS. It is passed unmodified to the underlying OS's interrupt handler creation code, so you need to refer to the OS documentation for usage. If the driver uses the ti.dpl interface instead of making OS calls directly, then the HwiP port handles the interrupt priority in an OS specific way. In the case of the SYS/BIOS port, intPriority is passed unmodified to Hwi_create().

A sample structure is shown below:

const CryptoCC26XX_HWAttrs cryptoCC26XXHWAttrs[] = {
    {
        .baseAddr = CRYPTO_BASE,
        .powerMngrId = PERIPH_CRYPTO,
        .intNum = INT_CRYPTO,
        .intPriority = (~0)
    }
};

Field Documentation

§ baseAddr

uint32_t CryptoCC26XX_HWAttrs::baseAddr

Crypto Peripheral's base address

§ powerMngrId

int CryptoCC26XX_HWAttrs::powerMngrId

Crypto Peripheral's power manager ID

§ intNum

int CryptoCC26XX_HWAttrs::intNum

Crypto Peripheral's interrupt vector

§ intPriority

uint8_t CryptoCC26XX_HWAttrs::intPriority

Crypto Peripheral's interrupt priority.

The CC26xx uses three of the priority bits, meaning ~0 has the same effect as (7 << 5).

(7 << 5) will apply the lowest priority.

(1 << 5) will apply the highest priority.

Setting the priority to 0 is not supported by this driver.

HWI's with priority 0 ignore the HWI dispatcher to support zero-latency interrupts, thus invalidating the critical sections in this driver.

The documentation for this struct was generated from the following file: