Problem with ligitswitch example in nrf52 MDK

[anilkunchalaece]

Hi,

I am trying to run lightswitch example in MDK.

Provisioner keep logging : 419, Unhandled Mesh Event: 4 

Button 1 is in on state.

and LD5 is keep blinking.

these are the logs.

For Provisioner 

 0> <t:          0>, main.c,  561, ----- BLE Mesh Light Switch Provisioner Demo -----
 0> <t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
 0> <t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
 0> <t:         15>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
 0> <t:        577>, main.c,  499, Initializing and adding models
 0> <t:        609>, main.c,  452, Restored: App data
 0> <t:        611>, main.c,  551, Restored: Handles 
 0> <t:        613>, provisioner_helper.c,  307, m_netkey_handle:0 m_appkey_handle:0 m_self_devkey_handle:1
 0> <t:        620>, main.c,  591, <start> 
 0> <t:        700>, main.c,  404, Mesh evt: FLASH_STABLE 
 0> <t:        702>, main.c,  578, Starting application ...
 0> <t:        704>, main.c,  580, Provisoned Nodes: 2, Configured Nodes: 2 Next Address: 0x0104
 0> <t:        709>, main.c,  581, Dev key : BA8A926F3954726A5860877723B1D450
 0> <t:        712>, main.c,  582, Net key : 482EF1D4CC88EDC4005CB3B97C6D3B55
 0> <t:        715>, main.c,  583, <t:     434364>, main.c,  459, Button 1 pressed
 0> <t:     434367>, main.c,  376, Waiting for Server node to be provisioned ...
 0> <t:     439130>, provisioner_helper.c,  288, Scanning For Unprovisioned Devices
 0> <t:    4112430>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    4740808>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    5399402>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    6060547>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:          0>, main.c,  561, ----- BLE Mesh Light Switch Provisioner Demo -----
 0> <t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
 0> <t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
 0> <t:         16>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
 0> <t:        571>, main.c,  499, Initializing and adding models
 0> <t:        604>, main.c,  452, Restored: App data
 0> <t:        606>, main.c,  551, Restored: Handles 
 0> <t:        608>, provisioner_helper.c,  307, m_netkey_handle:0 m_appkey_handle:0 m_self_devkey_handle:1
 0> <t:        616>, main.c,  591, <start> 
 0> <t:        694>, main.c,  404, Mesh evt: FLASH_STABLE 
 0> <t:        697>, main.c,  578, Starting application ...
 0> <t:        699>, main.c,  580, Provisoned Nodes: 2, Configured Nodes: 2 Next Address: 0x0104
 0> <t:        703>, main.c,  581, Dev key : BA8A926F3954726A5860877723B1D450
 0> <t:        707>, main.c,  582, Net key : 482EF1D4CC88EDC4005CB3B97C6D3B55
 0> <t:        710>, main.c,  583, App key : 9079B16ED17CA52528109FECEFBC79C9
 0> <t:        713>, main.c,  584, Press Button 1 to start provisioning and configuration process. 
 0> <t:     346024>, main.c,  459, Button 1 pressed
 0> <t:     346027>, main.c,  376, Waiting for Server node to be provisioned ...
 0> <t:     350789>, provisioner_helper.c,  288, Scanning For Unprovisioned Devices
 0> <t:    1244842>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    1625141>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    1903868>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    2562787>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    2612607>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    3270585>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    3549997>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    3927596>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    4534921>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    4884299>, main.c,  419, Unhandled Mesh Event: 4 
 0> <t:    5523284>, main.c,  419, Unhandled Mesh Event: 4 

Server

 0> <t:          0>, main.c,  206, ----- BLE Mesh Light Switch Server Demo -----
 0> <t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
 0> <t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
 0> <t:         15>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
 0> <t:        531>, main.c,  182, Initializing and adding models
 0> <t:        565>, main.c,  238, Device UUID : 005955AA00000000DEDC99CFA814A0AF
 0> <t:          0>, main.c,  206, ----- BLE Mesh Light Switch Server Demo -----
 0> <t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
 0> <t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
 0> <t:         16>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
 0> <t:        542>, main.c,  182, Initializing and adding models
 0> <t:        576>, main.c,  238, Device UUID : 005955AA00000000DEDC99CFA814A0AF

Client

 0> <t:          0>, main.c,  299, ----- BLE Mesh Light Switch Client Demo -----
 0> <t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
 0> <t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
 0> <t:         15>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
 0> <t:        531>, main.c,  266, Initializing and adding models
 0> <t:        565>, main.c,  331, Device UUID : 0059CCAA00000000EC60B59C43652615
 0> <t:          0>, main.c,  299, ----- BLE Mesh Light Switch Client Demo -----
 0> <t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
 0> <t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
 0> <t:         16>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
 0> <t:        520>, main.c,  266, Initializing and adding models
 0> <t:        554>, main.c,  331, Device UUID : 0059CCAA00000000EC60B59C43652615

If i close the rtt viewer the LD5 stops blinking, so i guess it is related to usb communication.

[Edvin]

Hello,

LED5 is the SEGGER chip's LED, so it will do it's own thing, sort of. Definitely related to the RTT logging.

Which version of the SDK for Mesh do you use?

Do you have an unmodified version of the "Regular" SDK15.0.0 in the same folder as the Mesh SDK?

It seems like your server and client projects keep resetting. Do you use Segger Embedded Studio?

Have you modified the light_switch server and client projects?

Best regards,

Edvin

[anilkunchalaece]

I'm using Mesh SDK 2.1.2

Do you have an unmodified version of the "Regular" SDK15.0.0 in the same folder as the Mesh SDK?

Yes

Do you use Segger Embedded Studio?

Yes

Have you modified the light_switch server and client projects?

No

[Edvin]

We don't have a 2.1.2 version of the Mesh SDK.

I am sorry that I keep asking for this, but I haven't seen any reports that this example is not working in any of the versions.

Do you use regular nRF52832 DKs in your test?

Can you try to run the script from SDK_for_mesh\scripts\quick_start\quick_start_demo.py? Does this work? Depending on which SDK version you use, you might have to move it to the root folder of the SDK.

To test the script, follow these instructions (section "Flashing the example firmware" and "Running and observing the demonstration"). If this works, then we know that the problem is not in the hardware.

BR,

Edvin