<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Unable to connect to AT&amp;amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/54849/unable-to-connect-to-at-t-after-upgrading-mfw-to-v1-1-0</link><description>We had been using an AT&amp;amp;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</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 15 Feb 2020 17:35:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/54849/unable-to-connect-to-at-t-after-upgrading-mfw-to-v1-1-0" /><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/234522?ContentTypeID=1</link><pubDate>Sat, 15 Feb 2020 17:35:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da814ebe-7c8e-4216-8267-18cc26504988</guid><dc:creator>chester314</dc:creator><description>&lt;p&gt;Sorry for the delayed reply but I&amp;#39;m please to report that 1.1.1 fixes our AT&amp;amp;T issue as well.&amp;nbsp; Thank you for the support.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/233345?ContentTypeID=1</link><pubDate>Fri, 07 Feb 2020 15:33:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4de526c4-6f9b-4b00-997d-cf79ee236832</guid><dc:creator>Tim_AFD</dc:creator><description>&lt;p&gt;The new release is working for me. &lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Tim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/233326?ContentTypeID=1</link><pubDate>Fri, 07 Feb 2020 14:23:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e4435923-5eb3-4508-9ed9-db6067c73027</guid><dc:creator>jbrzozoski</dc:creator><description>&lt;p&gt;Seems to work fine now.&amp;nbsp; No issues in our first few days of running with 1.1.1.&amp;nbsp; &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f44d.svg" title="Thumbsup"&gt;&amp;#x1f44d;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/233311?ContentTypeID=1</link><pubDate>Fri, 07 Feb 2020 14:00:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74158e39-18fe-42a2-9996-60d19e3ad282</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Hello again,&lt;/p&gt;
&lt;p&gt;This should now be fixed in the 1.1.1 release. Has it worked out? Do you have any feedback?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/223549?ContentTypeID=1</link><pubDate>Wed, 04 Dec 2019 10:39:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d969b060-92f9-4c26-a00d-d6d1bfa8310a</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;I can&amp;#39;t give you a specific date for this release.&lt;/p&gt;
&lt;p&gt;Edit; New information is available. Ignore the above, 1.1.1 will be released in January.&lt;/p&gt;
&lt;p&gt;Also, if you have used nRF&amp;nbsp;Connect version 3.3 and Programmer 1.3.1, then go back to release v1.0.1.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/223442?ContentTypeID=1</link><pubDate>Tue, 03 Dec 2019 22:47:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd013b7f-2dad-4a15-9977-72efe56fbc8b</guid><dc:creator>Tim_AFD</dc:creator><description>&lt;p&gt;I am also having this issue in the North Central USA using at_client and MFW v1.1.0.&lt;/p&gt;
&lt;p&gt;Hologram SIM (quickly) connects to AT&amp;amp;T, but official AT&amp;amp;T SIM does not.&lt;/p&gt;
&lt;p&gt;Here are the CNEC errors that I&amp;#39;m getting with the AT&amp;amp;T SIM:&lt;/p&gt;
&lt;p&gt;2019-12-03T20:50:05.211Z DEBUG modem &amp;lt;&amp;lt; &lt;b&gt;&lt;span style="color:#3333ff;"&gt;+CNEC_ESM: 33,0&lt;/span&gt;&lt;/b&gt;\x0D\x0A&lt;br /&gt; 2019-12-03T20:50:05.220Z DEBUG modem &amp;lt;&amp;lt; &lt;b&gt;&lt;span style="color:#3333ff;"&gt;+CNEC_EMM: 19&lt;/span&gt;&lt;/b&gt;\x0D\x0A&lt;br /&gt; 2019-12-03T20:50:05.636Z DEBUG modem &amp;lt;&amp;lt; %CESQ: 45,2,16,2\x0D\x0A&lt;br /&gt; 2019-12-03T20:50:06.554Z DEBUG modem &amp;lt;&amp;lt; %CESQ: 255,0,255,0\x0D\x0A&lt;br /&gt; 2019-12-03T20:50:06.559Z DEBUG modem &amp;lt;&amp;lt; +CEREG: 2,&amp;quot;FFFE&amp;quot;,&amp;quot;FFFFFFFF&amp;quot;,7\x0D\x0A&lt;br /&gt; 2019-12-03T20:50:08.022Z DEBUG modem &amp;lt;&amp;lt; %CESQ: 48,2,12,1\x0D&lt;br /&gt; 2019-12-03T20:50:08.027Z DEBUG modem &amp;lt;&amp;lt; +CEREG: 2,&amp;quot;C00C&amp;quot;,&amp;quot;02EE9002&amp;quot;,7\x0D\x0A&lt;br /&gt; 2019-12-03T20:50:08.199Z DEBUG modem &amp;lt;&amp;lt; &lt;b&gt;&lt;span style="color:#3333ff;"&gt;+CNEC_EMM: 11&lt;/span&gt;&lt;/b&gt;\x0D\x0A&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/223162?ContentTypeID=1</link><pubDate>Mon, 02 Dec 2019 20:53:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54648f85-ad56-48f5-b8ae-58b42bb9f7cf</guid><dc:creator>chester314</dc:creator><description>&lt;p&gt;Thank you.&amp;nbsp; Do you know approximately when 1.1.1 will be released?&amp;nbsp; (days?&amp;nbsp; weeks?)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/222829?ContentTypeID=1</link><pubDate>Fri, 29 Nov 2019 13:26:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4e0c619d-26de-4f13-a4ad-48df4645c3b8</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;It will be fixed in the 1.1.1 release. In the mean time you need to use a different SIM.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/222754?ContentTypeID=1</link><pubDate>Fri, 29 Nov 2019 10:28:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ccd1e29-9a3f-449a-89c8-e42d732c33d6</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Thanks, I will relay this information to the developers, and report back when they answer.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/222433?ContentTypeID=1</link><pubDate>Wed, 27 Nov 2019 15:55:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:240113da-a9e8-46ed-9eb0-e172adb08e09</guid><dc:creator>chester314</dc:creator><description>&lt;p&gt;Hello.&amp;nbsp; I have additional data again.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I found that I can connect with modem 1.1.0 if I use a hologram SIM but not with an ATT SIM.&amp;nbsp; It may be useful to note that I&amp;#39;ve seen the link monitor say the hologram sim roamed successfully on both verizon and ATT.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/modem101_5F00_att_5F00_sim_5F00_connects_5F00_in_5F00_10_5F00_secs.bin"&gt;devzone.nordicsemi.com/.../modem101_5F00_att_5F00_sim_5F00_connects_5F00_in_5F00_10_5F00_secs.bin&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/modem110_5F00_att_5F00_sim_5F00_no_5F00_connect.bin"&gt;devzone.nordicsemi.com/.../modem110_5F00_att_5F00_sim_5F00_no_5F00_connect.bin&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/modem110_5F00_hologram_5F00_sim_5F00_connects_5F00_in_5F00_15secs.bin"&gt;devzone.nordicsemi.com/.../modem110_5F00_hologram_5F00_sim_5F00_connects_5F00_in_5F00_15secs.bin&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/modem110_5F00_att_5F00_sim_5F00_no_5F00_connect_5F00_console_5F00_log.txt"&gt;devzone.nordicsemi.com/.../modem110_5F00_att_5F00_sim_5F00_no_5F00_connect_5F00_console_5F00_log.txt&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/modem_5F00_110_5F00_hologram_5F00_sim_5F00_connects_5F00_console_5F00_log.txt"&gt;devzone.nordicsemi.com/.../modem_5F00_110_5F00_hologram_5F00_sim_5F00_connects_5F00_console_5F00_log.txt&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/modem101_5F00_att_5F00_sim_5F00_console_5F00_log.txt"&gt;devzone.nordicsemi.com/.../modem101_5F00_att_5F00_sim_5F00_console_5F00_log.txt&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/222416?ContentTypeID=1</link><pubDate>Wed, 27 Nov 2019 15:07:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd16aa14-604c-4d9f-8787-41951cc21b5b</guid><dc:creator>Rory</dc:creator><description>&lt;p&gt;Here is the modem trace when trying to connect with the official AT&amp;amp;T SIM card.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_27T14_2D00_58_2D00_29.822Z.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_27T14_2D00_58_2D00_29.822Z.bin&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Here is a timeline of the CEREG notifications we get when trying to connect.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;[00:00:04.069,335] &amp;lt;inf&amp;gt; CEREG: 0,&amp;quot;0411&amp;quot;,&amp;quot;00F63F11&amp;quot;,7,0,0,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:04.849,426] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;0411&amp;quot;,&amp;quot;00F63F11&amp;quot;,7,0,0,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:05.767,028] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;0411&amp;quot;,&amp;quot;00F63F11&amp;quot;,7,0,19,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:07.032,684] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;FFFE&amp;quot;,&amp;quot;FFFFFFFF&amp;quot;,7,0,19,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:10.472,930] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;3B02&amp;quot;,&amp;quot;00E6C102&amp;quot;,7,0,19,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:11.676,757] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;3B02&amp;quot;,&amp;quot;00E6C102&amp;quot;,7,0,11,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:13.051,727] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;FFFE&amp;quot;,&amp;quot;FFFFFFFF&amp;quot;,7,0,11,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:14.315,734] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;0411&amp;quot;,&amp;quot;00F63F11&amp;quot;,7,0,11,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:15.202,514] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;0411&amp;quot;,&amp;quot;00F63F11&amp;quot;,7,0,19,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:16.484,100] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;FFFE&amp;quot;,&amp;quot;FFFFFFFF&amp;quot;,7,0,19,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;
[00:00:17.506,408] &amp;lt;inf&amp;gt; CEREG: 2,&amp;quot;0411&amp;quot;,&amp;quot;00F63F11&amp;quot;,7,0,19,&amp;quot;11100000&amp;quot;,&amp;quot;11100000&amp;quot;&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/222288?ContentTypeID=1</link><pubDate>Wed, 27 Nov 2019 10:19:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9766a0dd-a993-46cd-8502-1db2f46ceaf3</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Please perform modem trace and post the trace file here. &lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect"&gt;https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to connect to AT&amp;T after upgrading MFW to v1.1.0</title><link>https://devzone.nordicsemi.com/thread/222182?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2019 19:32:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c5fb95f4-d3a0-43c1-bb3b-ffd7cdf502a1</guid><dc:creator>chester314</dc:creator><description>&lt;p&gt;Hello.&amp;nbsp; I do not have a solution but I do have a potentially useful additional data point.&lt;/p&gt;
&lt;p&gt;We are also using official AT&amp;amp;T SIMs in southeast USA and modem fw V1.1.0 seems to have broken our ability to connect as well.&lt;/p&gt;
&lt;p&gt;After having problems with our app, we simplified to using the link monitor and stock at_client.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;What we saw in all cases is modem fw V1.0.1 getting a complete connection in &amp;lt; 10 seconds while V1.1.0 never connects.&lt;/p&gt;
&lt;p&gt;Below is with V1.1.0 (note we get:+CNEC_ESM and +CNEC_EMM messages):&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;SPM: NS reset vector at 0xde89
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS build v2.0.99-ncs1 *****
The AT host sample started
AT+CFUN=1
OK
AT+CFUN?
+CFUN: 1
OK
AT+CGSN=1
+CGSN: &amp;quot;352656100816191&amp;quot;
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9160-SICA
OK
AT+CGMR
mfw_nrf9160_1.1.0
OK
AT+CEMODE?
+CEMODE: 2
OK
AT%XCBAND=?
%XCBAND: (1,2,3,4,5,8,12,13,14,17,18,19,20,25,26,28,66)
OK
AT+CMEE?
+CMEE: 0
OK
AT+CMEE=1
OK
AT+CNEC?
+CNEC: 0
OK
AT+CNEC=24
OK
AT+CGEREP?
+CGEREP: 0,0
OK
AT+CGDCONT?
OK
AT+CGACT?
OK
AT+CGEREP=1
OK
AT+CIND=1,1,1
OK
AT+CEREG=2
OK
AT+CEREG?
+CEREG: 2,4,&amp;quot;FFFE&amp;quot;,&amp;quot;FFFFFFFF&amp;quot;,7
OK
AT%CESQ=1
OK
AT+CESQ
+CESQ: 99,99,255,255,255,255
OK
AT%XSIM=1
OK
AT%XSIM?
%XSIM: 1
OK
AT+CPIN?
+CPIN: READY
OK
AT+CPINR=&amp;quot;SIM PIN&amp;quot;
+CPINR: &amp;quot;SIM PIN&amp;quot;,3
OK
AT+CIMI
204080813511271
OK
AT+CESQ
+CESQ: 99,99,255,255,255,255
OK
AT+CPINR=&amp;quot;SIM PIN&amp;quot;
%CESQ: 43,2,10,1
+CEREG: 2,&amp;quot;9103&amp;quot;,&amp;quot;0236CE03&amp;quot;,7
+CPINR: &amp;quot;SIM PIN&amp;quot;,3
OK
AT+CIMI
204080813511271
OK
+CNEC_ESM: 38,0
+CNEC_EMM: 19
%CESQ: 38,1,10,1
%CESQ: 255,0,255,0
+CEREG: 2,&amp;quot;FFFE&amp;quot;,&amp;quot;FFFFFFFF&amp;quot;,7
%CESQ: 255,0,255,0
AT+CESQ
+CESQ: 99,99,255,255,255,255
OK
AT+CFUN?
+CFUN: 1
&amp;lt;snip&amp;gt;
OK
AT+CESQ
+CESQ: 99,99,255,255,255,255
OK
AT+CESQ
+CESQ: 99,99,255,255,255,255
OK
%CESQ: 31,1,4,0
+CEREG: 2,&amp;quot;3319&amp;quot;,&amp;quot;0ABA3210&amp;quot;,7
+CNEC_EMM: 11
%CESQ: 255,0,255,0
+CEREG: 2,&amp;quot;FFFE&amp;quot;,&amp;quot;FFFFFFFF&amp;quot;,7
%CESQ: 34,1,9,1
+CEREG: 2,&amp;quot;3319&amp;quot;,&amp;quot;0ABA3210&amp;quot;,7
AT+CESQ
+CESQ: 99,99,255,255,9,34
OK
+CNEC_ESM: 38,0
+CNEC_EMM: 19
%CESQ: 255,0,255,0
+CEREG: 2,&amp;quot;FFFE&amp;quot;,&amp;quot;FFFFFFFF&amp;quot;,7
%CESQ: 31,1,7,1
+CEREG: 2,&amp;quot;3319&amp;quot;,&amp;quot;0ABA3210&amp;quot;,7
AT+CESQ
+CESQ: 99,99,255,255,7,31
OK
AT+CESQ
+CESQ: 99,99,255,255,7,31
OK
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Here is with V1.1.0&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;
SPM: NS reset vector at 0xde89
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS build v2.0.99-ncs1 *****
The AT host sample started
AT+CFUN=1
OK
AT+CFUN?
+CFUN: 1
OK
AT+CGSN=1
+CGSN: &amp;quot;352656100816191&amp;quot;
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9160-SICA
OK
AT+CGMR
mfw_nrf9160_1.0.1
OK
AT+CEMODE?
+CEMODE: 2
OK
AT%XCBAND=?
%XCBAND: (1,2,3,4,5,8,12,13,14,17,18,19,20,25,26,28,66)
OK
AT+CMEE?
+CMEE: 0
OK
AT+CMEE=1
OK
AT+CNEC?
+CNEC: 0
OK
AT+CNEC=24
OK
AT+CGEREP?
+CGEREP: 0,0
OK
AT+CGDCONT?
+CGDCONT: 0,&amp;quot;IP&amp;quot;,&amp;quot;m2m64.com.attz&amp;quot;,&amp;quot;10.71.183.29&amp;quot;,0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
AT+CGEREP=1
OK
AT+CIND=1,1,1
OK
AT+CEREG=2
OK
AT+CESQ
+CESQ: 99,99,255,255,255,34
OK
AT+CEREG?
+CEREG: 2,1,&amp;quot;3319&amp;quot;,&amp;quot;0ABB1011&amp;quot;,7
OK
AT+COPS=3,2
OK
AT+COPS?
+COPS: 0,2,&amp;quot;310410&amp;quot;,7
OK
AT%XCBAND
%XCBAND: 17
OK
AT+CGDCONT?
+CGDCONT: 0,&amp;quot;IP&amp;quot;,&amp;quot;m2m64.com.attz&amp;quot;,&amp;quot;10.71.183.29&amp;quot;,0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
AT%CESQ=1
OK
AT+CESQ
+CESQ: 99,99,255,255,255,34
OK
AT%XSIM=1
OK
AT%XSIM?
%XSIM: 1
OK
AT+CPIN?
+CPIN: READY
OK
AT+CPINR=&amp;quot;SIM PIN&amp;quot;
+CPINR: &amp;quot;SIM PIN&amp;quot;,3
OK
AT+CIMI
310170833560137
OK
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I can open another ticket if requested but since it seems like it may be the same issue I&amp;#39;m starting here.&amp;nbsp; Please advise if there is anything we can do to help troubleshoot this.&amp;nbsp; Thank you in advance for any and all support.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>