CC2640R2F: With Hardware flow control, CC2640R2F RTS might pull low abnormally

Hi Jerry,

The RTS is pulled down (asserted) when the device is ready to receive data, and pulled up (de-asserted) otherwise.  So at some point the RTS should be de-asserted (pulled up) when the buffer is full.  No software code additions should be necessary.  Is the customer able to increase their buffers and FIFO thresholds, or can they monitor errors to flush the FIFO if the receiver gets stuck?  Please provide oscilloscope or logic analyzer screenshots if possible, and a detailed description of the exact issue which is being encountered.  https://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_5_30_00_03/docs/tidrivers/doxygen/html/_u_a_r_t_c_c26_x_x_8h.html 

Regards,
Ryan

Hi Ryan,

Customer use CC2640 (R1) before. They said with CC2640R1, UART works fine with the same modification (just assign .ctsPin, .rtsPin to valid DIO).

Do we have any simple UART example with hardware flow control ? Customer said the host_test NPI is too complicated. 

I will deliver your information to customer. Thank you.

What version of SIMPLELINK-CC2640R2-SDK is the customer using?  The NPI is the best example of software-controlled UART, along with the NPI/SDI resources from the ble_examples GitHub page.  Otherwise, two GPIOs can be configured for RTS output and CTS input (interrupt enabled) to develop a software solution.

Regards,
Ryan

HI Ryan,

SDK 5.30. Thank you.

Which project do you mention about the NPI/SDI resources from the ble_examples GitHub page. ?

simple_serial_socket_client/server from bleapps.

Regards,
Ryan