Advertising interferes with advertising in non-whitelisted mode

RE: Advertising interferes with advertising in non-whitelisted mode

emb_dev — Wed, 10 Feb 2021 08:08:34 GMT

It is set in the init function - it is adapted from the examples and was not suggested. Disabling it prevents the problem from happening which is a possible solution in our case.

Out of interest: Shouldn't it work with the directed advertising as well?

init.config.ble_adv_directed_enabled = true;
init.config.ble_adv_directed_interval = APP_ADV_DIRECTED_INTERVAL;
init.config.ble_adv_directed_timeout = APP_ADV_DIRECTED_DURATION;

RE: Advertising interferes with advertising in non-whitelisted mode

Edvin — Tue, 09 Feb 2021 20:54:28 GMT

Try setting it to undirected (BLE_ADV_MODE_FAST)

How are you setting this in the first place, and where did you find the implementation to suggest it? I can't see any of the examples that do this by default.

Best regards,

Edvin

RE: Advertising interferes with advertising in non-whitelisted mode

emb_dev — Tue, 09 Feb 2021 13:57:42 GMT

I found out that calling the ble_advertising_restart_without_whitelist function is only problematic if the advertising mode is BLE_ADV_MODE_DIRECTED. Does that help any further?

RE: Advertising interferes with advertising in non-whitelisted mode

emb_dev — Tue, 09 Feb 2021 12:25:17 GMT

The call to flags_set:

static ret_code_t flags_set(ble_advertising_t * const p_advertising, uint8_t flags)

So I have seen the description of the invalid param:

* @retval ::NRF_ERROR_INVALID_PARAM                   Invalid parameter(s) supplied:
*                                                      - Invalid advertising data configuration specified. See @ref ble_gap_adv_data_t.
*                                                      - Invalid configuration of p_adv_params. See @ref ble_gap_adv_params_t.
*                                                      - Use of whitelist requested but whitelist has not been set,
*                                                        see @ref sd_ble_gap_whitelist_set.




But the configuration is right because otherwise the advertising would not work at all if I get this right. And also the whitelist has been set when the error happens.

RE: Advertising interferes with advertising in non-whitelisted mode

Edvin — Tue, 09 Feb 2021 11:06:30 GMT

What call inside ble_advertising_restart_without_whitelist() returns NRF_ERROR_INVALID_PARAM?

RE: Advertising interferes with advertising in non-whitelisted mode

emb_dev — Mon, 08 Feb 2021 15:17:16 GMT

I need to correct myself, the debugger gave the error earlier. With debugging over logging, the error happens in the function

ret = flags_set(p_advertising, BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE); 

inside

uint32_t ble_advertising_restart_without_whitelist(ble_advertising_t * const p_advertising)

RE: Advertising interferes with advertising in non-whitelisted mode

emb_dev — Mon, 08 Feb 2021 14:54:32 GMT

Hello,

yes, that is the problem.

Disabling the advertising on disconnects prevents the error from happening. But we actually need the functionality to advertise upon disconnect.

When debugging, the problem arises in the function:

(void) sd_ble_gap_adv_stop(p_advertising->adv_handle);

RE: Advertising interferes with advertising in non-whitelisted mode

Edvin — Mon, 08 Feb 2021 14:39:25 GMT

Hello,

I am not sure I understood correctly, but is the issue that you are starting your advertisements from two places at once? That typically triggers an NRF_ERROR_INVALID_STATE, and not the NRF_ERROR_INVALID_PARAM, but in case that is the issue, try adding the following option in your advertising_init() function:

init.config.ble_adv_on_disconnect_disabled = true;

If that is not the issue, then there is something wrong with your advertising set.Try to debug ble_advertising_start() and ble_advertising_restart_without_whitelist() and see what function call that returns the value NRF_ERROR_INVALID_PARAM.

Best regards,

Edvin