UART2CC32XX Hardware attributes. More...
#include <UART2CC32XX.h>
Data Fields | |
UART2_BASE_HWATTRS UART2CC32XX_FifoThreshold | txIntFifoThr |
UART2CC32XX_FifoThreshold | rxIntFifoThr |
uint32_t | rxDmaChannel |
uint32_t | txDmaChannel |
UART2CC32XX Hardware attributes.
The fields, baseAddr and intNum are used by driverlib APIs and therefore must be populated by driverlib macro definitions. These definitions are found under the device family in:
intPriority is the UART 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.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(). The CC32XX 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.
A sample structure is shown below:
To enable flow control, the .ctsPin and/or .rtsPin must be assigned. In addition, .flowControl must be set to UART2_FLOWCTRL_HARDWARE.
UART2_BASE_HWATTRS UART2CC32XX_FifoThreshold UART2CC32XX_HWAttrs::txIntFifoThr |
UART TX interrupt FIFO threshold select
UART2CC32XX_FifoThreshold UART2CC32XX_HWAttrs::rxIntFifoThr |
UART RX interrupt FIFO threshold select
uint32_t UART2CC32XX_HWAttrs::rxDmaChannel |
uDMA channel for RX data
uint32_t UART2CC32XX_HWAttrs::txDmaChannel |
uDMA channel for TX data