Electron blinking cyan and green along with red bursts

I have had an issue where a couple of electrons randomly started flashing cyan after working fine for few months. On pressing the restart button, the electrons started flashing green and cyan with red bursts. We managed to fix the issue using this topic.

For me to be able to fix this issue, I had to physically connect the electron via a usb cable and run the commands mentioned in the above link. This makes it impossible to fix this issue when electron is deployed on a remote site. Has anyone else has witnessed this problem and found a way to fix this issue remotely?

What Device OS version are you running on your Electrons?


The lost keys, lost settings, and lost boot loader may be variations of this problem.

When some situation, it tends to be a low-power brown-out type of situation, occurs, it appears that certain flash sectors can be erased. Sometimes, it’s the sector that contains settings (like Wi-Fi settings or device keys), and sometimes it’s the boot loader.

When the boot loader gets erased, the only thing that happens is the blue D7 LED will light dimly, and it will not respond to other buttons. When this happens, we typically replace the device, though users can typically fix it with JTAG/SWD programmer.

This has a tendency to occur on Electrons mainly because more of them operate on battery power. It can also occur on Photons. It has also been seen on a RedBear Duo. All of these devices have similar STM32F205 processors, however. It also is not specific to battery power, it can happen when using a power adapter as well, though much less frequently.

Also, it’s not simply running at a low voltage. The processor has protection for that, and we’ve tried running the devices at all voltage levels and can’t make the problem happen. It appears to be some combination of factors that is quite elusive.

For battery powered devices, the best workaround until the problem is solved is to make sure you don’t run until the power goes completely out. Instead, use sleep modes to conserve power until sufficient power is available again. I recommend running with SYSTEM_MODE(SEMI_AUTOMATIC) and checking the battery SoC at boot or after waking from sleep. If it’s below 15 to 20% SOC, immediately go back to sleep and do not turn on the modem.

We’ve added code to system firmware 0.7.0 to be able to recover the server key automatically if this occurs, as well, though this may not work in all cases.

For automatically restoring your device private keys, this library can be used.

1 Like