nrf9160 Custom Board connectivity to nrf cloud

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Tue, 03 Jan 2023 19:41:29 GMT

Please add the certificates in the following files.

Regards,

RE: nrf9160 Custom Board connectivity to nrf cloud

azwawe — Tue, 03 Jan 2023 10:14:14 GMT

Hi Muhammad Usman, really thanks for your help. Will test that for entering any pins.

Not yet. In which part you add certificate on asset tracker v2 firmware, Muhammad?

I tought we just do provisioning certificates when the custom board runs on modem shell, right? thanks.

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Tue, 03 Jan 2023 08:37:08 GMT

Hi Azwawe

As for pin # , you can enter any pin # , i entered 654321. have you added the certificates to the asset tracker v2 firmware which you downloaded from the LTE link monitor and nrf cloud ? because it must be necessary to load certificates to the FW else you will not able to connect to nrf cloud or even log in

Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

azwawe — Tue, 03 Jan 2023 06:58:06 GMT

Hi Muhammad. Can you inform me which part in provisioning process to custom board that I define PIN for registering it to nrf cloud account? I already did provisioning process but still can't connect my custom board to nrf cloud, I receive wrong API Key, but I think I already did the process.

Thank you.

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Thu, 15 Dec 2022 19:09:19 GMT

Hi, charlie!

Thank you for the help now Connected! The issue was that I was not updating the certificates in

C:\Nordic\myapps\asset_tracker_v2_2_0\src\cloud-certs

thank you again for the help!

Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Thu, 15 Dec 2022 18:08:49 GMT

Hi Charlie!

Thank you for the help! I followed the flow chart as mentioned

https://miro.com/app/board/uXjVPfcfAd8=/

Asset tracker_V2 prj.config file is

#
# Copyright (c) 2021 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# General config
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_NANO=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_ASSERT=y
CONFIG_REBOOT=y
CONFIG_FPU=y

# Heap and stacks
CONFIG_HEAP_MEM_POOL_SIZE=47250
CONFIG_MAIN_STACK_SIZE=2048
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096
CONFIG_HW_STACK_PROTECTION=y
# Increase AT monitor heap size to be able to fit both neighbor cell measurement
# and other AT notifications that may come in rapid succession.
CONFIG_AT_MONITOR_HEAP_SIZE=1024

# Logging
CONFIG_LOG=y
CONFIG_LOG_MODE_DEFERRED=y

# nRF modem library
CONFIG_NRF_MODEM_LIB=y
CONFIG_NRF_MODEM_LIB_ON_FAULT_APPLICATION_SPECIFIC=y

# AT Host library - Used to send AT commands directy from an UART terminal and to allow
#		    integration with nRF Connect for Desktop LTE Link monitor application.
CONFIG_AT_HOST_LIBRARY=y

# Network
CONFIG_NETWORKING=y
CONFIG_NET_NATIVE=n
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_OFFLOAD=y
CONFIG_NET_IPV6=y
CONFIG_NET_IPV4=y

# LTE link control
CONFIG_LTE_AUTO_INIT_AND_CONNECT=n
CONFIG_LTE_NETWORK_MODE_LTE_M_GPS=y
## Power saving timers.
### 320 hours PSM.
CONFIG_LTE_PSM_REQ_RPTAU="11000001"
### 20 seconds active time.
CONFIG_LTE_PSM_REQ_RAT="00001010"

# Settings - Used to store real-time device configuration to flash.
CONFIG_SETTINGS=y
CONFIG_SETTINGS_FCB=y
CONFIG_FCB=y

# FOTA
CONFIG_FOTA_DOWNLOAD=y
CONFIG_DFU_TARGET=y
CONFIG_DOWNLOAD_CLIENT=y
CONFIG_DOWNLOAD_CLIENT_HTTP_FRAG_SIZE_1024=y
CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096
CONFIG_DOWNLOAD_CLIENT_BUF_SIZE=2300
CONFIG_DOWNLOAD_CLIENT_MAX_HOSTNAME_SIZE=128

# Flash - Used in FOTA, settings and storage for P-GPS.
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_STREAM_FLASH=y
CONFIG_MPU_ALLOW_FLASH_WRITE=y

# MCUBOOT
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_IMG_MANAGER=y
CONFIG_MCUBOOT_IMG_MANAGER=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y
CONFIG_SECURE_BOOT=y
CONFIG_BUILD_S1_VARIANT=y

# Watchdog
CONFIG_WATCHDOG_APPLICATION=y

# Application Event Manager
CONFIG_APP_EVENT_MANAGER=y
CONFIG_APP_EVENT_MANAGER_LOG_EVENT_TYPE=n

# cJSON - Used in cloud data encoding.
CONFIG_CJSON_LIB=y

# CAF - Common Application Framework
CONFIG_CAF=y
CONFIG_LED=y
CONFIG_CAF_LEDS=y
CONFIG_CAF_INIT_LOG_LED_READY_EVENTS=n
CONFIG_CAF_INIT_LOG_LED_EVENTS=n
CONFIG_CAF_INIT_LOG_MODULE_STATE_EVENTS=n

# Location related configuration
CONFIG_LOCATION=y
CONFIG_LOCATION_DATA_DETAILS=y
CONFIG_LOCATION_LOG_LEVEL_WRN=y

# Default cloud transport service
CONFIG_NRF_CLOUD_MQTT=y
CONFIG_HW_ID_LIBRARY=y
CONFIG_HW_ID_LIBRARY_SOURCE_IMEI=y


CONFIG_NRF_CLOUD_SEC_TAG= 16842753
CONFIG_CLOUD_CLIENT_ID_USE_CUSTOM=y
CONFIG_CLOUD_CLIENT_ID="351358814108376"

Asset Tracker Log file is

*** Booting Zephyr OS build v3.2.99-ncs1 ***<CR><LF>
I: Starting bootloader<CR><LF>
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Boot source: none<CR><LF>
I: Swap type: none<CR><LF>
I: Primary image: magic=bad, swap_type=0x0, copy_done=0x2, image_ok=0x1<CR><LF>
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Boot source: none<CR><LF>
I: Swap type: none<CR><LF>
I: Bootloader chainload address offset: 0x28000<CR><LF>
I: Jumping to the first image slot<CR>
*** Booting Zephyr OS build v3.2.99-ncs1 ***<CR><LF>
[00:00:00.486,541] <ESC>[0m<inf> app_event_manager: APP_EVT_START<ESC>[0m<CR><LF>
[00:00:00.487,609] <ESC>[0m<inf> app_event_manager: MODEM_EVT_INITIALIZED<ESC>[0m<CR><LF>
[00:00:00.555,419] <ESC>[0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING<ESC>[0m<CR><LF>
%CESQ: 50,2,19,2<CR><LF>
+CEREG: 2,"141A","02495602",7<CR><LF>
+CSCON: 1<CR><LF>
[00:00:01.506,072] <ESC>[0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT<ESC>[0m<CR><LF>
[00:00:01.696,533] <ESC>[0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE<ESC>[0m<CR><LF>
+CGEV: ME PDN ACT 0,0<CR><LF>
+CNEC_ESM: 50,0<CR><LF>
%MDMEV: SEARCH STATUS 2<CR><LF>
+CEREG: 5,"141A","02495602",7,,,"11100000","11100000"<CR><LF>
%XTIME: "4A","2221517125634A","00"<CR><LF>
[00:00:03.705,841] <ESC>[1;31m<err> modem_module: Event: PDP context 0, PDN type IPv4 only allowed<ESC>[0m<CR><LF>
[00:00:03.714,141] <ESC>[0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTED<ESC>[0m<CR><LF>
[00:00:03.714,813] <ESC>[0m<inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE<ESC>[0m<CR><LF>
[00:00:03.716,369] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_CONNECTING<ESC>[0m<CR><LF>
[00:00:03.722,259] <ESC>[0m<inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED<ESC>[0m<CR><LF>
[00:00:06.799,407] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_CONFIG_RECEIVED<ESC>[0m<CR><LF>
[00:00:06.807,525] <ESC>[0m<inf> app_event_manager: DATA_EVT_CONFIG_SEND<ESC>[0m<CR><LF>
[00:00:06.808,288] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS<ESC>[0m<CR><LF>
[00:00:09.647,705] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_DISCONNECTED<ESC>[0m<CR><LF>
[00:00:09.648,223] <ESC>[1;31m<err> nrf_cloud_transport: MQTT input error: -128<ESC>[0m<CR><LF>
[00:00:09.648,315] <ESC>[1;31m<err> nrf_cloud_transport: Error disconnecting from cloud: -128<ESC>[0m<CR><LF>
%CESQ: 55,2,23,3<CR><LF>
+CSCON: 0<CR><LF>
%CESQ: 54,2,17,2<CR><LF>
+CSCON: 1<CR><LF>
[00:00:35.716,369] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT<ESC>[0m<CR><LF>
[00:00:35.717,041] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_CONNECTING<ESC>[0m<CR><LF>
%CESQ: 53,2,22,3<CR><LF>
[00:00:38.755,310] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_CONFIG_RECEIVED<ESC>[0m<CR><LF>
[00:00:38.763,305] <ESC>[0m<inf> app_event_manager: DATA_EVT_CONFIG_SEND<ESC>[0m<CR><LF>
[00:00:38.764,068] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS<ESC>[0m<CR><LF>
[00:00:41.601,135] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_DISCONNECTED<ESC>[0m<CR><LF>
[00:00:41.601,654] <ESC>[1;31m<err> nrf_cloud_transport: MQTT input error: -128<ESC>[0m<CR><LF>
[00:00:41.601,745] <ESC>[1;31m<err> nrf_cloud_transport: Error disconnecting from cloud: -128<ESC>[0m<CR><LF>
+CSCON: 0<CR><LF>
%CESQ: 52,2,17,2<CR><LF>
%CESQ: 51,2,22,3<CR><LF>
+CSCON: 1<CR><LF>
[00:01:39.717,041] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT<ESC>[0m<CR><LF>
[00:01:39.717,712] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_CONNECTING<ESC>[0m<CR><LF>
[00:01:42.611,999] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_CONFIG_RECEIVED<ESC>[0m<CR><LF>
[00:01:42.619,995] <ESC>[0m<inf> app_event_manager: DATA_EVT_CONFIG_SEND<ESC>[0m<CR><LF>
[00:01:42.620,758] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS<ESC>[0m<CR><LF>
[00:01:45.467,254] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_DISCONNECTED<ESC>[0m<CR><LF>
[00:01:45.467,773] <ESC>[1;31m<err> nrf_cloud_transport: MQTT input error: -128<ESC>[0m<CR><LF>
[00:01:45.467,895] <ESC>[1;31m<err> nrf_cloud_transport: Error disconnecting from cloud: -128<ESC>[0m<CR><LF>
+CSCON: 0<CR><LF>
%CESQ: 48,2,17,2<CR><LF>
[00:02:01.506,683] <ESC>[0m<inf> app_event_manager: APP_EVT_DATA_GET_ALL<ESC>[0m<CR><LF>
[00:02:01.507,324] <ESC>[0m<inf> app_event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, MOD_STAT, LOCATION)<ESC>[0m<CR><LF>
[00:02:01.507,965] <ESC>[0m<inf> app_event_manager: LOCATION_MODULE_EVT_ACTIVE<ESC>[0m<CR><LF>
[00:02:01.508,819] <ESC>[0m<inf> app_event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED<ESC>[0m<CR><LF>
[00:02:01.529,998] <ESC>[0m<inf> app_event_manager: LOCATION_MODULE_EVT_AGPS_NEEDED<ESC>[0m<CR><LF>
[00:02:01.563,934] <ESC>[0m<inf> app_event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY<ESC>[0m<CR><LF>
[00:02:01.594,024] <ESC>[0m<inf> app_event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY<ESC>[0m<CR><LF>
[00:02:01.623,474] <ESC>[0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_READY<ESC>[0m<CR><LF>

To read the certificates using AT command AT%CMNG=1

2/15/2022 09:55:02.812 [TX] - <CR><LF>

12/15/2022 09:55:02.919 [RX] - %CMNG: 0,6,"0606060606060606060606060606060606060606060606060606060606060606"<CR><LF>
%CMNG: 16842753,0,"A86D8BF8D75130765A6453960E0E4E5158E0F3E43F86699EFE36190C463A25CF"<CR><LF>
%CMNG: 16842753,1,"9A2107CC7A59078994D3039432F18ED541A291180583AF47A883F968BFD9112A"<CR><LF>
%CMNG: 16842753,2,"62F617CF214BFCF2CDAFD7D168F3BC379907A7E8FA8E3A347C9E4215FFFA1742"<CR><LF>
%CMNG: 4294967293,10,"2C43952EE9E000FF2ACC4E2ED0897C0A72AD5FA72C3D934E81741CBD54F05BD1"<CR><LF>
%CMNG: 4294967294,6,"58120DADB439950EA64323883163E0E2D5102ACB10B4C8A0897CDB695982B69D"<CR><LF>
%CMNG: 4294967292,11,"B2C46C2AE7C81943A8BD6DD4ED2A50B659A225A098A177BACB575459CD57CAEF"<CR><LF>

nrf cloud

I also tested the google ping commands. Response is OK

[quote userid="101087" url="~/f/nordic-q-a/93734/nrf9160-custom-board-connectivity-to-nrf-cloud/399590"]e[/quote]

Can you please guide me to where is the issue?

Thanks & Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Thu, 08 Dec 2022 19:05:46 GMT

Hi Charlie

Thank you so much for the help!

Sure I will go through it and update you soon on this my findings after testing on "LTE IoT 4 Click board"

Thanks & regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Charlie — Thu, 08 Dec 2022 12:54:12 GMT

Hi Mhumannad,

Great! Good to hear both SLM and XPING work on your device now.

Next step, let´s provision your custom nRF9160 device with Just-In-Time Provisioning and run the Assert tracker V2 again.

I have a guide about nRF Cloud Access Provisioning including Decision flow for nRF Cloud Provisioning. You basically follow the red line in the flowchart.

Please pay attention that your custom board is not officially supported by Assert Tracker V2, so this application may be not fully functional on your board. but if you build with nRF9160dk_nrf9160_ns, we should at least see the device connect with nRF Cloud if you correctly provision the chip to nRF Cloud correctly. Let me see what you can get.

Best regards,

Charlie

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Thu, 08 Dec 2022 09:21:24 GMT

Hi Charlie!

Thank you so much for the response, i tried nRF9160: Serial LTE modem — nRF Connect SDK 2.1.2 documentation (nordicsemi.com) and it worked

here is the output

12/8/2022 01:15:52.162 [TX] - AT+CFUN=4<CR><LF>

12/8/2022 01:15:53.952 [RX] - <CR><LF>
OK<CR><LF>

12/8/2022 01:16:02.497 [TX] - AT+CFUN?<CR><LF>

12/8/2022 01:16:04.037 [RX] - <CR><LF>
+CFUN: 4<CR><LF>
<CR><LF>
OK<CR><LF>

12/8/2022 01:16:16.858 [TX] - AT%XSYSTEMMODE=1,0,0,0<CR><LF>

12/8/2022 01:16:19.232 [RX] - <CR><LF>
OK<CR><LF>

12/8/2022 01:16:26.622 [TX] - AT+CEREG=5<CR><LF>

12/8/2022 01:16:27.894 [RX] - <CR><LF>
OK<CR><LF>

12/8/2022 01:16:37.656 [TX] - AT+CFUN=1<CR><LF>

12/8/2022 01:16:39.311 [RX] - <CR><LF>
OK<CR><LF>
<CR><LF>
+CEREG: 2,"9003","050C4711",7<CR><LF>
<CR><LF>
+CEREG: 5,"9003","050C4711",7,,,"00001010","11000001"<CR><LF>

12/8/2022 01:16:48.287 [TX] - AT+CFUN?<CR><LF>

12/8/2022 01:16:49.526 [RX] - <CR><LF>
+CFUN: 1<CR><LF>
<CR><LF>
OK<CR><LF>

12/8/2022 01:16:57.935 [TX] - AT#XPING="www.google.com",45,5000,5,1000<CR><LF>

12/8/2022 01:16:59.886 [RX] - <CR><LF>
OK<CR><LF>
#XPING: 0.267 seconds<CR><LF>
#XPING: 0.270 seconds<CR><LF>
#XPING: 0.285 seconds<CR><LF>
#XPING: 0.274 seconds<CR><LF>
#XPING: 0.280 seconds<CR><LF>
#XPING: average 0.275 seconds<CR><LF>

Ping successful

Then what do you suggest where is the issue?

Thanks & Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Charlie — Wed, 07 Dec 2022 12:26:53 GMT

Hi Muhammad,

1) Which SLM you are using? The prebuilt one from nRF9160 DK application and modem firmware or nRF9160: Serial LTE modem — nRF Connect SDK 2.1.2 documentation (nordicsemi.com) built by yourself? Could you try both?

2) Could you wait longer after AT+CUFN=1? The device needs to take some time to connect to the network.

You need to wait until +CEREG comes with 1(registered with home network) or 5(registered with roaming network).

Best regards,

Charlie

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Tue, 06 Dec 2022 12:08:22 GMT

Hi Charlie,

Thank you again for the help!

I tried with SLM but still no response.

So I tried with Asset Tracker here is the response!

12/6/2022 03:55:42.527 [TX] - at<CR><LF>

12/6/2022 03:55:43.399 [RX] - OK<CR><LF>

12/6/2022 03:56:07.015 [TX] - AT+CFUN=4<CR><LF>

12/6/2022 03:56:08.567 [RX] - [00:00:52.586,761] <ESC>[0m<inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: 65534<ESC>[0m<CR><LF>
OK<CR><LF>

12/6/2022 03:56:23.217 [TX] - AT+CFUN?<CR><LF>

12/6/2022 03:56:24.257 [RX] - +CFUN: 4<CR><LF>
OK<CR><LF>

12/6/2022 03:56:33.733 [TX] - AT%XSYSTEMMODE=1,0,0,0<CR><LF>

12/6/2022 03:56:34.539 [RX] - OK<CR><LF>

12/6/2022 03:56:41.843 [TX] - AT+CEREG=5<CR><LF>

12/6/2022 03:56:42.686 [RX] - OK<CR><LF>

12/6/2022 03:56:49.668 [TX] - AT+CFUN=1<CR><LF>

12/6/2022 03:56:50.515 [RX] - OK<CR><LF>

12/6/2022 03:56:57.845 [TX] - AT+CFUN?<CR><LF>

12/6/2022 03:56:58.672 [RX] - +CFUN: 1<CR><LF>
OK<CR><LF>

12/6/2022 03:57:07.657 [TX] - AT#XPING="www.google.com",45,5000,5,1000<CR><LF>

12/6/2022 03:57:09.727 [RX] - [00:01:53.734,619] <ESC>[1;31m<err> at_host: Error while processing AT command: -8<ESC>[0m<CR><LF>
ERROR<CR><LF>

12/6/2022 03:57:21.462 [TX] - AT#XPING="www.google.com",45,5000,5,1000<CR><LF>

12/6/2022 03:57:23.537 [RX] - [00:02:07.544,525] <ESC>[1;31m<err> at_host: Error while processing AT command: -8<ESC>[0m<CR><LF>
ERROR<CR><LF>

Thanks & Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Charlie — Tue, 06 Dec 2022 09:23:04 GMT

Hi Muhammad,

For the SLM communication, can you use Termite with the following configuration to make sure CL+LF is attached at the end of each command?

You will get something like

Let's continue with assert tracker v2 if you get a similar result.

Best regards,

Charlie

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Mon, 05 Dec 2022 18:08:38 GMT

Hi Charlie,

Thank you so much for the support!

Now modem firmware is upgraded to v1.2.8 as suggested by you.

I followed the link for connection between the nrf9160DK and Mikroe(LTE-iot-4 CLick) to upload the modem firmware

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrf91_dk%2FUG%2Fnrf91_DK%2Fhw_debug_out.html

for reference this is also valid

[quote userid="101087" url="~/f/nordic-q-a/93734/nrf9160-custom-board-connectivity-to-nrf-cloud/395927"]

The purpose of testing this board was to debug the issue I faced with my custom board.

My connectivity with the LTE IoT 4 Click board is:

[/quote]

I was making a mistake that I was selecting my target board via FTDI. I should have to upload the modem via DK . Because it was acting as a debugger.

The second issue is, as you suggested to load the SLM and run the AT commands. I did that but got no response from the modem.Means when i press AT and press Enter then get no OK from modem. So I again loaded the asset tracker firmware with updated modem firmware but still faced the same issue. I pasted the log of the asset tracker here.

[00:01:03.560,638] <ESC>[0m<inf> asset_tracker: LTE cell changed: Cell ID: 90084118, Tracking area: 13801<ESC>[0m<CR><LF>
[00:01:03.623,809] <ESC>[0m<inf> asset_tracker: RRC mode: Connected<ESC>[0m<CR><LF>
[00:01:15.484,497] <ESC>[0m<inf> asset_tracker: RRC mode: Idle<ESC>[0m<CR><LF>
[00:01:25.591,613] <ESC>[0m<inf> asset_tracker: RRC mode: Connected<ESC>[0m<CR><LF>
[00:01:29.817,291] <ESC>[0m<inf> asset_tracker: Network registration status: Connected - roaming<ESC>[0m<CR><LF>
[00:01[00:01:29.826,721] <ESC>[0m<inf> asset_tracker: PSM parameter update: TAU: 1152000, Active time: 20<ESC>[0m<CR><LF>
:29.825,958] <ESC>[0m<inf> asset_tracker: Connected to LTE network.<ESC>[0m<CR><LF>
[00:01:29.841,796] <ESC>[0m<inf> asset_tracker: Connecting to cloud, attempt 1 of 8<ESC>[0m<CR><LF>
[00:01:29.849,243] <ESC>[0m<inf> asset_tracker: Cloud connection request sent.<ESC>[0m<CR><LF>
[00:01:29.856,231] <ESC>[0m<inf> asset_tracker: Connection response timeout is set to 30 seconds.<ESC>[0m<CR><LF>
[00:01:29.864,990] <ESC>[0m<inf> asset_tracker: DATE_TIME_OBTAINED_MODEM<ESC>[0m<CR><LF>
[00:01:29.871,429] <ESC>[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1<ESC>[0m<CR><LF>
[00:01:29.879,150] <ESC>[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING<ESC>[0m<CR><LF>
[00:01:29.887,725] <ESC>[0m<inf> asset_tracker: CLOUD_EVT_CONNECTING<ESC>[0m<CR><LF>
[00:01:30.090,209] <ESC>[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 3.224.146.136<ESC>[0m<CR><LF>
[00:01:30.098,510] <ESC>[0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 1<ESC>[0m<CR><LF>
[00:01:30.817,443] <ESC>[0m<inf> asset_tracker: DATE_TIME_OBTAINED_MODEM<ESC>[0m<CR><LF>
[00:01:32.106,231] <ESC>[0m<dbg> nrf_cloud_transport.nct_mqtt_connect: Using socket send timeout of 60 seconds<ESC>[0m<CR><LF>
[00:01:32.116,027] <ESC>[0m<dbg> nrf_cloud.nrf_cloud_run: Cloud connection request sent<ESC>[0m<CR><LF>
[00:01:34.264,678] <ESC>[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_DISCONNECT: result = -128<ESC>[0m<CR><LF>
[00:01:34.274,353] <ESC>[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1<ESC>[0m<CR><LF>
[00:01:34.282,104] <ESC>[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_DISCONNECTED<ESC>[0m<CR><LF>
[00:01:34.290,863] <ESC>[0m<inf> asset_tracker: CLOUD_EVT_DISCONNECTED: 1<ESC>[0m<CR><LF>
[00:01:34.297,424] <ESC>[0m<inf> asset_tracker: Disconnected by the cloud.<ESC>[0m<CR><LF>
[00:01:34.304,077] <ESC>[0m<inf> asset_tracker: This can occur during initial nRF Cloud provisioning.<ESC>[0m<CR><LF>
[00:01:34.313,140] <ESC>[0m<inf> asset_tracker: Attempting reconnect in 10 seconds...<ESC>[0m<CR><LF>
[00:01:34.320,800] <ESC>[1;31m<err> nrf_cloud_transport: MQTT input error: -128<ESC>[0m<CR><LF>
[00:01:34.327,880] <ESC>[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1<ESC>[0m<CR><LF>
[00:01:34.335,632] <ESC>[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_DISCONNECTED<ESC>[0m<CR><LF>
[00:01:34.344,390] <ESC>[0m<inf> asset_tracker: CLOUD_EVT_DISCONNECTED: 1<ESC>[0m<CR><LF>
[00:01:34.350,952] <ESC>[0m<inf> asset_tracker: Disconnected by the cloud.<ESC>[0m<CR><LF>
[00:01:34.357,635] <ESC>[0m<inf> asset_tracker: This can occur if the device has the wrong nRF Cloud certificates<ESC>[0m<CR><LF>
[00:01:34.367,736] <ESC>[0m<inf> asset_tracker: or if the device has been removed from nRF Cloud.<ESC>[0m<CR><LF>
[00:01:34.376,434] <ESC>[0m<inf> asset_tracker: Attempting reconnect in 480 seconds...<ESC>[0m<CR><LF>
[00:01:34.384,155] <ESC>[0m<dbg> nrf_cloud.nrf_cloud_run: The cloud socket is already closed<ESC>[0m<CR><LF>
[00:01:37.677,368] <ESC>[0m<inf> asset_tracker: RRC mode: Idle<ESC>[0m<CR><LF>

Should I run the at commands on asset tracker FW? Will it help you to diagnose the issue?

Thanks & Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Charlie — Mon, 05 Dec 2022 11:59:45 GMT

Hi Muhammad,

I did not play with LTE IoT 4 Click board before, so the easiest way is to check with Time-saving embedded tools - MIKROE support channel directly.

It seems the LTE IoT 4 Click does not have an onboard debugger on it, which is similar to Thingy:91. You can use an external debugger like the onboard debugger on nRF9160DK to program it. Or updating just through UART or USB if its application firmware supports MCUboot. See Update the modem firmware on the nRF9160 SiP for these two methods.

Best regards,

Charlie

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Mon, 05 Dec 2022 04:09:47 GMT

Hi Charlie!

Sorry for the late reply! The issue is that I am unable to update the modem firmware because it is only updated by nrf connect for Desktop ----> programmer .

In start-up of this post, you have mentioned that,

[quote userid="93921" url="~/f/nordic-q-a/93734/nrf9160-custom-board-connectivity-to-nrf-cloud/395071"]2)3) LTE Link Monitor only recognise nRF9160DK or Thingy91, but you can use any other general serial assistant software to access your device. Programmer only supports connecting with J-Link debugger, nRF9160DK has one onboard debugger so it is supported, Thingy91 has no onboard debugger so it is not supported. Your Serial to USB converter only supports serial connection, it is not a debugger which can be used to program the nRF9160.[/quote]

Can you please help me that how to load the modem firmware in the custom board/ LTE-iot-4 click board?

Thanks & Regards,

RE: nrf9160 Custom Board connectivity to nrf cloud

Charlie — Wed, 23 Nov 2022 10:24:38 GMT

Hi Muhammad,

The log shows the modem does not work properly. Did you update the modem firmware to MFW v1.2.8?

Can you test with the following commands after programming SLM and sharing the log file? remember to enable SETTINGS->Automatic requests on LTE Link Monitor.

AT+CFUN=4
AT+CFUN?
AT%XSYSTEMMODE=1,0,0,0
AT+CEREG=5
AT+CFUN=1
AT+CFUN?
AT#XPING="www.google.com",45,5000,5,1000

Best regards,

Charlie

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Tue, 22 Nov 2022 19:39:01 GMT

Hi Charlie!

Thank you for the response, i tried using the following.

CONFIG_NRF_CLOUD_SEC_TAG=16842753
CONFIG_CLOUD_CLIENT_ID_USE_CUSTOM=y

But when I enter the

CONFIG_CLOUD_CLIENT_ID="Device_ID"

it gives me a compilation error.

This is also defined in the .config file. So I entered there.

CONFIG_CLOUD_CLIENT_ID="client_id" and compiled successfully.

I got the log as follows:

[00:00:00.457,275] <ESC>[0m<inf> app_event_manager: APP_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:00.457,458] <ESC>[1;33m<wrn> modules_common: Module "app" shutdown registered<ESC>[0m<CR><LF>
[00:00:00.458,251] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:00.458,618] <ESC>[1;33m<wrn> modules_common: Module "cloud" shutdown registered<ESC>[0m<CR><LF>
[00:00:00.458,984] <ESC>[0m<inf> app_event_manager: SENSOR_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:00.459,106] <ESC>[1;33m<wrn> modules_common: Module "sensor" shutdown registered<ESC>[0m<CR><LF>
[00:00:00.621,765] <ESC>[0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING<ESC>[0m<CR><LF>
[00:00:01.451,477] <ESC>[0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT<ESC>[0m<CR><LF>
[00:00:01.452,117] <ESC>[0m<inf> app_event_manager: DATA_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:01.452,209] <ESC>[1;33m<wrn> modules_common: Module "data" shutdown registered<ESC>[0m<CR><LF>
[00:00:01.567,810] <ESC>[0m<inf> app_event_manager: MODEM_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:01.568,145] <ESC>[1;33m<wrn> modules_common: Module "modem" shutdown registered<ESC>[0m<CR><LF>
[00:00:01.568,176] <ESC>[1;33m<wrn> util_module: All modules have ACKed the reboot request.<ESC>[0m<CR><LF>
[00:00:01.568,176] <ESC>[1;33m<wrn> util_module: Reboot in 5 seconds.<ESC>[0m<CR><LF>
[00:00:06.568,298] <ESC>[1;31m<err> util_module: Rebooting!<ESC>[0m<CR>
<NUL>*** Booting Zephyr OS build v3.0.99-ncs1-1  ***<CR><LF>
Attempting to boot slot 0.<CR>
<CR><LF>
Attempting to boot from address 0x8200.<CR><LF>
<CR>
Verifying signature against key 0.<CR><LF>
<CR>
Hash: 0x42...ba<CR>
<CR><LF>
Firmware signature verified.<CR><LF>
<CR>
Firmware version 1<CR>
<CR><LF>
Booting (0x8200).<CR>
<CR>
*** Booting Zephyr OS build v3.0.99-ncs1-1  ***<CR><LF>
I: Starting bootloader<CR><LF>
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Boot source: none<CR><LF>
I: Swap type: none<CR><LF>
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3<CR><LF>
I: Boot source: none<CR><LF>
I: Swap type: none<CR><LF>
I: Bootloader chainload address offset: 0x28000<CR><LF>
I: Jumping to the first image slot<CR>
*** Booting Zephyr OS build v3.0.99-ncs1-1  ***<CR><LF>
[00:00:00.450,317] <ESC>[0m<inf> app_event_manager: APP_EVT_START<ESC>[0m<CR><LF>
[00:00:00.451,477] <ESC>[0m<inf> app_event_manager: MODEM_EVT_INITIALIZED<ESC>[0m<CR><LF>
[00:00:00.454,925] <ESC>[1;31m<err> modem_module: lte_lc_modem_events_enable failed, error: -14<ESC>[0m<CR><LF>
[00:00:00.454,956] <ESC>[1;31m<err> modem_module: Failed setting up the modem, error: -14<ESC>[0m<CR><LF>
[00:00:00.455,017] <ESC>[0m<inf> app_event_manager: MODEM_EVT_ERROR - Error code -14<ESC>[0m<CR><LF>
[00:00:00.455,688] <ESC>[0m<inf> app_event_manager: UTIL_EVT_SHUTDOWN_REQUEST<ESC>[0m<CR><LF>
[00:00:00.456,268] <ESC>[0m<inf> app_event_manager: UI_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:00.456,420] <ESC>[1;33m<wrn> modules_common: Module "ui" shutdown registered<ESC>[0m<CR><LF>
[00:00:00.456,542] <ESC>[0m<inf> app_event_manager: GNSS_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:00.456,756] <ESC>[1;33m<wrn> modules_common: Module "gnss" shutdown registered<ESC>[0m<CR><LF>
[00:00:00.457,336] <ESC>[0m<inf> app_event_manager: APP_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:00.457,519] <ESC>[1;33m<wrn> modules_common: Module "app" shutdown registered<ESC>[0m<CR><LF>
[00:00:00.458,312] <ESC>[0m<inf> app_event_manager: CLOUD_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:00.458,679] <ESC>[1;33m<wrn> modules_common: Module "cloud" shutdown registered<ESC>[0m<CR><LF>
[00:00:00.459,045] <ESC>[0m<inf> app_event_manager: SENSOR_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:00.459,197] <ESC>[1;33m<wrn> modules_common: Module "sensor" shutdown registered<ESC>[0m<CR><LF>
[00:00:00.621,795] <ESC>[0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING<ESC>[0m<CR><LF>
[00:00:01.451,538] <ESC>[0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT<ESC>[0m<CR><LF>
[00:00:01.452,178] <ESC>[0m<inf> app_event_manager: DATA_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:01.452,270] <ESC>[1;33m<wrn> modules_common: Module "data" shutdown registered<ESC>[0m<CR><LF>
[00:00:01.567,749] <ESC>[0m<inf> app_event_manager: MODEM_EVT_SHUTDOWN_READY<ESC>[0m<CR><LF>
[00:00:01.568,084] <ESC>[1;33m<wrn> modules_common: Module "modem" shutdown registered<ESC>[0m<CR><LF>
[00:00:01.568,115] <ESC>[1;33m<wrn> util_module: All modules have ACKed the reboot request.<ESC>[0m<CR><LF>
[00:00:01.568,115] <ESC>[1;33m<wrn> util_module: Reboot in 5 seconds.<ESC>[0m<CR><LF>

I also added the certificates in asset_tracker_v2 ---> src----> cloud-certs.Same certificates which I downloaded into the IoT 4 Click via LTE-Link monitor

One example of the Ca-cert is

#define NRF_CLOUD_CA_CERTIFICATE \
	"-----BEGIN CERTIFICATE-----\nMIIDQTCCAimgAwIBAgITBmyfz5m/jAo54vB4ikPmljZbyjANBgkqhkiG9w0BAQsF\nADA5MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRkwFwYDVQQDExBBbWF6\nb24gUm9vdCBDQSAxMB4XDTE1MDUyNjAwMDAwMFoXDTM4MDExNzAwMDAwMFowOTEL\nMAkGA1UEBhMCVVMxDzANBgNVBAoTBkFtYXpvbjEZMBcGA1UEAxMQQW1hem9uIFJv\nb3QgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALJ4gHHKeNXj\nca9HgFB0fW7Y14h29Jlo91ghYPl0hAEvrAIthtOgQ3pOsqTQNroBvo3bSMgHFzZM\n9O6II8c+6zf1tRn4SWiw3te5djgdYZ6k/oI2peVKVuRF4fn9tBb6dNqcmzU5L/qw\nIFAGbHrQgLKm+a/sRxmPUDgH3KKHOVj4utWp+UhnMJbulHheb4mjUcAwhmahRWa6\nVOujw5H5SNz/0egwLX0tdHA114gk957EWW67c4cX8jJGKLhD+rcdqsq08p8kDi1L\n93FcXmn/6pUCyziKrlA4b9v7LWIbxcceVOF34GfID5yHI9Y/QCB/IIDEgEw+OyQm\njgSubJrIqg0CAwEAAaNCMEAwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMC\nAYYwHQYDVR0OBBYEFIQYzIU07LwMlJQuCFmcx7IQTgoIMA0GCSqGSIb3DQEBCwUA\nA4IBAQCY8jdaQZChGsV2USggNiMOruYou6r4lK5IpDB/G/wkjUu0yKGX9rbxenDI\nU5PMCCjjmCXPI6T53iHTfIUJrU6adTrCC2qJeHZERxhlbI1Bjjt/msv0tadQ1wUs\nN+gDS63pYaACbvXy8MWy7Vu33PqUXHeeE6V/Uq2V8viTO96LXFvKWlJbYK8U90vv\no/ufQJVtMVT8QtPHRh8jrdkPSHCa2XV4cdFyQzR1bldZwgJcJmApzyMZFo6IQ6XU\n5MsI+yMRQ+hDKXJioaldXgjUkK642M4UwtBV8ob2xJNDd2ZhwLnoQdeXeGADbkpy\nrqXRfboQnoZsG4q5WTP468SQvvG5\n-----END CERTIFICATE-----\n"

is that ok ? or i am doing something wrong?

Thanks in advance

RE: nrf9160 Custom Board connectivity to nrf cloud

Charlie — Tue, 22 Nov 2022 14:59:46 GMT

Hi Muhammad,

As long as you can program application firmware to LTE IoT 4 Click with nRF9160DK, it should be the same for Modem Firmware update on your custom board as nRF9160DK

Best regards,

Charlie

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Tue, 22 Nov 2022 13:26:41 GMT

Hi Charlie!

Thank you so much for the reply and guidance.

Can you please tell me how to update the modem firmware in LTE IoT 4 Click /Custom Board ? In DK I can upload the modem firmware because in the programmer software option to write is enabled . But for LTE IoT 4 Click /Custom Board is not enabled and I can't connect it . Only the LTE link monitor is accessible to LTE IoT 4 Click /Custom Board.

Thanks in advance!

BR
Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Charlie — Tue, 22 Nov 2022 12:02:10 GMT

Hi Muhammad,

Sorry for the late reply, I attended electronica last week.

Thanks for the update, looks like you have made some progress.

1) You are using the JITP provision for your custom nRF9160 device LTE IoT 4 Click, so additional Assert Tracker V2 prj.conf configurations should be used:

CONFIG_NRF_CLOUD_SEC_TAG=<sec_tag>
CONFIG_CLOUD_CLIENT_ID_USE_CUSTOM=y
CONFIG_CLOUD_CLIENT_ID=<deviceId>

The Assert Tracker V2 should be able to connect with nRF Cloud, but may not be fully functional, because it is designed for nRF9160DK and Thingy91.

2) MFW update

We currently have two nRF9160 SIP versions, the LTE IoT 4 Click on you hand looks like using old B0(nRF9160 SiP Revision 1), which only supports MFW1.2.x.

You can download the latest MFW1.2.8 from nRF9160 SiP modem firmware and follow Updating the modem firmware with the current connection.

Best regards,

Charlie

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Thu, 17 Nov 2022 19:08:59 GMT

Hi Charlie,

Some more progress! I want to share it with you. Can you please help me onward?

I am using asset_tracker example V1.8.0, it's working fine with nrf9160DK as discussed before and I am able to see the data on nrf cloud.

1)In the Previous post I am having a sim connectivity issue so I used the LTE IoT 4 Click board as discussed before and the reasons for using it.

2)Now sim is detecting

3)Last time device was not added in nrf-cloud but now the device added successfully

4)But no data, for that I attached the log

Peripheral<HT>	<HT>	Domain<HT>	<HT>	Status<CR><LF>
00 NRF_P0               Non-Secure<HT>	OK<CR><LF>
01 NRF_CLOCK            Non-Secure<HT>	OK<CR><LF>
02 NRF_RTC0             Non-Secure<HT>	OK<CR><LF>
03 NRF_RTC1             Non-Secure<HT>	OK<CR><LF>
04 NRF_NVMC             Non-Secure<HT>	OK<CR><LF>
05 NRF_UARTE1           Non-Secure<HT>	OK<CR><LF>
06 NRF_UARTE2           Secure<HT>	<HT>	SKIP<CR><LF>
07 NRF_TWIM2            Non-Secure<HT>	OK<CR><LF>
08 NRF_SPIM3            Non-Secure<HT>	OK<CR><LF>
09 NRF_TIMER0           Non-Secure<HT>	OK<CR><LF>
10 NRF_TIMER1           Non-Secure<HT>	OK<CR><LF>
11 NRF_TIMER2           Non-Secure<HT>	OK<CR><LF>
12 NRF_SAADC            Non-Secure<HT>	OK<CR><LF>
13 NRF_PWM0             Non-Secure<HT>	OK<CR><LF>
14 NRF_PWM1             Non-Secure<HT>	OK<CR><LF>
15 NRF_PWM2             Non-Secure<HT>	OK<CR><LF>
16 NRF_PWM3             Non-Secure<HT>	OK<CR><LF>
17 NRF_WDT              Non-Secure<HT>	OK<CR><LF>
18 NRF_IPC              Non-Secure<HT>	OK<CR><LF>
19 NRF_VMC              Non-Secure<HT>	OK<CR><LF>
20 NRF_FPU              Non-Secure<HT>	OK<CR><LF>
21 NRF_EGU0             Non-Secure<HT>	OK<CR><LF>
22 NRF_EGU1             Non-Secure<HT>	OK<CR><LF>
23 NRF_EGU2             Non-Secure<HT>	OK<CR><LF>
24 NRF_EGU3             Non-Secure<HT>	OK<CR><LF>
25 NRF_EGU4             Non-Secure<HT>	OK<CR><LF>
26 NRF_EGU5             Non-Secure<HT>	OK<CR><LF>
27 NRF_DPPIC            Non-Secure<HT>	OK<CR><LF>
28 NRF_REGULATORS       Non-Secure<HT>	OK<CR><LF>
29 NRF_PDM              Non-Secure<HT>	OK<CR><LF>
30 NRF_I2S              Non-Secure<HT>	OK<CR><LF>
31 NRF_GPIOTE1          Non-Secure<HT>	OK<CR><LF>
<CR><LF>
SPM: NS image at 0x20200<CR><LF>
SPM: NS MSP at 0x20021b38<CR><LF>
SPM: NS reset vector at 0x2b6dd<CR><LF>
SPM: prepare to jump to Non-Secure image.<CR><LF>
*** Booting Zephyr OS build v2.7.0-ncs1  ***<CR><LF>
[00:00:00.206,420] <ESC>[1;33m<wrn> at_notif: Already initialized. Nothing to do<ESC>[0m<CR><LF>
[00:00:00.213,714] <ESC>[0m<inf> asset_tracker: Asset tracker started<ESC>[0m<CR><LF>
[00:00:00.219,940] <ESC>[0m<inf> watchdog: Watchdog timeout installed. Timeout: 60000<ESC>[0m<CR><LF>
[00:00:00.227,569] <ESC>[0m<inf> watchdog: Watchdog started<ESC>[0m<CR><LF>
[00:00:00.240,295] <ESC>[0m<dbg> nrf_cloud_transport.nct_client_id_set: client_id = nrf-351358814108376<ESC>[0m<CR><LF>
[00:00:00.249,816] <ESC>[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-351358814108376/shadow/get/accepted<ESC>[0m<CR><LF>
[00:00:00.261,260] <ESC>[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-351358814108376/shadow/get/rejected<ESC>[0m<CR><LF>
[00:00:00.273,834] <ESC>[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-351358814108376/shadow/update/delta<ESC>[0m<CR><LF>
[00:00:00.286,743] <ESC>[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-351358814108376/shadow/update<ESC>[0m<CR><LF>
[00:00:00.298,645] <ESC>[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-351358814108376/shadow/get<ESC>[0m<CR><LF>
[00:00:00.310,607] <ESC>[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1<ESC>[0m<CR><LF>
[00:00:00.318,420] <ESC>[0m<inf> asset_tracker: Connecting to LTE network.<ESC>[0m<CR><LF>
[00:00:00.325,042] <ESC>[0m<inf> asset_tracker: This may take several minutes.<ESC>[0m<CR><LF>
[00:00:02.033,294] <ESC>[0m<inf> asset_tracker: LTE cell changed: Cell ID: 84690705, Tracking area: 36867<ESC>[0m<CR><LF>
[00:00:02.149,444] <ESC>[0m<inf> asset_tracker: RRC mode: Connected<ESC>[0m<CR><LF>
[00:00:03.584,320] <ESC>[0m<inf> asset_tracker: Network registration status: Connected - roaming<ESC>[0m<CR><LF>
[00:00:0[00:00:03.593,902] <ESC>[0m<inf> asset_tracker: PSM parameter update: TAU: -1, Active time: -1<ESC>[0m<CR><LF>
3.593,017] <ESC>[0m<inf> asset_tracker: Connected to LTE network.<ESC>[0m<CR><LF>
[00:00:03.608,428] <ESC>[0m<inf> asset_tracker: Connecting to cloud, attempt 1 of 8<ESC>[0m<CR><LF>
[00:00:03.615,844] <ESC>[0m<inf> asset_tracker: Cloud connection request sent.<ESC>[0m<CR><LF>
[00:00:03.622,833] <ESC>[0m<inf> asset_tracker: Connection response timeout is set to 30 seconds.<ESC>[0m<CR><LF>
[00:00:03.631,591] <ESC>[0m<inf> asset_tracker: DATE_TIME_OBTAINED_MODEM<ESC>[0m<CR><LF>
[00:00:03.638,061] <ESC>[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1<ESC>[0m<CR><LF>
[00:00:03.645,751] <ESC>[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING<ESC>[0m<CR><LF>
[00:00:03.654,357] <ESC>[0m<inf> asset_tracker: CLOUD_EVT_CONNECTING<ESC>[0m<CR><LF>
[00:00:03.888,732] <ESC>[0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 54.237.207.157<ESC>[0m<CR><LF>
[00:00:03.897,125] <ESC>[0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 1<ESC>[0m<CR><LF>
[00:00:04.584,472] <ESC>[0m<inf> asset_tracker: DATE_TIME_OBTAINED_MODEM<ESC>[0m<CR><LF>
[00:00:05.905,975] <ESC>[0m<dbg> nrf_cloud_transport.nct_mqtt_connect: Using socket send timeout of 60 seconds<ESC>[0m<CR><LF>
[00:00:05.915,771] <ESC>[0m<dbg> nrf_cloud.nrf_cloud_run: Cloud connection request sent<ESC>[0m<CR><LF>
[00:00:08.097,106] <ESC>[0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_DISCONNECT: result = -128<ESC>[0m<CR><LF>
[00:00:08.106,781] <ESC>[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1<ESC>[0m<CR><LF>
[00:00:08.114,501] <ESC>[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_DISCONNECTED<ESC>[0m<CR><LF>
[00:00:08.123,260] <ESC>[0m<inf> asset_tracker: CLOUD_EVT_DISCONNECTED: 1<ESC>[0m<CR><LF>
[00:00:08.129,852] <ESC>[0m<inf> asset_tracker: Disconnected by the cloud.<ESC>[0m<CR><LF>
[00:00:08.136,535] <ESC>[0m<inf> asset_tracker: This can occur during initial nRF Cloud provisioning.<ESC>[0m<CR><LF>
[00:00:08.145,568] <ESC>[0m<inf> asset_tracker: Attempting reconnect in 10 seconds...<ESC>[0m<CR><LF>
[00:00:08.153,228] <ESC>[1;31m<err> nrf_cloud_transport: MQTT input error: -128<ESC>[0m<CR><LF>
[00:00:08.160,308] <ESC>[0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1<ESC>[0m<CR><LF>
[00:00:08.168,029] <ESC>[0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_DISCONNECTED<ESC>[0m<CR><LF>
[00:00:08.176,788] <ESC>[0m<inf> asset_tracker: CLOUD_EVT_DISCONNECTED: 1<ESC>[0m<CR><LF>
[00:00:08.183,380] <ESC>[0m<inf> asset_tracker: Disconnected by the cloud.<ESC>[0m<CR><LF>
[00:00:08.190,063] <ESC>[0m<inf> asset_tracker: This can occur if the device has the wrong nRF Cloud certificates<ESC>[0m<CR><LF>
[00:00:08.200,134] <ESC>[0m<inf> asset_tracker: or if the device has been removed from nRF Cloud.<ESC>[0m<CR><LF>
[00:00:08.208,831] <ESC>[0m<inf> asset_tracker: Attempting reconnect in 480 seconds...<ESC>[0m<CR><LF>
[00:00:08.216,583] <ESC>[0m<dbg> nrf_cloud.nrf_cloud_run: The cloud socket is already closed<ESC>[0m<CR><LF>
[00:00:13.533,843] <ESC>[0m<inf> asset_tracker: RRC mode: Idle<ESC>[0m<CR><LF>

from above log two reasons for not connecting

a)Wrong certificate

b)No device added to nrf cloud

5)For certificate addition I have followed the following procedure

a) Followed the following link to add the certificate to the LTE IoT 4 click Mikroe board

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_thingy91%2FUG%2Fthingy91%2Fupdating_certificates%2Fprovisioning_certificate.html

b)Certificates added successfully as you can see on LTE Link Monitor

to verify it I ran the command AT%CMNG=1 and got the following response

0,6,"0606060606060606060606060606060606060606060606060606060606060606"
%CMNG: 16842753,0,"0000000000000000000000000000000000000000000000000000000000000000"
%CMNG: 16842753,1,"0101010101010101010101010101010101010101010101010101010101010101"
%CMNG: 16842753,2,"0202020202020202020202020202020202020202020202020202020202020202"

is that OK ?

c)Next step was to add the certificates to the asset tracker firmware. For that I did ..

added the certificates and my client ID to certificates.h (in the asset tracker sample) and added CONFIG_NRF_CLOUD_PROVISION_CERTIFICATES=y to prj.conf

6)Modem FW version is 1.1.0, if need to update it then can you help me with how to update it? In Nrf DK we can load it via the programmer.

Thanks & Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Wed, 16 Nov 2022 09:43:15 GMT

Hi Charlie!

I started testing with the following board meanwhile I get a response from the nordic team regarding my schematic.

https://www.mikroe.com/lte-iot-4-click

The purpose of testing this board was to debug the issue I faced with my custom board.

My connectivity with the LTE IoT 4 Click board is:

This time the serial output I got is different from the custom board (unable to detect the SIM) . Now by using this board able to detect the SIM and then connect to the LTE network but in the end, the issue is when connecting to nrf cloud. You can see this from the serial output.

I got the IMEI number from AT+CGSN

I pasted in place of DEVICE ID with nrf- and as well as without.In place of HW ID/PIN, i entered 654321 or random numbers.

But got the same error as discussed before. Can you please help me in this regard?

Thanks & Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Fri, 11 Nov 2022 11:44:12 GMT

Hi Charlie!

Thank you so much for the support! Yes, I have nrf9160DK and sure I will test with that if find any issue i will ask again.

Thanks & Regards,

Muhammad Usman

RE: nrf9160 Custom Board connectivity to nrf cloud

Charlie — Fri, 11 Nov 2022 09:51:05 GMT

Hi Muhammad,

Good to hear, my colleague will have a look at your schematic design.

For the device provisioning, If you have an nRF9160DK or Thingy91 on hand, you can still follow https://docs.nrfcloud.com/Devices/Associations/Provisioning/#just-in-time-provisioning and it is the same as for your custom nRF91 device. You are free to choose deviceId and ownershipCode by yourself during the provisioning process.

Best regards,

Charlie

RE: nrf9160 Custom Board connectivity to nrf cloud

Muhammad Usman — Thu, 10 Nov 2022 16:37:19 GMT

Hi Charlie,

Thank you so much for the response! Yes, I have created a new ticket for the HW.

I will give feedback when I am able to enable the sim card with the help of the nordic support team. After that, I can test the nrf cloud part for adding the LTE device.

Thanks & Regards,

Muhammad Usman