• State Verified Answer
  • Replies 19 replies
  • Subscribers 63 subscribers
  • Views 2272 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 302938
Options

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

  • 0 in reply to drselim
    drselim said:
    Could you attach the hex/zip file for the blinky in this post? I'd like to follow the exact scenario with yours. I just tried to create a new build for the blinky example in Visual Studio Code by choosing thingy53_nrf5340_cpuapp_ns ( I tried it with thingy53_nrf5340_cpuapp as well, same result happening) 

    I did not get it working, it was a mere test to verify non-funtion, which I programmed using an external JLink programmer. 

    In order to make it work one must follow the steps provided in Developing with Thingy:53. My point was that I upgraded from a non-working sample using the USB Bootloader to one of the working precompiled samples. This way I could also use the the nRF Programmer for Thingy:53 enabling FOTA update from smart phone to Thingy:53. 


  • 0 in reply to Øyvind

    Can you try to write the FW that I built using edge impulse, and then try to roll back to the original FW?

    Here's my fw:

    drselim-tvprogram_recognition-thingy53-v4.zip

    By the way, I discovered the serial connection to the device and use the AT commands on it .

    I also checked for my fw, and it works (makes classification based on color sensor) however the problem is with the bluetooth connection which fails in all apps including nRF Connect, nRFProgrammer and nRF EdgeImpulse.

  • 0 in reply to drselim

    I tested with your application.


    No issues with updating from your application to Edge Impulse project in nRF Programmer for Thingy:53.

    drselim said:
    bluetooth connection which fails in all apps including nRF Connect, nRFProgrammer and nRF EdgeImpulse

    Can you elaborate more on what happens? When does it loose connection?  What phone are you testing with?

  • 0 in reply to Øyvind
    1. Hi Oyvind, once again thank you for your efforts. In my case, when I write the edge impulse fw with the programmer, I can see the device in nRF edge impulse app, i tap to connect to it, the led turns red and the connection times out. I also tried to connect with nRF programmer which again turns the led red and also times out (ı had attached the screenshot of log previously, there’s astrange error log there: “device capabilities not supported”)

    I am using iphone 8 plus with ios15.7.1 . Strange thing is when i first received the device I had no issues with connecting to it with nrf edge impulse app. The connection problem occured after I used my classification fw.

    Today I am out of town, I can provide you more  logs tonorrow. 
    Thanks

  • 0 in reply to drselim

    Hi Oyvind, I updated the nrf connect for desktop to 4.0 and again tried with the programmer tool, the situation is exactly the same: when I try to connect to the Thingy (Edge Impulse) in the nRF Edge Impulse app, the LED turns RED and times out. 

    Could you find a chance to inspect the warning log that I provided while trying to connect with the nRF programmer App:

    "“device capabilities not supported”

    Regards

    Selim

Related