|
|
I2CCC26XX Hardware attributes. More...
#include <I2CCC26XX.h>
Data Fields | |
| I2CBaseAddrType | baseAddr |
| unsigned long | powerMngrId |
| int | intNum |
| uint8_t | intPriority |
| I2C Peripheral's interrupt priority. More... | |
| uint8_t | sdaPin |
| uint8_t | sclPin |
I2CCC26XX 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 I2C 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:
| I2CBaseAddrType I2CCC26XX_HWAttrs::baseAddr |
I2C Peripheral's base address
| unsigned long I2CCC26XX_HWAttrs::powerMngrId |
I2C Peripheral's power manager ID
| int I2CCC26XX_HWAttrs::intNum |
I2C Peripheral's interrupt vector
| uint8_t I2CCC26XX_HWAttrs::intPriority |
I2C 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.
| uint8_t I2CCC26XX_HWAttrs::sdaPin |
I2C SDA pin mapping
| uint8_t I2CCC26XX_HWAttrs::sclPin |
I2C SCL pin mapping
