Wakeup from sd_app_evt_wait() on BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST

[Stefan Wyss]

I have customized the "nordic_blinky" app. My app contains a call to sd_app_evt_wait() in main (low power ON mode).

It seems that after the write connection event (BLE_GATTS_EVT_WRITE) the cpu wakes up and continues processing post sd_app_evt_wait() in main().That is the behaviour that I need in my application in order to process some sensor values in main() after every connection event. But when I issue a read event and BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST is handled, then the wakeup from sa_app_evt_wait() is not happening!

My questions:

1) What could be the reason for the different behaviour of BLE_GATTS_EVT_WRITE and BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST in terms of wakeup from sd_app_evt_wait()?

2) How can I resume from sd_app_evt_wait() after BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST is handled?

(I read somewhere in this forum that every interrupt could wakeup the cpu core, but I can not find the interrupt that is triggered by BLE_GATTS_EVT_WRITE connection event)

Thanks, Stefan

[Kenneth]

Hi, have you set attr_md.rd_auth for read and/or attr_md.wr_auth for write before calling sd_ble_gatts_characteristic_add?

 https://www.nordicsemi.com/DocLib/Content/SoftDevice_API_Doc/S132/v6-1-0/structble__gatts__attr__md__t 

[Stefan Wyss]

I have set ...

attr_md.rd_auth = 1;      
attr_md.wr_auth = 0;

... in all 3 of my characteristics before calling sd_ble_gatts_characteristic_add().

I do get the authorize request BLE events, that's not the problem. The problem is that there is no wakeup from sd_app_evt_wait() after the BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST event, but there is wakeup after the BLE_GATTS_EVT_WRITE connection event. (I just want to read a characteristic and wakeup my app).

[Kenneth]

This is strange, what softdevice version are you using here? Can you share the example so I may try here?

What security requirement have you set for read access? Is the 'char_props.read' also set to support read (=1)?

[Stefan Wyss]

Here is the link for my current FW:

https://drive.google.com/file/d/1_p5jeaIHz33PLexP4xDLm0mKe_gONNPr/view?usp=sharing

It should run on PCA10040 dev board. The directory layout should be:

. / nrf5_sdk / nRF5_SDK_14.2.0_17b948a
. / nrf52_3100-1_fw

Yes, char_props.read is = 1 to support read.

[Stefan Wyss]

Ok, my problem was somewhere else.

I tried to update a static var declared in main.c from service.c which did not work because static vars seem to be global only to the file they are declared in.

Thanks for your support!