There is no issue here with AT&T. There's a bit of progress, connecting intermittently to a tower, but no stable connection.
Steve
Back to flashing rapid green, no connection...
Steve
Reinstalled Device Doctor, here's the latest log:
0000003161 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000003163 [net.ppp.client] TRACE: PPP thread event ADM_UP data=0
0000003164 [net.ppp.client] TRACE: State NONE -> READY
0000003167 [ncp.at] TRACE: > AT+CFUN?
0000003168 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000003170 [ncp.at] TRACE: < +CFUN: 1,7
0000003171 [ncp.at] TRACE: < OK
0000003172 [ncp.at] TRACE: > AT+CCID
0000003196 [ncp.at] TRACE: < +CCID: 89883070000036139044
0000003197 [ncp.at] TRACE: < OK
0000003198 [ncp.at] TRACE: > AT+CGDCONT?
0000003204 [ncp.at] TRACE: < +CGDCONT: 1,"IPV4V6","","0.0.0.0 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,
0000003205 [ncp.at] TRACE: < OK
0000003205 [ncp.at] TRACE: > AT+CFUN=4
0000003219 [ncp.at] TRACE: < OK
0000003220 [ncp.at] TRACE: > AT+CGDCONT=1,"IP","super"
0000003225 [ncp.at] TRACE: < OK
0000003226 [ncp.at] TRACE: > AT+CFUN?
0000003229 [ncp.at] TRACE: < +CFUN: 4,7
0000003230 [ncp.at] TRACE: < OK
0000003231 [ncp.at] TRACE: > AT+CFUN=1
0000003316 [ncp.at] TRACE: < OK
0000003316 [ncp.at] TRACE: > AT+CEREG=2
0000003321 [ncp.at] TRACE: < OK
0000003321 [ncp.client] TRACE: NCP connection state changed: 1
0000003322 [net.pppncp] TRACE: NCP event 2
0000003322 [net.pppncp] TRACE: State changed event: 1
0000003323 [ncp.at] TRACE: > AT+COPS?
0000003323 [net.ppp.client] TRACE: PPP thread event LOWER_DOWN data=0
0000003327 [ncp.at] TRACE: < +COPS: 0
0000003328 [ncp.at] TRACE: < OK
0000003329 [ncp.at] TRACE: > AT+CEREG?
0000003332 [ncp.at] TRACE: < +CEREG: 2,0
0000003333 [ncp.at] TRACE: < OK
0000018334 [ncp.at] TRACE: > AT+CEREG?
0000018338 [ncp.at] TRACE: < +CEREG: 2,0
0000018338 [ncp.at] TRACE: < OK
0000018339 [ncp.at] TRACE: > AT+UCGED?
0000018345 [ncp.at] TRACE: < +UCGED: 2
0000018346 [ncp.at] TRACE: < 6,2,fff,fff
0000018347 [ncp.at] TRACE: < 65535,255,255,255,ffff,0000000,65535,00000000,ffff,ff,255,255,255,1,25
0000018348 [ncp.at] TRACE: < OK
0000023947 [ncp.at] TRACE: < +CEREG: 3
0000033448 [ncp.at] TRACE: > AT+CEREG?
0000033451 [ncp.at] TRACE: < +CEREG: 2,3
0000033452 [ncp.at] TRACE: < OK
0000033453 [ncp.at] TRACE: > AT+UCGED?
0000033460 [ncp.at] TRACE: < +UCGED: 2
0000033460 [ncp.at] TRACE: < 6,2,fff,fff
0000033461 [ncp.at] TRACE: < 2300,4,255,100,ffff,0000000,242,00000000,ffff,ff,61,19,18.00,1,255,255
0000033461 [ncp.at] TRACE: < OK
0000048562 [ncp.at] TRACE: > AT+CEREG?
0000048565 [ncp.at] TRACE: < +CEREG: 2,3
0000048566 [ncp.at] TRACE: < OK
0000048567 [ncp.at] TRACE: > AT+UCGED?
0000048573 [ncp.at] TRACE: < +UCGED: 2
0000048574 [ncp.at] TRACE: < 6,2,fff,fff
0000048575 [ncp.at] TRACE: < 2300,4,255,100,ffff,0000000,242,00000000,ffff,ff,61,19,18.00,1,255,255
0000048575 [ncp.at] TRACE: < OK
It appears the SIM is busy downloading a new profile, it should complete shortly.
The LED status indicator on the Boron is solid Cyan, not "breathing". What does that mode indication mean?
Thank you,
Steve
That's a crashed device - was it still running the debug firmware?
Good to know! Solid cyan means crashed device.
I've been changing from Device Doctor to normal operation by using the Device Restore dialog. When I did it this last time, I forgot to check the box to enable reflashing even if the device version is the same. I running through Device Restore again. I looks like it's stuck on the Flashing Bootloader step.
At this point I'll try manually putting it into DFU mode for the Restore.
Steve
OK, that worked. After another Device Restore cycle, the process executed completely. My Boron is now reporting as Online:
Now I think we're good!
So what was changed to shift the connection from attempting Verizon to successfully connecting to AT&T?
Thank you,
Steve
That seems to explain it.
Safe Mode is when the device is updating - typically DeviceOS.
Re. your question on Verizon moving to AT&T - the reason for that is not quite clear. The device did connect to AT&T, and then immediately tried Verizon. It's probably just a local tower issue, but I don't have the logs/information to explain this fully.
1 Like