Hi, I am interested to learn THINGY 52 working
I want to know how does the Thingy52 works?. any tutorial to explain the function of THINGY52
How to delete the boot loader and start work as a normal nRF52832 functions.
and How to return back into the DFU boot loader program and start work as it is
is there a procedure and zip file for doing this work.
and i need to work MESH in nordic thingy 52.
where i will get the mesh function for this thingy52.
Hi,
The standard Thingy:52 firmware does not support mesh, but there are Thingy:52 mesh demos.This is just an old demo, though.
If you want to understand BLE mash and DFU, you should look at the Mesh SDK documentation.
Hi Einar,
thanks for you fast reply.
i have seen this video. https://www.youtube.com/watch?v=wa_ARkZSr_U
is this mesh demo works as like this.
shall i know how to upload this mesh code to thingy.
for my understand:
1. if i am going to connect the thingy board to nRFgo studio. and give erase all means it will delete the boot loader also or only the application and soft device.
2. if i delete the boot loader in the sense how to return back to thingy firmware. how to add boot loader to the thingy.
because. I am new to this nRF. can you please guide to do this.
Hi,
Most of these questions are beginner questions, and therefore I strongly advice that you start of with the nRF52840 DK instead, as the Thingy:52 is not a development kit. It does not have an onboard debugger, and it is not supported out of the box in the Mesh SDK. I can almost guarantee that you will save time (and thus money) on using the DK to begin with.
Sunil vignesh said:
is there any tutorial to upload boot loader to board.?
i found some Downloadable files in Thingy page https://www.nordicsemi.com/Software-and-Tools/Development-Kits/Nordic-Thingy-52/Download#infotabs
The thingy firmware comes with DFU, but this is not mesh. Mesh DFU is very different from normal DFU, so it does not really make much sense to look at what is allready there. Instead, you should familiarize yourself with the Mesh SDK, and not think som much about the Thingy to begin with (think of it as just another board you can run BLE mesh on, like any other custom board). And when you work with custom boards, always start with the DK, since this is a known good platform with tested examples in the Mesh SDK.
Sunil vignesh said:
shall i know what that .zip file shows.
and what is the .hex file? . if i download the .hex file to thingy board through nRF5 DK. it will have boot loader.
or OTA concept will be done separately before the .HEX file upload?
I do not understand the question here. But again: please start with the DK, that will give you less unknowns in the beginning, since you actually have a known good starting point.
Hi,
I have nRF52832 DK boards. where i start developing my applications. As i want to enter into mesh network on IOT sensors. that time i look out this IOT SENSOR KIT THINGY52. and i have seen the video.
https://www.youtube.com/watch?v=wa_ARkZSr_U
and i bought 3 to test this mesh concept.
the github file that you given is similar to that. (is it works).
before try this github files. i need to take the backup of THINGY v2.2.0 boot loader file and the .hex file.
once i finish my testing. i need to restore the thingy v2.2.0 to the thingy board.
This is the case.
please guide me to
Where to get the Thingy v2.2.0 firmware, boot loader and hex files.
how to upload the boot loader to perform OTA DFU.
once upload the boot loader. than i need to do OTA to upload the firmware. is it possible?
Sunil vignesh said:Where to get the Thingy v2.2.0 firmware, boot loader and hex files.
I see. So now we are back at no mesh? Then you can download the Thingy:52-HEX from here. This includes everything you need: bootloader, application and SoftDevice in one merged .hex file.
Sunil vignesh said:how to upload the boot loader to perform OTA DFU.
You can then update to the lastest version via DFU from the Thingy phone app. This works out of the box, just select DFU from the app and it will perform it for you.
i have a case ,just to test the hex file working
i have upload the Thingy-52-HEX file to nRF5 DK board. and i scan the ble in the Nordic Thingy app. . it doesn't shows anything.
is it work for only Thingy board ?
as you said mesh part, i need to work out on DK board.
i have a quires :
shall i know how the OTA - DFU will works?. any step up step instruction to work on this.
if i done the OTA - DFU for the device. one time. shall i upload even blinky code also in OTA?
i am not clearly understand this OTA DFU concept. even in Thingy 52 too?
how to convert the normal nRF52 board to OTA - DFU nRF52 board (i.e wired transmission to wireless transmission).
Sunil vignesh said:is it work for only Thingy board ?
Yes, it relies on external peripherals which are not present on the DK.
Sunil vignesh said:shall i know how the OTA - DFU will works?. any step up step instruction to work on this.
Sunil vignesh said:if i done the OTA - DFU for the device. one time. shall i upload even blinky code also in OTA?
You can update any application, bootloader or SoftDevice using DFU. A simple "blinky" application is no different from another application in this regard.
Sunil vignesh said:i am not clearly understand this OTA DFU concept. even in Thingy 52 too?
The Thingy:52 is just another nRF52 product. Think of it as a custom board which could be an end product. It just happens to be developed by Nordic, and we supply the source code and schematics. It is based on the normal SDK (version 13), so it uses the same bootloader etc.
Sunil vignesh said:how to convert the normal nRF52 board to OTA - DFU nRF52 board (i.e wired transmission to wireless transmission).
There is no HW difference. It is just a matter of using a bootloader, and potentially some support for DFU in the application. DFU is quite (some might say very) complex, so I strongly recommend you spend some time reading documentation and experimenting with the DFU examples. Then you should use the DK for experimentation as all SDK example etc. are based on it, and it has an inboard debugger.
Sunil vignesh said:is it work for only Thingy board ?
Yes, it relies on external peripherals which are not present on the DK.
Sunil vignesh said:shall i know how the OTA - DFU will works?. any step up step instruction to work on this.
Sunil vignesh said:if i done the OTA - DFU for the device. one time. shall i upload even blinky code also in OTA?
You can update any application, bootloader or SoftDevice using DFU. A simple "blinky" application is no different from another application in this regard.
Sunil vignesh said:i am not clearly understand this OTA DFU concept. even in Thingy 52 too?
The Thingy:52 is just another nRF52 product. Think of it as a custom board which could be an end product. It just happens to be developed by Nordic, and we supply the source code and schematics. It is based on the normal SDK (version 13), so it uses the same bootloader etc.
Sunil vignesh said:how to convert the normal nRF52 board to OTA - DFU nRF52 board (i.e wired transmission to wireless transmission).
There is no HW difference. It is just a matter of using a bootloader, and potentially some support for DFU in the application. DFU is quite (some might say very) complex, so I strongly recommend you spend some time reading documentation and experimenting with the DFU examples. Then you should use the DK for experimentation as all SDK example etc. are based on it, and it has an inboard debugger.
Hi,
Question related to Thingy - 52.
if I "erase " the Thingy board. and
i program the Thingy board with the hex file - Thingy:52-HEX link
Is it show in Nordic Thingy App. and is it possible to do DFU updates. by only uploading the hex file to the board?
I have a question related to MESH.
as like this video Thingy-52 Mesh
is any other MESH example code to work in nRF5 DK board?
My case. I need to connect 5 boards in a Mesh network.
where i need to connect my mobile phone with one Master(board).
and that master will command the others.
I need to control the LEDs of the each slave boards, by whole at same time or particular board at a time.
and also i need to receive when the BUTTON is pressed in any salve boards.
Is there any example code related to this or else. any tutorial related to this?
Hi,
Sunil vignesh said:Is it show in Nordic Thingy App. and is it possible to do DFU updates. by only uploading the hex file to the board?
Yes, this is supported by the thingy firmware. However, the private key used to sign images are not available to customers. So, in the same way as any other bootloader example, you need to build and program a bootloader with your own public key in order to provide your own application hex files via DFU.
Sunil vignesh said:
I have a question related to MESH.
as like this video Thingy-52 Mesh
is any other MESH example code to work in nRF5 DK board?
My case. I need to connect 5 boards in a Mesh network.
where i need to connect my mobile phone with one Master(board).
and that master will command the others.
I need to control the LEDs of the each slave boards, by whole at same time or particular board at a time.
and also i need to receive when the BUTTON is pressed in any salve boards.
Is there any example code related to this or else. any tutorial related to this?
Please refer to the nRF5 SDK for Mesh documentation and examples which are part of the nRF5 SDK for Mesh distribution.
