I've been playing with the simple_uart example and it seems like it might be missing responses. Does it buffer incoming data until the simple_uart_get() is called?
I've been playing with the simple_uart example and it seems like it might be missing responses. Does it buffer incoming data until the simple_uart_get() is called?
So does the app_uart library provide better buffering support? It looks like you can configure the buffer size on the app_uart_init() call.
The devices I"m working with do not support flow control, but they work on a simple request-response protocol so I don't need to buffer unsolicited data, but I do have to handle the incoming responses after my request.
Hi Ole. I have been working with app_uart for a few hours now. But I don't see any code in app_uart dealing with buffering logic. It does set up a structure for doing that. A good indicator is the "flush" logic is not doing anything, only returning a success flag.
Hi Ole. I have been working with app_uart for a few hours now. But I don't see any code in app_uart dealing with buffering logic. It does set up a structure for doing that. A good indicator is the "flush" logic is not doing anything, only returning a success flag.