TI-RTOS for TivaC
2.14.04.31
|
UART driver implementation for a EUSCIA peripheral for MSP432.
============================================================================
The UARTMSP432 driver is (ring) buffered driver where it stores data it may already received in a user-supplied background buffer.
While permitted, it is STRONGLY suggested to avoid implementations where you call UART_read() within it own callback function (when in UART_MODE_CALLBACK).
Doing so, will require additional (task and system) stack for each nested UART_read() call.
Tool chain | Number of bytes per nested UART_read() call |
---|---|
GNU | 96 bytes + callback function stack requirements |
IAR | 40 bytes + callback function stack requirements |
TI | 80 bytes + callback function stack requirements |
It is important to note a potential worst case scenario: A full ring buffer with data; say 32 bytes The callback function calls UART_read() with a size of 1 (byte) No other variables are allocated in the callback function No other function calls are made in the callback function
As a result, you need an additional task and system stack of: 32 bytes * (80 bytes for TI + 0 bytes by the callback function) = 2.5kB
The UART header file should be included in an application as follows:
This UART driver implementation is designed to operate on a EUSCI controller in UART mode for MSP432 devices.
#include <stdint.h>
#include <stdbool.h>
#include <ti/drivers/ports/ClockP.h>
#include <ti/drivers/ports/HwiP.h>
#include <ti/drivers/ports/SemaphoreP.h>
#include <ti/drivers/Power.h>
#include <ti/drivers/UART.h>
#include <ti/drivers/uart/RingBuf.h>
Go to the source code of this file.
Data Structures | |
struct | UARTMSP432_FxnSet |
Complement set of read functions to be used by the UART ISR and UARTMSP432_read(). Internal use only. More... | |
struct | UARTMSP432_BaudrateConfig |
UARTMSP432 Baudrate configuration. More... | |
struct | UARTMSP432_HWAttrs |
UARTMSP432 Hardware attributes. More... | |
struct | UARTMSP432_Object |
UARTMSP432 Object. More... | |
Typedefs | |
typedef struct UARTMSP432_FxnSet | UARTMSP432_FxnSet |
Complement set of read functions to be used by the UART ISR and UARTMSP432_read(). Internal use only. More... | |
typedef struct UARTMSP432_BaudrateConfig | UARTMSP432_BaudrateConfig |
UARTMSP432 Baudrate configuration. More... | |
typedef struct UARTMSP432_HWAttrs | UARTMSP432_HWAttrs |
UARTMSP432 Hardware attributes. More... | |
typedef struct UARTMSP432_Object | UARTMSP432_Object |
UARTMSP432 Object. More... | |
typedef struct UARTMSP432_Object * | UARTMSP432_Handle |
Variables | |
const UART_FxnTable | UARTMSP432_fxnTable |
typedef struct UARTMSP432_FxnSet UARTMSP432_FxnSet |
Complement set of read functions to be used by the UART ISR and UARTMSP432_read(). Internal use only.
These functions should not be used by the user and are solely intended for the UARTMSP432 driver. The UARTMSP432_FxnSet is a pair of complement functions that are design to operate with one another in a task context and in an ISR context. The readTaskFxn is called by UARTMSP432_read() to drain a circular buffer, whereas the readIsrFxn is used by the UARTMSP432_hwiIntFxn to fill up the circular buffer.
readTaskFxn: Function called by UART read These variables are set and available for use to the readTaskFxn. object->readBuf = buffer; //Pointer to a user buffer object->readSize = size; //Desired no. of bytes to read object->readCount = size; //Remaining no. of bytes to read
readIsrFxn: The required ISR counterpart to readTaskFxn
typedef struct UARTMSP432_BaudrateConfig UARTMSP432_BaudrateConfig |
UARTMSP432 Baudrate configuration.
This structure is used to specifiy the EUSCI controller's clock divider settings to achieve the desired baudrate given the a clock input frequency. Divider values can be determined by referring to the MSP430 baudrate calculator. https://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430BaudRateConverter/index.html
A sample structure is shown below:
typedef struct UARTMSP432_HWAttrs UARTMSP432_HWAttrs |
UARTMSP432 Hardware attributes.
These fields are used by driverlib APIs and therefore must be populated by driverlib macro definitions. For MSP432Ware these definitions are found 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.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:
typedef struct UARTMSP432_Object UARTMSP432_Object |
UARTMSP432 Object.
The application must not access any member variables of this structure!
typedef struct UARTMSP432_Object * UARTMSP432_Handle |
const UART_FxnTable UARTMSP432_fxnTable |