Bonding procedure returns NRF_ERROR_STORAGE_FULL (peer manager)

RE: Bonding procedure returns NRF_ERROR_STORAGE_FULL (peer manager)

Jonathan — Thu, 10 Jan 2019 19:46:59 GMT

This error was occurring when using a Galaxy S6 for OOB pairing. There is no mechanism to erase the bluetooth cache so i am wondering if it had to do with the S6 not deleting it's pairing/bonding entry. I tried everything including erasing the phones cache through the boot menus and nothing would work. I tried my coworkers S9 and it pairs and bonds successfully every time. I am going to assume this is an issue with the phone I was using for testing.

RE: Bonding procedure returns NRF_ERROR_STORAGE_FULL (peer manager)

Jonathan — Thu, 10 Jan 2019 15:41:42 GMT

I have changed the experimental example ble_app_hrs_nfc_pairing to use

#define NFC_PAIRING_MODE NFC_PAIRING_MODE_OOB

instead of

#define NFC_PAIRING_MODE NFC_PAIRING_MODE_JUST_WORKS

and I am seeing the same error.

[Jan 10 09:33:51.601] <info> app: Heart Rate Sensor example started.
[Jan 10 09:34:08.269] <info> app: Connected
[Jan 10 09:34:08.899] heral, conn_handle: 0x0, procedure: Bonding, error: 132
[Jan 10 09:34:08.900] <info> app: Authorization failed with code: 132!

I also noticed in all of the examples using NFC pairing, there is no initiation of the security parameters. Is this done automatically with the nfc_ble_pair_init() api, or are we supposed to use the pm_sec_params_set() API? If so do we set this before nfc_ble_pair_init()?

RE: Bonding procedure returns NRF_ERROR_STORAGE_FULL (peer manager)

haakonsh — Thu, 10 Jan 2019 12:53:17 GMT

You need to step through the peer manager and find out where and why NRF_ERROR_STORAGE_FULL is returned.

RE: Bonding procedure returns NRF_ERROR_STORAGE_FULL (peer manager)

Jonathan — Wed, 09 Jan 2019 19:35:31 GMT

It is not related because there is no garbage to collect. I am getting this error consistently on the first pair attempt. Flash is completely erased every time I load the firmware and I can not successfully pair.

RE: Bonding procedure returns NRF_ERROR_STORAGE_FULL (peer manager)

catsunami — Wed, 09 Jan 2019 17:57:29 GMT

It's not related to this by any chance, is it? devzone.nordicsemi.com/.../nrf_error_storage_full-in-ble-central-code. Or maybe it has the same solution? Have you tried running garbage collection?