Thingy52 MESH demo

[ToasTer86]

Hey Nordic and co-nordic developpers,

Just to show some capabilities here at work I want to compile and run the mesh demo on the 10 Thingy52's we have here.

I am currently at step 5 & 6 from the Github Nordic playground project ( https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo) 
But a bit confused how I should be just simply downloading the firmware to Thingy52.

There are like I think 4 different ways of doing this:

• NRFutil, with a own premade key and packaged zip
• NRFconnect with a nRF52-DK board
• Using your phone as DFU uploader (still need to generate a package ?)
• Using segger and just downloading it ??
  
  Can I get some pointers how to do this ?
  
  

Thanks in advance,

ToasTer

[ToasTer86]

I have connected the Thingy52 like this to the nRF52840-PDK as can be seen in the picture. No I can download the new firmware (demo software from github) with SEGGER embedded studio to the Thingy52.
But after flashing the software the Thingy52's just go into DFU mode, the bridge & node software.

The reason I can see they are going into DFU mode is that when I grab my phone with NRFconnect I can see the Thingy's coming up as DFU.

What am I missing ? 

Thanks in advance.

[ToasTer86]

I used the precompiled hex file's from the demo, and transferred those using nRFgoStudio. 
First I erased them completely using NRFgoStudio then transferred the precompiled hex and that seemed to work. 

But still I will need some help why I could not get them to run using segger.

[Jui-Chou (Rick) Chung]

Hello ToasTer86,

Yes, you are on the correct direction, please don't use DFU to download the mesh demo firmware to Thingy.

Use nrfjprog to flash the hex image, or using Segger Embedded Studio to compile and program the demo firmware are both correct way.

I would like to suggest you erase the Thingy before using Segger Embedded Studio to compile and flash the firmware.

Since Segger Embedded Studio won't erase the entire flash during download the firmware, and some data which already stored in the flash will make Thingy demo firmware work incorrectly. So Please use nrfjprog to erase Thingy first, the command is:

> nrfjprog -f nrf52 -e

[Edvin]

What you describe here is correct. The bootloader that is preprogrammed on the Thingy is using a private key only known to someone in Nordic Semiconductor, so I couldn't tell it if I knew it. 

To program the Thingy, you must have a segger cable and a segger programming chip (like on the DK). The easiest way is to do as in the picture from OP (ToasTer86) from a couple of days ago.

 

Use "nrfjprog -f NRF52 -e" or nRFGo Studio to erase the Thingy:52 first, and then program the softdevice and your project to the thingy. If you program it with the bootloader project, you must create your own private and public keyset to be able to program it via DFU the next time. (guide here, not intended for Thingy, but it is the same key generation process).

 

BR,

Edvin