mesh shell errors provisioning over the air

RE: mesh shell errors provisioning over the air

AndyM — Wed, 11 Oct 2023 14:24:36 GMT

Thank you

RE: mesh shell errors provisioning over the air

tesc — Tue, 10 Oct 2023 14:27:44 GMT

Hi,

It seems the test was changed to == 9 earlier this year. This should eventually propagate to the release version of nRF Connect SDK: https://github.com/nrfconnect/sdk-zephyr/commit/e51a90934344dbae214cdd94a6130ce35246a550

Regards,
Terje

RE: mesh shell errors provisioning over the air

AndyM — Wed, 27 Sep 2023 14:16:41 GMT

Correct. I changed it to >=8 and was able to proceed further

RE: mesh shell errors provisioning over the air

tesc — Wed, 27 Sep 2023 14:12:10 GMT

Hi,

I can register a bug in our internal tracker.

Is it the check on line 1567 of zephyr/subsys/bluetooth/mesh/shell/cfg.c, in the function cmd_mod_pub(), which leads to error?

I.e. the first line of the following code:

	if (argc == 1 || argc == 8) {
		cid = shell_strtoul(argv[0], 0, &err);
		argc--;
		argv++;
	} else {
		cid = CID_NVAL;
	}

Regards,
Terje

RE: mesh shell errors provisioning over the air

AndyM — Wed, 27 Sep 2023 13:41:01 GMT

Thank you for pointing me to the doc

The code is still broken - because it expects exactly 8 parameters it prints an error and returns

Where do I file a bug?

Thank you

RE: mesh shell errors provisioning over the air

tesc — Tue, 26 Sep 2023 21:57:34 GMT

Hi,

It looks like this maps directly to "Number of Steps" and "Step resolution" in section 4.2.2.2 "Publish Period" of the Mesh Profile Specification v1.0.1.

"Number of Steps" is "PerSteps", and "Step resolution" is the same as in the description of "PerRes". The resulting publish period is specified as "Step Resolution" times "Number of Steps". In the case where "Number of Steps" equals 0 there will be no periodic publication.

Regards,
Terje

RE: mesh shell errors provisioning over the air

AndyM — Tue, 26 Sep 2023 15:41:23 GMT

Update

Found this description in SDK 2.4.2 documentation

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.2/zephyr/connectivity/bluetooth/api/mesh/shell.html

PerRes: Resolution of the publication period steps:
- 0x00: The Step Resolution is 100 milliseconds
- 0x01: The Step Resolution is 1 second
- 0x02: The Step Resolution is 10 seconds
- 0x03: The Step Resolution is 10 minutes
PerSteps: Number of publication period steps, or 0 to disable periodic publication.

Don't quite understand what "PerSteps" means here - can you give a couple of examples?

Generally it seems that this command should just take a number of seconds for a publication period and do the appropriate encoding internally - or just accept an already encoded value, as it used to in the previous versions

RE: mesh shell errors provisioning over the air

AndyM — Mon, 25 Sep 2023 23:45:01 GMT

Update

I changed the code on line 1587 in cfg.c from

if (argc == 1 || argc == 8) {

if (argc == 1 || argc >= 8) {

And now I can successfully set the publication parameters over the air.

Still need clarification for the res_steps and step parameter.

Mainly how to convert seconds to res_steps and step

Thank you