This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Unable to connect to AT&T after upgrading MFW to v1.1.0

We had been using an AT&T M1-enabled SIM in one of our development units successfully for quite some time.  After we upgraded that node to MFW v1.1.0, it is no longer able to connect to the cell network.  We tried swapping SIMs around between devices with different firmware versions confirmed that any node still running MFW v1.0.1 is able to connect to the AT&T network using this SIM, and any node running MFW v1.1.0 is not.  I put the SIM in one of our v1.1.0 nodes, loaded up at_client, and turned on as much output as I could.  The relevant error when trying to connect to the network is this:

It gets the CEREG failure almost immediately and then just sits there doing nothing.  (We waited 15+ minutes)

Again, this failure is using an official AT&T SIM that returns 2 to the AT%XOPERID command.

We are able to connect to the same AT&T cells using v1.1.0 if we put in an MVNO SIM (hologram).

What is the modem doing differently with and without the official AT&T SIM?  Whatever it is doing, it's breaking something in our testing.

Parents
  • Hello.  I have additional data again. 

    I found that I can connect with modem 1.1.0 if I use a hologram SIM but not with an ATT SIM.  It may be useful to note that I've seen the link monitor say the hologram sim roamed successfully on both verizon and ATT.

    Below are modem traces and console output of modem 1.0.1 working with the ATT SIM, 1.1.0 not working with the ATT SIM and 1.1.0 working with the hologram SIM.

    modem101_att_sim_connects_in_10_secs.bin

    modem110_att_sim_no_connect.bin

    modem110_hologram_sim_connects_in_15secs.bin

  • Thanks, I will relay this information to the developers, and report back when they answer.

  • It will be fixed in the 1.1.1 release. In the mean time you need to use a different SIM.

  • Thank you.  Do you know approximately when 1.1.1 will be released?  (days?  weeks?)

Reply Children
  • I can't give you a specific date for this release.

    Edit; New information is available. Ignore the above, 1.1.1 will be released in January.

    Also, if you have used nRF Connect version 3.3 and Programmer 1.3.1, then go back to release v1.0.1.

  • Hello again,

    This should now be fixed in the 1.1.1 release. Has it worked out? Do you have any feedback?

  • Seems to work fine now.  No issues in our first few days of running with 1.1.1.  Thumbsup

  • Sorry for the delayed reply but I'm please to report that 1.1.1 fixes our AT&T issue as well.  Thank you for the support.