dimming_server example stop responding when trying to set delta = 0

[Nikolay_D]

Hi, to repeat the problem, you need to press button 3 and then button 2 on the board with an example of dimming_client, after that the board with dimming_server stops responding.

1.  0> <t:          0>, main.c,  239, ----- BLE Mesh Light Switch Server Demo -----
2.  0> <t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
3.  0> <t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
4.  0> <t:         15>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
5.  0> <t:        565>, main.c,  215, Initializing and adding models
6.  0> <t:        570>, main.c,  250, PWM max ticks: 1600
7.  0> <t:       5440>, main.c,  273, Device UUID : 005955BB00000000C4301495C4674564
8.  0> <t:     828179>, main.c,  206, Successfully provisioned
9.  0> <t:     828181>, main.c,  210, Node Address: 0x0103
10.  0> <t:    1229922>, app_level.c,  513, Delta SET: delta: 10000  delay: 100  tt: 2000
11.  0> <t:    1229925>, app_level.c,  516, Delta SET: initial-level: 0  present-level: 0  target-level: 10000
12.  0> <t:    1233207>, app_level.c,  270, Selecting minimum tick interval
13.  0> <t:    1233210>, app_level.c,  280, timeout_rtc_ticks: 33 ticks
14.  0> <t:    1450338>, app_level.c,  513, Delta SET: delta: 0  delay: 100  tt: 2000
15.  0> <t:    1450341>, app_level.c,  516, Delta SET: initial-level: 10000  present-level: 10000  target-level: 10000

And one more case:

If you press button 1 on the dimming_client five times, then the board with dimming_server will also stop responding.

•  0> <t:          0>, main.c,  490, ----- BLE Mesh Light Switch Server Demo -----
•  0> <t:        564>, main.c,  417, Initializing and adding models
•  0> <t:       5458>, main.c,  547, Device UUID : 005955BB00000000A7123154A5976C18
•  0> <t:        551>, main.c,  408, Successfully provisioned
•  0> <t:        554>, main.c,  412, Node Address: 0x0103
•  0> <t:     707226>, app_level.c,  454, SET: Level: 10000  delay: 100  tt: 2000  req-delta: 10000
•  0> <t:     710507>, app_level.c,  270, Selecting minimum tick interval
•  0> <t:     710510>, app_level.c,  280, timeout_rtc_ticks: 33 ticks
•  0> <t:     888987>, app_level.c,  454, SET: Level: 20000  delay: 100  tt: 2000  req-delta: 10000
•  0> <t:     892270>, app_level.c,  270, Selecting minimum tick interval
•  0> <t:     892272>, app_level.c,  280, timeout_rtc_ticks: 33 ticks
•  0> <t:    1135748>, app_level.c,  454, SET: Level: 30000  delay: 100  tt: 2000  req-delta: 10000
•  0> <t:    1139029>, app_level.c,  270, Selecting minimum tick interval
•  0> <t:    1139032>, app_level.c,  280, timeout_rtc_ticks: 33 ticks
•  0> <t:    1280788>, app_level.c,  454, SET: Level: 32767  delay: 100  tt: 2000  req-delta: 2767
•  0> <t:    1284069>, app_level.c,  270, Selecting minimum tick interval
•  0> <t:    1284072>, app_level.c,  280, timeout_rtc_ticks: 33 ticks
•  0> <t:    1447308>, app_level.c,  454, SET: Level: 32767  delay: 100  tt: 2000  req-delta: 0

How to fix this problem?

[Bjørn Kvaale]

Did you provision the examples via the provisioner board or via the nRF Mesh app? Also, it's probably a good idea to adjust the RAM base to the value shown in the first log you uploaded.

[Nikolay_D]

The first log was obtained from a modified dimming_server example, I added proxy support there. This example was provisioned using the  nRF Mesh app. Second log from the original example. Provisioned with a board.

How to adjust the RAM base?

[Bjørn Kvaale]

Right-click on the Project in Segger Embedded Studios -> Edit Options ->change to the Common configuration -> Linker tab -> Section Placement macros -> change the RAM_START value. See if that helps at all. If not, let me know & I will take a closer look.

[Nikolay_D]

After changing the RAM_START value, the problem did not disappear.

0> <t: 0>, main.c, 490, ----- BLE Mesh Light Switch Server Demo -----
0> <t: 566>, main.c, 417, Initializing and adding models
0> <t: 5454>, main.c, 547, Device UUID : 005955BB00000000A7123154A5976C18
0> <t: 550>, main.c, 408, Successfully provisioned
0> <t: 552>, main.c, 412, Node Address: 0x0103
0> <t: 348254>, app_level.c, 513, Delta SET: delta: 10000 delay: 100 tt: 2000
0> <t: 348258>, app_level.c, 516, Delta SET: initial-level: 0 present-level: 0 target-level: 10000
0> <t: 351539>, app_level.c, 270, Selecting minimum tick interval
0> <t: 351542>, app_level.c, 280, timeout_rtc_ticks: 33 ticks
0> <t: 467073>, app_level.c, 513, Delta SET: delta: 0 delay: 100 tt: 2000
0> <t: 467076>, app_level.c, 516, Delta SET: initial-level: 10000 present-level: 10000 target-level: 10000

[Nikolay_D]

Inside the function a_transition_start, in the calculation of transition_step_us the division into zero occurs.
Please tell me the best way to fix this?
   

   github.com/.../app_level.c

[Bjørn Kvaale]

I have just tested this with three nrf52832 dev kits & I was unfortunately not able to replicate the issue. I provisioned with the light switch provisioner example instead of the nRF Mesh app. Could it maybe be something to do with the nRF Mesh application? Did you follow the documentation under "Provisioning with the nRF Mesh app" here?

[Nikolay_D]

Please look at the static void function a_transition_start (void * p_data). If delta is zero, division by zero occurs. In the logs you can see that the delta becomes zero. Do not you have it?