RE: sd_ble_gap_connect with BLE_GAP_PHY_2MBPS causes SOFTDEVICE: ASSERTION FAILED

jsample — Wed, 22 Aug 2018 14:29:34 GMT

Hi Sigurd,

I would suggest maybe just changing the API documentation, because it seems like the sd_ble_gap_connect case behaves just like the sd_ble_gap_scan_start case where you're basically just setting what primary phys will be used during scanning. Unless the intent was to allow the user to not allow connections to be made on the 2Mbps phy by leaving it out of scan_phys in the sd_ble_gap_connect case, but it doesn't seem to behave that way currently.

John

RE: sd_ble_gap_connect with BLE_GAP_PHY_2MBPS causes SOFTDEVICE: ASSERTION FAILED

Sigurd — Tue, 21 Aug 2018 16:16:06 GMT

Hi,

Thank you for reporting this softdevice assertion.

[quote userid="8282" url="~/f/nordic-q-a/37563/sd_ble_gap_connect-with-ble_gap_phy_2mbps-causes-softdevice-assertion-failed"]but when I call sd_ble_gap_connect I get a SOFTDEVICE: ASSERTION FAILED error. Should this work? [/quote]

I think that the function should have returned NRF_ERROR_INVALID_PARAM in this case. I will add a new reply here when I have verified this.

The scan_phys is used for the primary advertising channels. The scanner will accept all types of PHY’s for the secondary advertising channel PHYs, independent on the PHYs used in scan_phys. So the connection will be established on the secondary_phy, even if the secondary_phy is not a part of the scan_phys. So yes, you are connected on 2MBPS.
The scanner can see what the secondary_phy is set to in the advertising report. To know what phy you are currently on, you can try to do a phy update to the phy that you would like to use.

Update:
The API documentation states that scan_phys may be set to 2MBPS. If the SoftDevice assert for this configuration, this means that it is a SoftDevice bug. This bug does however not restrict any use-cases because 2Mbps is not used in scanning anyways. It was allowed in the API only to simplify application code.