NRF5340 BLE Mesh setup problem in nrf connect sdk v1.4.99-dev1

[new]

We bought 4 NRF5340 PDK and trying to setup BLE mesh.
As suggested in the getting started guide, there are two BLE mesh example samples from nordic and zephyr.
However, for common BLE examples, it is said that before building any example it is better to program hci_rpmsg to the network core. But it is not mentioned how to configure for BLE mesh examples.
I was able to run BLE mesh light example once but afterward, the board was not recognized in mobile even after rebuilding.

When I tried to flash other board with BLE mesh light control or light switch build error halts the process in "lc_pwm_led.c": 'unsupported board: PWM-led0 device tree alias is not defined".
I would like to know how to correctly set up the BLE mesh light control and BLE mesh light on the board. Following the getting started guide is incomplete.
Other questions like, how to reset the mesh light back to an unprovisioned state after once provisioned.
If we are using nordic BLE sample examples 'light, light control, light switch', is there any guide that how to add more resources such as SPI/i2c, ADC to the same.
Do nordic BLE mesh example uses soft device or HCI of zephyr. What should be the correct configuration to get sample BLE mesh light-light control running?

Thank you.

[Mttrinh]

Hi,

Answering your initial post:

A correction to the thread I referred to in my previous reply. It seems like after NCS v1.4, Mesh samples should run with the default config on the network core

Note that the Bluetooth: Mesh Light Control example does not support the nRF5340. This is not an issue with the mesh stack itself, but the way the sample interacts with the hardware.

how to reset the mesh light back to an unprovisioned state after once provisioned.

You can reset the device to an unprovisioned state by calling bt_mesh_reset().

If we are using nordic BLE sample examples 'light, light control, light switch', is there any guide that how to add more resources such as SPI/i2c, ADC to the same.

There are no specific guide for this but perhaps look at the zephyr documentation, including the devicetree guide, and the device model. There are a lot of samples on driver usage both in NCS and Zephyr, those are a good starting point. There's nothing about the mesh stack that should interfere with the HW drivers.

new said:

Also, how to see debug output in nordic specific embedded studio for NRF_CONNECT_SDK examples. No RTT settings seen and project options are disable or un-selectable (greyed out).

Try adding "CONFIG_SERIAL=y" to prj.conf.

I will come back to you regarding the other questions soon.

[Mttrinh]

Add these lines to prj.conf to see printk output in SES Debug Console:

# Config logger

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y

CONFIG_LOG_BACKEND_UART=n

CONFIG_SERIAL=y