Verification failed during quick start demo using nRF Connect for desktop

[Surya09]

I was going through the Cellular IOT fundamental tutorial. I downloaded the nRF connect for desktop application and started with "quick start".  I selected the asset tracking, program the board. During stage "automatic kit communication with AT commands", I clicked verify, but I get Error. I opened the log file and observe "unable to find the AT Client". Additionally, I have noticed the LED5 (activity led) keeps blinking.  Could anyone kindly tell how to fix this issue?

Fullscreen 3058.2024-02-29T12_35_21.070Z-log.txt Download

2024-02-29T12:35:21.388Z INFO Initialising nrfutil module: device
2024-02-29T12:35:21.404Z DEBUG Started watching devices
2024-02-29T12:35:23.258Z INFO Using nrfutil-device version: 2.1.1
2024-02-29T12:35:23.259Z INFO Using nrf-device-lib version: 0.17.5
2024-02-29T12:35:23.260Z INFO Using nrfjprog DLL version: 10.24.0
2024-02-29T12:35:23.260Z INFO Using JLink version: JLink_V7.94e
2024-02-29T12:35:27.737Z DEBUG Selected device: nRF9160 DK
2024-02-29T12:35:27.764Z DEBUG Changed step: info
2024-02-29T12:35:28.842Z DEBUG Changed step: rename
2024-02-29T12:35:30.722Z DEBUG Changed step: program
2024-02-29T12:36:33.307Z DEBUG Changed step: verify
2024-02-29T12:36:40.125Z INFO Opened port with options: {"path":"COM12","baudRate":115200}
2024-02-29T12:36:42.154Z INFO Closed port: COM12
2024-02-29T12:36:42.156Z INFO Opened port with options: {"path":"COM11","baudRate":115200}
2024-02-29T12:36:44.166Z INFO Opened port with options: {"path":"COM10","baudRate":115200}
2024-02-29T12:36:44.169Z INFO Closed port: COM11
2024-02-29T12:36:46.190Z ERROR Error: Unable to find the AT client.
2024-02-29T12:36:46.208Z INFO Closed port: COM10
2024-02-29T12:37:20.874Z DEBUG Changed step: program
2024-02-29T12:38:31.523Z DEBUG Changed step: verify
2024-02-29T12:38:32.542Z DEBUG Changed step: program
2024-02-29T12:38:50.950Z DEBUG Changed step: verify
2024-02-29T12:38:51.940Z DEBUG Changed step: sim
2024-02-29T13:36:34.899Z DEBUG Changed step: verify
2024-02-29T13:36:35.342Z DEBUG Changed step: sim
2024-02-29T13:36:36.217Z DEBUG Changed step: verify
2024-02-29T13:36:37.054Z DEBUG Changed step: program
2024-02-29T13:36:37.779Z DEBUG Changed step: verify
2024-02-29T13:36:39.283Z DEBUG Changed step: program
2024-02-29T13:38:05.567Z DEBUG Changed step: verify
2024-02-29T13:38:08.204Z INFO Opened port with options: {"path":"COM12","baudRate":115200}
2024-02-29T13:38:10.211Z INFO Closed port: COM12
2024-02-29T13:38:10.213Z INFO Opened port with options: {"path":"COM11","baudRate":115200}
2024-02-29T13:38:12.222Z INFO Closed port: COM11
2024-02-29T13:38:12.224Z INFO Opened port with options: {"path":"COM10","baudRate":115200}
2024-02-29T13:38:14.226Z ERROR Error: Unable to find the AT client.
2024-02-29T13:38:14.246Z INFO Closed port: COM10
2024-02-29T13:38:16.397Z DEBUG Changed step: program
2024-02-29T13:38:22.118Z DEBUG Changed step: verify
2024-02-29T13:38:23.091Z INFO Opened port with options: {"path":"COM12","baudRate":115200}
2024-02-29T13:38:25.098Z INFO Closed port: COM12
2024-02-29T13:38:25.100Z INFO Opened port with options: {"path":"COM11","baudRate":115200}
2024-02-29T13:38:27.108Z INFO Closed port: COM11
2024-02-29T13:38:27.110Z INFO Opened port with options: {"path":"COM10","baudRate":115200}
2024-02-29T13:38:29.112Z ERROR Error: Unable to find the AT client.
2024-02-29T13:38:29.134Z INFO Closed port: COM10
2024-02-29T13:54:31.622Z DEBUG Changed step: program
2024-02-29T13:54:59.594Z DEBUG Changed step: verify
2024-02-29T13:56:17.158Z DEBUG Changed step: program
2024-02-29T13:57:48.274Z DEBUG Changed step: verify
2024-02-29T13:57:51.975Z INFO Opened port with options: {"path":"COM12","baudRate":115200}
2024-02-29T13:57:53.985Z INFO Closed port: COM12
2024-02-29T13:57:53.989Z INFO Opened port with options: {"path":"COM11","baudRate":115200}
2024-02-29T13:57:56.001Z INFO Opened port with options: {"path":"COM10","baudRate":115200}
2024-02-29T13:57:56.001Z INFO Closed port: COM11
2024-02-29T13:57:58.003Z ERROR Error: Unable to find the AT client.
2024-02-29T13:57:58.009Z INFO Closed port: COM10

[Surya09]

an update on this.

Since, I couldn't get the verification working. I jumped ahead with getting started! 

I download the nRF9160 SIP modem firmware from "www.nordicsemi.com/.../Download installed it using programmer in the nRF connect for Desktop. Furthermore, I flashed the code given by the cellular IOT fundamental lesson2 exercise2 code which is related to  using LTE Link Controller library in nRF Connect SDK to establish the LTE connection. But, I still can't get LTE connection. This is the error I get. I think the error is related to the firmware not get properly verified. But, I would appreciate any help. I am really stuck on this. 

 

[helsing]

Hi Siddharth,

Could you try the following: Open Cellular Monitor from nRF Connect for Desktop. Select the board, and program the device using the "Program device" button. Select Asset Tracker v2 or Serial LTE Modem and check if you are able to get any connection.

[Surya09]

Hello helsing 

Thank you for reply. I tried the suggestion given by you, but I still didn't get any connection. Also, the led1, led2, led3, and led4 doesn't turn on at all. Led5 keeps blinking slowly. This is the from the cellular Monitor by programming it for Asset Tracker v2.

[helsing]

Try following the steps here instead: Getting started using Quick Start

Verify that the PROG/DEBUG SW10 switch on the nRF9160 DK is set to nRF91.

[Surya09]

 helsing Thanks for reply. 

I found out the issue. It was related to the Modem firmware. I flashed the firmware version 1.2.8 which is for board 9160 rev1 and now it finally works!

[helsing]

Great to hear that it is now working. However, MFW v1.2.8 is only tested with the older nRF Connect SDK version, v1.5.2, as acoording to the modem firmware compatibility matrix.

What happens if you now try to upgrade to a newer modem firmware, for example MFW v1.3.6?

[Surya09]

I programmed the NRF9160 with the modem firmware version to v1.3.5 as I am using nRF connect SDK version 2.4.0. I flashed the at_client application and this the output I obtained. 

[helsing]

Surya09 said:

I found out the issue. It was related to the Modem firmware. I flashed the firmware version 1.2.8 which is for board 9160 rev1 and now it finally works!

Good to hear that you are able to proceed. However, please note that nRF9160 Revision 1(B0) is tested with MFW < v1.2.8. This version is compatible with nRF Connect SDK v1.5.2, as according to the compatibility matrix. Some newer versions of the SDK and MFW migh work with B0 but this is not guranateed. It is OK to use some of these combinations for some development purposes but you might run into issues. For production you should use the correct version. Also see the modem firmware release notes for more details.