Peer manager rewrites peer data to flash on every connection, when using BLE privacy mode

RE: Peer manager rewrites peer data to flash on every connection, when using BLE privacy mode

00000000 — Fri, 29 Nov 2019 11:02:02 GMT

Yes.
I have done some further debugging by printing out all filesystem access.
It seems to me that in fact flash is NOT being written - although it seems from the debug out I have provided that it would be, in fact as we progress lower down the driver stack it actually isnt.
I am satisfied with the behavior for the moment.

RE: Peer manager rewrites peer data to flash on every connection, when using BLE privacy mode

Kenneth — Thu, 21 Nov 2019 17:15:11 GMT

Did you also erase the bond on the phone side?

RE: Peer manager rewrites peer data to flash on every connection, when using BLE privacy mode

00000000 — Thu, 21 Nov 2019 11:29:40 GMT

Yes, and no luck :-(

RE: Peer manager rewrites peer data to flash on every connection, when using BLE privacy mode

Kenneth — Thu, 21 Nov 2019 11:02:43 GMT

Did you do an "nrfjprog --eraseall"? Since you will need to re-bond if you do this kind of change.

Kenneth

RE: Peer manager rewrites peer data to flash on every connection, when using BLE privacy mode

00000000 — Thu, 21 Nov 2019 09:23:51 GMT

I dont like the idea that flash must be written upon every connection, are you able to confirm whether or not his is necessary?
I tried your suggestion and set PM_PEER_RANKS_ENABLED to 0. The result is that after an initial pair/bond, subsequent connections are rejected:

<info> app: Connected.
<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Pairing, error: 133
<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 133

RE: Peer manager rewrites peer data to flash on every connection, when using BLE privacy mode

Kenneth — Mon, 18 Nov 2019 12:54:04 GMT

I don't think you will be wearing out the flash, since the data we stored using FDS, which will store the updated data to a new location every time (until a flash is full,then it will do a garbage collection to clean up the flash). That said, you may likely avoid this by setting PM_PEER_RANKS_ENABLED 0.