"Failed enabling advertiser" when running mesh provisioner on nRF5340

RE: "Failed enabling advertiser" when running mesh provisioner on nRF5340

Simonr — Tue, 01 Mar 2022 09:33:19 GMT

Sorry about the late reply, but I was out of office on Friday, and had some catching up to do.

No, extended advertising is not part of the Mesh stack. This is by specification. See this case by my colleague Terje for more details.

I can't find any mention of a config called CONFIG_BT_MESH_EXT_ADV. I think you need to enable/disable extended advertising (with CONFIG_BT_EXT_ADV) whenever you switch between Mesh and Direction Finding.

Best regards,

Simon

RE: "Failed enabling advertiser" when running mesh provisioner on nRF5340

unkn0wnerr0r — Mon, 28 Feb 2022 09:08:41 GMT

Hi Simon,

Any updates?

RE: "Failed enabling advertiser" when running mesh provisioner on nRF5340

unkn0wnerr0r — Fri, 25 Feb 2022 12:12:59 GMT

Hi Simon,

After some experiments, I think I know the reason.

Since Direction Finding relies on Extended Advertising, configuring this in prj.conf would automatically switch on CONFIG_BT_MESH_EXT_ADV. And from what I see, mesh samples both in NRF Connect SDK and in Zephyr are on Legacy Advertising.

Is there a support for Bluetooth Mesh extended advertising for nRF5340?

RE: "Failed enabling advertiser" when running mesh provisioner on nRF5340

unkn0wnerr0r — Thu, 24 Feb 2022 09:48:32 GMT

[quote userid="75734" url="~/f/nordic-q-a/85041/failed-enabling-advertiser-when-running-mesh-provisioner-on-nrf5340/354740#354740"]How do you initialize the Mesh stack before calling this "bt_mesh_main" function, and how does your bt_mesh_main function look?[/quote]

"bt_mesh_main" isn't a function, it's a log module of zephyr/subsys/bluetooth/mesh/main.c. The function calling this is bt_mesh_start:

int bt_mesh_start(void)
{
	int err;

	err = bt_mesh_adv_enable();
	if (err) {
		BT_ERR("Failed enabling advertiser");
		return err;
	}

	if (bt_mesh_beacon_enabled()) {
		bt_mesh_beacon_enable();
	} else {
		bt_mesh_beacon_disable();
	}

	if (!IS_ENABLED(CONFIG_BT_MESH_PROV) || !bt_mesh_prov_active() ||
	    bt_mesh_prov_link.bearer->type == BT_MESH_PROV_ADV) {
		if (IS_ENABLED(CONFIG_BT_MESH_PB_GATT)) {
			(void)bt_mesh_pb_gatt_disable();
		}

		if (IS_ENABLED(CONFIG_BT_MESH_GATT_PROXY)) {
			(void)bt_mesh_proxy_gatt_enable();
			bt_mesh_adv_gatt_update();
		}
	}

	if (IS_ENABLED(CONFIG_BT_MESH_LOW_POWER)) {
		bt_mesh_lpn_init();
	} else {
		bt_mesh_scan_enable();
	}

	if (IS_ENABLED(CONFIG_BT_MESH_FRIEND)) {
		bt_mesh_friend_init();
	}

	if (IS_ENABLED(CONFIG_BT_MESH_PROV)) {
		struct bt_mesh_subnet *sub = bt_mesh_subnet_next(NULL);
		uint16_t addr = bt_mesh_primary_addr();

		bt_mesh_prov_complete(sub->net_idx, addr);
	}

	bt_mesh_hb_start();

	bt_mesh_model_foreach(model_start, NULL);

	return 0;
}

It is triggered when calling bt_mesh_adv_enable(). So when bt_ready_prov function is called, it calls bt_mesh_provision, the the stack follows like this: bt_mesh_adv_enable() (in adv_ext.c) -> bt_le_ext_adv_create() -> le_ext_adv_param_set (in adv.c) -> bt_hci_cmd_send_sync() -> bt_hci_cmd_send_sync (in hci_core.c)

As for mesh stack inilialisation, here are the prov and comp objects passed to bt_ready_prov:

/* This application only needs one element to contain its models */
struct bt_mesh_model models[] = {
	BT_MESH_MODEL_CFG_SRV,
        BT_MESH_MODEL_CFG_CLI(&cfg_cli),
        BT_MESH_MODEL_HEALTH_CLI(&health_cli_prov),
	BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub),
	BT_MESH_MODEL(BT_MESH_MODEL_ID_GEN_ONOFF_SRV, gen_onoff_srv_op, &gen_onoff_srv_pub,
		      NULL),
	BT_MESH_MODEL(BT_MESH_MODEL_ID_GEN_ONOFF_CLI, gen_onoff_cli_op, &gen_onoff_cli_pub,
		      NULL),
        BT_MESH_MODEL(BT_MESH_MODEL_ID_GEN_LEVEL_SRV, gen_level_srv_op, &gen_level_srv_pub,
		      NULL),
        BT_MESH_MODEL(BT_MESH_MODEL_ID_GEN_LEVEL_CLI, gen_level_cli_op, &gen_level_cli_pub,
		      NULL),
        BT_MESH_MODEL_VND(ATAMATE_CID, VND_CLI_MODEL_ID, vnd_cli_ops, &gen_level_vnd_pub, &vnd_user_data),
};

struct bt_mesh_elem elements[] = {
	BT_MESH_ELEM(0, models, BT_MESH_MODEL_NONE),
};

const struct bt_mesh_comp comp = {
	.cid = BT_COMP_ID_LF,
	.elem = elements,
	.elem_count = ARRAY_SIZE(elements),
};


static void unprovisioned_beacon(uint8_t uuid[16],
				 bt_mesh_prov_oob_info_t oob_info,
				 uint32_t *uri_hash)
{
	memcpy(node_uuid, uuid, 16);
	k_sem_give(&sem_unprov_beacon);
}

static void node_added(uint16_t net_idx, uint8_t uuid[16], uint16_t addr, uint8_t num_elem)
{
	node_addr = addr;
	k_sem_give(&sem_node_added);
}


const struct bt_mesh_prov provisioner = {
	.uuid = dev_uuid,
        .unprovisioned_beacon = unprovisioned_beacon,
        .node_added = node_added,
};

Except for the bigger number of mesh models and its implementation (which I did based on samples and walkthroughs), the rest is based on Zephyr samples.

[quote userid="75734" url="~/f/nordic-q-a/85041/failed-enabling-advertiser-when-running-mesh-provisioner-on-nrf5340/354740#354740"]4. Yes, -5 is an I/O error, what exact function returns this. If you don't have an antenna array connected to the nRF53 device (which is required on the RX side in an AoA application).[/quote]

It's actually called not because of Direction Finding, but because of mesh initialisation. The function I mentioned above, bt_mesh_adv_enable(), returns that error. Which, in fact, gets that error from.

P.S: about antenna array - you mean configuring it like it's described here developer.nordicsemi.com/.../README.html ? I've done that

P.P.S: is it possible that some configuration options might prevent from working correctly?

RE: "Failed enabling advertiser" when running mesh provisioner on nRF5340

Simonr — Thu, 24 Feb 2022 09:05:20 GMT

1 & 2. Okay, then it doesn't seem to be a conflict between Direction Finding and Mesh, but rather something in the Mesh side of the application not working as intended. How do you initialize the Mesh stack before calling this "bt_mesh_main" function, and how does your bt_mesh_main function look?

3. I see, it will be hard to debug this without knowing what exact function returns this.

4. Yes, -5 is an I/O error, what exact function returns this. If you don't have an antenna array connected to the nRF53 device (which is required on the RX side in an AoA application).

Best regards,

Simon

RE: "Failed enabling advertiser" when running mesh provisioner on nRF5340

unkn0wnerr0r — Wed, 23 Feb 2022 14:36:14 GMT

[quote userid="75734" url="~/f/nordic-q-a/85041/failed-enabling-advertiser-when-running-mesh-provisioner-on-nrf5340/354614#354614"]I have a few questions here. First off, the nRF52840 doesn't support the Direction Finding (introduced in BLE 5.1) so it seems strange that the locator application would work with that board at all. [/quote]

It doesn't. But I've had in CMakeLists.txt and in the code itself safety measures, such as "if the chosen board isn't nRF5340, then all direction finding code won't be included in the project". That had no issues. So basically when I ran this code in nRF52840, anything related to direction finding isn't there and it runs only provisioner.

[quote userid="75734" url="~/f/nordic-q-a/85041/failed-enabling-advertiser-when-running-mesh-provisioner-on-nrf5340/354614#354614"]is this advertising happening in over Bluetooth Mesh?[/quote]

I guess so, because the code was supposed to launch mesh provisioner.

[quote userid="75734" url="~/f/nordic-q-a/85041/failed-enabling-advertiser-when-running-mesh-provisioner-on-nrf5340/354614#354614"]The error from your log does not seem to be related to advertising but rather an error from a log line with "direction_rx" (which I can't find in the nRF Connect SDK). Have you added this logging line yourself?[/quote]

"direction_rx" is basically the sample code from direction_finding_connectionless_rx from the Nordic samples. Only thing I changed was to rename "main" to a different function so I could run it as a thread.

[quote userid="75734" url="~/f/nordic-q-a/85041/failed-enabling-advertiser-when-running-mesh-provisioner-on-nrf5340/354614#354614"]Are you able to see what the err -5 returns as? What NCS version are you working on?[/quote]

-5 is EIO, which is weird for me. NCS is the latest one, 1.9.0.

[quote userid="75734" url="~/f/nordic-q-a/85041/failed-enabling-advertiser-when-running-mesh-provisioner-on-nrf5340/354614#354614"]Lastly, Bluetooth Mesh and Direction Finding features are not trivial to combine I'm afraid, since they both use timeslots they will likely have quite a few conflicts on time critical tasks, so you need to use something like the MPSL timeslot functionality to handle correctly.[/quote]

Duly noted, I'll look at this, thanks!

P.S: even if I comment the thread initialisation for Direction Finding so it could run only provisioner, it still throws "Failed enabling advertiser". Could there be something around configuration files? I have a regular "prj.conf", and "hci_rpmg.conf" in "child_image" folder which is copied from Direction Finding sample. Also, if I run a sample of mesh_provisioner from Zephyr samples, during the provision of another remote device it reboots throwing stack overflow error and hard reset.

RE: "Failed enabling advertiser" when running mesh provisioner on nRF5340

Simonr — Wed, 23 Feb 2022 14:07:49 GMT

I have a few questions here. First off, the nRF52840 doesn't support the Direction Finding (introduced in BLE 5.1) so it seems strange that the locator application would work with that board at all.

Secondly, you say that the error you see is "Failed enabling advertiser" but the Direction Finding locator doesn't advertise, is this advertising happening in over Bluetooth Mesh? The error from your log does not seem to be related to advertising but rather an error from a log line with "direction_rx" (which I can't find in the nRF Connect SDK). Have you added this logging line yourself? Are you able to see what the err -5 returns as? What NCS version are you working on?

Lastly, Bluetooth Mesh and Direction Finding features are not trivial to combine I'm afraid, since they both use timeslots they will likely have quite a few conflicts on time critical tasks, so you need to use something like the MPSL timeslot functionality to handle correctly.

Best regards,

Simon