Random Bonding problem

RE: Random Bonding problem

Vidar Berg — Fri, 14 Feb 2025 11:24:25 GMT

[quote user="DaniSi"]Ok, I've reverted back. We will probably need some more time to again verify if the problem still persist.[/quote]

Sounds good thanks. You will not get the exact same error at least.

[quote user="DaniSi"]

The assert happens at the same spot as I wrote in the first topic. In the modified code this was line 300

err_code = sd_ble_gatts_sys_attr_get(conn_handle, sys_attr_data, &len, peer_data.p_local_gatt_db->flags);

ASSERT(err_code == NRF_SUCCESS);

[/quote]

I see. I realize now that it is from the code I posted and that it does not exist in the original SDK 17.1.0 code which I was looking at.

RE: Random Bonding problem

DaniSi — Fri, 14 Feb 2025 09:35:29 GMT

[quote userid="4240" url="~/f/nordic-q-a/118678/random-bonding-problem/522995"]I recommend reverting your changes to the peer manager if it's not too late and use the official fix which was tested as a part of the SDK release.[/quote]

Ok, I've reverted back. We will probably need some more time to again verify if the problem still persist.

[quote userid="4240" url="~/f/nordic-q-a/118678/random-bonding-problem/522995"]This indicates that the attribute table has changed. Was there anything that happened prior to this (e.g., a device firmware update)? [/quote]

The last scenario occurred during development. We have different branches so maybe attribute table has changed, but I cant confirm. But we got already a report that suddenly crashes started occurring with no changes in attribute table.

[quote userid="4240" url="~/f/nordic-q-a/118678/random-bonding-problem/522995"]What is the ASSERT you have at this line? This is also different from the error you reported initially. [/quote]

The assert happens at the same spot as I wrote in the first topic. In the modified code this was line 300

err_code = sd_ble_gatts_sys_attr_get(conn_handle, sys_attr_data, &len, peer_data.p_local_gatt_db->flags);

ASSERT(err_code == NRF_SUCCESS);

RE: Random Bonding problem

Vidar Berg — Fri, 14 Feb 2025 09:17:16 GMT

Hi,

The issue discussed in the linked Q&A was already fixed in nRF5 SDK 17.1.0:

*** Bug fixes
****************

NRFFOETT-2519: The local db data will not be written to flash if it is already up to date.
This means that if a client updates a CCCD to the same value as before,
no flash operation will happen.

I recommend reverting your changes to the peer manager if it's not too late and use the official fix which was tested as a part of the SDK release.

[quote user="DaniSi"][1;33m<warning> peer_manager_gcm: The local database has changed, so some subscriptions to notifications and indications could not be restored for conn_handle 0[0m
[1;33m<warning> peer_manager_handler: Local DB could not be applied: conn_handle: 0, peer_id: 0[0m[/quote]

This indicates that the attribute table has changed. Was there anything that happened prior to this (e.g., a device firmware update)?

[quote user="DaniSi"][1;31m<error> app: ASSERTION FAILED at /home/dani/projects/tq/hpr-disp-04-05-fw/nRF5-SDK/components/ble/peer_manager/gatt_cache_manager.c:300[/quote]

What is the ASSERT you have at this line? This is also different from the error you reported initially.

RE: Random Bonding problem

DaniSi — Wed, 12 Feb 2025 09:23:38 GMT

Hi Vidar,

It took us a while to reproduce it again, and once more I can confirm the error code=12. Bellow are the logs:
[0m<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change[0m
[1;33m<warning> peer_manager_gcm: The local database has changed, so some subscriptions to notifications and indications could not be restored for conn_handle 0[0m
[1;33m<warning> peer_manager_handler: Local DB could not be applied: conn_handle: 0, peer_id: 0[0m
[0m<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Encryption[0m
[0m<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change[0m
[1;31m<error> app: ASSERTION FAILED at /home/dani/projects/tq/hpr-disp-04-05-fw/nRF5-SDK/components/ble/peer_manager/gatt_cache_manager.c:300

I forgot to mention that we have included the fix
RE: Peer manager and FDS, new records at each connection.

which as I see now was implemented by you.

Additionally, I noticed that this is caused by the 0x2902 Service changed.

RE: Random Bonding problem

Vidar Berg — Fri, 07 Feb 2025 06:44:36 GMT

Hello,

It is not clear how the program is crashing even if sd_ble_gatts_sys_attr_get() is returning with NRF_ERROR_DATA_SIZE. Are you able to get debug logs from the device? And does the program enter the app_error_fault_handler()?

Best regards,

Vidar