Hi all - Perhaps some of you have encountered this?
The post linked below shows the Kinetis UART continues to transmit after th e receiver has de-asserted CTS:
Here's my question: As this is an asynchronous link, the receiver can de-as sert CTS at any time. What is the transmitter supposed to do? For example, suppose CTS is de-asserted in the middle of transmitting a character: Must the transmitter immediately stop, and restart transmitting the character fr om the start bit when CTS is again asserted (which in turn introduces a rac e condition around the end of character transmission)? Or finish the curren t character transmission and then pause (another race condition for "curren t character")? Is there any specification on how this should be handled? Or even any consensus?
Thanks in advance, Best Regards, Dave
PS: I've always used a protocol layer that corrects dropped characters so n ever had this impact an application, but using some parts like SiLabs blueg iga for SPP don't give that option (at the layer of controlling the Bluetoo th device, or supporting a non-protocol client expecting a simple ASCII dat a stream). Even worse, these things drop status messages into the (applicat ion data) stream with no consistent header/delimiter - good luck catching a ll possible Bluetooth events.