RE: Max packet size when using bonding

kurtovic — Tue, 03 Oct 2023 23:59:58 GMT

Hi,

I have figured out what has been going on. It turns out the issue is isolated to the device I've been running the nRF Connect app on (it is a very old tablet). If I attempt the same procedure using a more up-to-date mobile device, I have no issues pairing when using the 251/247 configuration.

RE: Max packet size when using bonding

kurtovic — Fri, 29 Sep 2023 02:54:05 GMT

Hi,

My last post was a false-positive, I must have misinterpreted log output and thought bonds were succeeding with the increased values of 251/247.

Here is a sample of the log output from the nrf52840 running peripheral/ble_app_gls while I try to bond via the nRF connect app.

With data length = 27 and mtu = 23, I see the pairing prompt on the app.

<info> app_timer: RTC: initialized.
<debug> nrf_ble_lesc: Initialized nrf_crypto.
<debug> nrf_ble_lesc: Initialized nrf_ble_lesc.
<debug> nrf_ble_lesc: Generating ECC key pair
<info> app: Glucose example started.
<info> app: Fast advertising
<debug> nrf_ble_gq: Registering connection handle: 0x0000
<info> app: Connected
<debug> app: BLE_GAP_EVT_SEC_PARAMS_REQUEST
<info> app: Passkey: 872149
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Bonding
<info> app: Link secured. Role: 1. conn_handle: 0, Procedure: 1
<debug> nrf_ble_lesc: Generating ECC key pair
<info> app: BLE_GAP_EVT_AUTH_STATUS: status=0x0 bond=0x1 lv4: 0 kdist_own:0x3 kdist_peer:0x3
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Bonding data, action: Update
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
<debug> nrf_ble_gq: Processing the request queue...
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Central address resolution, action: Update

With data length = 251 and mtu = 247, the app connects but never shows the pairing prompt

<info> app_timer: RTC: initialized.
<debug> nrf_ble_lesc: Initialized nrf_crypto.
<debug> nrf_ble_lesc: Initialized nrf_ble_lesc.
<debug> nrf_ble_lesc: Generating ECC key pair
<info> app: Glucose example started.
<info> app: Fast advertising
<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.
<debug> nrf_ble_gq: Registering connection handle: 0x0000
<info> app: Connected
<debug> nrf_ble_gq: Processing the request queue...
<debug> nrf_ble_gatt: ATT MTU updated to 247 bytes on connection 0x0 (response).
<info> app: Fast advertising
<info> app: Disconnected

The app shows error 129 (0x81) GATT INTERNAL ERROR, and 133 (0x85) GATT ERROR for the latter configuration.

Edit: Updated the second log with DEBUG log level since it was missing originally.

RE: Max packet size when using bonding

kurtovic — Fri, 22 Sep 2023 10:11:14 GMT

Hi,

I believe I must have overlooked some other error after getting successful bonding. I'm able to revert back to the original values of 251/247, and everything appears to be working as expected still (even after deleting bonds).

Sorry for the mistake

RE: Max packet size when using bonding

Maria Gilje — Wed, 20 Sep 2023 08:07:44 GMT

Hello,

I am looking into this.

Best regards,

Maria