• State Verified Answer
  • Replies 10 replies
  • Subscribers 74 subscribers
  • Views 5812 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 204631
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Thingy 52 - can't connect - thingy keeps restarting

Jakub J.

Hello

Recently, after a long time not using my Thingy52,  I encountered a problem with it. I cannot connect to the device. Earlier it worked fine (can't remember if it was prior to the fw update or something).

Tried reflashing it with the newest software (the oldest available too), I uninstalled and installed the thingy app on my android, tried connected with nRF Connect.

Whenever I try connect to the device, the green led turns on for a moment and then blue breathing led comes in. It seems that as soon as I connect to the device, the thingy restarts itself.

Any ideas?

Parents
  • 0

    The green light on the Thingy device means it is already connected to another Bluetooth device. When it turns blue, this is the default mode for the Thingy. I also believe this means that the Bluetooth device that is connected to the Thingy is not currently connected (i.e. might be turned off). 

    How did you flash the newest firmware to the Thingy? Via an nrf52 DK & a SWD cable? Are you able to connect to the Thingy device & change the color of the LEDs? Or does the Thingy restart every time you try to connect? This case might be useful.

  • 0 in reply to Bjørn Kvaale

    I flashed Thingy using an SWD cable and Segger J-Link Plus.

    Problem is I am not able to connect at all.  When I'm pairing the Thingy with Thingy Android app, as soon the device got paired and I am able to set its name I get a message that device has disconnected. Later I am not able to reconnect.

    Both during initial connection and later when trying reconnecting there is one flash of green light and then it seems to restart (blue light is flashing. I guess this is my latest LED Setting)

    I checked the privileges on my android and everything is alright. 

  • 0 in reply to Jakub J.

    There could be something fishy happening with the Samsung A3 phone. We have noticed that sometimes the A series from Samsung breaks the Bluetooth spec, which might lead to this issue (see link). Could you try downloading the nrf sniffer software & using your nrf52 pca10040 as a bluetooth sniffer & sniffing what happens when you try to connect your Samsung to the Thingy device? You can post the sniffer log here & I will take a look at it. 

    Do you another phone you can test with to see if you can connect to the Nordic Thingy:52 device?

  • 0 in reply to Bjørn Kvaale

    connect.pcapng

    connect2.pcapng

    Initial.pcapng

    Initial.pcapng shows traffic during initial connection with thingy.
    connect.pcapng and connect2.pcapng shows traffic after the thingy was found and added, when I try to connect to it.

    I'll try to borrow some other phone to try it out over the weekend.

  • 0 in reply to Jakub J.

    Have you been able to test with another phone? Did it work to connect to the Thingy:52 then? My sniffer has been slightly buggy, so I have not been able to do a sniffer trace of my Thingy:52 with an iPhone 8 yet. From your wireshark sniffer traces, it seems connection is not established between the phone & the Thingy:52 (like you mentioned previously, the Thingy device resets itself). 

  • 0 in reply to Bjørn Kvaale

    I tried it with Samsung S6, it worked perfectly.

    How Thingy's firmware is different from examples projects available in SDK14.2? I use my Samsung A3 while developing projects using NRF51 and NRF52 and everything works just fine.

  • +1 in reply to Jakub J.

    Good to know that it works on the Samsung Galaxy S6!

    The Thingy's firmware is based on SDK 13. You could test your Samsung A3 with an example from SDK 13 & see how that works on the nrf52. If it works on the nrf52 dk, it should work on the Thingy, as both use the same nrf52832 chip.

    The Thingy also uses a different softdevice than in SDK 14.2 (believe it is S132 v4.0.2). You could try this link here to see if that is helpful. Even though it seems the Samsung A3 is doing something incorrect, oftentimes we are able to update our Softdevice to take this into account. In this case, it seems updating to a newer softdevice fixed the issue.

    I'll let you know when I get the sniffer trace working & will post it here.

Reply
  • +1 in reply to Jakub J.

    Good to know that it works on the Samsung Galaxy S6!

    The Thingy's firmware is based on SDK 13. You could test your Samsung A3 with an example from SDK 13 & see how that works on the nrf52. If it works on the nrf52 dk, it should work on the Thingy, as both use the same nrf52832 chip.

    The Thingy also uses a different softdevice than in SDK 14.2 (believe it is S132 v4.0.2). You could try this link here to see if that is helpful. Even though it seems the Samsung A3 is doing something incorrect, oftentimes we are able to update our Softdevice to take this into account. In this case, it seems updating to a newer softdevice fixed the issue.

    I'll let you know when I get the sniffer trace working & will post it here.

Children
Related
Terms of service