RE: Only two correct bytes when for read and notify as BLE central

xudongz — Mon, 07 Oct 2019 15:34:06 GMT

It turns out that the problem is saving/copying p_ble_evt->evt.gattc_evt.params.read_rsp as a variable. The solution was to store a pointer (or just accessing the data directly via p_ble_evt->evt.gattc_evt.params.read_rsp.data)

ble_gattc_evt_read_rsp_t *resp = &p_ble_evt->evt.gattc_evt.params.read_rsp;

RE: Only two correct bytes when for read and notify as BLE central

Edvin — Thu, 26 Sep 2019 12:37:52 GMT

Hello,

I am a bit confused from your explanation and your snippets. You say that you want to use notifications, and you refer to the ble_nus_c service (which uses notifications). Notifications is something other than read. Did you test the ble_app_uart and ble_app_uart_c examples together? Does that work? Notifications will trigger an event at the central, which you can use to receive the data, and it is in general a bit easier to work with than the sd_ble_gattc_read().

I also get the impression that you try to use queued write, or long write. Is that correct? And is that intentional?

If you need to use write and sd_ble_gattc_read(), is there a reason for this, and how do you write this in your peripheral?

Sorry that I don't have an exact answer, but I need to nest up in a few things first, so that we are on the same page.