TI-RTOS Drivers
tidrivers_cc13xx_cc26xx_2_20_00_08
|
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... | |
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:
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. For example, for SYS/BIOS applications, refer to the ti.sysbios.family.arm.m3.Hwi documentation for SYS/BIOS usage of interrupt priorities. If the driver uses the ti.drivers.ports 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:
uint32_t CryptoCC26XX_HWAttrs::baseAddr |
Crypto Peripheral's base address
int CryptoCC26XX_HWAttrs::powerMngrId |
Crypto Peripheral's power manager ID
int CryptoCC26XX_HWAttrs::intNum |
Crypto Peripheral's interrupt vector
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.