Reload Thingy hex file once erased with new executable.

[rods]

I am using a Mac with SES installed.  I created a DFU example and downloaded it to the Thingy 52 to see how it works.  That all went fine.  Unfortunately, it has disabled the Thingy 52 from doing it's normal function.  I would like to refresh the device with a good executable.  Looks like that is available somewhere on Nordic's site thingy_v2.1.0.HW_1.0.hex, but I can't find it.  Please provide me a link to this file.  My plan is to load it using my existing JLink SWD  connection to my Mac.  I am assuming I can do that through SES.

[haakonsh]

I read my own Thingy's flash out, it should be stock firmware. 
Thingy52v1.0.0.hex

[rods]

Thanks, When I load the file (using SES), I get an error that the file fails to download.  BTW, the file is only downloadable as an Intel Hex File type.  Also, when I verify the file (again using SES) it shows a large segment starting somewhere in the middle of the file in red (I assume as being incorrect).  Could the file have gotten corrupted in transfer or am I doing something else obviously wrong?

[rods]

A JLink JTAG SWD-SDO device.

[rods]

I went back and read the nfu tutorial and ran both the nRFConnect and Thingy apps on my iPhone.  nRF Connect actually detects the Thingy in NFU mode.  I can connect to it, but the Secure DFU services doesn't expand as in the instructions.  When I launch the Thingy app, it will not connect (I suspect it is looking for the normal UUID, not the ThingyNFU UUID).  That is too bad as the proper .zip file for the Thingy firmware is in the Thingy app (I did that update before trying to download compiled code to the Thingy via the JLink device).  I'd love to be able to do a restore using the nRFConnect app as it does actually see the device and (seems) to be connected in DFU mode, which should allow me to download the .zip file.  Any advice on getting past this little sticking point?

[rods]

BTW, Here is what I see in nRFConnect:  

[rods]

So ... the Android nRFConnect app works better.  I was able to connect to the Thingy and force it into DFU mode.  Then, I was able to go back to my iPhone, connect the Thingy app to the ThingyDfu device that was showing and do a firmware update.  After only a week and a half, I am back to where I can experiment with the device again and have confidence I can reset it once I destroy the firmware load.

[haakonsh]

I'm glad to hear you've gotten back on track. 

Do you have any logs or something from the iPhone nRF Connect app issue?

[rods]

No, I can't see where you allow turning a log on/off or specifying the level of log information captured.  I have developed iOS apps for Bluetooth communication and the log feature is a conditional compilation feature for debugging; not generally put in the shipping version.

[haakonsh]

Aah, I see.