Asset Tracker V2, connecting problem to AWS Iot

[Minyaev]

Hello,

I am trying to connect asset_tracker_v2 to my aws iot cloud with MQTT,

then storing this data in aws database, when i changing parameters to AWS Iot library,

i have a fatal error, i am not understanding why ?

• I am workin whit nRF9160, thingy:91 and nRF9160_DK
• I use nRF Connect SDK V1.8.0 whit SEGGER embedded Studio
• I have an alredy existing AWS account
• I have downloaded certificate successfully to µc

That is my configuration:

And that is my log output when building and running:

2021-12-26T14:20:10.118Z INFO Application data folder: C:\Users\Portable\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-12-26T14:20:10.209Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2021-12-26T14:20:10.209Z DEBUG App path: C:\Users\Portable\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-12-26T14:20:10.209Z DEBUG nRFConnect 3.9.1, required by the app is (^3.8.0)
2021-12-26T14:20:10.209Z DEBUG nRFConnect path: C:\Users\Portable\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-12-26T14:20:10.209Z DEBUG HomeDir: C:\Users\Portable
2021-12-26T14:20:10.209Z DEBUG TmpDir: C:\Users\Portable\AppData\Local\Temp
2021-12-26T14:20:13.457Z INFO Modem port is opened
2021-12-26T14:20:13.471Z DEBUG modem >> AT+CFUN?
2021-12-26T14:20:29.013Z ERROR Opening COM8: Access denied
2021-12-26T14:20:32.530Z INFO Modem port is closed
2021-12-26T14:20:40.120Z INFO Modem port is opened
2021-12-26T14:20:40.128Z DEBUG modem >> AT+CFUN?
2021-12-26T14:20:41.311Z DEBUG modem << *** Booting Zephyr OS build v2.7.0-ncs1  ***
2021-12-26T14:20:41.340Z DEBUG modem << [00:00:00.223,297] [1;33m<wrn> at_notif: Already initialized. Nothing to do[0m
2021-12-26T14:20:41.342Z DEBUG modem << [00:00:00.230,377] [0m<inf> at_host: UART check failed: 13. Dropping buffer and retrying.[0m
2021-12-26T14:20:41.396Z DEBUG modem << [00:00:00.260,162] [0m<inf> event_manager: APP_EVT_START[0m
2021-12-26T14:20:41.398Z DEBUG modem << [00:00:00.281,066] [0m<inf> event_manager: DATA_EVT_CONFIG_INIT[0m
2021-12-26T14:20:41.400Z DEBUG modem << [00:00:00.287,597] [0m<inf> event_manager: APP_EVT_ACTIVITY_DETECTION_DISABLE[0m
2021-12-26T14:20:41.402Z DEBUG modem << [00:00:00.295,410] [0m<inf> event_manager: MODEM_EVT_INITIALIZED[0m
2021-12-26T14:20:41.541Z DEBUG modem << [00:00:00.310,821] [1;31m<err> aws_iot: Application subscription list count mismatch[0m
2021-12-26T14:20:41.544Z DEBUG modem << [00:00:00.318,634] [1;31m<err> aws_iot_integration: cloud_ep_subscriptions_add, error: -122[0m
2021-12-26T14:20:41.549Z DEBUG modem << [00:00:00.327,087] [1;31m<err> aws_iot_integration: populate_app_endpoint_topics, error: -122[0m
2021-12-26T14:20:41.554Z DEBUG modem << [00:00:00.335,754] [1;31m<err> cloud_module: cloud_wrap_init, error: -122[0m
2021-12-26T14:20:41.559Z DEBUG modem << ASSERTION FAIL [err == 0] @ ../src/modules/cloud_module.c:698
2021-12-26T14:20:41.564Z DEBUG modem << setp() failed
2021-12-26T14:20:41.569Z DEBUG modem << [00:00:00.349,487] [1;31m<err> os: r0/a1:  0x00000004  r1/a2:  0x000002ba  r2/a3:  0x00000001[0m
2021-12-26T14:20:41.574Z DEBUG modem << [00:00:00.358,123] [1;31m<err> os: r3/a4:  0x00026c11 r12/ip:  0x0000a000 r14/lr:  0x0001ca7d[0m
2021-12-26T14:20:41.579Z DEBUG modem << [00:00:00.366,760] [1;31m<err> os:  xpsr:  0x41000000[0m
2021-12-26T14:20:41.592Z DEBUG modem << [00:00:00.371,978] [1;31m<err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000[0m
2021-12-26T14:20:41.597Z DEBUG modem << [00:00:00.382,354] [1;31m<err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000[0m
2021-12-26T14:20:41.602Z DEBUG modem << [00:00:00.392,730] [1;31m<err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000002[0m
2021-12-26T14:20:41.605Z DEBUG modem << [00:00:00.403,106] [1;31m<err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000[0m
2021-12-26T14:20:41.607Z DEBUG modem << [00:00:00.413,452] [1;31m<err> os: fpscr:  0x3e2887a6[0m
2021-12-26T14:20:41.609Z DEBUG modem << [00:00:00.418,640] [1;31m<err> os: Faulting instruction address (r15/pc): 0x0003b4d8[0m
2021-12-26T14:20:41.611Z DEBUG modem << [00:00:00.426,513] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0[0m
2021-12-26T14:20:41.613Z DEBUG modem << [00:00:00.434,204] [1;31m<err> os: Current thread: 0x200151c8 (unknown)[0m

That is also my project:

asset_tracker_v2.rar

Thank you for your help

Minyaev

[Didrik Rokhaug]

Hi,

The assertion fail happens because you have told the application in the configuration options that you will not subscribe to any topics, while in the application you try to subscribe to some.

The reason for this mismatch is probably that you didn't include the AWS Kconfig overlay file. See this part of the Asset tracker V2 documentation: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker_v2/doc/asset_tracker_v2_description.html#building-with-overlays 

The overlay file you want to add is called 'overlay-aws.conf'.

Best regards,

Didrik

[Minyaev]

Hi,

Yes it was done, but nothing has changed,

That is my overlay file:

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

CONFIG_AWS_IOT=y
CONFIG_AWS_IOT_TOPIC_UPDATE_DELTA_SUBSCRIBE=y
CONFIG_AWS_IOT_TOPIC_GET_REJECTED_SUBSCRIBE=y
CONFIG_AWS_IOT_AUTO_DEVICE_SHADOW_REQUEST=y
CONFIG_AWS_IOT_MQTT_RX_TX_BUFFER_LEN=2048
CONFIG_AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT=3
CONFIG_AWS_IOT_CLIENT_ID_APP=y
CONFIG_AWS_FOTA=y

# Options that must be configured in order to establish a connection.
CONFIG_AWS_IOT_SEC_TAG=42
CONFIG_AWS_IOT_BROKER_HOST_NAME="a1t6ipfx1jqfnp-ats.iot.us-west-2.amazonaws.com"

# MQTT Transport library
# Maximum specified MQTT keepalive timeout for AWS IoT is 1200 seconds.
CONFIG_MQTT_KEEPALIVE=1200

And that is my include configuration:

Thank

Minyaev

[Didrik Rokhaug]

It's not enough to just provide the path of the overlay configuration file, you must provide the whole command line argument:

-DOVERLAY_CONFIG=overlay-aws.conf

Edit: I originally wrote -D_OVERLAY_CONFIG. That is wrong. It should be -DOVERLAY_CONFIG.

[Minyaev]

The configuration Work, i have no errors like this:

I make like you suggested me:

But the problem is : no data in my AWS account, i verify it in "activity":

i have no traces that asset_tracker_V2 is trying to connect in my AWS account with MQTT :

2021-12-27T14:23:40.968Z INFO Application data folder: C:\Users\Portable\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-12-27T14:23:41.113Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2021-12-27T14:23:41.114Z DEBUG App path: C:\Users\Portable\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-12-27T14:23:41.114Z DEBUG nRFConnect 3.9.1, required by the app is (^3.8.0)
2021-12-27T14:23:41.114Z DEBUG nRFConnect path: C:\Users\Portable\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-12-27T14:23:41.114Z DEBUG HomeDir: C:\Users\Portable
2021-12-27T14:23:41.114Z DEBUG TmpDir: C:\Users\Portable\AppData\Local\Temp
2021-12-27T14:23:43.409Z INFO Modem port is opened
2021-12-27T14:23:43.424Z DEBUG modem >> AT+CFUN?
2021-12-27T14:23:43.441Z DEBUG modem << +CFUN: 1
2021-12-27T14:23:43.444Z DEBUG modem << 
2021-12-27T14:23:43.447Z DEBUG modem << OK
2021-12-27T14:23:43.468Z DEBUG modem >> AT+CGSN=1
2021-12-27T14:23:43.485Z DEBUG modem << +CGSN: "352656109828478"
2021-12-27T14:23:43.487Z DEBUG modem << OK
2021-12-27T14:23:43.493Z DEBUG modem >> AT+CGMI
2021-12-27T14:23:43.509Z DEBUG modem << Nordic Semiconductor ASA
2021-12-27T14:23:43.519Z DEBUG modem << 
2021-12-27T14:23:43.521Z DEBUG modem << OK
2021-12-27T14:23:43.525Z DEBUG modem >> AT+CGMM
2021-12-27T14:23:43.533Z DEBUG modem << nRF9160-SICA
2021-12-27T14:23:43.535Z DEBUG modem << OK
2021-12-27T14:23:43.538Z DEBUG modem >> AT+CGMR
2021-12-27T14:23:43.544Z DEBUG modem << mfw_nrf9160_1.3.1
2021-12-27T14:23:43.548Z DEBUG modem << OK
2021-12-27T14:23:43.550Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.1] SerNr: 352656109828478
2021-12-27T14:23:43.555Z DEBUG modem >> AT+CEMODE?
2021-12-27T14:23:43.560Z DEBUG modem << +CEMODE: 2
2021-12-27T14:23:43.569Z DEBUG modem << OK
2021-12-27T14:23:43.585Z DEBUG modem >> AT%XCBAND=?
2021-12-27T14:23:43.604Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2021-12-27T14:23:43.606Z DEBUG modem << OK
2021-12-27T14:23:43.621Z DEBUG modem >> AT+CMEE?
2021-12-27T14:23:43.636Z DEBUG modem << +CMEE: 0
2021-12-27T14:23:43.639Z DEBUG modem << OK
2021-12-27T14:23:43.644Z DEBUG modem >> AT+CMEE=1
2021-12-27T14:23:43.658Z DEBUG modem << OK
2021-12-27T14:23:43.671Z DEBUG modem >> AT+CNEC?
2021-12-27T14:23:43.677Z DEBUG modem << +CNEC: 0
2021-12-27T14:23:43.685Z DEBUG modem << OK
2021-12-27T14:23:43.693Z DEBUG modem >> AT+CNEC=24
2021-12-27T14:23:43.704Z DEBUG modem << OK
2021-12-27T14:23:43.708Z DEBUG modem >> AT+CGEREP?
2021-12-27T14:23:43.719Z DEBUG modem << +CGEREP: 0,0
2021-12-27T14:23:43.722Z DEBUG modem << OK
2021-12-27T14:23:43.725Z DEBUG modem >> AT+CGDCONT?
2021-12-27T14:23:43.735Z DEBUG modem << %C[00:00:01.473,632] [0m<inf> event_manager: MODEM_EVT_LTE_DISCONNECTED[0m
2021-12-27T14:23:43.737Z DEBUG modem << [00:00:01.480,926] [0m<inf> event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2021-12-27T14:23:43.740Z DEBUG modem << ESQ: 43,2,18,2
2021-12-27T14:23:43.742Z DEBUG modem << +CGDCONT: 0,"","","",0,0
2021-12-27T14:23:43.744Z DEBUG modem << OK
2021-12-27T14:23:44.105Z DEBUG modem >> AT+CGACT?
2021-12-27T14:23:44.115Z DEBUG modem << +CGACT: 0,0
2021-12-27T14:23:44.117Z DEBUG modem << OK
2021-12-27T14:23:44.125Z DEBUG modem >> AT+CGEREP=1
2021-12-27T14:23:44.132Z DEBUG modem << OK
2021-12-27T14:23:44.135Z DEBUG modem >> AT+CIND=1,1,1
2021-12-27T14:23:44.141Z DEBUG modem << OK
2021-12-27T14:23:44.143Z DEBUG modem >> AT+CEREG=5
2021-12-27T14:23:44.148Z DEBUG modem << OK
2021-12-27T14:23:44.153Z DEBUG modem >> AT+CEREG?
2021-12-27T14:23:44.160Z DEBUG modem << +CEREG: 5,2,"332C","0110B208",7
2021-12-27T14:23:44.166Z DEBUG modem << OK
2021-12-27T14:23:44.175Z DEBUG modem >> AT%CESQ=1
2021-12-27T14:23:44.184Z DEBUG modem << OK
2021-12-27T14:23:44.188Z DEBUG modem >> AT+CESQ
2021-12-27T14:23:44.194Z DEBUG modem << +CESQ: 99,99,255,255,19,42
2021-12-27T14:23:44.202Z DEBUG modem << 
2021-12-27T14:23:44.204Z DEBUG modem << OK
2021-12-27T14:23:44.211Z DEBUG modem >> AT%XSIM=1
2021-12-27T14:23:44.218Z DEBUG modem << OK
2021-12-27T14:23:44.221Z DEBUG modem >> AT%XSIM?
2021-12-27T14:23:44.226Z DEBUG modem << %XSIM: 1
2021-12-27T14:23:44.234Z DEBUG modem << OK
2021-12-27T14:23:44.241Z DEBUG modem >> AT+CPIN?
2021-12-27T14:23:44.253Z DEBUG modem << +CPIN: READY
2021-12-27T14:23:44.255Z DEBUG modem << OK
2021-12-27T14:23:44.261Z DEBUG modem >> AT+CPINR="SIM PIN"
2021-12-27T14:23:44.274Z DEBUG modem << +CPINR: "SIM PIN",3
2021-12-27T14:23:44.275Z DEBUG modem << OK
2021-12-27T14:23:44.285Z DEBUG modem >> AT+CIMI
2021-12-27T14:23:44.291Z DEBUG modem << 204080813637384
2021-12-27T14:23:44.293Z DEBUG modem << OK
2021-12-27T14:23:44.295Z INFO IMSIdentity: 204080813637384
2021-12-27T14:23:45.508Z DEBUG modem << +CGEV:[00:00:03.252,014] [0m<inf> event_manager: MODEM_EVT_LTE_CONNECTED[0m
2021-12-27T14:23:45.525Z DEBUG modem << [00:00:03.259,033] [0m<inf> event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
2021-12-27T14:23:45.543Z DEBUG modem <<  ME PDN ACT 0,0
2021-12-27T14:23:45.552Z DEBUG modem << +CNEC_ESM: 50,0
2021-12-27T14:23:45.572Z DEBUG modem << +CEREG: 5,"332C","0110B208",7,,,"00001010","11000010"
2021-12-27T14:23:45.584Z DEBUG modem << +CIND: "service",1
2021-12-27T14:23:45.596Z DEBUG modem << +CIND: "roam",1
2021-12-27T14:23:45.608Z DEBUG modem >> AT+COPS=3,2
2021-12-27T14:23:45.615Z DEBUG modem << [00:00:03.278,076] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2021-12-27T14:23:45.616Z DEBUG modem << [00:00:03.286,437] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2021-12-27T14:23:45.625Z DEBUG modem << OK
2021-12-27T14:23:45.631Z DEBUG modem >> AT+COPS?
2021-12-27T14:23:45.637Z DEBUG modem << +COPS: 0,2,"20610",7
2021-12-27T14:23:45.640Z DEBUG modem << OK
2021-12-27T14:23:45.652Z DEBUG modem >> AT%XCBAND
2021-12-27T14:23:45.657Z DEBUG modem << %XCBAND: 20
2021-12-27T14:23:45.659Z DEBUG modem << 
2021-12-27T14:23:45.661Z DEBUG modem << OK
2021-12-27T14:23:45.673Z DEBUG modem >> AT+CGDCONT?
2021-12-27T14:23:45.684Z DEBUG modem << +CGDCONT: 0,"IP","ibasis.iot","10.160.50.109",0,0
2021-12-27T14:23:45.687Z DEBUG modem << OK
2021-12-27T14:23:45.694Z DEBUG modem >> AT+CGACT?
2021-12-27T14:23:45.704Z DEBUG modem << +CGACT: 0,1
2021-12-27T14:23:45.706Z DEBUG modem << OK
2021-12-27T14:23:50.093Z DEBUG modem << [00:00:07.837,036] [0m<inf> event_manager: CLOUD_EVT_CONFIG_RECEIVED[0m
2021-12-27T14:23:50.112Z DEBUG modem << [00:00:07.851,348] [0m<inf> event_manager: DATA_EVT_CONFIG_SEND[0m
2021-12-27T14:23:50.952Z DEBUG modem << [00:00:08.697,052] [0m<inf> event_manager: CLOUD_EVT_CONNECTED[0m
2021-12-27T14:23:50.959Z DEBUG modem << [00:00:08.703,826] [0m<inf> event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
2021-12-27T14:23:50.979Z DEBUG modem << [00:00:08.711,242] [0m<inf> event_manager: APP_EVT_DATA_GET - Requested data types (MOD_DYN, BAT, ENV, NEIGHBOR_CELLS, GNSS, MOD_STAT)[0m
2021-12-27T14:23:50.987Z DEBUG modem << [00:00:08.731,964] [0m<inf> event_manager: GPS_EVT_ACTIVE[0m
2021-12-27T14:23:51.003Z DEBUG modem << [00:00:08.738,647] [0m<inf> event_manager: GPS_EVT_AGPS_NEEDED[0m
2021-12-27T14:23:51.006Z DEBUG modem << [00:00:08.746,398] [0m<inf> event_manager: SENSOR_EVT_ENVIRONMENTAL_NOT_SUPPORTED[0m
2021-12-27T14:23:51.107Z DEBUG modem << [00:00:08.849,182] [0m<inf> event_manager: MODEM_EVT_MODEM_STATIC_DATA_READY[0m
2021-12-27T14:23:51.188Z DEBUG modem << [00:00:08.931,610] [0m<inf> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_READY[0m
2021-12-27T14:23:51.233Z DEBUG modem << [00:00:08.975,585] [0m<inf> event_manager: MODEM_EVT_BATTERY_DATA_READY[0m
2021-12-27T14:23:51.242Z DEBUG modem << [00:00:08.985,015] [0m<inf> event_manager: MODEM_EVT_NEIGHBOR_CELLS_DATA_READY[0m
2021-12-27T14:24:07.886Z DEBUG modem << [00:00:25.630,218] [0m<inf> event_manager: UI_EVT_BUTTON_DATA_READY[0m
2021-12-27T14:24:07.905Z DEBUG modem << [00:00:25.637,084] [0m<inf> event_manager: DATA_EVT_UI_DATA_READY[0m
2021-12-27T14:24:07.929Z DEBUG modem << [00:00:25.645,263] [0m<inf> event_manager: DATA_EVT_UI_DATA_SEND[0m
2021-12-27T14:24:07.933Z DEBUG modem << [00:00:25.654,174] [0m<inf> event_manager: CLOUD_EVT_DATA_ACK[0m
2021-12-27T14:24:08.215Z DEBUG modem << %CESQ: 35,1,8,1
2021-12-27T14:24:08.269Z DEBUG modem << %CESQ: 41,2,17,2

i received successfully data to nRF cloud:

But not in my AWS Iot account, maybe i do something wrong, can you help me whit this, 

if i use aws_iot, all work great, but my goal is that asset_tracker work whit AWS Iot

Thank you

Minyaev

[Didrik Rokhaug]

My appologies, it should be DOVERLAY_CONFIG, without the _ between D and OVERLAY.

I'll edit my previous reply as well.

Note that you will also need to set you AWS hostname in CONFIG_AWS_IOT_BROKER_HOST_NAME on line 18 in overlay-aws.conf.