This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

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.

  • We are very much disappointed with the way NRF5340 has been released with incomplete support.

    1. Being unable to set up the BLE Mesh light switch and incompatible PWM example for NRF5340PDK v0.8.0, we tried custom PWM.

    Later we got to know even PWM3 is also not available in NRF5340PDK and fixed in a later release.

    We ordered 4 NRF5340, knowing that all BLE Mesh examples, PWM is supported, but nothing is working and issues are seen later.

    Is there any exchange program for NRF5340DK with NRF5340PDK? We need a minimum of 4 PWM, 2 SPI, and 2 I2C instances to get started with application building. But unsure of what to do with this deprecated NRF5340PDK.

  • Hi,

    Most of the earlier questions you posted should be solved by switching to nRF5340DKs. The nRF5340PDKs are preview kits and are deprecated for the later versions of NCS. The first thing would be to go over to the nRF5340DKs. 

    Unfortunately, we do not have any mesh specific guide for the nRF5340, but the nRF53 User Guide has a lot of setup information that is helpful.

    new said:
    I lately found that mesh light control, mesh sensor client, mesh sensor server not supported for NRF5340 and got disappointed. I expected those features for NRF5340. Do these examples support NRF5340 in the future connect SDK releases?

    new said:
    Is there any exchange program for NRF5340DK with NRF5340PDK?

    As for future roadmap questions and exchanging PDKs for DKs, I suggest you contact your RSM(Regional Sales Manager) about this. You can do this by using this link: Contact Us and make a a ticket under "Sales Related questions". 

  • 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
Related