[EXT_EP-9278] UART_read returns 0 in portable after a power-cycle on CC13x0 and CC26x0 devices - Software Issue Report (SIR)

XML

Word

Printable

Product:
TI Device Drivers
Internal ID:
TIDRIVERS-3635
Found In Release:
3.80.00
Fix In Release:
TIDRIVERS_4_20_NEXT
Release Notes:

Hide
On the portable (and portableNative) examples, the UART_read in the console thread returns 0 on the first read after a power cycle. The example currently takes this as an error and closes the UART.

A simple work-around is to either:

1. Delay the first UART_read until the UART is stabilized after the power cycle. We've found the following enough of a delay.

** for (i = 0; i < 100000; i++)

{ }
2. Don't treat the zero return as an error. Instead simply call UART_read again.

Show
On the portable (and portableNative) examples, the UART_read in the console thread returns 0 on the first read after a power cycle. The example currently takes this as an error and closes the UART. A simple work-around is to either: 1. Delay the first UART_read until the UART is stabilized after the power cycle. We've found the following enough of a delay. ** for (i = 0; i < 100000; i++) { } 2. Don't treat the zero return as an error. Instead simply call UART_read again.

UART_read returns 0 in portable after a power-cycle on CC13x0 and CC26x0 devices