CC1312R: About the UART FIFO function on CC1312R

Hi Nomo

1)

The UART driver is implemented for a specific configuration of the UART HW module.

If you change this configuration, you most likely need to re-write the driver implementation as well.

Why can’t you use the driver implementation available from TI? What functionality do you need that the driver is not providing you?

The way to use the UART driver, is explained in the UART driver documentation:

https://dev.ti.com/tirex/explore/node?a=eCfARaV__1.50.00.08&node=AP24VgJ7gbuZWQrdF16tIg__pTTHBmu__LATEST

You say that the second argument is 200? What is meant by that? The second argument is const void * buffer, where buffer contains the data you want to write:

const char textToWrite[] = "Test\r\n";
UART_Handle uart;
UART_Params uartParams;

UART_init();

UART_Params_init(&uartParams);
uartParams.writeDataMode = UART_DATA_BINARY;
uartParams.readDataMode = UART_DATA_BINARY;
uartParams.readReturnMode = UART_RETURN_FULL;
uartParams.baudRate = 115200;

uart = UART_open(CONFIG_UART_0, &uartParams);
UART_write(uart, textToWrite, sizeof(textToWrite));

2)

When you configure the UART through sysConfig, the UART driver must be used as provided by TI. If you alter the driver implementation, we cannot tell you how sysConfig will work together with your modifications.

3)

I agree that it looks like there is a typo in the TRM

BR

Siri

I am still confused as to why you are asking what happens if you disable the FIFO, as this is not possible with our drivers.

The FIFO is enabled by setting LCRH.FEN = 1 and this is hard coded in the driver implementation, so unless you are changing our driver, you are not able to disable the FIFO:

UARTCC26XX_open calls UARTCC26XX_initHw(handle), which does the following:

/* Enable UART FIFOs */
HWREG(hwAttrs->baseAddr + UART_O_LCRH) |= UART_LCRH_FEN;

This is done regardless of the ring buffer size. The ring buffer serves as an extension of the FIFO. If data is received when UART_read() is not called, data will be stored in the ring buffer. The size can be changed to suit the application.

Also still confused regarding the arguments.

In the first e-mail you wrote:

"In case the 2nd argument (*buffer) is 200 and the 3rd argument (size) is 100,"

In the last e-mail you state that buffer size is 200 byte.

As explained in the documentation, the first argument is the handle, the second argument is the array where data is stored, and the third argument is the size of that array (if you want to send all elements in the array).

BR

Siri

Hi Siri-san,

Thank you for your reply.

Everything is clear.

Best Regards,

Nomo