NUS UART data handler issue

RE: NUS UART data handler issue

Stefan Birnir Sverrisson — Wed, 28 Sep 2016 13:53:17 GMT

Hi Ankush

If you are getting every message in the ble_dispatch function, but not in the UART handler in the application, then something in the ble_nus_on_ble_evt function is not forwarding the callback to the application. Just step through the code from where you break in ble_evt_dispatch to see why the UART handler in the application is not called.

RE: NUS UART data handler issue

Ankush — Tue, 27 Sep 2016 04:20:27 GMT

Hi ,

Any updates over the issue.

RE: NUS UART data handler issue

Ankush — Sat, 24 Sep 2016 09:53:08 GMT

Hi Stefan,

I tried putting the breakpoints in ble_dispatch function. It is hitting all the times to breakpoints when I am sending data from APP. I am getting values as folloew: 1)uuid_type = 0x02 2)service handle = 15 3)value handle = 20 4)_evt_id = 80 5)evt_len = 19

It is happening only with UART. HRS and BAS service working fine.

Can you suggest any steps to resolve the issue.

RE: NUS UART data handler issue

Stefan Birnir Sverrisson — Fri, 23 Sep 2016 13:00:25 GMT

Try to set a breakpoint in ble_evt_dispatch function in the main.c file. That should be hit when you send something over BLE. If you get nothing there, then you could get a sniffer trace to see what is happening on air. If the phone is not sending anything, then it is a phone/phone app problem.

RE: NUS UART data handler issue

Ankush — Fri, 23 Sep 2016 07:56:58 GMT

Hi Stefan,

I tried what you suggested but facing the same issue. I tried putting a variable in onwrite function of nus.c and using the same variable in main function. Like if var = 0x01 then perform the task. But still facing the same issue.

RE: NUS UART data handler issue

Stefan Birnir Sverrisson — Mon, 19 Sep 2016 11:31:41 GMT

Hi Ankush

Im trying this with nRF Connect on iphone, SD 132 3.0.0 and ble_app_uart from SDK 12.0.0. I observe that the app does not accept sending values 1 or 2, you need to type in 01 or 02, because the expression is in hex numbers, i.e. 0x01 and 0x02. Also if you write a high number, e.g. FF, you need to write that in capital letters, ff is not accepted.

RE: NUS UART data handler issue

Ankush — Sat, 17 Sep 2016 07:22:56 GMT

Hi Stefan,

Thanks for reply. Sorry for late reply. You are right. Sometimes when I am sending uint8 value from APP, NUS data handler is not getting called.This is not the problem with other BLE codes that I have implemented previously. I am not getting what is exactly the issue.

I have set APP_TIMER_OP_QUEUE_SIZE = 16. Does it makes any difference?

RE: NUS UART data handler issue

Stefan Birnir Sverrisson — Fri, 16 Sep 2016 15:28:17 GMT

Hi Ankush

I am not sure I understand the problem. Can you clarify? Are you not always getting interrupt from the nus service when sending data from the app?