BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Wed, 11 Sep 2024 12:50:54 GMT

ok, I will check them out I just thought it was a simple configuration issue. It seems it is not 🙂

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Wed, 11 Sep 2024 10:05:11 GMT

My suggestion to debug further:
- for test try to change the security parameters to see if that impact the issue
- for test try to change the service and characteristics to see if that impact the issue

It can be that Windows have specific requirements, and it's difficult to know exactly what that may be. So the best is really some try and error approach here. Btw, you don't write anything about iOS works, but that is something you can also try.

You can also try to install and run nRF Sniffer for BLE, then I can at least check if I see any errors:
https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Wed, 11 Sep 2024 09:22:43 GMT

It is just a peripheral device( with no IO capabilities) that transmits data through NUS to a central device. When the central is a tablet with( nRF connect) the pairing process works properly, meaning that it does not disconnect after pairing with the central. The issue occurs only when the PC is used as a central .

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Tue, 10 Sep 2024 14:15:14 GMT

Hello,

What application is this? Is it a HID device or something else? I assume a HID device with errors in the report map may be disconnected. Maybe try to only keep battery service and see if you experience the same.

Kenneth

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Tue, 10 Sep 2024 08:40:35 GMT

it returns BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION 0x13 so it must be on he PC side

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Mon, 09 Sep 2024 13:02:25 GMT

Try something like:

case BLE_GAP_EVT_DISCONNECTED:
printf("Disconnected, reason: 0x%x\n", p_ble_evt->evt.gap_evt.params.disconnected.reason);
break;

Kenneth

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Mon, 09 Sep 2024 11:53:13 GMT

Yes that is what I am trying to do since I created the ticket. Anyway thank you for your time

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Mon, 09 Sep 2024 09:09:48 GMT

Try to find out what is the disconnect reason, to understand if it's called locally og from the PC, and what the reason is.

Kenneht

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Thu, 05 Sep 2024 14:28:20 GMT

Yes sorry I un-commented it for a test and then I forgot to re-comment it 😛

When I remove it the device is disconnected. I suppose that the attributes of the PC are not the same with those of the nRF BLE stack and the PC stops the connection. But on the other hand the device seems to be paired on the PC. What is going on...

<info> app: IMU Default attached at Power-On
<info> app: TX_POWER_ROLE_ADV : OK
<info> app: Clearing all data from peers
<debug> peer_manager_handler: Event PM_EVT_PEERS_DELETE_SUCCEEDED
<info> peer_manager_handler: All peers deleted.
<info> app: PM_EVENT_HANDLER: 12
<info> app: PM_EVT_PEERS_DELETE_SUCCEEDED
<info> app: Security parameters set.
<info> app: sec_param: bond=1, mitm=1, lesc=0, io_caps=0
<info> app: NACK AFTER SENDING DATA
<info> app: NACK AFTER SENDING DATA
<info> app: NACK AFTER SENDING DATA
<info> app: NACK AFTER SENDING DATA
<info> app: Gauge Initialized
<info> app: USB power detected
<info> app: USB ready
<info> app: Device  event started
<info> app: Device suspend event
<info> app: Device resume event
<info> app: Device reset event
<info> app: Device reset event
<info> app: Device reset event
<debug> nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.
<debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.
<info> app: BLE GAP Connected
<info> app: TX_POWER_ROLE_CONN: OK
<debug> peer_manager_handler: Event PM_EVT_CONN_SEC_PARAMS_REQ
<debug> peer_manager_handler: Security parameter request
<info> app: PM_EVENT_HANDLER: 5
<info> app: PM_EVT_CONN_SEC_PARAMS_REQ
<info> app: Security parameters request received.
<debug> nrf_ble_gatt: Peer on connection 0x0 requested an ATT MTU of 527 bytes.
<debug> nrf_ble_gatt: Updating ATT MTU to 247 bytes (desired: 247) on connection 0x0.
<debug> nrf_ble_gatt: ATT MTU updated to 247 bytes on connection 0x0 (response).
<debug> app: ATT MTU exchange completed. central 0xF7 peripheral 0xF7
<debug> peer_manager_handler: Event PM_EVT_CONN_SEC_START
<debug> peer_manager_handler: Connection security procedure started: role: Peripheral, conn_handle: 0, procedure: Bonding
<info> app: PM_EVENT_HANDLER: 1
<debug> peer_manager_handler: Event PM_EVT_CONN_SEC_PARAMS_REQ
<debug> peer_manager_handler: Security parameter request
<info> app: PM_EVENT_HANDLER: 5
<info> app: PM_EVT_CONN_SEC_PARAMS_REQ
<info> app: Security parameters request received.
<info> app: sec_param: bond=1, mitm=1, lesc=0, io_caps=0
<info> app: REPLIED WITH SEC_PARAMS 537132156
0.
<debug> nrf_ble_gatt: max_rx_octets: 27
<debug> nrf_ble_gatt: max_tx_octets: 27
<debug> nrf_ble_gatt: max_rx_time: 328
<debug> nrf_ble_gatt: max_tx_time: 328
<debug> app: ATT MTU exchange completed. central 0xF7 peripheral 0xF7
<info> app: PASSKEY DISPLAY: 832577
<info> app: NACK AFTER SENDING DATA
<debug> peer_manager_handler: Event PM_EVT_CONN_SEC_SUCCEEDED
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Bonding
<info> app: PM_EVENT_HANDLER: 2
<info> app: Authentication status: 0
<info> app: Bonding succeeded.
<debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
<debug> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Bonding data, action: Update
<info> app: PM_EVENT_HANDLER: 8
<debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
<debug> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update
<info> app: PM_EVENT_HANDLER: 8
<debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
<debug> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
<info> app: PM_EVENT_HANDLER: 8
<debug> peer_manager_handler: Event PM_EVT_PEER_DATA_UPDATE_SUCCEEDED
<debug> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Central address resolution, action: Update
<info> app: PM_EVENT_HANDLER: 8
<debug> peer_manager_handler: Event PM_EVT_LOCAL_DB_CACHE_APPLIED
<debug> peer_manager_handler: Previously stored local DB applied: conn_handle: 0, peer_id: 0
<info> app: PM_EVENT_HANDLER: 14
<info> app: PM_EVT_LOCAL_DB_CACHE_APPLIED event received.
<info> app: NACK AFTER SENDING DATA
<info> app: BLE GAP Disconnected
<info> app: BLE Disconnected

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Thu, 05 Sep 2024 12:09:18 GMT

But as mentioned, this should not be executed by the application. It's handled by the peer manager module (when / if neccessary).

Kenneth

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Thu, 05 Sep 2024 11:33:13 GMT

The error occurs in the BLE_GATTS_EVT_SYS_ATTR_MISSING event when the err_code = sd_ble_gatts_sys_attr_set(*m_conn_handle_gen, NULL, 0, 0); is executed

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Thu, 05 Sep 2024 10:49:12 GMT

But then I don't really see any problem here, what is really failing?

What is the disconnect reason? Have you checked if it's possible that the peripheral is disconnecting here? Maybe check all instances of sd_ble_gap_disconnect()?

Kenneth

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Thu, 05 Sep 2024 10:00:22 GMT

Number 8 of the pm_evt_id_t enum
is the PM_EVT_PEER_DATA_UPDATE_SUCCEEDED in peer_manager_types.h

I changed the pm log to level 4

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Thu, 05 Sep 2024 09:41:17 GMT

I was hoping to get more information from what is happening inside the peer manager module. Are you able to increase the debug level (e.g. PM_LOG_LEVEL 4) to get some more information? It looks like the peer manager module is throwing 8 (PM_EVT_ERROR_UNEXPECTED?), so I do believe it should provide more information as to why.

Kenneth

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Wed, 04 Sep 2024 13:44:49 GMT

Yes it is enabled in the sdk_config

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Wed, 04 Sep 2024 12:47:28 GMT

Can you turn on logging from the PM module: PM_LOG_ENABLED?

Kenneth

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Wed, 04 Sep 2024 12:36:15 GMT

no the same happens

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Wed, 04 Sep 2024 12:17:58 GMT

Does running an nrfjprog --eraseall make any difference?

Kenneth

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Wed, 04 Sep 2024 09:31:26 GMT

After removing the ATTR_MISSING event the device disconnects from BLE . Here is the debugger log

When I use the tablet, the PM_EVENT: 14 is not triggered and the connection is ok.

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Wed, 04 Sep 2024 09:23:26 GMT

Let me check it . Thanks!

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Wed, 04 Sep 2024 09:22:30 GMT

If you remove the handling of BLE_GATTS_EVT_SYS_ATTR_MISSING in ble_evt_handler(), does anything fail?

Kenneth

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

masterLee — Wed, 04 Sep 2024 09:16:45 GMT

Do you mean the BLE_GATTS_EVT_SYS_ATTR_MISSING event?
I don't know what to look for since I can't find a specific list of attributes what value to set them to in order to fit the windows settings. Also I don't understand what are those attributes

RE: BLE Pairing/Bonding issue betweennRF52840 as server and PC as a client

Kenneth — Wed, 04 Sep 2024 08:56:00 GMT

Hello,

I don't have any direct explaination as to why you only see this with the tablet vs. Windows. However normally Windows will allways apply the "strongest" common security level upon connection/bonding, while I know other OS may only apply the such security depending on the actual requirement of the services and characteristics of the GATT database. In any case, if you are using peer manager, then this event will be handled by the peer manager module, and it's not intended to be used/handled by the application.

Kenneth