Can not reset Thingy 53 back to its original Edge Impulse FW.

[drselim]

Hi, Last week I received a Thingy 53 in addition to an nRF7002 DK and nRF52840 dongle from Nordic, first let me thank the Nordic team for that.

Let me summarize the issue I'm having with my Thing 53:

As I received my device I registered to Edge Impluse web site and created a new project. Using nRF Edge Impulse Mobile App, I easily added my Thingy 53 to my project and started recording 10 sec samples from the light sensor (I was thinking of making classification based on the RGB values received). I setup my training and test sets, created my Impulse with success and managed to go to the end of the process to deployment, chose Nordic Thingy 53 from the 'Build Firmware' section and built my FW, then I set my device in DFU mode by pressing sw2 and turning it on, in the Programmer Tool, I saw and chose the Thingy 53 in MCU boot mode, I 'wrote' the .zip file created by Edge Impulse, successfully finished. Turned my device off and on and tried to connect to it with the Edge Impulse Mobile App, the device was discoverable, however never managed to connect to it.

That's why I tried to go to "factory settings" for the Thingy 53 (with Edge Impulse FW on it for sure), lloked up the internet tried several builds which failed (From Edge Impulse) , finally after reading the recent tickets about similar topic about Thingy 53 in this platform, I saw that the supposed FW was "edge_impulse_1.0.0_thingy53_nrf5340.zip" which was included in the "2022-08-03-precompiled-application-firmware" included in the device's page in Nordic (https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-53/Downloads?lang=en#infotabs)

So i "wrote" this zip file using the same process (DFU mode & Programmer tool). After writing the fw, I can again see the device from the nRF Edge Impulse Mobile App, however when I try to connect to it, the RGB LED turns 'RED' and the connection times out. 

I tried several other things without success and I see from the tickets that similar issue is reported by others 

• Case ID: 302592

To summarize I need the the correct procedure & FW to set the Thingy 53 to its original state as it was shipped to me. 

Thank you for your time.

Selim Gullulu

[Øyvind]

Hello Selim, 

Turned my device off and on and tried to connect to it with the Edge Impulse Mobile App, the device was discoverable, however never managed to connect to it.

I tried the same on my side and see that the RGB LED turns RED as well. I will ask our developers, however, the edge impulse FW delivered through our precompiled package is developed by Edge Impulse themselves. More information can be found here in the Edge Impulse Thingy:53 documentation.

In order to get out of the "RED LED", I found that you can go to Inferencing and then click on Start. Now your device should respond and you will be able to test the current model/impulse i.e. idle, snake, up-down, and wave. 

Turned my device off and on and tried to connect to it with the Edge Impulse Mobile App, the device was discoverable, however never managed to connect to it.

I'm not sure if the nRF Edge Impulse app is usable with any other app than the Edge Impulse FW. Did you try the Deploy button in the app itself?

Kind regards,
Øyvind

[drselim]

Hello Oyvind, thank you for the fast response. 

As I mentioned, after "writing" the 'edge_impulse_1.0.0_thingy53_nrf5340.zip' on the device, I can not connect to the thingy 53 from the Edge Impulse App, and as I try to connect the RED LED is on and the connection always times out. 

Is my understanding correct: you managed to connect to the Thingy via the edge impulse app (after programming the device with the programmer tool with edge_impulse_1.0.0_thingy53_nrf5340.zip) even though the RGB LED turns RED as soon as you tap to connect? and after that you could go to inferencing tab and tap on 'start' since, in my case, the 'start' icon is inactive since I'm not connected to the Thingy at the first place. 

nRF app should be usable for such classification purposes, there's already a similar example here which uses the microphone as input and makes classification (4 classes):

https://docs.edgeimpulse.com/experts/prototype-and-concept-projects/environmental-noise-classification

To conclude, I'm still stuck at the stage where I 'write' the edge_impulse_1.0.0_thingy53_nrf5340.zip file via programmer and not able to connect to the Thingy 53 via the edge impulse app.

Thank you.

Selim

[Øyvind]

drselim said:

I was thinking of doing the proposal, I ordered a 10 pin SWD cable for connection between the 7002 DK and the Thingy 53 and waiting for it to arrive, As soon as I receive it I'll update the ticket here and at edge impulse..

Yes, at this time I would agree that the next step is to reprogram the device using an external programmer as you propose. Make sure to perform the full erase and then try to reprogram the Edge Impulse sample from the procompiled package using the Programmer app in nRF Connect for Desktop.

[drselim]

Thank you Oyvind, I'll let you know when I perform it. I also documented my project in a video, you can take a look at it if you'd like:

https://youtu.be/dQrAdGYdvfs

[Øyvind]

drselim said:

Thank you Oyvind, I'll let you know when I perform it

Looking forward to hear back from you. 

drselim said:

I also documented my project in a video, you can take a look at it if you'd like:

This is excellent! Great work!

[drselim]

Thank you!

[drselim]

Hi Oyvind, I haven't tested to re-program the Thingy:53 with the external programmer yet. However I programmed the nRF52840 Dongle as BLE sniffer and captured the process with Wireshark. I'm attaching the capture log. In the log, c9:43:2e:a7:d5:40 is the Thingy:53 edge impulse, and the 7d:9c:d2:d2:5c:15 is the nRFEndgeImpulse mobile app on my phone. 

I could not understand the reason from the log, maybe you can help me with it. I see that at packet nr 5025, CONNECT_IND is sent, connection is created (since we see master_... messages), but no connection is established since no response is received from the Thingy. (no Slave_... messages) 

CAn it be related with channel selection algorithm? I see that in the advertisement Thingy sends CSA2, however the app sends CSA as 1 in the Connect_IND.

Regards

Selim

9_3_2023_thingy53_edge_impls_mob_app_connect_att.pcapng

[drselim]

Hi Oyvind, I could not access the Thingy:53 with the SWD cable over nRF7002DK. I created another ticket with the details:

https://devzone.nordicsemi.com/f/nordic-q-a/97805/thingy-53-can-t-be-reached-with-programmer-tool-nrfjprog-using-swd-cable-over-nrf7002dk

• Case ID: 304739

Thanks

[drselim]

Hi Øyvind The issue is solved with upgrading the programmer app to 3.0.8 in nRF connect for desktop 4.0.1. Now as I write the "edge_impulse_1.0.0_thingy53_nrf5340" from "2023-03-24-precompiled-application-firmware" (https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-53/Downloads#infotabs) the Thingy:53 goes back to its original state and I can connect with the Edge Impulse mobile app and collect sensor data. Thank you for your support.

Selim