New Boron Worked for a Day, Now Flashing Green Constantly

I have a new Boron device that connected immediately, and after a bit of work and testing stopped entirely. I tried working through the troubleshooting (which is in no way simple, by the way), and nothing worked.

Cloud debug log:

0000015369 [app] INFO: Starting Tests!
0000015369 [app] INFO: Platform: Boron
0000015369 [app] INFO: Binary compiled for: 1.5.2                                                                                                                              0000015370 [app] INFO: Cloud Debug Release 1.5.3
0000015370 [app] INFO: System version: 2.0.1
0000015371 [app] INFO: Device ID: e00fce68074bdf4351c284c8
0000015371 [app] INFO: Power source: VIN
0000015372 [app] INFO: Battery state: disconnected, SoC: -1.00
0000015372 [app] INFO: This device could have Ethernet (is 3rd generation)
0000015373 [app] INFO: FEATURE_ETHERNET_DETECTION not enabled, so Ethernet will not be used (even i
0000023381 [app] INFO: deviceID: e00fce68074bdf4351c284c8
0000023382 [app] INFO: PMIC inputVoltageLimit: 3880 mV
0000023383 [app] INFO: PMIC inputCurrentLimit: 900 mA
0000023384 [app] INFO: PMIC minimumSystemVoltage: 3500 mV
0000023385 [app] INFO: PMIC chargeCurrentValue: 896 mA
0000023386 [app] INFO: PMIC chargeVoltageValue: 4112 mV
0000023386 [app] INFO: modem is not yet responding
0000023389 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
0000023389 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000023391 [net.pppncp] TRACE: PPP netif event from queue: 1
0000023391 [ncp.client] TRACE: Modem already on
0000023392 [ncp.client] TRACE: Setting UART voltage translator state 1
0000023393 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000023402 [app] INFO: Still trying to connect to cellular 00:00
0000023402 [app] INFO: Power source: VIN
0000023402 [app] INFO: Battery state: disconnected, SoC: -1.00
0000023492 [ncp.client] TRACE: Setting UART voltage translator state 0
0000023592 [ncp.client] TRACE: Setting UART voltage translator state 1
0000023592 [ncp.client] TRACE: Muxer is not currently running
0000023593 [ncp.client] TRACE: Initialized muxer @ 460800 baudrate
0000023593 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000023594 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000023894 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000023894 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000023894 [gsm0710muxer] INFO: Closing all muxed channels
0000023895 [gsm0710muxer] INFO: Muxed channel 1 already closed
0000023895 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000023895 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000023896 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000024546 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000025446 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000025496 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000025496 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000025497 [ncp.client] TRACE: Initialized muxer @ 115200 baudrate
0000025497 [gsm0710muxer] INFO: Starting GSM07.10 muxer
0000025497 [gsm0710muxer] INFO: GSM07.10 muxer thread started
0000025797 [gsm0710muxer] INFO: Stopping GSM07.10 muxer
0000025797 [gsm0710muxer] INFO: Gracefully stopping GSM07.10 muxer
0000025797 [gsm0710muxer] INFO: Closing all muxed channels
0000025798 [gsm0710muxer] INFO: Muxed channel 1 already closed
0000025798 [gsm0710muxer] INFO: Muxed channel 2 already closed
0000025798 [gsm0710muxer] INFO: Muxed channel 3 already closed
0000025799 [gsm0710muxer] INFO: Muxed channel 4 already closed
0000026449 [gsm0710muxer] INFO: Sending CLD (multiplexer close down)
0000027349 [gsm0710muxer] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000027399 [gsm0710muxer] INFO: GSM07.10 muxer thread exiting
0000027399 [gsm0710muxer] INFO: GSM07.10 muxer stopped
0000027400 [ncp.at] TRACE: > AT
0000028400 [ncp.at] TRACE: > AT
0000029400 [ncp.client] TRACE: Modem is not responsive @ 460800 baudrate
0000029401 [ncp.at] TRACE: > AT
0000030401 [ncp.at] TRACE: > AT
0000031401 [ncp.at] TRACE: > AT
0000032401 [ncp.at] TRACE: > AT
0000033401 [ncp.at] TRACE: > AT
0000034401 [ncp.client] TRACE: Modem is not responsive @ 115200 baudrate
0000034401 [ncp.client] ERROR: No response from NCP
0000034402 [ncp.client] TRACE: Setting UART voltage translator state 0
0000034402 [ncp.client] TRACE: Hard resetting the modem
0000034402 [ncp.client] TRACE: Modem waiting up to 30s to power off with PWR_UC...
0000075503 [net.pppncp] TRACE: NCP event 3
0000075503 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_DOWN
0000075503 [system.nm] TRACE: Interface 4 power state changed: 1
0000075504 [ncp.client] TRACE: Deinit modem serial.
0000075505 [net.pppncp] ERROR: Failed to initialize cellular NCP client: -210
0000075505 [app] INFO: modem is not yet responding
0000075506 [app] INFO: Still trying to connect to cellular 00:52
0000075506 [app] INFO: Power source: VIN
0000075506 [app] INFO: Battery state: disconnected, SoC: -1.00
0000075519 [app] INFO: modem is not yet responding
0000075605 [net.pppncp] TRACE: NCP event 3
0000075605 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_POWERING_UP
0000075605 [system.nm] TRACE: Interface 4 power state changed: 4
0000075606 [ncp.client] TRACE: Powering modem on
0000075756 [net.pppncp] TRACE: NCP event 3
0000075756 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_UP
0000075756 [system.nm] TRACE: Interface 4 power state changed: 2
0000075757 [ncp.client] TRACE: Modem powered on
0000075757 [ncp.client] TRACE: Setting UART voltage translator state 1
0000075857 [ncp.client] TRACE: Setting UART voltage translator state 0
0000075957 [ncp.client] TRACE: Setting UART voltage translator state 1
0000076958 [ncp.at] TRACE: > AT
0000077958 [ncp.at] TRACE: > AT
0000078958 [ncp.at] TRACE: > AT
0000079958 [ncp.at] TRACE: > AT
0000080958 [ncp.at] TRACE: > AT
0000081958 [ncp.at] TRACE: > AT
0000082958 [ncp.at] TRACE: > AT
0000083958 [ncp.at] TRACE: > AT
0000084958 [ncp.at] TRACE: > AT
0000085505 [app] INFO: Still trying to connect to cellular 01:02
0000085505 [app] INFO: Power source: VIN
0000085505 [app] INFO: Battery state: disconnected, SoC: -1.00
0000085958 [ncp.at] TRACE: > AT
0000086958 [ncp.at] TRACE: > AT
0000087959 [ncp.at] TRACE: > AT
0000088959 [ncp.at] TRACE: > AT
0000089959 [ncp.at] TRACE: > AT
0000090959 [ncp.at] TRACE: > AT
0000091959 [ncp.client] ERROR: No response from NCP
0000091959 [ncp.client] TRACE: Setting UART voltage translator state 0
0000091960 [ncp.client] TRACE: Hard resetting the modem
0000091960 [ncp.client] TRACE: Modem waiting up to 30s to power off with PWR_UC...
0000132962 [net.pppncp] TRACE: NCP event 3
0000132962 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_DOWN
0000132963 [system.nm] TRACE: Interface 4 power state changed: 1
0000132963 [ncp.client] TRACE: Deinit modem serial.
0000132964 [net.pppncp] ERROR: Failed to initialize cellular NCP client: -210
0000132964 [app] INFO: modem is not yet responding
0000132965 [app] INFO: Still trying to connect to cellular 01:49
0000132965 [app] INFO: Power source: VIN
0000132965 [app] INFO: Battery state: disconnected, SoC: -1.00
0000132980 [app] INFO: modem is not yet responding
0000133064 [net.pppncp] TRACE: NCP event 3
0000133064 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_POWERING_UP
0000133065 [system.nm] TRACE: Interface 4 power state changed: 4
0000133065 [ncp.client] TRACE: Powering modem on
0000133215 [net.pppncp] TRACE: NCP event 3
0000133215 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_UP
0000133216 [system.nm] TRACE: Interface 4 power state changed: 2
0000133216 [ncp.client] TRACE: Modem powered on
0000133216 [ncp.client] TRACE: Setting UART voltage translator state 1
0000133316 [ncp.client] TRACE: Setting UART voltage translator state 0
0000133416 [ncp.client] TRACE: Setting UART voltage translator state 1
0000134417 [ncp.at] TRACE: > AT
0000135417 [ncp.at] TRACE: > AT
0000136417 [ncp.at] TRACE: > AT
0000137417 [ncp.at] TRACE: > AT
0000138417 [ncp.at] TRACE: > AT
0000139417 [ncp.at] TRACE: > AT
0000140417 [ncp.at] TRACE: > AT
0000141417 [ncp.at] TRACE: > AT
0000142417 [ncp.at] TRACE: > AT
0000142965 [app] INFO: Still trying to connect to cellular 01:59
0000142965 [app] INFO: Power source: VIN
0000142965 [app] INFO: Battery state: disconnected, SoC: -1.00
0000143417 [ncp.at] TRACE: > AT
0000144418 [ncp.at] TRACE: > AT
0000145418 [ncp.at] TRACE: > AT
0000146419 [ncp.at] TRACE: > AT
0000147420 [ncp.at] TRACE: > AT
0000148421 [ncp.at] TRACE: > AT
0000149422 [ncp.client] ERROR: No response from NCP
0000149423 [ncp.client] TRACE: Setting UART voltage translator state 0
0000149423 [ncp.client] TRACE: Hard resetting the modem
0000149423 [ncp.client] TRACE: Modem waiting up to 30s to power off with PWR_UC...
0000190424 [net.pppncp] TRACE: NCP event 3
0000190424 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_DOWN
0000190425 [system.nm] TRACE: Interface 4 power state changed: 1
0000190425 [ncp.client] TRACE: Deinit modem serial.
0000190426 [net.pppncp] ERROR: Failed to initialize cellular NCP client: -210
0000190426 [app] INFO: modem is not yet responding
0000190427 [app] INFO: Still trying to connect to cellular 02:47
0000190427 [app] INFO: Power source: VIN
0000190428 [app] INFO: Battery state: disconnected, SoC: -1.00
0000190443 [app] INFO: modem is not yet responding
0000190526 [net.pppncp] TRACE: NCP event 3

Please help with this, it is clear from the posts that this is not an isolated incident. Also I tried to create a ticket, but it seems to be failing to submit. I have tried to submit it multiple times, and it just reloads the ticket screen with no confirmation that it has been submitted.

very common- this seems to happen on 1-5% of the borons we buy(about 4/100 so far)… I know another guy at another company who has the same exact issue with about the same prevalence with a totally different setup. as of yet particle keeps telling us that this bug is a figment of our imagination… but it seems that we’ve “been havin the same old dreams”- bob dylan.

anyways… yeah this keeps happening. if you do manage to get a ticket open they will probably tell you it’s the 142 day bug, which would have the same symptoms… it’s not- if you bought you’re device within the past couple years it would be immune to it. the chances of hitting the 142 day but in the first place are astronomically small.

the worst part is that it can happen really at any time… so it can happen on the field and brick you’re whole device.

good luck, I think if enough people complain they have to look into it.

I just purchased the device a few weeks ago. It is very much new. I cannot get a support ticket through, it just refreshes the page with no confirmation.

Can I please get some support from Particle here? This is not a great start. This is my first interaction with Particle, and I just spent $80 on a starter kit + shipping and it does not work at all.

Please support me.
Regards,
Tom

@marekparticle can you help Tom here, please?
thanks!

@tdvdesign - I am not able to reproduce the ticket submission issue. Are you attempting to log in to the support page? At present that is not supported.

Can you please:

a) Open another browser and try and reproduce.
b) Attempt to reproduce with Chrome. Right-click anywhere on your browser page and select “Inspect” then navigate to the “Console” within the window that pops up. Attempt to submit a ticket and please produce for me any errors or notices that appear within that window.

Can you also send the precise link over with which you are attempting to submit a ticket?

@marekparticle Any clues on the green blinking issue? Same prob here.

Hey @superseb - there are a number of things that can put a Boron in this state, most commonly the issue described here: TAN001 - SARA-R410M "124-day" – Particle Support.

We are actively looking to identify any trends related to this failure state; for this reason we need the specificity and metadata we get from support tickets.

Can you please create a ticket (support.particle.io)? Please ping me if you’re unable to do so, my number one priority this morning is making sure there isn’t some blocker with ticket generation but I am unable to reproduce on any browser.

Things we need in a ticket reporting this issue:
a) Device ID / Serial Number
b) A brief statement about how your device uses power, including (if possible) a hardware schematic.
c) A brief statement about use of 3rd Party SIM cards - if you use them, what type, how are they connected to the board, and with what Device OS version are you working.
d) A brief abstraction of your application firmware flow, including any handling the device does of low-power states.
e) Logs produced like the above via Cloud Debug.

@marekparticle
Sadly it’s not the 124 days bug (the one @ccunningham called 142 days I’m guessing). I sent a ticket particle is offering to replace it but I just want a solution, not devices dying on the field.

Can you send me the ticket ID?

Hi,
I am attempting to submit the ticket over the support page:
https://support.particle.io/hc/en-us/requests

Console does not show anything when I hit submit.

If this is not the correct page, please redirect me.
Regards,
Tom

That’s the right page. Can you submit a very short ticket, just as a test (not a lot of information just fill out necessary fields with “test” or a random drop-down selection)? I see another customer hit an invisible character limit with our ticket infrastructure provider - I’m curious if this is the same thing.

I successfully submitted a test ticket with no cloud debug data and very short descriptions.
Next step?
Thanks,
Tom

I’ve added a little notice as a placeholder while I investigate the character limit cutoff issue. You can just go ahead and respond to the ticket you created and I’ll have the team respond to you there!

Hi,
I responded to the ticket a few days ago - please let me know if you received my response.
Thank you,
Tom

Hey, we’ve been in touch. We’re just waiting on a shipping label to be produced for you!

Great, thanks for your help.
Tom