Could not make example runing on V2.2.0

[weizhen]

I am working on mesh v2.2.0. but I cannot make the light switch example works. I did everything as same as the early versions, this version just stops working. I get one provisioner, one client, and three servers. after powering the PCA10040 dev kit, all four LEDs on for all of them. and then I try to press button 1 on provisioner, but nothing happened. are there any big changes happened on v2.2.0? what should I do to make it work?

[Bjørn Kvaale]

It should be the same procedure as earlier light switch examples. Have you remembered to erase all of the devices before you programmed them. Have you tried running a debug session in SES to see what is happening in the log?

[weizhen]

yes, I do erase all of the devices. I do not check the log yet, but if it is as same as earlier version, it should blinking all LEDs twice and keep all of them off. but right now, it only turns on all LEDs, and then do nothing, seems like it died at the start state.

[Bjørn Kvaale]

The log clearly shows that you are getting an assert on each of the boards. Could you open up the .map file in your _build folder & see where the assert is happening: 0x2F60E, 0x2F55E, 0x31E72. Are you sure that you ran an nrfjprog --eraseall on all of the boards before you tried running the examples?

Also, have you set the MESH_ROOT & SDK_ROOT folders to the proper path? Go to Tools -> Options -> Building Tab -> Global Macros -> set the correct path.

Should be similar to this:

SDK_ROOT=C:/NordicSemi/SDKs/nRF5_SDK_15.0.0_a53641a

MESH_ROOT=C:/NordicSemi/SDKs/nrf5_SDK_for_Mesh_v2.2.0_src

If you needed to change any of these paths, remember to compile the examples again before testing.

[weizhen]

yes, I am doing nrfjprog --eraseall everytime before I flash the chip. I am using cmake to build the code. I followed this link, https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v12.0.0%2Fstructble__bps__init__t.html. 

I check the .map file, and all assert is happening between mesh_config_init and mesh_config_load.

[Bjørn Kvaale]

Which nrf5 sdk version are you currently using? If you are not using sdk v15.0.0, I would highly recommend using that, as it is the recommended version to use. Could you please update your link that you followed? I do not believe the link you sent was relevant to this discussion unfortunately.

[weizhen]

this is the link, https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v2.2.0%2Fmd_doc_getting_started_how_to_build.html&cp=4_1_0_1_1

Also, I am using SDK v15.0.0 and softdevice S132 v6.0.0.

[Bjørn Kvaale]

Are you building the examples with cmake or segger embedded studio? I would recommend SES. If you still cannot get it to build, I would recommend downloading nrf5 sdk v15.0.0 & mesh sdk v2.2.0 again. You should keep the path quite short, so I would download it very close to the C drive. This should work out of the box. Also, make sure to use the correct MESH_SDK & SDK_ROOT paths like explained in the readme when you open a mesh segger project.

[weizhen]

I am using cmake, and I already try to download these sdks and rerun everything again and again, and nothing helps. but the mesh sdk v2.1.1 works fine there.

[Bjørn Kvaale]

Do you still receive the same assert as you did previously? You can use the addr2line tool to figure out where the assert occured in the code. You can use the .elf file that is located in the build folder.

[weizhen]

the addr2line shows that happened in /mesh/core/src/mesh_config.c:228, and it is in side a function called entry_validation.

[Bjørn Kvaale]

weizhen Could you try to apply the patch in the comment to see if it works?