MSPM0G1107: MSPM0 SDK (2.02.00.05) SysConfig support for FreeRTOS/TI-Drivers

We'll consider that an option (modifying ti_drivers_config.c/h).

Right now, we're looking at the alternative of rolling our own thread-safe drivers and interrupt handlers. In particular, I'm referencing the UART module from TI-Drivers to see if anything special is being done to write interrupt handlers that work with/do not interfere with FreeRTOS. I do not see anything in particular indicating that it needs to coordinate directly with the RTOS. It seems that the UARTMSP_interruptHandler function allows the NVIC to nest interrupts like normal, but I did notice some callouts for hardware interrupts to be disabled. In particular, the receive function is preceded by this comment:

/*
 *  ======== UARTMSP_getRxData ========
 *  Must be called with HWI disabled.
 */
__STATIC_INLINE size_t UARTMSP_getRxData(UART_Handle handle, size_t size)
{
    UARTMSP_HWAttrs *hwAttrs           = UART_HWAttrs_Ptr(handle);
    UART_Object *uartObject            = UART_Obj_Ptr(handle);
    UART_Buffers_Object *buffersObject = UART_buffersObject(uartObject);

    size_t consumed = 0;
    uint8_t data;

    while (!(DL_UART_isRXFIFOEmpty(hwAttrs->regs)) && size)
    {
        data = DL_UART_receiveData(hwAttrs->regs);
        RingBuf_put(&buffersObject->rxBuf, data);
        ++consumed;
        --size;
    }
    return (consumed);
}

This code is only referenced in this same file (it's called directly in UARTMSP_interruptHandler) and no where else. But, I do not see any calls to HwiP_disable anywhere. Is this a bug or an obsolete comment?

Hi Derrick,

The code comment should be obsolete, as the UART data won't be overwritten by other UART processes due to this function getting called inside of the UART ISR.

Regards,
Luke