tests/bluetooth/mesh_shell : Cannot turn on advertising

[bschuster1031-nxp]

Describe the bug
Platform: FRDM-MCXW71
Running "mesh prov pb-adv on" (turn on advertising), I run into the error "Failed to enable PB-ADV"
uart:~$ mesh prov pb-adv on
Failed to enable PB-ADV (err -120)

To Reproduce
Steps to reproduce the behavior:

1. Flash the board with example
2. cFlash the board with the correct NBU
3. Type "mesh prov pb-adv on" in terminal
4. See error

Expected behavior
Supposed to enable PB-ADV

Impact
Cannot advertise

Logs and console output
*** Booting Zephyr OS build v4.0.0 ***
Initializing...
[00:00:00.034,000] fs_nvs: 8 Sectors of 8192 bytes
[00:00:00.034,000] fs_nvs: alloc wra: 0, 1e50
[00:00:00.034,000] fs_nvs: data wra: 0, 1d0
Press the button for supported commands.
Before any Mesh commands you must run "mesh init"
[00:00:00.062,000] bt_hci_core: No ID address. App must call settings_load()
Bluetooth initialized
[00:00:00.215,000] bt_mesh_access: Invalid vendor model index 0
[00:00:00.215,000] bt_mesh_access: Failed to get model for elem_idx 0 mod_idx 0
[00:00:00.215,000] settings: set-value failure. key: bt/mesh/v/0/sub error(-2)
[00:00:00.222,000] bt_hci_core: Identity: 00:60:37:3E:00:4D (public)
[00:00:00.222,000] bt_hci_core: HCI: version 5.3 (0x0c) revision 0x8300, manufacturer 0x0025
[00:00:00.222,000] bt_hci_core: LMP: version 5.3 (0x0c) subver 0x1400
Mesh initialized
Mesh network restored from flash
uart:~$ mesh

For a detailed description of the commands and arguments in this shell module,
please refer to the Zephyr Project documentation online.

mesh - Bluetooth Mesh shell commands
Subcommands:
init
reset-local
models : Model commands
lpn : Low Power commands
cdb : Configuration Database
proxy : Proxy commands
prov : Provisioning commands
test : Test commands
target : Target commands
stat : Statistic commands
uart:~$ mesh prov pb-adv on
Failed to enable PB-ADV (err -120)

Environment (please complete the following information):

• OS: Windows
• Toolchain Zephyrv4.0
• Commit SHA or Version used

Additional context

Tasks

Preview Give feedback

No tasks being tracked yet.

Tasks

Preview Give feedback

No tasks being tracked yet.

[github-actions]

Hi @bschuster1031-nxp! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[bschuster1031-nxp]

Using nRF connect and nRF mesh I also find that the mesh does not appear to show up

[carlescufi]

Using nRF connect and nRF mesh I also find that the mesh does not appear to show up

@PavelVPV @alxelax could you please confirm if this is reproduceable on Nordic hw?

[PavelVPV]

Since CDB is enabled, you need to execute mesh cdb create command in shell first.

[PavelVPV]

Sorry, I was wrong. -120 means that the device is already provisioned.

From the logs, it seems something was stored in the flash, so mesh thinks it is provisioned:

[00:00:00.215,000] bt_mesh_access: Invalid vendor model index 0
[00:00:00.215,000] bt_mesh_access: Failed to get model for elem_idx 0 mod_idx 0
[00:00:00.215,000] settings: set-value failure. key: bt/mesh/v/0/sub error(-2)

One reason why it could happen is that a new firmware with a different Composition Data was flashed to the already provisioned device without unprovisioning.

Mesh shell works in zephyr, just checked.