Using Whitelist with undirected advertising returns NRF_ERROR_INVALID_PARAM

RE: Using Whitelist with undirected advertising returns NRF_ERROR_INVALID_PARAM

Niclas Heitz — Tue, 04 Dec 2018 10:13:46 GMT

Hi Einar,

it seems we had a slight error in our test, so that the whitelist was indeed not set correctly. I assume the previous SD didn't had the "!whitelist" check since the test worked there.

Anyway, thank you for your help it made the behaviour much more understandable.

Best regards,

Niclas

RE: Using Whitelist with undirected advertising returns NRF_ERROR_INVALID_PARAM

Einar Thorsrud — Tue, 04 Dec 2018 07:28:35 GMT

Hi Niclas,

The reason is that if you use anything other than BLE_GAP_ADV_FP_ANY, you need a filtering method, either whitelist or directed advertising. The check in the SD is similar to this:

if (!direct_advertising &&
    filter_policy != BLE_GAP_ADV_FP_ANY &&
    !whitelist)
{
    return NRF_ERROR_INVALID_PARAM;
}

I have suggested ot the SoftDevice developers that the API documentation should be updated.

RE: Using Whitelist with undirected advertising returns NRF_ERROR_INVALID_PARAM

Niclas Heitz — Mon, 03 Dec 2018 15:21:49 GMT

Hi Einar,

yes we configuered a whitelist, as i said in my OP we use pm_whitelist_set() to configure it. This seems to work with our old firmware using SDK12. I will try to verify that the whitelist is actually set but at least the function returns success.

Was there no check if the whitelist is set in the old function? Otherwise I can't explain why it was working since the parameters given where the same.

Also why is it working with BLE_GAP_ADV_TYPE_CONNECTABLE_NONSCANNABLE_DIRECTED? Is the filter policy ignored for direct advertising? It would make sense, but there's nothing in the documentation.

Thanks,

Niclas

RE: Using Whitelist with undirected advertising returns NRF_ERROR_INVALID_PARAM

Einar Thorsrud — Mon, 03 Dec 2018 13:46:02 GMT

Hi Niclas,

Have you configured a whitelist before the call to sd_ble_gap_adv_set_configure()? You will get NRF_ERROR_INVALID_PARAM from sd_ble_gap_adv_set_configure() if you use anything other than BLE_GAP_ADV_FP_ANY when no whitelist is set. This makes sense, as there is nothing to filter on without a whitelist, but I agree that it should have been stated in the API documentation. I will create an internal ticket suggesting that the API documentation is updated.

Einar