• State Verified Answer
  • Replies 19 replies
  • Subscribers 63 subscribers
  • Views 2279 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

Parents
  • 0

    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

  • 0 in reply to Øyvind

    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

  • 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

  • 0 in reply to drselim

    Hi Selim, I've tried to reproduce your issue and I'm not sure if I am able to do so. Here are the steps I took: 

    1. Reprogrammed the Thingy:53 with thingy53_fw_2022-08-03-precompiled-application-firmware\2022-08-03-precompiled-application-firmware\Edge_Impulse using my JLink Base compact. (As I had installed another sample which did not provide USB UART). Red, Green and Blue blinked to indicate start.

    2. Connected to Thingy:53 using the nRF Edge Impulse app v1.0.4 (iOS 16.2). This would turn on RED LED.

    3. Data Aquisition --> record new data i.e. updown for motion recognition project. No issues, RED LED still on. 

    4. Deployment --> build project. First time fails on upload, then I click on retry. Starts to upload and applies update. RED LED turns off. Thingy:53 disconnected. 

    5. Reconnect under Devices. RED LED on.

    6. Switched to nRF Programmer. Try to install nRF Machine Learning. Device is not visible in list. RED LED still on.

    7. Switch back to nRF Edge Impulse. Error: "Lost Device Rremot Management Connection. Disconnecting from device." RED LED still on.

    8. Try to reconnect in nRF Edge Impulse. Not possible --> Connection Timed out. 

    9. Turn off and on Thingy:53. Reconnect in nRF Edge Impulse. RED LED on. Disconnect in nRF Edge Impulse. RED LED off.

    10. Switch to nRF Programmer. Install nRF Machine Learning. Device is visible in list. Update without issues. 

    11. Thingy:53 blinking as per nRF Machine Learning --> device changed name to EI Thingy53. Reinstall Edge Impulse through nRF Programmer with success. Asked to forget device in app --> removed.

    12. Switch back to nRF Edge Impulse. Connect to device. RED LED on. iPhone screen turned off and lock: Error: Lost Device Remote Management connection. Disconnecting from device. RED LED still on.

    13. Try to reconnect in nRF Edge Impulse. Connection time out.

  • 0 in reply to Øyvind

    Hi Oyvind, thanks a lot for your efforts. At the moment the situation is the same for me, as I load the edge impulse Fw using the nRF connect for desktop -> Programmer. After turning the Thingy off and on, I still can not connect with the nRF Edge Impulse App, the led goes RED and the connection always times out.

    I created a ticket at the Edge Impulse forum as well:

    --------

    https://forum.edgeimpulse.com/t/thingy-53-cant-connect-with-edge-impulse-app-after-rolling-back-to-initial-edge-impulse-fw/6573

    Edge Impulse team's reply:

    Hi @drselim !
    Your problem looks like an issue with CPUNET firmware (Bluetooth core), not with Edge Impulse firmware. However, I recommend getting an external programmer (e.g. nRF5340DK) and trying to perform a full-erase chip and flash from scratch using the firmware from the Nordic website.
    Let me know if you have any progress or update on this topic.

    Best regards,
    Mateusz

    -----------

    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..

    I think that I somehow managed to create a corrupt firmware with Edge Impulse Studio website (I did not use the mobile app, I used it just to get sensor logs, then I switched to studio web) to create the ML model and the firmware. And now I can not remove / repair that corruption with the nrf connect desktop -> programmer tool. 

    Regards

    Selim

Reply
  • 0 in reply to Øyvind

    Hi Oyvind, thanks a lot for your efforts. At the moment the situation is the same for me, as I load the edge impulse Fw using the nRF connect for desktop -> Programmer. After turning the Thingy off and on, I still can not connect with the nRF Edge Impulse App, the led goes RED and the connection always times out.

    I created a ticket at the Edge Impulse forum as well:

    --------

    https://forum.edgeimpulse.com/t/thingy-53-cant-connect-with-edge-impulse-app-after-rolling-back-to-initial-edge-impulse-fw/6573

    Edge Impulse team's reply:

    Hi @drselim !
    Your problem looks like an issue with CPUNET firmware (Bluetooth core), not with Edge Impulse firmware. However, I recommend getting an external programmer (e.g. nRF5340DK) and trying to perform a full-erase chip and flash from scratch using the firmware from the Nordic website.
    Let me know if you have any progress or update on this topic.

    Best regards,
    Mateusz

    -----------

    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..

    I think that I somehow managed to create a corrupt firmware with Edge Impulse Studio website (I did not use the mobile app, I used it just to get sensor logs, then I switched to studio web) to create the ML model and the firmware. And now I can not remove / repair that corruption with the nrf connect desktop -> programmer tool. 

    Regards

    Selim

Children
Related