Hi. When i use ble_app_uart
i have problem with my device over uart. It does not response to my commands.
I'm using custom pcb based on nrf52
with nrf UART v2.0
android app.
Is there something i'm missing?
Hi. When i use ble_app_uart
i have problem with my device over uart. It does not response to my commands.
I'm using custom pcb based on nrf52
with nrf UART v2.0
android app.
Is there something i'm missing?
Hi,
Does your phone support BLE 4.2 ? If not you will have to do a small modification to the ble_app_uart project. See this answer.
Also note that the old UART 2.0 app is deprecated (over 3 years since last update). I recommend using the nRF-Toolbox app, and use the UART function there instead.
Thanks for the toolbox recomendation.
Is there a diference in TX and RX therminology regarding driver and library?
between the uart driver and library? In the library we have the function app_uart_put()
that will place the provided byte in the TX FIFO. (using the driver function nrf_drv_uart_tx()
).
Ok. I have some more news. The initialisation was before BLE after i put it after BLE but before advertising i got something. Now i have new problem. I don't get the letters into firmware. But i can see them on logic analyzer. The event that i get is uart_event_handle CASE: 3
which means APP_UART_TX_EMPTY
i guess. And i get this 18 times, the same as the letters count.