This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

should ble_app_rscs store bond info?

I'm experimenting with the relay as well as hrs and rscs demos. Basically, I want to check at startup for IRKs stored in flash on startup in the peripherals. I'm only working on the rscs demo at the moment. Taking a step back, should I expect the ble_app_rscs demo to store bond information in flash? I have debug tracing turned on and in one instance I saw that there was an IRK value stored on my device acting as the rscs after pairing with the relay device, but I have since not been able to repeat it.

Parents
  • Yes, the bond info should be stored in flash. Either the IRK if the peer uses a private resolvable address, or the device address if the peer uses a static address. Note that once saved this will be stored in flash and used in all subsequent connections. So you have to delete it on both peers, if you want to see it written to flash again (the devices will bond again in this case).

  • You could use a static address in the whitelist for both the scanning and advertising device. In addition you could use MITM with a pre shared static passkey (this is configured in the options api).

    It is possible to configure a private resolvable address as well, but the given address is ignored and the SoftDevice will generate a new private address automatically every BLE_GAP_DEFAULT_PRIVATE_ADDR_CYCLE_INTERVAL_S seconds.

Reply
  • You could use a static address in the whitelist for both the scanning and advertising device. In addition you could use MITM with a pre shared static passkey (this is configured in the options api).

    It is possible to configure a private resolvable address as well, but the given address is ignored and the SoftDevice will generate a new private address automatically every BLE_GAP_DEFAULT_PRIVATE_ADDR_CYCLE_INTERVAL_S seconds.

Children
No Data
Related