thingy 52 crash

[Marty de Vries]

We recently purchased a few Thingy 52s, and we're very impressed with the simplicity!

After playing with the Thingy 52,and upgrading the FW to 2.2.0, I noticed that the device locks up after a while. This manifests itself as a blinking yellow/green LED, and it's not possible to connect to the Thingy anymore.

The only way to get back control is to turn the power off and then back on again.

In 'normal operation', the blue LED is flashing away happily, and when the device enters sleep, pressing the button on the front of device or shaking it usually works. However, this 'locked up' state appears quite often.

Any ideas?

-Marty.

[Karl Ylvisaker]

Hello,

we're very impressed with the simplicity!

I am happy to hear that you enjoyed the Thingy:52!

After playing with the Thingy 52,and upgrading the FW to 2.2.0, I noticed that the device locks up after a while. This manifests itself as a blinking yellow/green LED, and it's not possible to connect to the Thingy anymore.

Could you elaborate on what application or sample you were running the Thingy:52 with at the time? Could you also elaborate how you have programmed your device?
Please see this ticket regarding flashing .hex files to the Thingy:52.
Blinking green means that the Thingy:52 is in bootloader mode. Bootloader mode can be entered by holding down the button upon power-up. Is this something you might have done accidentally?
Rapidly fading in an out yellow LED means that the Thingy:52 has entered DFU mode.
Both of which will be resolved by a power-cycling, placing the device back at the application start.
So, what remains is to identify the reason for the Thingy:52 to enter the bootloader/DFU mode.

To find out more about why this happens, I will need to know more about what application the Thingy:52 is running.

Looking forward to resolving this issue together,

Best regards,
Karl