Peer manager and Softdevice

[GOAA]

Hello,

Sorry for this long question but these questions are bothering me and I need these to carry on with my project.

1) What is the peer manager's device identity list. I understand whitelist but what is device identity

2) When will PM_EVT_CONN_SEC_CONFIG_REQ be triggered. I tried various combinations multiple times but not once was it triggered. I need this to know whether or not to enable pairing when that event fires.

3) In the NUS service, in the peripheral side why is BLE_NUS_EVT_TX_RDY being triggered via the event handler every time? Its written "Service is ready to accept new data to be transmitted". Does that mean that the central is sending an empty packet to the peripheral for start of the connection event (as per Bluetooth protocols)?

4) In the softdevice release notes its given that we have to modify the SEVOPEND flag for priorities>6. I dont see that anywhere being done in the BLE NUS example nor the heart rate example.

Thanks a Ton in advance

[Amanda Hsieh]

Hi, 

1. Device identity list is used for tracking Identity Resolving Key (IRK) device. 

2. The default behavior in the example is to reject pairing request from an already bonded peer. If the bone or pair info is deleted on the central side like the phone and the central would like to connect the device, it will get the PM_EVT_CONN_SEC_CONFIG_REQ. When deleting bond or pair info, you have to delete the info on both sides (central and peripheral).

3. Which SDK and example do you refer to? 

4. The Priority setting is in the sdk_config.h, but I don't know what is SEVOPEND flag. What do you mean "SEVOPEND flag"?

Please note that due to the Easter holiday, we're low on staff, so somewhat lower response times must be expected until April 6th. Sorry about the inconvenience.

-Amanda H.

[GOAA]

Thank you for your response

Amanda Hsieh said:

Device identity list is used for tracking Identity Resolving Key (IRK) device. 

As per my understanding, this gets exchanged whenever the devices are bonded. Since the devices are bonded, if I advertise and scan with whitelist, is the device address random static or private resolvable. Or is it dependent on how I configure?

Amanda Hsieh said:

Which SDK and example do you refer to?

SDK 15.0.0 nordic UART service. I modified it to send data based on timer but whenever I send that data, I get BLE_NUS_EVT_TX_RDY event as explained above.

Amanda Hsieh said:

What do you mean "SEVOPEND flag"?

Sorry, my bad. I meant SEVONPEND.

[Amanda Hsieh]

Hi, 

GOAA said:

is the device address random static or private resolvable. Or is it dependent on how I configure?

It depends on your setting.  

 

3) In the NUS service, in the peripheral side why is BLE_NUS_EVT_TX_RDY being triggered via the event handler every time? Its written "Service is ready to accept new data to be transmitted". Does that mean that the central is sending an empty packet to the peripheral for start of the connection event (as per Bluetooth protocols)?

When the BLE_GATTS_EVT_HVN_TX_COMPLETE event is generated, that causes the NUS data handler to be called with event BLE_NUS_EVT_TX_RDY to indicate TX data has been sent over BLE.

 

4) In the softdevice release notes its given that we have to modify the SEVOPEND flag for priorities>6. I dont see that anywhere being done in the BLE NUS example nor the heart rate example.

 You cannot change the priority levels used by the softdevice. Here is some information about what levels are being used: S132 Interrupt priority levels. See this post and this post. 

-Amanda H.