establishing mesh network by using a nrf52840 devkit and two nrf52840 dongle boards

[Sama]

Hello everyone,

I am going tp establish a mesh network by using a devkit and two or more dongle. take as an example, turning off a led on the dongle boards by using a bottom on the devkit through the mesh network.

Thanks for help in advance. 

[Sama]

Hello everyone,

Thank you for your reply.

I could program the devkit as a client by adding the root of the example in the Global Macros.

I saw the devkit in the nrf Mesh application as nrf mesh switch. 

After which, I followed the instruction suggested in this link to program the dongle board as a server.

https://devzone.nordicsemi.com/nordic/short-range-guides/b/getting-started/posts/nrf52840-dongle-programming-tutorial

I used the hex file built in the build folder in the server folder to program the dongle through nrf connect software. 

after witting the hex file, these messages appeared.

04:35:21.240

Reopen device failed: Timeout while waiting for device D4AC8646D4D6 to be attached and enumerated

04:35:21.240

Nordic DFU Trigger Interface was not found.Please physically reset device.

04:35:21.266

Device not found due to failure during DFU

04:35:22.283

Target device closed.

unfortunately I could not find the dongle as a server in the nrf Mesh application.

Could you please help me about this problem?

Thank you

[Hung Bui]

Hi Sama,

Please try to test first with blinky example as showed in the tutorial. 

Have you ever managed to program any example into the dongle using nRF Connect software ? 

I suspect that the bootloader doesn't run on your dongle. 

If you press the reset button on the dongle do you see the  red LED breathing ? 

[Sama]

Hi Hung,

Thank you for your advice. I will do it and inform you about the results.

What about the soft device code ID?

During programing, the NRF connect software required the soft device code ID. I used S140_nrf52_7.2.0. so I entered 0x0100 code, which I found in the devezone.nordic for the soft device.

was that wrong?

Actually I think this is the last thing I should test before soldering the SWD connector.

Further, I have built the hex code in the debug mode in SES. Is there any different in Release or Debug mode? Does it affect solving the problem?

Regards,

Sama

[Hung Bui]

HI Sama, 
I don't really understand why you need the softdevice ID ? 
Just select the softdevice you plan to use and click write. 

Before testing the dongle with mesh, please try to test it with normal BLE application. 

[Sama]

Hi Hung,

This is the stage which the NRF connect software needs the softdevice ID I am using.

As you can see there is not the s140_nrf52_7.2.0 version in the list and I have to enter the softdevice ID.

I used the 0x0100 code in this stage and I think that was wrong.

I would appreciate if you can advice me on the hex ID of the softdevice.

Thank you,

Sama

[Sama]

Hi Hung,

Thank you for your reply.

I found my mistake. Actually I did not load the softdevice correctly through the dfu folder.

Thanks a lot.

Sama

[awneil]