ble_evt_handler isn't triggered when trying to connect (s112)

[PabloRozario]

Hello everyone,

I'm trying to develop an application with BLE, using an example as a base.

The advertising is good, well configurated, I can edit manufacturer specific data, edit interval, etc.

But, when I try to connect to the nRF using nRF Connect in android, the app hangs on Discovering Services.

The flow returns NRF_SUCESS to me, in the registration of the service and characteristics, but, when I try to connect, I see that the ble_evt_handler isn't triggered.

I run the example in my custom board and works fine, but my project, don't.

I configured everything in the project equal to the example, add the same include directories, and nothing.

So, if you can help me, I will be very grateful.

SOME INFORMATION

IDE: Segger Embbeded Studio 5.32

SDK version: 17.0.2

SoftDevice: s112

TERMINAL LOG

<info> app_timer: RTC: initialized.
<info> app: app_timer_init: 0
<info> app: nrf_pwr_mgmt_init: 0
<info> app: nrf_sdh_enable_request: 0
<info> app: nrf_sdh_ble_default_cfg_set: 0
<info> app: nrf_sdh_ble_enable: 0
<info> app: ble_evt_handler registered.
<info> app: sd_ble_gap_device_name_set: 0
<info> app: sd_ble_gap_ppcp_set: 0
<info> app: nrf_ble_gatt_init: 0
<info> app: nrf_ble_gatt_init: 0
<info> app: nrf_ble_qwr_init: 0
<info> app: ble_services_initialize: 0
<info> app: ble_services_initialize: 0
<info> app: ble_advertising_init: 0
<info> app: ble_advertising_conn_cfg_tag_set: 0
<info> app: ble_conn_params_init: 0
<info> app: BLE_ADV_EVT_FAST
<info> app: ble_advertising_start: 0
<info> app: START!

Thank you so much guys

[Vidar Berg]

Hello,

The ble_evt_handler() should have been invoked by the SoftDevice Handler library when it received the BLE_GAP_EVT_CONNECTED event from the Softdevice. Have you selected the NRF_SDH_DISPATCH_MODEL_INTERRUPT setting in your sdk_config.h header? In any case, to start troubleshooting, please place a breakpoint in the  nrf_sdh.c::SD_EVT_IRQHandler() to see if the Softdevice interrupt gets triggered at all.

Best regards,

Vidar

[PabloRozario]

Thanks, I checked the parameters and was fine. I copy all the parameters of the ble uart example, with use the NUS. 

And another thing, it's a problem with the Bluetooth cache on the side of the android Bluetooth. Tested with another phone and connected successfully, and after cleared the cache, connected successfully too!

[Vidar Berg]

Thanks for the update, glad to hear that it works. Also note that you may disable caching by enabling the NRF_SDH_BLE_SERVICE_CHANGED setting in your project. This tells the client that it is not allowed to cache the services across connections. You can read more about the attribute caching rules in vol. 3, Part G, section 2.5.2 of the BT core specification: