Light's Hope Hardware Changed. Reload Default Settings?

Condition LED - Boron

You are viewing the Status LED and Device Modes for the Boron. To view the documentation for other devices, use the blue device selector beneath the Particle logo on the left side of the page.

Standard Modes

These modes are the typical behaviors you will run into from your device on a regular ground. They are the light patterns of a healthy device.

Here's the typical blueprint of after power upwardly.

Connected

When it is breathing cyan, your device is happily connected to the Net. When it is in this mode, you lot can telephone call functions and flash code.

OTA Firmware Update

If your device is blinking magenta (reddish and blue at the same time), it is currently loading an app or updating its firmware. This state is triggered by a firmware update or past flashing lawmaking from the Web IDE, CLI, or Workbench. You might encounter this style when you connect your device to the cloud for the first time.

Note that, if you enter this way past holding Mode on kick, blinking magenta indicates that letting go of the Manner button will enter safe mode to connect to the cloud and not run application firmware.

Looking For Cyberspace

If your device is blinking green, information technology is trying to connect to cellular.

More information

Electrons that are blinking green have successfully read the APN data from the inserted SIM card and are attempting to connect to a cellular tower. At that place are many different reasons that your Electron might fail to connect to your nearby cellular network. Here are a few things yous tin bank check if you find your device in an endless loop (5 minutes+) of blinking green:

1) Is your Electron compatible with your local cellular network?

There are three different variants of the Electron, and they each work in different parts of the earth:

The Boron LTE can be used in other locations with a tertiary-party SIM menu on bands 2, three, 4, five, 8, 12, 13, twenty, and 28.

Make sure that your device is uniform with the cellular infrastructure in your country. Small state-by-country variations from the generalized tabular array to a higher place may apply. For a detailed list of 3G service state by country, please visit the post-obit link.

If your device is not compatible with the cellular infrastructure in your land, information technology will be unable to connect to the Internet using a Particle SIM or any other SIM.

ii) Is your antenna connected?

Your Electron cannot connect without the included external cellular antenna. Please make certain it is connected every bit depicted below:

3) Is your bombardment connected?

Your Electron, Eastward Series E310, or Boron 2G/3G requires a Li-Po battery or high current power source to communicate wirelessly. Brand sure your battery is continued as depicted beneath:

While the Electron does non require that yous adhere the USB cable, this volition ensure that your battery does not run out of accuse during the connection procedure.

The E Series E402 (LTE Cat M1) and Boron LTE can exist used merely powered past USB.

iv) Is your SIM activated?

In social club for your Particle SIM carte du jour to connect to the cellular network, it needs to be activated. The simply style to exercise this is to go through SIM activation and setup at https://setup.particle.io or the mobile apps. Follow the on-screen prompts to complete device setup and SIM activation.

five) Are you using a tertiary party (non-Particle) SIM?

If yous're not using a Particle SIM, yous will take to change the cellular APN on the Electron before it can connect. A Username and Password may too exist required. To connect the Electron with a 3rd party SIM, visit our setup folio, cull "Setup an Electron with SIM card" and follow the on screen instructions to set your APN, download a new firmware binary, and flash it to your device.

NOTE: Until you have done this, your device will not be able to connect to the Cyberspace.

If y'all are using the Boron, you should follow the Boron 3rd-party SIM instructions instead.

six) Check the cellular coverage in your area

The Electron leverages a number of cellular carriers to provide excellent coverage, just it is possible that you are outside GSM coverage in your country. Fortunately, information technology's relatively simple to cheque:

• Notice the carrier from the carrier listing
• Use a tool such as the OpenSignal mobile app to discover coverage. The OpenSignal apps for iOS and Android can provide coverage information earth-wide.
• If y'all are using an E Series E402 (LTE) or Boron LTE, the born Particle SIM card can simply be used in the United States, on AT&T. It will just piece of work in areas with LTE coverage; it cannot fall back to 3G.

If you lot are outside of the coverage map, it's possible that the Particle SIM does not have coverage in your area, and your device will be unable to connect. We are always looking to expand our coverage network, and promise to provide coverage in your area soon!

vii) Check the cellular reception in your location

Cellular coverage and cellular reception are slightly dissimilar. Coverage is determined past the location and availability of cellular towers in your neighborhood. Fifty-fifty if there is coverage, your device might not take reception. Things like RF interference, being in a basement, or a damaged antenna might affect your device's ability to get a skillful point from the cell belfry nearby.

In that location are a bunch of things that you can do to improve your cellular reception:

• Check the coverage on your telephone (if it is on a GSM network) as a comparison indicate. Do you become a practiced signal?
• Try going outside, or by a window, to confirm that your device tin can connect

eight) Check your data limit

If you lot've been using your Electron successfully for a while and it's at present just started flashing green, you might have hit your data limit, and your SIM might be paused. You can check your information usage and update your information limits past visiting the SIM console at the following link:

https://console.particle.io/billing

9) Cold kicking your device

If all else fails, try restarting information technology! Remove both the USB cable and Li-Po battery from the Electron, so that the RGB LED fully powers off. Then, reconnect the Li-Po battery and USB cable--the Electron should reboot and retry the connection sequence.

x) Are Particle's mobile carriers experiencing issues?

Bank check out our status page to see if there'south a known issue with Particle's mobile carriers.

11) Contact Particle

Still having issues? Write us an email and include the following to assistance us with troubleshooting:

• Your Device ID
• Your ICCID (SIM Number)
• A photo of your device setup to help with troubleshooting.

Connecting to the Cloud

When the device is in the process of connecting to the deject, information technology will rapidly glimmer cyan. You frequently run across this mode when y'all starting time connect your device to a network, after it has merely blinked green.

Listening Mode

When your device is in Listening Mode, information technology is waiting for you lot to configure your mesh network, or is waiting for configuration by USB serial.

Commonly, when you lot've successfully configured your Gen 3 device using the mobile apps for iOS or Android, the setup consummate flag is set up and you will exit Listening Mode.

If yous have reset your configuration or have gear up using USB, you may need to manually set the configuration washed flag using these instructions to employ the particle usb setup-done control.

To put your device in Listening Mode, hold the Manner button for three seconds, until the RGB LED begins blinking blue.

You lot can also utilise particle usb start-listening to enter listening manner.

Cellular Signal Forcefulness

Tapping the Fashion button on your device will glimmer out the bars of signal strength. More than blinks indicate a stronger signal.

Network Reset (fast blinking blue)

To erase the stored network settings on your device, hold the MODE button blinks dark blue, then go along to hold it down for nigh ten seconds longer, until the RGB LED blinks blue rapidly, then release.

• For all Gen 3 devices information technology will clear the mesh settings and the setup complete flag, and then the device will go back into setup fashion (listening mode)
• For the Argon it will also articulate Wi-Fi settings.
• For the Boron, it will besides articulate the cellular APN and SIM pick.
• For Ethernet, information technology volition also clear the using Ethernet flag.

Cellular Off

If your device is breathing white, the cellular module is off. You might encounter this mode if:

• You take set your module to Manual or SEMI_AUTOMATIC in your user firmware
• Yous have called Cellular.off() or WiFi.off() in your user firmware

Safe Mode

Condom style, breathing magenta (ruby and blue at the aforementioned fourth dimension), connects the device to the deject, simply does non run whatsoever awarding firmware. This mode is one of the most useful for development or for troubleshooting. If something goes wrong with the app you lot loaded onto your device, you can fix your device to Condom Mode. This runs the Device Os but doesn't execute any application code, which tin be useful if the application code contains bugs that end the device from connecting to the cloud.

The device indicates that it is in Safe Mode with the LED animate magenta.

To put your device in Safe Style:

1. Hold downwards BOTH buttons
2. Release only the RESET push button, while holding down the Mode button.
3. Wait for the LED to start blinking magenta
4. Release the Mode button

Before inbound rubber mode, the device will proceed through the normal steps of connecting to the cloud; blinking dark-green, blinking cyan, and fast blinking cyan. If you're unable to connect to the cloud, yous won't actually end up with breathing magenta, just execution of awarding firmware volition withal be blocked - so y'all are in a "sort-of rubber way" (e.grand. to enter "Prophylactic Listening Fashion").

The device will itself automatically enter safe mode if there is no awarding lawmaking flashed to the device or when the application is not valid.

You can too utilise the particle usb safe-mode command to enter safe fashion.

DFU Manner (Device Firmware Upgrade)

If you lot wish to program your device with a custom firmware via USB, you'll need to apply this mode. This fashion triggers the on-board bootloader that accepts firmware binary files via dfu-util

Installation tutorial can be found here.

And a usage guide here.

To enter DFU Mode:

1. Concord down BOTH buttons
2. Release only the RESET button, while belongings downwardly the Fashion push.
3. Await for the LED to start flashing yellow (it volition wink magenta showtime)
4. Release the Way button

The device now is in the DFU fashion.

DFU manner requires device drivers under Windows. These should automatically be installed by the Particle CLI installer, merely if you call up yous are having driver issues, at that place are boosted DFU troubleshooting tips hither.

Some users have reported issues with dfu-util on a USB3 ports (typically the blueish ones). Use a USB2 port if the USB3 port doesn't work.

Y'all tin likewise utilize the particle usb dfu command to enter DFU mode.

Firmware Reset

Gen 3 devices tin store a backup re-create of any desired user firmware in wink memory at accost 0x80200000, separate from user wink memory which is located at 0x000D4000. This fill-in copy of firmware can be restored to user memory with a button sequence that is only available when the backup re-create flash memory contains a valid firmware epitome.

To program your device with a backup re-create of user firmware via USB, yous'll demand to put it in DFU Style and run a command like ane of the following:

Argon:

          dfu-util -d 2b04:d00c -a ii -s 0x80200000 -D tinker-0.8.0-rc.25-argon.bin                  

Boron:

          dfu-util -d 2b04:d00d -a two -s 0x80200000 -D tinker-0.viii.0-rc.25-boron.bin                  

Xenon:

          dfu-util -d 2b04:d00e -a 2 -s 0x80200000 -D tinker-0.8.0-rc.25-xenon.bin                  

You don't have to wink tinker, of grade, that'southward only an instance. Note that the d00c, d00d, or d00e varies depending on the type of device which is why there are 3 different commands.

To factory reset the user firmware after flashing valid firmware using the previous pace:

Hold down the Way button and tap RESET. The status LED will glimmer:

• Magenta (cherry and bluish at the same fourth dimension, safe mode)
• Yellow (DFU way)
• Fast blinking yellow (restore factory firmware)

Exist sure to release the mode button every bit soon as you lot get to fast blinking yellowish, otherwise you'll get one stride farther and clear all of your settings as well.

Factory Reset

Gen 3 (Argon, Boron) devices from the mill somewhat ironically exercise not accept a factory user firmware backup image installed. Thus it's best if you pre-install 1 using the steps above first.

To factory reset, hold down the Manner button and tap RESET. The status LED will blink:

• Magenta (red and blueish at the same time, safe mode)
• Yellow (DFU manner)
• Fast blinking yellowish (restore factory firmware)
• Fast blinking white (factory reset)

This will:

• Restore the manufacturing plant backup user firmware (if present)
• Clear mesh credentials (1.5.2 and earlier)
• Boron: Clear any saved APN and default to internal SIM
• Argon: Clear Wi-Fi credentials
• Ethernet: Clear the using Ethernet flag
• Articulate the setup complete flag, to strength setup way once more

Troubleshooting Modes

These modes allow y'all know about more than singular issues your device might exist exhibiting. Use this section to troubleshoot strange colors you might see from your device.

Cloud Non Connected

When your device is continued to cellular merely not to the cloud, it will be breathing light-green.

More than data

I can't wink my device anymore

Breathing green means that cellular is on, only you lot're not connected to the Particle cloud. Because of this, yous cannot flash your device from the cloud. That includes the Particle Web IDE, Particle Workbench, and Particle CLI cloud-based flashing commands.

Fortunately, you lot tin usually get effectually this past inbound condom mode, breathing magenta.

Hold downwards RESET and Fashion, release RESET and continue to hold downwards MODE until the device blinks magenta, then release MODE. The device will and then get through the normal sequence of colors: blinking green, blinking cyan, fast blinking cyan, so breathing magenta. Once breathing magenta, you should be able to OTA flash again.

But to go rid of the breathing green, yous'll probably need to make some changes to your lawmaking.

Cause 1: Blocking the loop

In this simple program, you'll breathe cyan, so nearly ten seconds after, you'll go to animate green. Why? You've blocked the loop from returning, and in the default threading and arrangement fashion, that stops the cloud from being processed, which causes breathing green.

Don't do this:

            void setup() { }  void loop() {      // Don't do this: preventing loop from returning will cause breathing light-green     while(true) {      } }                      

Of class your code probably has a more subtle bug than that. For example, if you take a part that's called from setup or loop that never returns, that tin cause problems.

Some libraries that deal with sensor hardware might deport strangely when the hardware is not bachelor, which could cause a call to cake forever equally well.

Solution i: Add some Particle.process() calls

One way to solve this is to sprinkle Particle.process() calls in code that blocks. You might practise something like this:

            void waitForSwitch() {     while(digitalRead(D7) == High) {         // Without the following line, you'd go into breathing green         Particle.procedure();     } }                      

In general it's better to structure your code and so it always returns from loop(), but if that's not a viable solution, yous tin sprinkle some Particle.process() calls in your code.

Solution ii: Enable SYSTEM_THREAD

The other solution is to apply SYSTEM_THREAD way.

            SYSTEM_THREAD(ENABLED);                      

You insert this at the top of your source file. What it does is run the cloud processing in a separate arrangement thread, so if y'all block your loop, the cloud will all the same be serviced and yous will stay in breathing cyan instead of going to breathing green.

The just thing to exist conscientious is that when you practice this, your loop lawmaking will run before connected to the cloud. 1 solution is to add this in your setup() code, before you practice any Particle.publish calls:

            waitUntil(Particle.connected);                      

You might also practice something like this in loop():

            if (Particle.connected()) {     Particle.publish("myEvent", PRIVATE); }                      

Rainbows/Nyan

Using the Signal option in the Web IDE, or the particle deject nyan CLI command, you can have a device's condition LED brandish a rainbow pattern. This is handy if y'all have multiple devices nearby and are not certain which one is which.

Red Blink Bones Errors

Blinking red indicates diverse errors.

While connecting to the Cloud, the RGB LED will exist blinking cyan followed by:

• ane orange blink: Decryption fault.
• 2 orange blinks: Could not accomplish the internet.
• 3 orange blinks: Connected to the cyberspace, just could not achieve the Particle Device Cloud. This sometimes is seen as yellow or scarlet and indicates bad server keys.
• ane magenta blink: Authentication error.
• one cerise blink: Generic handshake error. The device could have the wrong keys or has but encountered a generic error in the handshake process.

Repair instructions

Almost keys related issues can be resolved using the Particle CLI.

Put the device into Listening mode (blinking blue) by holding down Fashion until it blinks blueish. Then issue the CLI control:

            particle identify                      

Salvage the Device ID; you'll need it later.

Then put the device in DFU manner past holding down both the RESET and MODE buttons, releasing RESET and continuing to concord down Fashion until it blinks yellowish and result the commands below, in order.

            particle keys server particle keys physician YOUR_DEVICE_ID                      

If you become this error under Windows:

            'openssl' is non recognized every bit an internal or external control, operable program or batch file.                      

it may work if you practise:

            cd c:\OpenSSL-Win32\bin particle keys doctor YOUR_DEVICE_ID                      

There are additional tips for a missing openssl error on this page, including tips for macOS (Os X) and Linux.

Red Wink SOS

Is your device blinking ruby? Oh no!

A pattern of more than 10 carmine blinks is caused by the firmware crashing. The pattern is 3 short blinks, 3 long blinks, 3 short blinks (SOS pattern), followed by a number of blinks that depend on the fault, and so the SOS pattern again.

Enter condom mode, tweak your firmware and endeavor again!

You can as well reset your device to a known state by following these instructions.

There are a number of other scarlet glimmer codes that may be expressed after the SOS blinks:

1. Hard fault
2. Non-maskable interrupt fault
3. Retention Manager mistake
4. Passenger vehicle mistake
5. Usage fault
6. Invalid length
7. Exit
8. Out of heap memory
9. SPI over-run
10. Assertion failure
11. Invalid instance
12. Pure virtual call
13. Stack overflow
14. Heap mistake

The two most common ones are:

Difficult Error (1 blink betwixt 2 SOS patterns)

Some causes of hard fault include:

• Using an invalid pointer.
• Memory corruption caused by freeing retention twice, overwriting the end of a block of retention, etc.
• Making Wire (I2C) calls without calling Wire.begin().

Exit (7 blinks between two SOS patterns)

This occurs if the standard C part abort() is chosen. In a Unix program, this would be used to abruptly stop the procedure. Device Bone itself does not use this function, simply the SOS can happen if user firmware calls arrest() or _exit(). Since Particle devices just effectively support a unmarried procedure, the user firmware, the effect is an SOS+7 and reboot. This could besides happen if a library used abort().

Out of heap memory (8 blinks betwixt two SOS patterns)

If your device crashes repeatedly with an SOS code, first try recovering with Safe Mode and flashing Tinker with the CLI to see if it was something recently added in your user application.

          particle flash <mydevice> tinker                  

Some tips for reducing the retentivity used by your firmware can be constitute here.

Assertion failure (10 blinks between 2 SOS patterns)

Assertion failure is triggered when a examination for something that should never occur occurs, and there is no solution other than to SOS and restart.

Code might do this if the internal state is invalid and non what is expected, for example. Or something that should never happen and is non-recoverable, for example if the system thread cannot be created.

At the moment, all of the AssertionFailures are in things related to threads and the arrangement thread, but that'due south just because those are the only things that have been instrumented with an AssertionFailure panic.

Stack overflow (thirteen blinks between 2 SOS patterns)

Stack overflow occurs when yous endeavor to store too much information on the stack. The size is quite express, and storing large temporary objects on the stack can cause issues.

• Main loop thread: 6144 bytes
• Software timer callbacks: 1024 bytes

Heap error (14 blinks between 2 SOS patterns)

SOS+14 signifies:

• Semaphore lock timeout
• Since 0.eight.0 60 seconds expired while trying to acquire a semaphore lock, likely due to dynamic memory allotment
• Since i.2.0 Other heap-related fault, such as allocating retentiveness from an ISR

Prior to 1.two.0, attempting to allocate memory from an interrupt service routine would sometimes work, and sometimes corrupt the heap causing the software to crash sometime afterward, while doing something completely different. Since this is very difficult to debug, now a SOS+fourteen is thrown immediately.

Some locations that are interrupt service routines:

• ISRs attached using attachInterrupt
• Organisation event push handlers (just button_status, button_click, and button_final_click handlers, non all organisation events)
• SPI transaction callbacks
• SparkIntervalTimer library timer callbacks

Things you should non do from an ISR:

• Any retention allocation or costless: new, delete, malloc, free, strdup, etc.
• Any Particle class function like Particle.publish, Particle.subscribe, etc.
• Most API functions, with the exception of pinSetFast, pinResetFast, and analogRead.
• delay or other functions that block
• Log.info, Log.error, etc.
• sprintf, Series.printlnf, etc. with a %f (bladder) value.

Solid colors

Solid colors are rare. In that location simply expected state of affairs is:

• Solid magenta if y'all are loading code in ymodem serial way.

In most cases, solid colors are the side effect of a bug. If code crashes or infinitely loops with interrupts disabled, it's possible that the LED blitheness volition stop. The color of the LED is the color information technology terminal was earlier failure. So for example, information technology could be solid cyan if it was previously animate cyan, or solid scarlet if it was trying to output an SOS pattern.

No condition LED

If y'all power up your device and the status LED never comes on, you could have a missing or corrupted bootloader.

• Unplug the USB (and battery, if you are using one)
• Hold down the SETUP button while plugging in the USB power

If you even so encounter no change in the status LED you lot probably have a missing or corrupted bootloader.

This tin be corrected using a JTAG/SWD programmer if y'all have one. Otherwise, you should contact support.

Share this post