• State Suggested Answer
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 87 subscribers
  • Views 2052 views
  • Users 0 members are here
Attachments (9) Download All
Nordic Case Info
  • Case ID: 271203
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

While following the steps required to provision the nRF9160 Connect for Cloud certificate,I entered the 'AT+CFUN=4' in the AT command text field and I clicked 'Send' but then the following error message comes up in the log file: Error:'

Jacek Majda

While following the steps required to provision the nRF9160 Connect for Cloud certificate, I entered the 'AT+CFUN=4' in the AT command text field and I clicked 'Send' but then the following error message comes up in the log file: Error:'AT+CFUN=4' timed out.

As instructed, I completed the following steps in order to provision the nRF Connect for Cloud certificate:

1. I downloaded the relevant " *.cert.json" file to my PC.

2. I opened the nRF Connect for Desktop on my PC and I launched the nRF Connect LTE Link Monitor.

3. In the setting pane, I deselected the checkbox for 'Automatic requests'.

4. I did not insert any SIM card into my nRF9160 DK.

5. I connected the nRF9160 DK to my PC and I turned it on. (In the navigation bar "No devices available" changed to "Select Device").

6. I selected my device (nRF9160 DK).

7. I clicked 'Terminal' in the navigation bar to switch to the terminal view.

8. I entered 'AT+CFUN=4' in the AT command text field and I clicked "Send".

9. As soon as I clicked "Send" , the following error message appeared in the log file: "Error: 'AT+CFUN=4' timed out".  I also did not see any OK or other confirmation that my message was received.

10. I then tried to enter "AT+CFUN?" in the AT command text field and I clicked "Send" but again, I did not see any OK or other confirmation that my message was received and again the Error message "Error: 'AT+CFUNC?' timed out" appeared in the log file.

N.B.

1. The version of my nRF9160 DK is v 0.8.2.

2. I am using Windows 10 Pro operating system, version: 20H2, OS build: 19042.631

3. I am using nRF Connectt v.3.6.1

  • 0

    Hello, 

    From the LTE Link Monitor can you please provide a full log output?

    What application are you running on your device? Please make sure you are running latest version of either Asset Tracker or AT client.

    Kind regards,
    Øyvind

  • 0

    Hello Øyvind,

    Herewith is the full log output from the LTE Link Monitor:

    Fullscreen Log-output from LTE Link Monitor 2021-06-07_T14_07_27.189Z-log.txt Download 
    2021-06-07T14:07:35.192Z INFO Application data folder: C:\Users\Administrator\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-06-07T14:07:35.284Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official
2021-06-07T14:07:35.285Z DEBUG App path: C:\Users\Administrator\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-06-07T14:07:35.285Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-06-07T14:07:35.285Z DEBUG nRFConnect path: C:\Users\Administrator\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-06-07T14:07:35.286Z DEBUG HomeDir: C:\Users\Administrator
2021-06-07T14:07:35.286Z DEBUG TmpDir: C:\Users\ADMINI~1\AppData\Local\Temp
2021-06-07T14:07:35.421Z VERBOSE Could not fetch serial number for serial port at COM3
2021-06-07T14:07:44.726Z INFO Modem port is opened
2021-06-07T14:09:28.295Z DEBUG modem >> AT+CFUN=4
2021-06-07T14:09:29.297Z ERROR Error: 'AT+CFUN=4
' timed out
2021-06-07T14:10:24.507Z DEBUG modem >> AT+CFUN?
2021-06-07T14:10:25.509Z ERROR Error: 'AT+CFUN?
' timed out

    I am running the Asset Tracker Application: nRF9160dk_asset_tracker_nbiot_2021-03-01_8e8c6089.hex and I attach this file below:

    2843.nrf9160dk_asset_tracker_nbiot_2021-03-01_8e8c6089.hex

    Regards,

    Jacek Majda

  • 0 in reply to Jacek Majda

    Thanks for sharing with me. 

    There seems to be something on your side. I had no issues with programming this image on my nRF9160 DK v0.8.2, and running AT commands as expected.

    1. Connected the board to USB.
    2. Opened nRF Connect for Desktop - Programmer
    3. Connected to PCA10090
    4. Added the .hex file
    5. Clicked erase and write
      Fullscreen TS_DZ-P_2021-06-08T06_31_23.645Z-log.txt Download 
      2021-06-08T06:31:23.847Z INFO Application data folder: C:\Users\oysa\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-06-08T06:31:23.916Z DEBUG App pc-nrfconnect-programmer v1.4.10 official
2021-06-08T06:31:23.916Z DEBUG App path: C:\Users\oysa\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2021-06-08T06:31:23.916Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-06-08T06:31:23.916Z DEBUG nRFConnect path: C:\Users\oysa\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-06-08T06:31:23.916Z DEBUG HomeDir: C:\Users\oysa
2021-06-08T06:31:23.916Z DEBUG TmpDir: C:\Users\oysa\AppData\Local\Temp
2021-06-08T06:31:23.927Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-06-08T06:31:24.856Z VERBOSE Could not fetch serial number for serial port at COM1
2021-06-08T06:31:24.856Z VERBOSE Could not fetch serial number for serial port at COM3
2021-06-08T06:31:27.138Z INFO Using nrfjprog to communicate with target
2021-06-08T06:31:27.777Z INFO Using J-Link Software version 6.88
2021-06-08T06:31:28.256Z INFO Segger serial:  960075900
2021-06-08T06:31:28.256Z INFO Segger speed:  2000  kHz
2021-06-08T06:31:28.256Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-06-08T06:31:28.256Z INFO Core probed: 960075900
2021-06-08T06:31:28.256Z INFO Core RAM: 256KiB
2021-06-08T06:31:28.256Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-06-08T06:31:28.568Z INFO Model: NRF9160_xxAA_REV1.
2021-06-08T06:31:29.236Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-06-08T06:31:38.826Z INFO Core0: Non-volatile memory has been read. 5 non-empty memory blocks identified 
2021-06-08T06:31:49.094Z INFO Parsing HEX file:  C:\Temp\Support\271203\2843.nrf9160dk_asset_tracker_nbiot_2021-03-01_8e8c6089.hex
2021-06-08T06:31:49.118Z INFO File was last modified at  6/8/2021, 8:29:49 AM
2021-06-08T06:33:00.857Z INFO Writing image to disable app readback protection
2021-06-08T06:33:00.865Z ERROR Second argument must be a string
2021-06-08T06:33:00.865Z INFO Recovery procedure finished
2021-06-08T06:33:00.873Z INFO Using nrfjprog to communicate with target
2021-06-08T06:33:01.375Z INFO Using J-Link Software version 6.88
2021-06-08T06:33:01.856Z INFO Segger serial:  960075900
2021-06-08T06:33:01.856Z INFO Segger speed:  2000  kHz
2021-06-08T06:33:01.856Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-06-08T06:33:01.856Z INFO Core probed: 960075900
2021-06-08T06:33:01.856Z INFO Core RAM: 256KiB
2021-06-08T06:33:01.856Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-06-08T06:33:02.163Z INFO Model: NRF9160_xxAA_REV1.
2021-06-08T06:33:02.799Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-06-08T06:33:03.544Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.
2021-06-08T06:33:03.804Z INFO Writing procedure starts for core0
2021-06-08T06:33:24.199Z INFO Write procedure finished
2021-06-08T06:33:24.201Z INFO Using nrfjprog to communicate with target
2021-06-08T06:33:24.821Z INFO Using J-Link Software version 6.88
2021-06-08T06:33:25.395Z INFO Segger serial:  960075900
2021-06-08T06:33:25.395Z INFO Segger speed:  2000  kHz
2021-06-08T06:33:25.395Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2021-06-08T06:33:25.395Z INFO Core probed: 960075900
2021-06-08T06:33:25.395Z INFO Core RAM: 256KiB
2021-06-08T06:33:25.395Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-06-08T06:33:25.692Z INFO Model: NRF9160_xxAA_REV1.
2021-06-08T06:33:26.304Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-06-08T06:33:35.861Z INFO Core0: Non-volatile memory has been read. 6 non-empty memory blocks identified

    1. Opened nRF Connect for Desktop - LTE Link Monitor
    2. Connected to PCA10090
    3. Pressed reset on board
      Fullscreen TS_DZ-LLM_2021-06-08T06_35_21.188Z-log.txt Download 
      2021-06-08T06:35:22.411Z INFO Application data folder: C:\Users\oysa\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-06-08T06:35:22.431Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official
2021-06-08T06:35:22.431Z DEBUG App path: C:\Users\oysa\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-06-08T06:35:22.431Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-06-08T06:35:22.431Z DEBUG nRFConnect path: C:\Users\oysa\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-06-08T06:35:22.431Z DEBUG HomeDir: C:\Users\oysa
2021-06-08T06:35:22.431Z DEBUG TmpDir: C:\Users\oysa\AppData\Local\Temp
2021-06-08T06:35:22.434Z VERBOSE Could not fetch serial number for serial port at COM1
2021-06-08T06:35:22.435Z VERBOSE Could not fetch serial number for serial port at COM3
2021-06-08T06:35:24.627Z INFO Modem port is opened
2021-06-08T06:35:24.632Z DEBUG modem >> AT+CFUN?
2021-06-08T06:35:24.655Z DEBUG modem << +CFUN: 4
2021-06-08T06:35:24.656Z DEBUG modem << OK
2021-06-08T06:35:24.665Z DEBUG modem >> AT+CFUN=1
2021-06-08T06:35:24.708Z DEBUG modem << OK
2021-06-08T06:35:24.946Z DEBUG modem << +CEREG: 90
2021-06-08T06:35:24.958Z DEBUG modem << [00:01:37.394,409] [0m<inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: -1[0m
2021-06-08T06:35:25.082Z DEBUG modem << [00:01:37.527,557] [0m<inf> asset_tracker: No SIM card detected.[0m
2021-06-08T06:35:25.091Z DEBUG modem << [00:01:37.533,691] [0m<inf> asset_tracker: Insert SIM and reset device to run the asset tracker.[0m
2021-06-08T06:36:02.549Z DEBUG modem << *** Booting Zephyr OS build v2.3.0-rc1-ncs2  ***
2021-06-08T06:36:02.556Z DEBUG modem << [00:00:00.005,035] [0m<inf> mcuboot: Starting bootloader[0m
2021-06-08T06:36:02.563Z DEBUG modem << [00:00:00.013,244] [0m<inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3[0m
2021-06-08T06:36:02.569Z DEBUG modem << [00:00:00.026,672] [0m<inf> mcuboot: Boot source: none[0m
2021-06-08T06:36:02.576Z DEBUG modem << [00:00:00.033,966] [0m<inf> mcuboot: Swap type: none[0m
2021-06-08T06:36:02.924Z DEBUG modem << [00:00:00.458,221] [0m<inf> mcuboot: Bootloader chainload address offset: 0x10000[0m
2021-06-08T06:36:02.930Z DEBUG modem << [00:00:00.465,942] [0m<inf> mcuboot: Jumping to the first image slot[0m
2021-06-08T06:36:02.935Z DEBUG modem << *** Booting Zephyr OS build v2.4.99-ncs1  ***
2021-06-08T06:36:02.938Z DEBUG modem << Flash regionsDomainPermissions
2021-06-08T06:36:02.943Z DEBUG modem << 00 02 0x00000 0x18000 Securerwxl
2021-06-08T06:36:02.946Z DEBUG modem << 03 31 0x18000 0x100000 Non-Securerwxl
2021-06-08T06:36:02.951Z DEBUG modem << Non-secure callable region 0 placed in flash region 2 with size 32.
2021-06-08T06:36:03.123Z DEBUG modem << SRAM regionDomainPermissions
2021-06-08T06:36:03.135Z DEBUG modem << 00 07 0x00000 0x10000 Securerwxl
2021-06-08T06:36:03.136Z DEBUG modem << 08 31 0x10000 0x40000 Non-Securerwxl
2021-06-08T06:36:03.136Z DEBUG modem << PeripheralDomainStatus
2021-06-08T06:36:03.137Z DEBUG modem << 00 NRF_P0               Non-SecureOK
2021-06-08T06:36:03.139Z DEBUG modem << 01 NRF_CLOCK            Non-SecureOK
2021-06-08T06:36:03.142Z DEBUG modem << 02 NRF_RTC0             Non-SecureOK
2021-06-08T06:36:03.146Z DEBUG modem << 03 NRF_RTC1             Non-SecureOK
2021-06-08T06:36:03.148Z DEBUG modem << 04 NRF_NVMC             Non-SecureOK
2021-06-08T06:36:03.152Z DEBUG modem << 05 NRF_UARTE1           Non-SecureOK
2021-06-08T06:36:03.155Z DEBUG modem << 06 NRF_UARTE2           SecureSKIP
2021-06-08T06:36:03.160Z DEBUG modem << 07 NRF_TWIM2            Non-SecureOK
2021-06-08T06:36:03.162Z DEBUG modem << 08 NRF_SPIM3            Non-SecureOK
2021-06-08T06:36:03.166Z DEBUG modem << 09 NRF_TIMER0           Non-SecureOK
2021-06-08T06:36:03.169Z DEBUG modem << 10 NRF_TIMER1           Non-SecureOK
2021-06-08T06:36:03.172Z DEBUG modem << 11 NRF_TIMER2           Non-SecureOK
2021-06-08T06:36:03.176Z DEBUG modem << 12 NRF_SAADC            Non-SecureOK
2021-06-08T06:36:03.179Z DEBUG modem << 13 NRF_PWM0             Non-SecureOK
2021-06-08T06:36:03.183Z DEBUG modem << 14 NRF_PWM1             Non-SecureOK
2021-06-08T06:36:03.186Z DEBUG modem << 15 NRF_PWM2             Non-SecureOK
2021-06-08T06:36:03.189Z DEBUG modem << 16 NRF_PWM3             Non-SecureOK
2021-06-08T06:36:03.193Z DEBUG modem << 17 NRF_WDT              Non-SecureOK
2021-06-08T06:36:03.196Z DEBUG modem << 18 NRF_IPC              Non-SecureOK
2021-06-08T06:36:03.200Z DEBUG modem << 19 NRF_VMC              Non-SecureOK
2021-06-08T06:36:03.203Z DEBUG modem << 20 NRF_FPU              Non-SecureOK
2021-06-08T06:36:03.206Z DEBUG modem << 21 NRF_EGU1             Non-SecureOK
2021-06-08T06:36:03.210Z DEBUG modem << 22 NRF_EGU2             Non-SecureOK
2021-06-08T06:36:03.213Z DEBUG modem << 23 NRF_DPPIC            Non-SecureOK
2021-06-08T06:36:03.217Z DEBUG modem << 24 NRF_REGULATORS       Non-SecureOK
2021-06-08T06:36:03.220Z DEBUG modem << 25 NRF_GPIOTE1          Non-SecureOK
2021-06-08T06:36:03.225Z DEBUG modem << SPM: NS image at 0x1c200
2021-06-08T06:36:03.226Z DEBUG modem << SPM: NS MSP at 0x20025598
2021-06-08T06:36:03.228Z DEBUG modem << SPM: NS reset vector at 0x26805
2021-06-08T06:36:03.231Z DEBUG modem << SPM: prepare to jump to Non-Secure image.
2021-06-08T06:36:03.444Z DEBUG modem << *** Booting Zephyr OS build v2.4.99-ncs1  ***
2021-06-08T06:36:03.459Z DEBUG modem << [00:00:00.212,280] [0m<inf> asset_tracker: Asset tracker started[0m
2021-06-08T06:36:03.465Z DEBUG modem << [00:00:00.218,444] [0m<inf> watchdog: Watchdog timeout installed. Timeout: 60000[0m
2021-06-08T06:36:03.468Z DEBUG modem << [00:00:00.226,013] [0m<inf> watchdog: Watchdog started[0m
2021-06-08T06:36:03.477Z DEBUG modem << [00:00:00.231,323] [0m<inf> watchdog: Watchdog feed enabled. Timeout: 30000[0m
2021-06-08T06:36:03.493Z DEBUG modem << [00:00:00.245,758] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100051328[0m
2021-06-08T06:36:03.503Z DEBUG modem << [00:00:00.254,882] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100051328/shadow[0m
2021-06-08T06:36:03.515Z DEBUG modem << [00:00:00.266,479] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100051328/shadow/get/accepted[0m
2021-06-08T06:36:03.527Z DEBUG modem << [00:00:00.277,893] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100051328/shadow/get/rejected[0m
2021-06-08T06:36:03.539Z DEBUG modem << [00:00:00.290,344] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100051328/shadow/update/delta[0m
2021-06-08T06:36:03.552Z DEBUG modem << [00:00:00.303,161] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100051328/shadow/update[0m
2021-06-08T06:36:03.564Z DEBUG modem << [00:00:00.314,941] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100051328/shadow/get[0m
2021-06-08T06:36:03.569Z DEBUG modem << [00:00:00.326,782] [0m<inf> asset_tracker: Connecting to LTE network.[0m
2021-06-08T06:36:03.578Z DEBUG modem << [00:00:00.333,374] [0m<inf> asset_tracker: This may take several minutes.[0m
2021-06-08T06:36:03.868Z DEBUG modem << +CEREG: 90
2021-06-08T06:36:03.877Z DEBUG modem << [00:00:00.631,561] [0m<inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: -1[0m
2021-06-08T06:36:03.906Z DEBUG modem << +CEREG: 0,"FFFE","FFFFFFFF",9,0,0,"11100000","11100000"
2021-06-08T06:36:03.916Z DEBUG modem << [00:00:00.669,982] [0m<inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: 65534[0m
2021-06-08T06:36:04.021Z DEBUG modem << [00:00:00.778,930] [0m<inf> asset_tracker: No SIM card detected.[0m
2021-06-08T06:36:04.030Z DEBUG modem << [00:00:00.785,064] [0m<inf> asset_tracker: Insert SIM and reset device to run the asset tracker.[0m

    Note that my board did not have a SIM inserted, but that should not have any impact. Please provide screenshots of your nRF Connect for Desktop applications, and describe the setup on your board. Have you tried to update the modem FW?

    Thanks!

    Kind regards,
    Øyvind

  • 0

    Hello Øyvind,

    I am not sure what exactly do you refer by "screenshots of my nRF Connect for Desktop applications".

    I was using the Asset Tracker application: nRF9160dk_asset_tracker_nbiot_2021-03-01_8e8c6089.hex and I attach this file below:

    4075.nrf9160dk_asset_tracker_nbiot_2021-03-01_8e8c6089.hex

    I also tried to use the alternative, legacy Asset Tracker application, namely:  nRF9160dk_asset_tracker_nbiot_legacy_pco_2021-03-01_8e8c6089.hex       and I attach this file below:

    nrf9160dk_asset_tracker_nbiot_legacy_pco_2021-03-01_8e8c6089.hex

    I also updated the modem FM with the following zip file:

    mfwnrf9160123.zip

    I attach two screenshots from my nRF Connect for Desktop for your reference:

    Screenshot-1.docx

    and

    Screenshot-2.docx

    The setup of my nRF9160 DK board is as follows:

    1. The Prog/Debug (SW5) selector switch is in the nRF91 position.

    2. Both Switch 1 and Switch 2 are in the GND position.

    Regards,

    Jacek

  • 0

    Jacek, thanks for providing this information! The issue is the .hex files that you are using does not include the bootloader. 

    This is how my Programmer looks, running AT client on my board and loaded the img_app_bl/nrf9160dk_asset_tracker_nbiot_2021-03-01_8e8c6089.hex

    And this is with the file you provided, assuming this is: img_fota_dfu_hex/nrf9160dk_at_client_2021-03-01_8e8c6089.hex

    Please try with images found in img_app_bl/ (Full application images, including bootloader. Updated only via debug probe.)

    Let me know how that works for you.

    Kind regards,
    Øyvind

Related
Terms of service