ble_db_discovery_start return 0x11

[zjk]

info: my board core is nrf52832

i want to use examples\ble_central\ble_app_uart_c  to connect with a Slave，i have only modified  the UUID,and it can connect ok,but when it run after ble_db_discovery_start(),it return err(errcode = 0x11),I don't know why.log under:

00> <debug> ble_db_disc: Starting discovery of service with UUID 0xFEE7 on connection handle 0x0.

00> 

00> <debug> nrf_ble_gq: Adding item to the request queue

00> 

00> <debug> nrf_ble_gq: GATTC Primary Services Discovery Request

00> 

00> <debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted                       again later.

00> 

00> <debug> nrf_ble_gq: Processing the request queue...

00> 

00> <debug> nrf_ble_gq: GATTC Primary Service Discovery Request

00> 

00> <debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted                           again later.

00> 

00> <info> app: Connection BLE_GAP_EVT_CONNECTED...

00> 

00> <info> ble_db_disc: ble_db_discovery_on_ble_evt:17

00> 

00> <info> app: Disconnected.

[Simonr]

Hi

The error code 0x11 points towards the SoftDevice being busy, which means that the SoftDevice is busy doing something else when you're calling the ble_db_discovery_start() function. From your log, it seems like you're doing this while the device is trying to connect to a peripheral. Please try calling this once the device has connected successfully to the peripheral device.

Best regards,

Simon

[zjk]

but I have call one times

[Simonr]

Hi

Initially, you said that the only modification you made was to edit the UUID, but it seems like you've removed quite a bit of the code in the BLE event handler. The SoftDevice might be busy waiting for an ADV_REPORT event (the one you have removed) or similar, which could be why you are seeing this error.

I suggest you check out our BLE Getting Started tutorial series to get a better understanding of BLE advertising and scanning.

Best regards,

Simon

[m5k8]

I have similar problem: https://devzone.nordicsemi.com/f/nordic-q-a/97637/ble-central-disconnect-event-received-immediately-after-connection

Simonr, please have a look again.

Simonr said:

Please try calling this once the device has connected successfully to the peripheral device.

He clearly calls this AFTER successful connection - it happens in CONNECT event. So he has a connection here. He is logging CONNECT event after db_discovery_start(), so messages are mixed, but his code shows it clearly.

Simonr said:

The SoftDevice might be busy waiting for an ADV_REPORT event

I don't understand that. ADV_REPORT is emitted from SoftDevice, not the other way around? He deleted code handling ADV_REPORT, but that shouldn't influence anything - one is not expected to do anything with this event, or inform the SoftDevice that it was consumed. Not doing anything is fine, as far as I understand?

zjk, did you resolve this issue?

[Simonr]

My colleague Susheel is currently working on your open ticket, I'll leave it for zjk  to answer here.

Best regards,
Simon