Add UART1 to bluetoothds example on nrf52840

RE: Add UART1 to bluetoothds example on nrf52840

SRose — Wed, 08 Nov 2017 17:53:24 GMT

Perfect! Thanks for all your help.

RE: Add UART1 to bluetoothds example on nrf52840

Jørgen Holmefjord — Wed, 08 Nov 2017 16:34:55 GMT

The queues defined using NRF_SERIAL_QUEUES_DEF() will be implemented using nrf_queue library.

Looking at the implementation of the macro, you can see that it creates an object of type nrf_serial_queues_t, which point to both RX and TX queues. You can check the available queue size using the nrf_queue functions nrf_queue_available_get(), nrf_queue_utilization_get(), nrf_queue_is_empty(), and nrf_queue_is_full().

Using the names in the Serial example in the SDK, you can check available queue sizes like this:

size_t rx_available = nrf_queue_available_get(serial_queues.p_rxq);
size_t tx_available = nrf_queue_available_get(serial_queues.p_txq);

Best regards,

Jørgen

RE: Add UART1 to bluetoothds example on nrf52840

SRose — Mon, 06 Nov 2017 14:37:34 GMT

Jørgen, I think we figured this out. It seems the next call to nrf_serial_write() would return the timeout error if the TX queue was still filled with data and the call would overflow the TX queue. With flow ctrl in place, the sensor was having a problem reading the data fast enough. We fixed that and data is being sent OK now. Question, is there a way to check the amount of used bytes in the TX queue on Serial before calling nrf_serial_write() to prevent overflow?

RE: Add UART1 to bluetoothds example on nrf52840

Jørgen Holmefjord — Fri, 03 Nov 2017 15:12:49 GMT

0x000D (13) means NRF_ERROR_TIMEOUT, as I mentioned above. This error is thrown by nrf_serial_write() when timeout_ms is reached and there are still data left to be written.

RE: Add UART1 to bluetoothds example on nrf52840

SRose — Fri, 03 Nov 2017 15:02:35 GMT

I updated the error handler to the new code. This is the error code. <error> app: Error: ID: 16385, PC: 0x0 <error> app: Error: Code: 0x000D (13), Line: 62, File: ./bcdlogic.c where line 62 is the APP_ERROR_CHECK(ret) call after my call to nrf_serial_write. I'm trying to figure out what this error code means...

RE: Add UART1 to bluetoothds example on nrf52840

Jørgen Holmefjord — Fri, 03 Nov 2017 08:18:18 GMT

You should set a breakpoint in app_error_fault_handler, and check the error code manually, or you can add this code to print the error. Make sure you set optimization to -O0.

RE: Add UART1 to bluetoothds example on nrf52840

SRose — Thu, 02 Nov 2017 19:09:15 GMT

Hi Jørgen. The return value of nrf_serial_init() is NRF_SUCCESS. Also the first call to nrf_serial_write() is NRF_SUCCESS The second call causes the reboot. Changing the timeout_ms to 1000 didn't change anything. I've added the #define DEBUG, which stopped the rebooting, but the only line I have in the logging is <error> app: Fatal After playing around, I set my sensor to no flow ctrl and changed the setup to NRF_UART_HWFC_DISABLED. After I did this I am able to send and receive on UART1. Does this give any insight on why flow ctrl would cause an error? Thanks.

RE: Add UART1 to bluetoothds example on nrf52840

Jørgen Holmefjord — Wed, 01 Nov 2017 15:44:44 GMT

Have you debugged the application and checked the return value from nrf_serial_init() and nrf_serial_write()? I tried your code and get NRF_ERROR_TIMEOUT (0x0D) from nrf_serial_write(). Increasing the timeout_ms parameter solves this issue.