Another Boron 404X stuck on blinking green and won't connect to network or cloud

Connectivity Cellular
1

Hello.

I just got a Boron 404X (HW v1.5.1) that was connecting to the T-Mobile network but now does not (e.g., blinking green). So, I reset it with the "Device Doctor" and "Device restore over USB" but I still cannot get it to connect. It has a battery and the included Particle cellular antenna.

Module                   Valid   Version
bootloader                 ✅    3000
system-part1               ✅    6101
User Part (index 2)        ✅    6
Softdevice (Radio Stack)   ✅    202

Last handshake: Aug 17th 2024, 3:25 pm
Last heard: Aug 17th 2024, 6:04 pm

0001286119 [ncp.client] TRACE: Sticky not registering EPS state for 15 s, PLMN reselection
0001286120 [ncp.at] TRACE: > AT+COPS=0,2
0001334266 [ncp.at] TRACE: < OK
0001334268 [ncp.at] TRACE: > AT+CIMI
0001334269 [ncp.at] TRACE: < +CEREG: 1,"4fec","074d6e08",7
0001334290 [ncp.at] TRACE: < 310260543747619
0001334291 [ncp.at] TRACE: < OK
0001334292 [ncp.at] TRACE: > AT+CEREG?
0001334296 [ncp.at] TRACE: < +CEREG: 2,1,"4fec","074d6e08",7
0001334297 [ncp.at] TRACE: < OK
0001334298 [ncp.at] TRACE: > AT+UCGED?
0001334305 [ncp.at] TRACE: < +UCGED: 2
0001334305 [ncp.at] TRACE: < 6,4,310,260
0001334306 [ncp.at] TRACE: < 5035,12,25,25,4fec,74d6e08,488,00000000,ffff,ff,13,6,-5.00,1,255,255,255,255,255,0,255,255,0
0001334307 [ncp.at] TRACE: < OK
0001334407 [ncp.client] TRACE: NCP connection state changed: 2

The T-Mobile IoT coverage map says that I have LTE-M coverage. @rickkas7 talked about MCC/MNC and I see MCC/MNC 310/260. @Colleen noted that devices can be temporarily blocked.

Does that include devices on other mobile networks?

I'm happy to provide device ID, ICCID, IMEI, etc in a private conversation.

Thank you.

1 Like
2

I re-ran the steps to use a 3rd party SIM in case that would help but it does not. The Particle.io page about 3rd part SIM mentions UMNOPROF and the diagnostic output shows:

0000316564 [ncp.at] TRACE: > AT+UMNOPROF?
0000316567 [ncp.at] TRACE: < +UMNOPROF: 100
0000316568 [ncp.at] TRACE: < OK
0000316569 [ncp.at] TRACE: > AT+UBANDMASK?
0000316572 [ncp.at] TRACE: < +UBANDMASK: 0,6170,0

100 is for "Standard Europe", right? Does this need to be changed for T-Mobile?

@support -- Is there a process for submitting a ticket? I see a guided web page that mainly points to online documentation or the community forum.

Thanks again.

3

I increased your member level so you can message support with the affected Device IDs. Only enterprise users can submit tickets directly.

Also include the full debugging log in the message. I can't tell what's wrong from the section in the first post.

Is the first log using the Particle SIM? I could not find the IMSI listed from AT+CIMI.

The band mask is normal. 100 is used for all devices and is really "custom band mask" even though u-blox refers to it as Europe.

4

Hello and thanks for the information. This is a T-mobile SIM that was working. I've moved to a more populated area with better cellular to test with the same results. Let me include a more complete log from the device doctor.

Serial monitor opened successfully:
> 0000003600 [app] INFO: Auto-connect disabled
0000004141 [ncp.at] TRACE: > AT+CFUN?
0000004145 [ncp.at] TRACE: < +CFUN: 1,7
0000004146 [ncp.at] TRACE: < OK
0000004147 [ncp.at] TRACE: > AT+CCID
0000004169 [ncp.at] TRACE: < +CCID: 8901260540737476193
0000004171 [ncp.at] TRACE: < OK
0000004172 [ncp.at] TRACE: > AT+CGSN
0000004176 [ncp.at] TRACE: < 351457833522847
0000004177 [ncp.at] TRACE: < OK
0000004179 [ncp.at] TRACE: > ATI9
0000004188 [ncp.at] TRACE: < 03.15,A00.01
0000004189 [ncp.at] TRACE: < OK
0000004524 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000004527 [net.ppp.client] TRACE: PPP thread event ADM_UP data=0
0000004528 [net.ppp.client] TRACE: State NONE -> READY
0000004530 [ncp.at] TRACE: > AT+CFUN?
0000004531 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000004533 [ncp.at] TRACE: < +CFUN: 1,7
0000004534 [ncp.at] TRACE: < OK
0000004535 [ncp.at] TRACE: > AT+CCID
0000004558 [ncp.at] TRACE: < +CCID: 8901260540737476193
0000004559 [ncp.at] TRACE: < OK
0000004560 [ncp.at] TRACE: > AT+CIMI
0000004603 [ncp.at] TRACE: < 310260543747619
0000004603 [ncp.at] TRACE: < OK
0000004604 [ncp.at] TRACE: > AT+CGDCONT?
0000004611 [ncp.at] TRACE: < +CGDCONT: 1,"IP","fast.t-mobile.com.mnc260.mcc310.gprs","25.88.139.125",0,0,0,2,0,0,0,0,0,0,0
0000004612 [ncp.at] TRACE: < OK
0000004613 [ncp.at] TRACE: > AT+CFUN=4
0000005111 [ncp.at] TRACE: < OK
0000005113 [ncp.at] TRACE: > AT+CGDCONT=1,"IP",""
0000005114 [ncp.at] TRACE: < +CEREG: 0
0000005114 [ncp.at] TRACE: < +CGEV: ME PDN DEACT 1
0000005115 [ncp.at] TRACE: < +CGEV: ME DETACH
0000005117 [ncp.at] TRACE: < OK
0000005118 [ncp.at] TRACE: > AT+CFUN?
0000005121 [ncp.at] TRACE: < +CFUN: 4,7
0000005122 [ncp.at] TRACE: < OK
0000005123 [ncp.at] TRACE: > AT+CFUN=1
0000005178 [ncp.at] TRACE: < OK
0000005178 [ncp.at] TRACE: > AT+CEREG=2
0000005182 [ncp.at] TRACE: < OK
0000005183 [ncp.client] TRACE: NCP connection state changed: 1
0000005183 [net.pppncp] TRACE: NCP event 2
0000005184 [net.pppncp] TRACE: State changed event: 1
0000005185 [ncp.at] TRACE: > AT+COPS?
0000005185 [net.ppp.client] TRACE: PPP thread event LOWER_DOWN data=0
0000005188 [ncp.at] TRACE: < +COPS: 0
0000005189 [ncp.at] TRACE: < OK
0000005190 [ncp.at] TRACE: > AT+CEREG?
0000005194 [ncp.at] TRACE: < +CEREG: 2,0
0000005194 [ncp.at] TRACE: < OK
0000006694 [ncp.at] TRACE: < +CEREG: 1,"4fec","00e98e15",7
0000006695 [ncp.client] TRACE: NCP connection state changed: 2
0000006696 [mux] INFO: Openning mux channel 2
0000006700 [net.pppncp] TRACE: NCP event 100
0000006701 [net.pppncp] TRACE: New auth info
0000006703 [net.pppncp] TRACE: NCP event 2
0000006703 [net.pppncp] TRACE: State changed event: 2
0000006705 [ncp.at] TRACE: > AT+CIMI
0000006705 [ncp.at] TRACE: < +CGEV: ME PDN ACT 1
0000006705 [net.ppp.client] TRACE: PPP thread event LOWER_UP data=0
0000006707 [net.ppp.client] TRACE: State READY -> CONNECT
0000006708 [net.ppp.client] TRACE: State CONNECT -> CONNECTING
0000006728 [ncp.at] TRACE: < 310260543747619
0000006728 [ncp.at] TRACE: < OK
0000006730 [ncp.at] TRACE: > AT+CGATT?
0000006734 [ncp.at] TRACE: < +CGATT: 1
0000006734 [ncp.at] TRACE: < OK
0000007736 [ncp.at] TRACE: > AT
0000007739 [ncp.at] TRACE: < OK
0000007740 [ncp.at] TRACE: > AT+UPORTFWD=100,1
0000007744 [ncp.at] TRACE: < +UPORTFWD: 100,1
0000007744 [ncp.at] TRACE: < OK
0000007745 [ncp.at] TRACE: > ATD*99***1#
0000007751 [ncp.at] TRACE: < CONNECT
0000007752 [net.ppp.client] TRACE: PPP phase -> Initialize
0000007753 [net.ppp.client] TRACE: PPP phase -> Establish
0000007754 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000007763 [lwip.ppp] TRACE: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000011047 [lwip.ppp] TRACE: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <mru 1500> <auth pap> <accomp> <pcomp>]
0000011047 [lwip.ppp] TRACE: sent [LCP ConfRej id=0x1 <auth pap>]
0000011055 [lwip.ppp] TRACE: rcvd [LCP TermReq id=0x2]
0000011055 [lwip.ppp] TRACE: sent [LCP TermAck id=0x2]
0000013754 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000019755 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000025756 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000031757 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000037758 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000043759 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000049760 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000055761 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000061762 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000067763 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x5852125c> <pcomp> <accomp>]
0000073764 [net.ppp.client] TRACE: PPP phase -> Disconnect
0000073765 [net.ppp.client] TRACE: PPP phase -> Dead
0000073765 [net.ppp.client] TRACE: PPP thread event ERROR data=6
0000073766 [net.pppncp] ERROR: PPP error event data=6
0000073767 [net.ppp.client] TRACE: PPP thread event DOWN data=0
0000073768 [net.ppp.client] TRACE: State CONNECTING -> DISCONNECT
0000073768 [net.ppp.client] TRACE: State DISCONNECT -> DISCONNECTING
0000073769 [net.ppp.client] TRACE: PPP thread event ERROR data=5
0000073770 [net.pppncp] ERROR: PPP error event data=5
0000073771 [net.ppp.client] TRACE: PPP thread event DOWN data=0
0000073771 [net.ppp.client] TRACE: State DISCONNECTING -> DISCONNECTED
0000073772 [net.ppp.client] TRACE: State DISCONNECTED -> CONNECT
0000073872 [net.ppp.client] TRACE: State CONNECT -> CONNECTING
0000073873 [ncp.at] TRACE: > AT+CGATT?
0000073877 [ncp.at] TRACE: < +CGATT: 1
0000073878 [ncp.at] TRACE: < OK
0000074881 [ncp.at] TRACE: > AT
0000074883 [ncp.at] TRACE: < OK
0000074884 [ncp.at] TRACE: > AT+UPORTFWD=100,1
0000074888 [ncp.at] TRACE: < +UPORTFWD: 100,1
0000074889 [ncp.at] TRACE: < OK
0000074890 [ncp.at] TRACE: > ATD*99***1#
0000074895 [ncp.at] TRACE: < CONNECT
0000074896 [net.ppp.client] TRACE: PPP phase -> Initialize
0000074897 [net.ppp.client] TRACE: PPP phase -> Establish
0000074899 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000074900 [lwip.ppp] TRACE: rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <mru 1500> <auth pap> <accomp> <pcomp>]
0000074901 [lwip.ppp] TRACE: sent [LCP ConfRej id=0x0 <auth pap>]
0000074910 [lwip.ppp] TRACE: rcvd [LCP ConfAck id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000074912 [lwip.ppp] TRACE: rcvd [LCP TermReq id=0x1]
0000074913 [lwip.ppp] TRACE: sent [LCP TermAck id=0x1]
0000080899 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000086900 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000092901 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000098902 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000104903 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000110904 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000116905 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000122906 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000128907 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000134908 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b343c0> <pcomp> <accomp>]
0000140909 [net.ppp.client] TRACE: PPP phase -> Disconnect
0000140910 [net.ppp.client] TRACE: PPP phase -> Dead
0000140911 [net.ppp.client] TRACE: PPP thread event ERROR data=5
0000140911 [net.pppncp] ERROR: PPP error event data=5
0000140912 [net.ppp.client] TRACE: PPP thread event DOWN data=0
0000140913 [net.ppp.client] TRACE: State CONNECTING -> DISCONNECT
0000140913 [net.ppp.client] TRACE: State DISCONNECT -> DISCONNECTING
0000140914 [net.ppp.client] TRACE: PPP thread event ERROR data=5
0000140915 [net.pppncp] ERROR: PPP error event data=5
0000140916 [net.ppp.client] TRACE: PPP thread event DOWN data=0
0000140916 [net.ppp.client] TRACE: State DISCONNECTING -> DISCONNECTED
0000140917 [net.ppp.client] TRACE: State DISCONNECTED -> CONNECT
0000141017 [net.ppp.client] TRACE: State CONNECT -> CONNECTING
0000141018 [ncp.at] TRACE: > AT+CGATT?
0000141022 [ncp.at] TRACE: < +CGATT: 1
0000141023 [ncp.at] TRACE: < OK
0000142025 [ncp.at] TRACE: > AT
0000142028 [ncp.at] TRACE: < OK
0000142028 [ncp.at] TRACE: > AT+UPORTFWD=100,1
0000142032 [ncp.at] TRACE: < +UPORTFWD: 100,1
0000142033 [ncp.at] TRACE: < OK
0000142034 [ncp.at] TRACE: > ATD*99***1#
0000142041 [ncp.at] TRACE: < CONNECT
0000142042 [net.ppp.client] TRACE: PPP phase -> Initialize
0000142043 [net.ppp.client] TRACE: PPP phase -> Establish
0000142045 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x3 <asyncmap 0x0> <magic 0x4bbd456d> <pcomp> <accomp>]
0000142046 [lwip.ppp] TRACE: rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <mru 1500> <auth pap> <accomp> <pcomp>]
0000142047 [lwip.ppp] TRACE: sent [LCP ConfRej id=0x0 <auth pap>]
0000142055 [lwip.ppp] TRACE: rcvd [LCP ConfAck id=0x3 <asyncmap 0x0> <magic 0x4bbd456d> <pcomp> <accomp>]
0000142058 [lwip.ppp] TRACE: rcvd [LCP TermReq id=0x1]
0000142058 [lwip.ppp] TRACE: sent [LCP TermAck id=0x1]
0000148045 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x3 <asyncmap 0x0> <magic 0x4bbd456d> <pcomp> <accomp>]
0000154046 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x3 <asyncmap 0x0> <magic 0x4bbd456d> <pcomp> <accomp>]
0000160047 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x3 <asyncmap 0x0> <magic 0x4bbd456d> <pcomp> <accomp>]
0000166048 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x3 <asyncmap 0x0> <magic 0x4bbd456d> <pcomp> <accomp>]
0000172049 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x3 <asyncmap 0x0> <magic 0x4bbd456d> <pcomp> <accomp>]
5

It looks it is able to connect to cellular (there is a tower), but is unable to establish an IP data session. The most common reason this happens is that the SIM is not configured for IP data. If the SIM previously worked, that's less likely, but not impossible. It's also possible that SIM was banned from the network for some reason, such as aggressive reconnection, or unapproved IMEI.

In any case, we have no visibility into what's happening on the network side with a 3rd-party SIM, so there isn't much else we can provide.

6

Okay. Now I know which fork in the road I need to follow so I will go talk with T-Mobile since it was working.

What in the log was an indicator? The repeated grouping of initialize/establish, disconnect/dead message pairs or something else?

0000321297 [net.ppp.client] TRACE: PPP phase -> Initialize
0000321298 [net.ppp.client] TRACE: PPP phase -> Establish
...
0000387309 [net.ppp.client] TRACE: PPP phase -> Disconnect
0000387310 [net.ppp.client] TRACE: PPP phase -> Dead

Thanks,
Mark

7

Quick update...

The SIM works in an iPad. T-Mobile said it's not banned and doesn't see an issue on their side with the device being banned either.

But, they kept saying that U-Blox wasn't supported (certified?) on their network and suggested that I pick another cellular modem. It's like it was completely foreign to them until I pointed to the SARA-R510S on the T-Mobile IoT certification page.

So they changed my service line to IoT yet it does not work. Told me to wait a day then get a SyncUP DRIVE SIM from a retail store...

To their credit, I asked about many AT modem commands and they looked up each one to see if there were known issues.

8

I knew this was an issue with Verizon and AT&T, but wasn't sure if it was an issue with T-Mobile in the United States.

In order to use their IoT SIMs with LTE Cat M1 devices, the device needs to be approved and the IMEI registered or the device can be banned from the network. With Verizon, you get up to around 36 hours and then it will never work again.

When you use the Particle SIM, our IMEIs are approved for use on their networks already through our SIM provider.

9

A post was split to a new topic: Boron 404X unable to connect

10

Indeed. So far, no ban on the device but I've been misled by TMO in the past.

So I was started looking at Particle SIM pricing but couldn't grasp how to get one.

Unless the pricing is strictly block based; starting at $299/month/720K blocks that can be spread across 100 devices.

Is that an accurate pricing description?

11

That is correct if you exceed the limits of the free tier. If you have fewer than 100 devices and 720K data operations per month, it's free. There's no time limit, you can do that every month.

The Particle SIM is soldered on the board, so if you switch back to internal SIM you can use it for free until you exceed the limits and move to the basic (paid) plan.