nrf7002DK mqtt_client_tls_connect() errno -123 on aws_iot sample with ble provisioning

[mscherer]

I started with the BLE provisioning sample (ncs\v2.7.0\nrf\samples\wifi\provisioning\ble) using nrf7002dk/nrf5340/cpuapp build target with sysbuild which works fine to provision WiFi credentials, then added in the AWS IoT sample (ncs\v2.7.0\nrf\samples\net\aws_iot) which completes IP allocation and certificate provisioning before hitting an error with mqtt_client_tls_connect() and zsock_socket().

It appears that zsock_socket is not able to allocate a socket properly and returns a -1. Could this be a memory issue? Prj.conf included below based on the two samples along with relevant log.

prj.conf

0207.prj.conf

Log

Fullscreen 2063.log.txt Download

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
[00:00:00.660,125] <inf> net_config: Initializing network
[00:00:00.660,156] <inf> net_config: Waiting interface 1 (0x20001180) to be up...
[00:00:00.660,400] <inf> net_config: IPv4 address: 192.165.100.150
[00:00:00.660,430] <inf> net_config: Running dhcpv4 client...
[00:00:00.665,771] <dbg> net_sock_svc: socket_service_thread: (0x20002bd8): Service WEST_TOPDIR/zephyr/subsys/net/lib/dns/resolve.c:70 has 1 pollable sockets
[00:00:00.665,771] <dbg> net_sock_svc: socket_service_thread: (0x20002bd8): Monitoring 1 socket entries
[00:00:00.665,832] <dbg> net_sock_svc: socket_service_thread: Socket service thread RESTART - k_mutex_lock
[00:00:00.665,832] <dbg> net_sock_svc: socket_service_thread: Socket service thread RESTART - k_mutex_unlock
[00:00:00.674,133] <wrn> net_sock: ret: 8
[00:00:00.811,614] <dbg> mqtt_helper: mqtt_helper_poll_loop: Waiting for connection_poll_sem
[00:00:01.690,917] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:01.690,948] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:01.690,979] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 214.51162 Build 1926957230
[00:00:01.727,172] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x21fb, manufacturer 0x0059
[00:00:01.727,203] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x21fb
[00:00:01.727,233] <inf> ble_provision: Bluetooth initialized.
[00:00:01.727,233] <inf> ble_provision: Wi-Fi provisioning service starts successfully.
[00:00:01.727,264] <inf> ble_provision: update_dev_name to: AO1001C82
[00:00:01.729,431] <inf> ble_provision: BT Advertising successfully started.
[00:00:39.557,281] <wrn> ble_provision: BT Connected
[00:00:40.064,483] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:00:42.104,766] <inf> ble_provision: BT pairing completed
[00:00:42.104,919] <inf> ble_provision: BT Security changed
[00:00:42.134,735] <inf> wifi_prov: Wi-Fi Provisioning service - data out: notifications enabled
[00:00:42.284,729] <inf> wifi_prov: Wi-Fi Provisioning service - control point: indications enabled
[00:00:42.404,937] <inf> wifi_prov: Start parsing...
[00:00:42.404,968] <inf> wifi_prov: GET_STATUS received...
[00:00:43.455,230] <inf> wifi_prov: Start parsing...
[00:00:43.455,261] <inf> wifi_prov: Start_Scan received...
[00:01:01.530,120] <inf> wifi_prov: Start parsing...
[00:01:01.530,181] <inf> wifi_prov: Set_config received...
[00:01:04.364,685] <dbg> net_sock_packet: zpacket_received_cb: (0x20002dc8): ctx=0x2000497c, pkt=0x200474d0, st=0, user_data=0
[00:01:04.379,486] <dbg> net_sock_packet: zpacket_received_cb: (0x20002dc8): ctx=0x2000497c, pkt=0x20047510, st=0, user_data=0
[00:01:04.405,273] <wrn> ble_provision: Connected to a Wi-Fi Network!
[00:01:04.500,183] <inf> wifi_prov: Start parsing...
[00:01:04.500,244] <inf> wifi_prov: GET_STATUS received...
[00:01:07.427,551] <dbg> net_sock_packet: zpacket_received_cb: (0x20002dc8): ctx=0x2000497c, pkt=0x200474d0, st=0, user_data=0
[00:01:07.427,856] <wrn> net_sock: sock_family->is_supported
[00:01:07.427,917] <dbg> net_sock: zsock_socket_internal: (0x20002dc8): socket: ctx=0x20004a24, fd=13
[00:01:07.427,947] <wrn> net_sock: ret: 13
[00:01:07.439,514] <dbg> net_sock_packet: zpacket_received_cb: (0x20002dc8): ctx=0x2000497c, pkt=0x20047510, st=0, user_data=0
[00:01:07.439,849] <inf> net_dhcpv4: Received: 192.168.1.38
[00:01:07.440,032] <inf> net_config: IPv4 address: 192.168.1.38
[00:01:07.440,063] <inf> net_config: Lease time: 86400 seconds
[00:01:07.440,093] <inf> net_config: Subnet: 255.255.255.0
[00:01:07.440,155] <inf> net_config: Router: 192.168.1.1
metal: warning:   tx_vq: freeing non-empty virtqueue
metal: warning:   rx_vq: freeing non-empty virtqueue
[00:01:09.450,225] <inf> wifi_prov: Wi-Fi Provisioning service - control point: indications disabled
[00:01:09.450,286] <inf> wifi_prov: Wi-Fi Provisioning service - data out: notifications disabled
[00:01:09.450,378] <inf> ble_provision: BT Disconnected
[00:01:09.450,439] <wrn> ble_provision: bt_disabled!
[00:01:09.450,469] <inf> aws_iot_c: The AWS IoT sample started, version: v1.1.1
[00:01:09.450,531] <wrn> aws_iot_c: Network connectivity established
[00:01:09.450,561] <inf> aws_iot_c: l4_event_handler triggered!
[00:01:09.450,622] <inf> conn_mgr: conn_mgr_mon_resend_status
[00:01:09.450,622] <inf> aws_iot_c: Bringing network interface up and connecting to the network
[00:01:09.450,714] <dbg> mqtt_helper: mqtt_state_set: State transition: MQTT_STATE_UNINIT --> MQTT_STATE_DISCONNECTED
[00:01:09.450,714] <inf> aws_iot_c: aws_iot_client_init completed
[00:01:14.450,622] <inf> aws_iot_c: Connecting to AWS IoT
[00:01:14.450,775] <dbg> aws_iot: aws_iot_connect: No hostname provided, using Kconfig value: xxx.amazonaws.com
[00:01:14.450,805] <dbg> aws_iot: aws_iot_connect: No device ID provided, using Kconfig value: nrf7002
[00:01:14.450,866] <dbg> aws_iot: shadow_topics_construct: get_topic: $aws/things/nrf7002/shadow/get
[00:01:14.450,897] <dbg> aws_iot: shadow_topics_construct: update_topic: $aws/things/nrf7002/shadow/update
[00:01:14.450,958] <dbg> aws_iot: shadow_topics_construct: delete_topic: $aws/things/nrf7002/shadow/delete
[00:01:14.450,988] <dbg> net_mqtt: mqtt_client_init: mqtt_client_init completed
[00:01:14.451,019] <dbg> mqtt_helper: broker_init: Resolving IP address for xxx.amazonaws.com
[00:01:14.451,110] <dbg> net_sock_addr: exec_query: (0x20003bf0): Timeout 2000
[00:01:14.451,232] <dbg> net_dns_resolve: dns_resolve_name: (0x20003bf0): DNS id will be 27827
[00:01:14.451,354] <dbg> net_dns_resolve: dns_write: (0x20003bf0): [0] submitting work to server idx 0 for id 27827 hash 1971
[00:01:14.492,340] <dbg> net_sock_packet: zpacket_received_cb: (0x20002dc8): ctx=0x2000497c, pkt=0x200474d0, st=0, user_data=0
[00:01:14.492,492] <dbg> net_sock: zsock_received_cb: (0x20002dc8): ctx=0x20004a24, pkt=0x20047510, st=0, user_data=0
[00:01:14.602,203] <dbg> net_sock_svc: socket_service_thread: (0x20002bd8): Received restart event.
[00:01:14.602,233] <dbg> net_sock_svc: socket_service_thread: Socket service thread RESTART - k_mutex_lock
[00:01:14.602,264] <dbg> net_sock_svc: socket_service_thread: Socket service thread RESTART - k_mutex_unlock
[00:01:14.602,539] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -100
[00:01:14.602,569] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -100
[00:01:14.602,569] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -100
[00:01:14.602,600] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): getaddrinfo entries overflow
[00:01:14.602,600] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -100
[00:01:14.602,600] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): getaddrinfo entries overflow
[00:01:14.602,630] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -100
[00:01:14.602,661] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): getaddrinfo entries overflow
[00:01:14.602,691] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -100
[00:01:14.602,691] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): getaddrinfo entries overflow
[00:01:14.602,691] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -100
[00:01:14.602,722] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): getaddrinfo entries overflow
[00:01:14.602,722] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -100
[00:01:14.602,752] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): getaddrinfo entries overflow
[00:01:14.602,752] <dbg> net_sock_addr: dns_resolve_cb: (0x20002bd8): dns status: -103
[00:01:14.602,844] <dbg> mqtt_helper: broker_init: IPv4 Address found XX.X.XXX.XXX (AF_INET)
[00:01:14.602,874] <dbg> mqtt_helper: broker_init: broker_init completed with err: 0
[00:01:14.602,905] <dbg> mqtt_helper: client_connect: broker_init success
[00:01:14.602,905] <dbg> mqtt_helper: certificates_provision: certificates_provision started
[00:01:14.602,935] <wrn> mqtt_helper: Certificates Provisioned Successfully!
[00:01:14.602,966] <dbg> mqtt_helper: mqtt_state_set: State transition: MQTT_STATE_DISCONNECTED --> MQTT_STATE_TRANSPORT_CONNECTING
[00:01:14.602,996] <dbg> net_mqtt: mqtt_connect: mqtt_mutex_lock(client)
[00:01:14.602,996] <wrn> net_mqtt_sock_tls: mqtt_client_tls_connect STARTED
[00:01:14.603,027] <wrn> net_sock: ret: -1
[00:01:14.603,057] <dbg> net_mqtt_sock_tls: mqtt_client_tls_connect: (0x20003bf0): client->transport.tls.sock = -1; broker->sa_family: 1, type: 1
[00:01:14.603,057] <err> net_mqtt: mqtt_transport_connect err_code: -123
[00:01:14.603,057] <dbg> net_mqtt: mqtt_connect: client_connect err_code: -123
[00:01:14.603,088] <err> mqtt_helper: mqtt_connect, error: -123
[00:01:14.603,118] <dbg> mqtt_helper: mqtt_state_set: State transition: MQTT_STATE_TRANSPORT_CONNECTING --> MQTT_STATE_DISCONNECTED
[00:01:14.603,118] <err> aws_iot: mqtt_helper_connect, error: -123
[00:01:14.603,149] <inf> aws_iot_c: AWS Iot Connect failed (err: -123), Next connection retry in 30 seconds
[00:01:14.603,302] <err> net_dns_resolve: DNS recv error (-103)

[Marte Myrvold]

Hi,

How much RAM and flash is used by the application? You should see this close to the end of the build log. Please make sure to share all instances of this from the build log, or share the complete build log.

using nrf7002dk/nrf5340/cpuapp build target

The AWS IoT sample supports board targets with the */ns variant, i.e. nrf7002dk/nrf5340/cpuapp/ns. Trying to use the code without /ns might cause issues.

Best regards,
Marte

[mscherer]

Hi Marte,

Here's the build logs for the cpuapp showing RAM and Flash usage:

And for the cpuapp_ns build:

However when I run the cpuapp_ns build, I hit a SECURE FAULT when attempting to connect to AWS:

Fullscreen log - _ns build SECURE FAULT.txt Download

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
[00:00:00.655,151] <inf> net_config: Initializing network
[00:00:00.655,181] <inf> net_config: Waiting interface 1 (0x20009128) to be up...
[00:00:00.655,426] <inf> net_config: IPv4 address: 192.165.100.150
[00:00:00.655,456] <inf> net_config: Running dhcpv4 client...
[00:00:00.661,712] <dbg> net_sock_svc: socket_service_thread: (0x2000ab80): Service WEST_TOPDIR/zephyr/subsys/net/lib/dns/resolve.c:70 has 1 pollable sockets
[00:00:00.661,712] <dbg> net_sock_svc: socket_service_thread: (0x2000ab80): Monitoring 1 socket entries
[00:00:00.661,743] <dbg> net_sock_svc: socket_service_thread: Socket service thread RESTART - k_mutex_lock
[00:00:00.661,773] <dbg> net_sock_svc: socket_service_thread: Socket service thread RESTART - k_mutex_unlock
[00:00:00.670,501] <wrn> net_sock: ret: 8
[00:00:00.808,990] <dbg> mqtt_helper: mqtt_helper_poll_loop: Waiting for connection_poll_sem
[00:00:01.672,943] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:01.672,973] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:01.673,004] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 214.51162 Build 1926957230
[00:00:01.709,167] <inf> bt_hci_core: Identity: F1:60:DB:2B:65:E2 (random)
[00:00:01.709,197] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x21fb, manufacturer 0x0059
[00:00:01.709,228] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x21fb
[00:00:01.709,228] <inf> ble_provision: Bluetooth initialized.
[00:00:01.709,259] <inf> ble_provision: Wi-Fi provisioning service starts successfully.
[00:00:01.709,289] <inf> ble_provision: update_dev_name to: AO1001C82 
[00:00:01.711,486] <inf> ble_provision: BT Advertising successfully started.
[00:00:03.265,472] <inf> wifi_mgmt_ext: Connection requested
[00:00:04.520,568] <dbg> net_sock_packet: zpacket_received_cb: (0x2000ad70): ctx=0x2000c3f4, pkt=0x2004fe54, st=0, user_data=0
[00:00:04.540,832] <dbg> net_sock_packet: zpacket_received_cb: (0x2000ad70): ctx=0x2000c3f4, pkt=0x2004fe94, st=0, user_data=0
[00:00:04.564,575] <wrn> ble_provision: Connected to a Wi-Fi Network!
[00:00:04.564,636] <inf> wifi_prov: BT not connected. Ignore notification request.
[00:00:04.564,666] <inf> wifi_prov: BT not connected. Ignore notification request.
[00:00:04.564,697] <inf> wifi_prov: BT not connected. Ignore notification request.
[00:00:04.564,727] <inf> wifi_prov: BT not connected. Ignore notification request.
[00:00:07.590,240] <dbg> net_sock_packet: zpacket_received_cb: (0x2000ad70): ctx=0x2000c3f4, pkt=0x2004fe54, st=0, user_data=0
[00:00:07.590,515] <wrn> net_sock: sock_family->is_supported
[00:00:07.590,606] <dbg> net_sock: zsock_socket_internal: (0x2000ad70): socket: ctx=0x2000c49c, fd=13
[00:00:07.590,606] <wrn> net_sock: ret: 13
[00:00:07.601,928] <dbg> net_sock_packet: zpacket_received_cb: (0x2000ad70): ctx=0x2000c3f4, pkt=0x2004fe94, st=0, user_data=0
[00:00:07.602,294] <inf> net_dhcpv4: Received: 192.168.1.38
[00:00:07.602,478] <inf> net_config: IPv4 address: 192.168.1.38
[00:00:07.602,478] <inf> net_config: Lease time: 86400 seconds
[00:00:07.602,539] <inf> net_config: Subnet: 255.255.255.0
[00:00:07.602,569] <inf> net_config: Router: 192.168.1.1
metal: warning:   tx_vq: freeing non-empty virtqueue
metal: warning:   rx_vq: freeing non-empty virtqueue
[00:00:09.567,016] <wrn> ble_provision: bt_disabled!
[00:00:09.567,047] <inf> aws_iot_c: The AWS IoT sample started, version: v1.1.1
[00:00:09.567,077] <inf> aws_iot_c: Bringing network interface up and connecting to the network
[00:00:09.567,138] <dbg> mqtt_helper: mqtt_state_set: State transition: MQTT_STATE_UNINIT --> MQTT_STATE_DISCONNECTED
[00:00:09.567,169] <inf> aws_iot_c: aws_iot_client_init completed
[00:00:09.567,230] <wrn> aws_iot_c: Network connectivity established
[00:00:09.567,260] <inf> aws_iot_c: l4_event_handler triggered!
[00:00:09.567,291] <inf> conn_mgr: conn_mgr_mon_resend_status
[00:00:14.567,321] <inf> aws_iot_c: Connecting to AWS IoT
[00:00:14.569,885] <err> os: ***** SECURE FAULT *****
[00:00:14.569,915] <err> os:   Address: 0x0
[00:00:14.569,915] <err> os:   Attribution unit violation
[00:00:14.569,915] <err> os: r0/a1:  0x00000000  r1/a2:  0x00000001  r2/a3:  0x00000033
[00:00:14.569,946] <err> os: r3/a4:  0x00000000 r12/ip:  0x00000003 r14/lr:  0x0000ba01
[00:00:14.569,946] <err> os:  xpsr:  0x21000000
[00:00:14.569,946] <err> os: Faulting instruction address (r15/pc): 0x00009876
[00:00:14.570,007] <err> os: >>> ZEPHYR FATAL ERROR 41: Unknown error on CPU 0
[00:00:14.570,007] <err> os: Current thread: 0x2000bb98 (unknown)
[00:00:14.637,756] <err> coredump: #CD:BEGIN#
[00:00:14.642,822] <err> coredump: #CD:5a4501000300050029000000
[00:00:14.649,414] <err> coredump: #CD:4102004400
[00:00:14.654,846] <err> coredump: #CD:000000000100000033000000000000000300000001ba00007698000000000021
[00:00:14.664,947] <err> coredump: #CD:0000000000000000000000000000000000000000000000000000000000000000
[00:00:14.674,987] <err> coredump: #CD:00000000
[00:00:14.680,236] <err> coredump: #CD:4d010098bb002040bc0020
[00:00:14.686,676] <err> coredump: #CD:a097002000dd0020000000000180ff0000000000000000000000000000000000
[00:00:14.696,777] <err> coredump: #CD:000000000000000000000000000000000000000098bb0020ffffffffffffffff
[00:00:14.706,848] <err> coredump: #CD:00000000356107000000000000000000f87a022000000000f0bb0020f0bb0020
[00:00:14.716,949] <err> coredump: #CD:0000000000000000000000000000000000000000807302200008000018000000
[00:00:14.727,050] <err> coredump: #CD:c08b00206c7b0220000000000000000000000000000000000000000000000000
[00:00:14.737,121] <err> coredump: #CD:0000000000bc0000
[00:00:14.743,041] <err> coredump: #CD:4d010080730220807b0220
[00:00:14.749,481] <err> coredump: #CD:f0f0f0f0aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.759,582] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.769,683] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.779,754] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.789,855] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.799,957] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.810,058] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.820,129] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.830,230] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.840,332] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.850,433] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.860,504] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.870,605] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.880,706] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.890,808] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.900,878] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.910,980] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.921,081] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.931,182] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.941,253] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.951,354] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.961,456] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.971,557] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.981,658] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:14.991,760] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.001,861] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.011,932] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.022,033] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.032,135] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.042,236] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.052,337] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.062,438] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.072,540] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.082,611] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.092,712] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.102,813] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.112,915] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.122,985] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.133,087] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.143,188] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.153,289] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.163,360] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.173,461] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.183,563] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.193,634] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.203,735] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.213,836] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[00:00:15.223,907] <err> coredump: #CD:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaadced0420c9910500f4900020ffffffff
[00:00:15.234,008] <err> coredump: #CD:00000000ffffffffffffffffdced0420ffffffffdced0420800000005b9c0100
[00:00:15.244,079] <err> coredump: #CD:000000000100000033000000000000000300000001ba00007698000000000021
[00:00:15.254,180] <err> coredump: #CD:ffffffffdced042000000000a4ed0420ffffffff1c0000000100000002000000
[00:00:15.264,282] <err> coredump: #CD:6c7a02205798090002000000020000000000000094f904201400000014000000
[00:00:15.274,353] <err> coredump: #CD:0000008094f90420080000000800000000000000277506000000000000000000
[00:00:15.284,454] <err> coredump: #CD:0041000000000000507a022020000000b07a02200a000000040000003de50000
[00:00:15.294,555] <err> coredump: #CD:0a000000647a022004000000ffff7f009ec8070000000000a0bd070020000000
[00:00:15.304,626] <err> coredump: #CD:500100003d800600a4e804200000000000000000000000002000000000000000
[00:00:15.314,727] <err> coredump: #CD:8a9b0900d07a0220d07a022000000000000000000000000000000000bbe00200
[00:00:15.324,829] <err> coredump: #CD:000000000000000000000000ddbe050007000002579809008a9b090000000000
[00:00:15.334,899] <err> coredump: #CD:0000000000000000000000000103030500000000000000000000000000000000
[00:00:15.345,001] <err> coredump: #CD:000000000000000000000000000000000000000098bb002018dd002010dd0020
[00:00:15.355,102] <err> coredump: #CD:000000005daa00000000000077aa0000a4fa0000000000610000000000000000
[00:00:15.365,203] <err> coredump: #CD:000000000080002098bb002071950500ffffffffffffffff00000000aaaaaaaa
[00:00:15.375,274] <err> coredump: #CD:aaaaaaaa6c7b02206d94050098bb0020000000000000000008000000ffbc0000
[00:00:15.385,375] <err> coredump: #CD:00000000aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa98bb00200000000000000000
[00:00:15.395,416] <err> coredump: #CD:END#
[00:00:15.400,299] <err> os: Halting system

[mscherer]

Update: I was able to get the nrf7002dk/nrf5340/cpuapp/ns build target working after creating a pm_static.yml file to address the "TF-M non-secure start address is not aligned to SPU HW requirements" error. It was off by 0x200. Now using the non-secure build I'm still hitting the same mqtt_connect, error: -123

If I add "CONFIG_NET_SOCKETS_SOCKOPT_TLS=y" to the prj.conf I get different errors (net_dns_resolve: DNS recv error (-103) and net_sock_tls: Failed to parse CA certificate, err: -0x262e)

It's the standard Amazon Root CA 1 pem file place in certs/ with CR+LF EOLs, as per the AWS IoT documentation.

[Marte Myrvold]

Hi,

Have you setup the AWS IoT server instance as described in AWS IoT sample - setup? Are you able to get the AWS IoT sample working, without the BLE provisioning?

Best regards,
Marte