Err happens when running "...\examples\serial" example of mesh SDK

[Tomlee]

Hi, 

when I am running mesh serial example ,   err happens, Could you help me , please?

00> <t: 2300092>, net_packet.c, 228, Unencrypted data: : FFFF433DCB14253CEFF4F4
00> <t: 2300098>, transport.c, 1045, Message decrypted
00> <t: 2300103>, app_error_weak.c, 105, Mesh assert at 0x0002FD20 (:0)

[tesc]

Hi,

What version of nRF5 SDK for Mesh are you using, and with what SoftDevice and version?

Regards,
Terje

[Tomlee]

Hi, 

Thanks for your reply.

1.mesh sdk version： V5.0.0
2.nrf sdk version:        V17.0.2

Softdevice:   s113_nrf52_7.2.0_softdevice

[tesc]

Hi,

Under the sdk folder/examples/serial/build/ folder you should have another folder (which was created when you built the project) and in that folder there should be a file named serial_nrf52833_xxAA_s113_7.2.0.map. Can you share that file?

Also, can you do a debug session triggering the assert, and share the stack trace?

With that information, we should be able to point to where the error happens.

In case we need to try to reproduce in our end: What is your setup, and what steps do you follow to test the example?

Regards,
Terje

[Tomlee]

serial_nrf52833_xxAA_s113_7.2.0.hexserial_nrf52833_xxAA_s113_7.2.0.map

Test board:   Ev board #1(serial_nrf52833_xxAA_s113_7.2.0.hex)

                     Ev board #2(light_switch_client_nrf52833_xxAA_s113_7.2.0.hex)

Step:

1)  Using serial comand to provison and add key for light switch example  via Ev board #1

2)  Must Set the publish addr to 0xFFFF for light switch client example(Ev board #2)

3)  Input button 1 on Ev board #2 RTT viewer window

4)  err log will happen

00> <t: 4880612>, net_packet.c, 228, Unencrypted data: : FFFF4331894B81D08E21F07130
00> <t: 4880618>, transport.c, 1045, Message decrypted
00> <t: 4880623>, app_error_weak.c, 105, Mesh assert at 0x00025D14 (:0)

[Tomlee]

err happens here line

[tesc]

Hi,

Right, so the error seems to happen on reception of packets addressed to the "all nodes" address 0xFFFF? Do you see the same issue when addressing to a group address, and/or a unicast address?

Regards,
Terje

[Tomlee]

tesc said:

Do you see the same issue when addressing to a group address, and/or a unicast address?

No,   I checked 0xFFFE, also have this err happened.

[tesc]

Hi,

0xFFFE is a special group address very much like the 0xFFFF all nodes address. What I meant was, do you see this with normal assignable group addresses (or unicast addresses) as well?

Regards,
Terje