nRF Mesh connection for nRF6936

[Marry]

Hello everyone. I have the following issue: I would like to connect some Nordic Thingy:52 nRF6936 devices in a mesh network, using the application nRF Mesh. In theory, the first step should be very simple (there is also an official video about this: https://www.youtube.com/watch?v=XthbU9NP0Yg).

However, in practice, my nodes are not found. Is there some previous set-up which needs to be made? Do you have any suggestions?

Remarks: I have the latest version of the app + all firmware updates and the nodes are recognised in other apps, for example in Nordic Thingy App or nRF Toolbox - nRF Connect App.

Thank you in advance!

[Marry]

Hello Mttrinh and thanks for your answer! I checked the firmware version - you may see it below, attached.

From my understanding, it is the latest version, because I updated it, as soon as I used the device the first time (last week). Am I right about this? Or is there another firmware to be installed, which does not come by default?

Nevertheless, I followed the Thingy Mesh demo from Github, which you provided me, but at the moment I do not have that specific cable, so I am on-hold at step 6. I will come back with updates next week.

Have a good time until then, Marry.

[Mttrinh]

Marry said:

Or is there another firmware to be installed, which does not come by default?

To be able to use the Thingy:52 with Mesh you need to use the firmware found in the Thingy Mesh demo Github. Won't work with Mesh with the default firmware.

[Marry]

Ok, I understand - I will try that. Thank you for your help!

[Mttrinh]

No problem, glad to be of help :) 

[Marry]

Hello again! As I am trying to connect to my Thingys, I have some questions regarding the tutorial on GitHub that you provided me in your first reply. 

Step 7. Do an erase all to remove the Thingy original firmware and bootloader - how should I do that? Should a window pop-up when I connect my nrf52833 to the thingy, via the SWD cable? Or should I do it from the SES Program?

Step 9. Make sure you followed the SES.md guide - I am also not sure if I did that correctly (since there are so many SDK5 folders), I would be grateful if you could have a look - I attach it as the first picture.

Step 10. Compile one of the project provided in this repo and flash the firmware - here I also have a little problem, since the project I have cannot be compiled - I attach the second picture below.

I do not understand why those files do not exist in the project (I imagine they should be there). I see that in my include folder there are the following .h files: app_config, light_switch_example, my_mesh_provisionee, nrf_mesh_config_app, sdk_config, simple_hal_thingy and thingy_config. But I see that many more .h files are included in the main.c file from this project. Could you please guide how to debug this problem?

Thank you very much,

Best regards,

Marry

[Mttrinh]

Marry said:

Step 7. Do an erase all to remove the Thingy original firmware and bootloader - how should I do that? Should a window pop-up when I connect my nrf52833 to the thingy, via the SWD cable? Or should I do it from the SES Program?

You can do this from SES.

Marry said:

Step 9. Make sure you followed the SES.md guide - I am also not sure if I did that correctly (since there are so many SDK5 folders), I would be grateful if you could have a look - I attach it as the first picture.

You need to use nRF5 SDK v15.3(as mentioned in step 3).

Marry said:

Step 10. Compile one of the project provided in this repo and flash the firmware - here I also have a little problem, since the project I have cannot be compiled - I attach the second picture below.

I do not understand why those files do not exist in the project (I imagine they should be there). I see that in my include folder there are the following .h files: app_config, light_switch_example, my_mesh_provisionee, nrf_mesh_config_app, sdk_config, simple_hal_thingy and thingy_config. But I see that many more .h files are included in the main.c file from this project. Could you please guide how to debug this problem?

You probably get this error because you used the worn SDK version. Changing to SDK v15.3 should fix this.