My nRf9160-DK has suddenly stopped being able to connect to the LTE-M network.

[Julia]

 It has been working with no problems. Neither the At application or the asset-tracker one will work.  Is there anyway I can test/ find out whether  there is an issue with the LTE-M network. I am in Cambridge UK where I believe there is a test LTE-M network. Thanks

[Martin Lesund]

Hello Julia,

Please upgrade the modem firmware version to the latest one: https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs

Then update the nrf Connect SDK:

cd nrf
git pull
west update

//Then flash the AT-client
cd samples/nrf9160/at_client
west build -b nrf9160_pca10090ns -d build_1
west flash -d build_1

Then post the log output you get when using the LTE link monitor.

Run the command "AT+CFUN?" a couple of times.

It's can give us an indication what is happening on the modem.

Best Regards,
Martin L,

[Martin Lesund]

Hello Julia,

Please upgrade the modem firmware version to the latest one: https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs

Then update the nrf Connect SDK:

cd nrf
git pull
west update

//Then flash the AT-client
cd samples/nrf9160/at_client
west build -b nrf9160_pca10090ns -d build_1
west flash -d build_1

Then post the log output you get when using the LTE link monitor.

Run the command "AT+CFUN?" a couple of times.

It's can give us an indication what is happening on the modem.

Best Regards,
Martin L,

[Julia]

Thank-you for getting back to me.  Took me a while to get setup to build with the new version.

Hope this is what you wanted

***** Booting Zephyr OS v1.14.99-ncs1-rc1-2-g33c06133c197 *****
Flash region        Domain        Permissions
00 0x00000 0x02000     Secure        rwxl
01 0x02000 0x04000     Non-Secure    rwxl
02 0x04000 0x06000     Non-Secure    rwxl
03 0x06000 0x08000     Non-Secure    rwxl
04 0x08000 0x0a000     Non-Secure    rwxl
05 0x0a000 0x0c000     Non-Secure    rwxl
06 0x0c000 0x0e000     Non-Secure    rwxl
07 0x0e000 0x10000     Non-Secure    rwxl
08 0x10000 0x12000     Non-Secure    rwxl
09 0x12000 0x14000     Non-Secure    rwxl
10 0x14000 0x16000     Non-Secure    rwxl
11 0x16000 0x18000     Non-Secure    rwxl
12 0x18000 0x1a000     Non-Secure    rwxl
13 0x1a000 0x1c000     Non-Secure    rwxl
14 0x1c000 0x1e000     Non-Secure    rwxl
15 0x1e000 0x20000     Non-Secure    rwxl
16 0x20000 0x22000     Non-Secure    rwxl
17 0x22000 0x24000     Non-Secure    rwxl
18 0x24000 0x26000     Non-Secure    rwxl
19 0x26000 0x28000     Non-Secure    rwxl
20 0x28000 0x2a000     Non-Secure    rwxl
21 0x2a000 0x2c000     Non-Secure    rwxl
22 0x2c000 0x2e000     Non-Secure    rwxl
23 0x2e000 0x30000     Non-Secure    rwxl
24 0x30000 0x32000     Non-Secure    rwxl
25 0x32000 0x34000     Non-Secure    rwxl
26 0x34000 0x36000     Non-Secure    rwxl
27 0x36000 0x38000     Non-Secure    rwxl
28 0x38000 0x3a000     Non-Secure    rwxl
29 0x3a000 0x3c000     Non-Secure    rwxl
30 0x3c000 0x3e000     Non-Secure    rwxl
31 0x3e000 0x40000     Non-Secure    rwxl

SRAM region        Domain        Permissions
00 0x00000 0x01000    Secure        rwxl
01 0x01000 0x02000    Secure        rwxl
02 0x02000 0x03000    Secure        rwxl
03 0x03000 0x04000    Secure        rwxl
04 0x04000 0x05000    Secure        rwxl
05 0x05000 0x06000    Secure        rwxl
06 0x06000 0x07000    Secure        rwxl
07 0x07000 0x08000    Secure        rwxl
08 0x08000 0x09000    Non-Secure    rwxl
09 0x09000 0x0a000    Non-Secure    rwxl
10 0x0a000 0x0b000    Non-Secure    rwxl
11 0x0b000 0x0c000    Non-Secure    rwxl
12 0x0c000 0x0d000    Non-Secure    rwxl
13 0x0d000 0x0e000    Non-Secure    rwxl
14 0x0e000 0x0f000    Non-Secure    rwxl
15 0x0f000 0x10000    Non-Secure    rwxl
16 0x10000 0x11000    Non-Secure    rwxl
17 0x11000 0x12000    Non-Secure    rwxl
18 0x12000 0x13000    Non-Secure    rwxl
19 0x13000 0x14000    Non-Secure    rwxl
20 0x14000 0x15000    Non-Secure    rwxl
21 0x15000 0x16000    Non-Secure    rwxl
22 0x16000 0x17000    Non-Secure    rwxl
23 0x17000 0x18000    Non-Secure    rwxl
24 0x18000 0x19000    Non-Secure    rwxl
25 0x19000 0x1a000    Non-Secure    rwxl
26 0x1a000 0x1b000    Non-Secure    rwxl
27 0x1b000 0x1c000    Non-Secure    rwxl
28 0x1c000 0x1d000    Non-Secure    rwxl
29 0x1d000 0x1e000    Non-Secure    rwxl
30 0x1e000 0x1f000    Non-Secure    rwxl
31 0x1f000 0x20000    Non-Secure    rwxl

Peripheral        Domain        Status
00 NRF_P0        Non-Secure    OK
01 NRF_CLOCK        Non-Secure    OK
02 NRF_RTC1        Non-Secure    OK
03 NRF_NVMC        Non-Secure    OK
04 NRF_UARTE1        Non-Secure    OK
05 NRF_UARTE2        Secure        SKIP
06 NRF_IPC        Non-Secure    OK
07 NRF_VMC        Non-Secure    OK
08 NRF_FPU        Non-Secure    ERROR
09 NRF_EGU1        Non-Secure    OK
10 NRF_EGU2        Non-Secure    OK
11 NRF_TWIM2        Non-Secure    OK
12 NRF_SPIM3        Non-Secure    OK
13 NRF_TIMER0        Non-Secure    OK
14 NRF_TIMER1        Non-Secure    OK
15 NRF_TIMER2        Non-Secure    OK
16 NRF_SAADC        Non-Secure    OK
17 NRF_GPIOTE1        Non-Secure    OK

SPM: MSP_NS 200236c8
SPM: prepare to jump to Non-Secure image
***** Booting Zephyr OS v1.14.99-ncs1-rc1-2-g33c06133c197 *****
The AT host sample started
AT+CFUN?
+CFUN: 4
OK
AT+CFUN=1
OK
AT+CFUN?
+CFUN: 1
OK
AT+CGSN=1
+CGSN: "352656100103723"
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9160
OK
AT+CGMR
mfw-m1_nrf9160_0.6.8-131.alpha
OK
AT+CEMODE?
+CEMODE: 2
OK
AT%XCBAND=?
%XCBAND: (3,4,13,20)
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,"FFFE","FFFFFFFF",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="SIM PIN"
+CPINR: "SIM PIN",3
OK
AT+CIMI
204080813511352
OK
%CESQ: 255,0
+CEREG: 2,"FFFE","FFFFFFFF",7
%CESQ: 255,0
%CESQ: 255,0
%CESQ: 255,0


Type AT command here...
Send
AT
AT+CFUN?
AT+CFUN=1

Log

[Martin Lesund]

Hi Julia,
That is very strange that it worked fine before, since the Received signal quality parameters states that the "RSRP" (Reference Signal Received Power) is "not known or not detectable".

Which SIM card are you using?

Which network are you trying to connect to?

---

Let's take a detailed modem trace:

at_client_tracing.hex

using the command: nrfjprog --program at_client_tracing.hex -f nrf91 --sectorerase -r --verify

Then run the "Trace collector" from "nRF Connect for Desktop" and  "LTE Link Monitor".

In both windows select your nrf91 DK, then in the Trace Collector app click "Start Capture"

Then go over to the LTE Link Monitor window and hit the physical reset button on the nRF91 DK and verify that the log output updates accordingly.

Make sure you have "Automatic Requests" checked:

Then please send the AT-command: AT+CFUN?

Then wait ~10 sec and send the same command again. 

Wait for ~5-10 mins while the Trace collector does it's job.

You can send the AT-Command: AT+CFUN? in the LTE Link Monitor to see if there are any updates.

When you are happy, you can "stop capture" in the Trace collector app and then send me the .bin file.

---

Best Regards,

Martin L.

[Julia]

Thank you , Sorry for the delay Ii was on Holiday.

I have done the above.

Is there a way of attaching the .bin file rather than just pasting into edit box?