How to reflash Thingy52?

[philbrock]

Hello Nordic,

I have multiple Thingy52 devices upgraded to V2.2 firmware via nRF Connect application on my android phone.

Have been trying to add the BL Mesh light switch example to no avail, using the precompiled .hex files in nrf5_sdk_for_mesh (version 3.1).

I have bricked a Thingy and would like to reflash to original factory state (v2.2), but have not found a download for that on your site.

I am using a Segger jlink device and the nrf tools (e.g. nrfjprog).

Thank you.

Phil

[philbrock]

I found the download page here: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/Nordic-Thingy-52/Download#infotabs

This worked like a charm.

Now I will return to adding Mesh functionality to the Thingy.

I should be able to do that using *only* precompiled hex files in the SDK for BLE Mesh version 3.1.0, is that correct?

Thank you.

[Bjørn Kvaale]

Have you tried using the Thingy:52 FW found here? This is the basis of the demo on Youtube here.

[philbrock]

Hi Bjorn,

Yes, that is exactly the demo I am trying to reproduce.

However, I am using the latest versions of the sdks:

nRF5 Mesh SDK v3.1.0    (article uses v2.2.0)

Nordic Thingy:52 SDK v2.1.0    (article uses the same)

Nordic nRF5 SDK v15.3.0 (article uses v15.0.0)

So Question 1: Can I use the most recent versions or should I use the exact SDK versions from the article?

Typically I prefer to use the most recent versions of SDKs as they are more mature.

The demo states under the "Building the Demo" section:

To run the demo, you can use the precompiled firmware, or ....

So before I compile and build my own version with the Seeger IDE toolchain, I want to try with the precompiled firmware. There are two .hex files in the hex folder of the github repo:

s132_nrf52_6.0.0_softdevice.hex

thingy52-mesh-provisioning-demo.hex

If I am going to manually flash a Thingy over a jlink connection using nrfjprog, I imagine I need to use hexmerge to combine the two hex files above into one:

hexmerge s132_nrf52_6.0.0_softdevice.hex thingy52-mesh-provisioning-demo.hex -o prebuiltdemo.hex

Then I wiped the Thingy:

nrfjprog -e -f nrf52

Then I flashed the Thingy:

nrfjprog -p prebuiltdemo.hex -f nrf52

Then I power cycled the Thingy and got the Breathing Red color, so I could configure it via nRF Mesh application on my mobile phone. Hooray!

So the problem I had last week was I did not combine the two prebuilt .hex files. I had only tried flashing with thingy52-mesh-provisioning-demo.hex

If you could kindly answer my question above, you can close this ticket.

Thank you Bjorn!

Phil

[philbrock]

The reason I asked the question above about using the most current versions of SDKs is because when I follow each step of the "Building the demo" section, when I open the thingy52-mesh-provisioning-demo solution/project in SES and try to build, I get errors that files are missing.

A few files are missing from the Application folder within SES. 

For example: ...\nrf_sdk_for_mesh\common\src\rtt_input.c: No such file or directory

The rtt_input.c file above is actually in ...\nrf_sdk_for_mesh\examples\common\src

My SDK_ROOT Global Macros are defined correctly.

[Bjørn Kvaale]

philbrock said:

So Question 1: Can I use the most recent versions or should I use the exact SDK versions from the article?

 No, it's best to use the mesh sdk v2.2.0. You could update the code to work on v3.1.0, but it would require a bit of work (see this migration guide for info). In addition, just want to point out that the Thingy mesh example uses a simplified version of the generic on off server, not the standard on/off server. This may make migration a bit more difficult.