Connection error after OTA update

Hey @marko
Would you be able to help me with an issue I’m having connecting to Golioth since this morning.
Current Setup: Application uses Certificate Provisioning example/guide. I’m using mcumgr to copy device certificate and key (like in the repo and blog’s guide). Cohorts is setup for remote updates for this device.
Till 4 hours ago both of the services were working as expected. i.e. I can new device via device certificate and key. Perform OTA for new version of the app
Issue: Error after connection to LTE
[00:15:32.481,079] golioth_coap_client_zephyr: Failed to connect to socket: -22
[00:15:32.481,475] golioth_coap_client_zephyr: Failed to connect: -22
Way to replicate: golioth/reference-design-template 's shell commands to set credentials
OR
certificate_provisioning example with device certificate and key located on device

Project Config
west.yaml
path: modules/lib/golioth-firmware-sdk
revision: v0.16.0

prj.conf

CONFIG_GOLIOTH_SAMPLE_COMMON=y

CONFIG_LOG_BACKEND_GOLIOTH=y

CONFIG_GOLIOTH_FIRMWARE_SDK=y

CONFIG_GOLIOTH_FW_UPDATE=y

CONFIG_GOLIOTH_SETTINGS=y

CONFIG_FLASH=y

CONFIG_FLASH_MAP=y

CONFIG_STREAM_FLASH=y

CONFIG_IMG_MANAGER=y

CONFIG_IMG_ERASE_PROGRESSIVELY=y

CONFIG_FILE_SYSTEM=y

CONFIG_FILE_SYSTEM_LITTLEFS=y

CONFIG_FILE_SYSTEM_SHELL=y

CONFIG_HEAP_MEM_POOL_SIZE=4096

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2304

CONFIG_ZCBOR=y

CONFIG_MCUMGR=y

CONFIG_CONSOLE=y

CONFIG_UART_CONSOLE=y

CONFIG_UART_CONSOLE_MCUMGR=y

CONFIG_SHELL=y

CONFIG_SHELL_BACKEND_SERIAL=y

CONFIG_BASE64=y

CONFIG_MCUMGR_TRANSPORT_SHELL=y

CONFIG_MCUMGR_GRP_FS=y

CONFIG_SHELL_BACKEND_DUMMY=y

CONFIG_MCUMGR_GRP_SHELL=y

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2304

CONFIG_MAIN_STACK_SIZE=2048

CONFIG_GOLIOTH_AUTH_METHOD_CERT=y

CONFIG_GOLIOTH_SAMPLE_HARDCODED_CREDENTIALS=n

CONFIG_LOG_CMDS=y

CONFIG_SETTINGS_FILE=y

CONFIG_SETTINGS_FILE_PATH=“/lfs1/settings”

Debugging notes

  1. Two devices used (with different sim provider): Thingy91 and 9160DK
  2. Cleared any secure credentials stored via Cellular Monitor → Certificate Manager
  3. Build examples with no modification
  4. Altering app version numbers

Hey @ash.vetchip,

Just to make sure I understand correctly, in the two scenarios you’re testing:

  1. Using the Reference Design Template with Pre-Shared Keys set via shell commands,
  2. Using the certificate_provisioning example,

You’re able to connect to Golioth, but after a successful OTA update, you’re encountering the following errors:

[00:15:32.481,079] golioth_coap_client_zephyr: Failed to connect to socket: -22
[00:15:32.481,475] golioth_coap_client_zephyr: Failed to connect: -22

If that’s the case, let’s start by focusing on the Reference Design Template with Pre-Shared Keys and the nRF9160 DK.

After building and flashing the Reference Design template using:

$ west build -p -b nrf9160dk/nrf9160/ns --sysbuild app
$ west flash

And setting the Pre-Shared Keys with the following shell commands:

uart:~$ settings set golioth/psk-id <my-psk-id@my-project>
uart:~$ settings set golioth/psk <my-psk>
uart:~$ kernel reboot cold

The nRF9160 DK successfully connects to Golioth, correct?

If so, let’s proceed with the OTA update steps:

  • Change the VERSION file from 2.5.0 to 2.6.0 and rebuild the app.
  • In the console, create a Package named main.
  • Generate a New Version of the package and upload the zephyr.signed.bin file located at: golioth-reference-design-template/build/app/zephyr/.
  • Add the nRF9160 DK device to a Cohort.
  • Create a Deployment to trigger the OTA update.

Once the nRF9160 DK has downloaded the image, can you confirm if it’s running the 2.6.0 version?

Are you still encountering the connection issues after this?

Apologies I think I didn’t explained the issue clearly.
Background: For past couple of weeks I’ve been working on various Golioth examples and reference design template. Goal is to 1. get some telemetry from Bluetooth devices 2. send it to Golioth (similar to BLE gateway) with Thingy91’s on board sensors data.
So far I have had success with understating basics, FOTA and Cert Provisioning, building on top of the Reference Design Template.
Issue: Since Friday I couldnt connect my 9160dk (or Thingy91) to Golioth. To debug I started fresh examples (Basic and Cert) with no luck. Errors on debug terminal:

[00:15:32.481,079] golioth_coap_client_zephyr: Failed to connect to socket: -22
[00:15:32.481,475] golioth_coap_client_zephyr: Failed to connect: -22

Response:
The nRF9160 DK successfully connects to Golioth, correct?

  • No success since last Friday.

Once the nRF9160 DK has downloaded the image, can you confirm if it’s running the 2.6.0 version?

  • FOTA building with new version number and deploying wasnt an issue.

Notes:

  1. nRF cloud examples work with 1.3.7 modem firmware on 9160dk and Thingy91
  2. Both SIMs have data and tested in isolated conditions
  3. Config with current setup is posted above.

Hey @ash.vetchip,

Thank you for the clarification!

It’s certainly unusual to suddenly encounter this issue with your application, or even with examples from the SDK or Reference Design template.

The -22 error code translates to “invalid argument,” which can stem from various causes. In the past, we’ve seen this error occur when credentials were corrupted.

To help diagnose the issue, could you share a more detailed serial output from the device, starting from bootup to when the error occurs? Additionally, could you provide or attach the generated config build file?

Finally, could you run the following commands:

settings get golioth/psk-id
settings get golioth/psk

with the Reference Design Template and confirm that the Pre-Shared Keys are not corrupted?

Thanks @marko
Commands returned credentials after hard reboot.

Log after boot:

*** Booting MCUboot v2.1.0-dev-4594a8693738 ***
*** Using nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0x10000
I: Jumping to the first image slot
*** Booting My Application v2.5.0-2a68fb8851da ***
*** Using nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
[00:00:00.505,676] <inf> golioth_settings_autoload: Initializing settings subsystem
[00:00:00.511,199] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.511,230] <inf> fs_nvs: alloc wra: 0, fa8
[00:00:00.511,230] <inf> fs_nvs: data wra: 0, a8
[00:00:00.511,291] <inf> golioth_settings_autoload: Loading settings
[00:00:00.511,474] <dbg> golioth_rd_template: main: Start Reference Design Template sample
[00:00:00.511,535] <inf> golioth_rd_template: Firmware version: 2.5.0
[00:00:00.518,157] <inf> golioth_rd_template: Modem firmware version: mfw_nrf9160_1.3.7
[00:00:00.518,188] <inf> golioth_rd_template: Connecting to LTE, this may take some time...
[00:00:00.569,305] <dbg> app_sensors: app_sensors_read_and_stream: No connection available, skipping streaming counter: 0
[00:00:05.474,029] <inf> lte_monitor: Network: Searching
[00:00:09.334,838] <inf> lte_monitor: Network: Registered (roaming)
[00:00:09.335,388] <inf> golioth_mbox: Mbox created, bufsize: 1320, num_items: 10, item_size: 120
[00:00:09.336,090] <inf> golioth_fw_update: Current firmware version: main - 2.5.0
[00:00:13.146,697] <err> golioth_coap_client_zephyr: Failed to connect to socket: -11
[00:00:13.154,846] <err> golioth_coap_client_zephyr: Failed to connect: -11
[00:00:13.154,846] <wrn> golioth_coap_client_zephyr: Failed to connect: -11
[00:00:21.156,921] <err> golioth_coap_client_zephyr: Failed to connect to socket: -11
[00:00:21.164,947] <err> golioth_coap_client_zephyr: Failed to connect: -11
[00:00:21.164,947] <wrn> golioth_coap_client_zephyr: Failed to connect: -11
[00:00:29.167,022] <err> golioth_coap_client_zephyr: Failed to connect to socket: -11
[00:00:29.175,201] <err> golioth_coap_client_zephyr: Failed to connect: -11
[00:00:29.175,201] <wrn> golioth_coap_client_zephyr: Failed to connect: -11

I’m assuming you mean pm.config build file, here:

PM_MCUBOOT_OFFSET=0x0
PM_MCUBOOT_ADDRESS=0x0
PM_MCUBOOT_END_ADDRESS=0xc000
PM_MCUBOOT_SIZE=0xc000
PM_MCUBOOT_NAME=mcuboot
PM_MCUBOOT_ID=0
PM_mcuboot_ID=PM_MCUBOOT_ID
PM_mcuboot_IS_ENABLED=1
PM_0_LABEL=MCUBOOT
PM_EMPTY_0_OFFSET=0xc000
PM_EMPTY_0_ADDRESS=0xc000
PM_EMPTY_0_END_ADDRESS=0x10000
PM_EMPTY_0_SIZE=0x4000
PM_EMPTY_0_NAME=EMPTY_0
PM_EMPTY_0_ID=1
PM_empty_0_ID=PM_EMPTY_0_ID
PM_empty_0_IS_ENABLED=1
PM_1_LABEL=EMPTY_0
PM_MCUBOOT_PAD_OFFSET=0x10000
PM_MCUBOOT_PAD_ADDRESS=0x10000
PM_MCUBOOT_PAD_END_ADDRESS=0x10200
PM_MCUBOOT_PAD_SIZE=0x200
PM_MCUBOOT_PAD_NAME=mcuboot_pad
PM_MCUBOOT_PAD_ID=2
PM_mcuboot_pad_ID=PM_MCUBOOT_PAD_ID
PM_mcuboot_pad_IS_ENABLED=1
PM_2_LABEL=MCUBOOT_PAD
PM_MCUBOOT_PRIMARY_OFFSET=0x10000
PM_MCUBOOT_PRIMARY_ADDRESS=0x10000
PM_MCUBOOT_PRIMARY_END_ADDRESS=0x80000
PM_MCUBOOT_PRIMARY_SIZE=0x70000
PM_MCUBOOT_PRIMARY_NAME=mcuboot_primary
PM_MCUBOOT_PRIMARY_ID=3
PM_mcuboot_primary_ID=PM_MCUBOOT_PRIMARY_ID
PM_mcuboot_primary_IS_ENABLED=1
PM_3_LABEL=MCUBOOT_PRIMARY
PM_MCUBOOT_PRIMARY_SPAN=“app tfm mcuboot_pad”
PM_TFM_SECURE_OFFSET=0x10000
PM_TFM_SECURE_ADDRESS=0x10000
PM_TFM_SECURE_END_ADDRESS=0x18000
PM_TFM_SECURE_SIZE=0x8000
PM_TFM_SECURE_NAME=tfm_secure
PM_TFM_SECURE_ID=4
PM_tfm_secure_ID=PM_TFM_SECURE_ID
PM_tfm_secure_IS_ENABLED=1
PM_4_LABEL=TFM_SECURE
PM_TFM_SECURE_SPAN=“mcuboot_pad tfm”
PM_MCUBOOT_PRIMARY_APP_OFFSET=0x10200
PM_MCUBOOT_PRIMARY_APP_ADDRESS=0x10200
PM_MCUBOOT_PRIMARY_APP_END_ADDRESS=0x80000
PM_MCUBOOT_PRIMARY_APP_SIZE=0x6fe00
PM_MCUBOOT_PRIMARY_APP_NAME=mcuboot_primary_app
PM_MCUBOOT_PRIMARY_APP_ID=5
PM_mcuboot_primary_app_ID=PM_MCUBOOT_PRIMARY_APP_ID
PM_mcuboot_primary_app_IS_ENABLED=1
PM_5_LABEL=MCUBOOT_PRIMARY_APP
PM_MCUBOOT_PRIMARY_APP_SPAN=“app tfm”
PM_TFM_OFFSET=0x10200
PM_TFM_ADDRESS=0x10200
PM_TFM_END_ADDRESS=0x18000
PM_TFM_SIZE=0x7e00
PM_TFM_NAME=tfm
PM_TFM_ID=6
PM_tfm_ID=PM_TFM_ID
PM_tfm_IS_ENABLED=1
PM_6_LABEL=TFM
PM_APP_OFFSET=0x18000
PM_APP_ADDRESS=0x18000
PM_APP_END_ADDRESS=0x78000
PM_APP_SIZE=0x60000
PM_APP_NAME=app
PM_APP_ID=7
PM_app_ID=PM_APP_ID
PM_app_IS_ENABLED=1
PM_7_LABEL=APP
PM_TFM_NONSECURE_OFFSET=0x18000
PM_TFM_NONSECURE_ADDRESS=0x18000
PM_TFM_NONSECURE_END_ADDRESS=0x80000
PM_TFM_NONSECURE_SIZE=0x68000
PM_TFM_NONSECURE_NAME=tfm_nonsecure
PM_TFM_NONSECURE_ID=8
PM_tfm_nonsecure_ID=PM_TFM_NONSECURE_ID
PM_tfm_nonsecure_IS_ENABLED=1
PM_8_LABEL=TFM_NONSECURE
PM_TFM_NONSECURE_SPAN=“app”
PM_NVS_STORAGE_OFFSET=0x78000
PM_NVS_STORAGE_ADDRESS=0x78000
PM_NVS_STORAGE_END_ADDRESS=0x7e000
PM_NVS_STORAGE_SIZE=0x6000
PM_NVS_STORAGE_NAME=nvs_storage
PM_NVS_STORAGE_ID=9
PM_nvs_storage_ID=PM_NVS_STORAGE_ID
PM_nvs_storage_IS_ENABLED=1
PM_9_LABEL=NVS_STORAGE
PM_MCUBOOT_SECONDARY_OFFSET=0x80000
PM_MCUBOOT_SECONDARY_ADDRESS=0x80000
PM_MCUBOOT_SECONDARY_END_ADDRESS=0xf0000
PM_MCUBOOT_SECONDARY_SIZE=0x70000
PM_MCUBOOT_SECONDARY_NAME=mcuboot_secondary
PM_MCUBOOT_SECONDARY_ID=10
PM_mcuboot_secondary_ID=PM_MCUBOOT_SECONDARY_ID
PM_mcuboot_secondary_IS_ENABLED=1
PM_10_LABEL=MCUBOOT_SECONDARY
PM_EMPTY_2_OFFSET=0xf0000
PM_EMPTY_2_ADDRESS=0xf0000
PM_EMPTY_2_END_ADDRESS=0xf8000
PM_EMPTY_2_SIZE=0x8000
PM_EMPTY_2_NAME=EMPTY_2
PM_EMPTY_2_ID=11
PM_empty_2_ID=PM_EMPTY_2_ID
PM_empty_2_IS_ENABLED=1
PM_11_LABEL=EMPTY_2
PM_NONSECURE_STORAGE_OFFSET=0xf8000
PM_NONSECURE_STORAGE_ADDRESS=0xf8000
PM_NONSECURE_STORAGE_END_ADDRESS=0xfa000
PM_NONSECURE_STORAGE_SIZE=0x2000
PM_NONSECURE_STORAGE_NAME=nonsecure_storage
PM_NONSECURE_STORAGE_ID=12
PM_nonsecure_storage_ID=PM_NONSECURE_STORAGE_ID
PM_nonsecure_storage_IS_ENABLED=1
PM_12_LABEL=NONSECURE_STORAGE
PM_NONSECURE_STORAGE_SPAN=“settings_storage”
PM_SETTINGS_STORAGE_OFFSET=0xf8000
PM_SETTINGS_STORAGE_ADDRESS=0xf8000
PM_SETTINGS_STORAGE_END_ADDRESS=0xfa000
PM_SETTINGS_STORAGE_SIZE=0x2000
PM_SETTINGS_STORAGE_NAME=settings_storage
PM_SETTINGS_STORAGE_ID=13
PM_settings_storage_ID=PM_SETTINGS_STORAGE_ID
PM_settings_storage_IS_ENABLED=1
PM_13_LABEL=SETTINGS_STORAGE
PM_EMPTY_1_OFFSET=0xfa000
PM_EMPTY_1_ADDRESS=0xfa000
PM_EMPTY_1_END_ADDRESS=0x100000
PM_EMPTY_1_SIZE=0x6000
PM_EMPTY_1_NAME=EMPTY_1
PM_EMPTY_1_ID=14
PM_empty_1_ID=PM_EMPTY_1_ID
PM_empty_1_IS_ENABLED=1
PM_14_LABEL=EMPTY_1
PM_OTP_OFFSET=0x0
PM_OTP_ADDRESS=0xff8108
PM_OTP_END_ADDRESS=0xff83fc
PM_OTP_SIZE=0x2f4
PM_OTP_NAME=otp
PM_MCUBOOT_SRAM_OFFSET=0x0
PM_MCUBOOT_SRAM_ADDRESS=0x20000000
PM_MCUBOOT_SRAM_END_ADDRESS=0x20008000
PM_MCUBOOT_SRAM_SIZE=0x8000
PM_MCUBOOT_SRAM_NAME=mcuboot_sram
PM_MCUBOOT_SRAM_SPAN=“tfm_sram”
PM_SRAM_SECURE_OFFSET=0x0
PM_SRAM_SECURE_ADDRESS=0x20000000
PM_SRAM_SECURE_END_ADDRESS=0x20008000
PM_SRAM_SECURE_SIZE=0x8000
PM_SRAM_SECURE_NAME=sram_secure
PM_SRAM_SECURE_SPAN=“tfm_sram”
PM_TFM_SRAM_OFFSET=0x0
PM_TFM_SRAM_ADDRESS=0x20000000
PM_TFM_SRAM_END_ADDRESS=0x20008000
PM_TFM_SRAM_SIZE=0x8000
PM_TFM_SRAM_NAME=tfm_sram
PM_NRF_MODEM_LIB_CTRL_OFFSET=0x8000
PM_NRF_MODEM_LIB_CTRL_ADDRESS=0x20008000
PM_NRF_MODEM_LIB_CTRL_END_ADDRESS=0x200084e8
PM_NRF_MODEM_LIB_CTRL_SIZE=0x4e8
PM_NRF_MODEM_LIB_CTRL_NAME=nrf_modem_lib_ctrl
PM_NRF_MODEM_LIB_SRAM_OFFSET=0x8000
PM_NRF_MODEM_LIB_SRAM_ADDRESS=0x20008000
PM_NRF_MODEM_LIB_SRAM_END_ADDRESS=0x2000c568
PM_NRF_MODEM_LIB_SRAM_SIZE=0x4568
PM_NRF_MODEM_LIB_SRAM_NAME=nrf_modem_lib_sram
PM_NRF_MODEM_LIB_SRAM_SPAN=“nrf_modem_lib_ctrl nrf_modem_lib_tx nrf_modem_lib_rx”
PM_SRAM_NONSECURE_OFFSET=0x8000
PM_SRAM_NONSECURE_ADDRESS=0x20008000
PM_SRAM_NONSECURE_END_ADDRESS=0x20040000
PM_SRAM_NONSECURE_SIZE=0x38000
PM_SRAM_NONSECURE_NAME=sram_nonsecure
PM_SRAM_NONSECURE_SPAN=“sram_primary nrf_modem_lib_ctrl nrf_modem_lib_tx nrf_modem_lib_rx”
PM_NRF_MODEM_LIB_TX_OFFSET=0x84e8
PM_NRF_MODEM_LIB_TX_ADDRESS=0x200084e8
PM_NRF_MODEM_LIB_TX_END_ADDRESS=0x2000a568
PM_NRF_MODEM_LIB_TX_SIZE=0x2080
PM_NRF_MODEM_LIB_TX_NAME=nrf_modem_lib_tx
PM_NRF_MODEM_LIB_RX_OFFSET=0xa568
PM_NRF_MODEM_LIB_RX_ADDRESS=0x2000a568
PM_NRF_MODEM_LIB_RX_END_ADDRESS=0x2000c568
PM_NRF_MODEM_LIB_RX_SIZE=0x2000
PM_NRF_MODEM_LIB_RX_NAME=nrf_modem_lib_rx
PM_SRAM_PRIMARY_OFFSET=0xc568
PM_SRAM_PRIMARY_ADDRESS=0x2000c568
PM_SRAM_PRIMARY_END_ADDRESS=0x20040000
PM_SRAM_PRIMARY_SIZE=0x33a98
PM_SRAM_PRIMARY_NAME=sram_primary
PM_NUM=15
PM_ALL_BY_SIZE=“mcuboot_pad otp nrf_modem_lib_ctrl nrf_modem_lib_rx settings_storage nonsecure_storage nrf_modem_lib_tx EMPTY_0 nrf_modem_lib_sram EMPTY_1 nvs_storage tfm EMPTY_2 tfm_sram mcuboot_sram sram_secure tfm_secure mcuboot sram_primary sram_nonsecure app tfm_nonsecure mcuboot_primary_app mcuboot_secondary mcuboot_primary”

Hey @ash.vetchip,

Looking at the console output, the error is now -11 instead of -22 from before.

Can you check if the device has an IP address by running the command net iface from the device shell and post the output here? In the Reference Design Template, the Net Shell is enabled by default with the CONFIG_NET_SHELL option.

Regarding the pm.config file, that’s generated by the Partition Manager. I was actually referring to the generated .config file, which for the RD Template can be found here: build/app/zephyr/.config. It would be really helpful to have that file to review the application configuration.

@marko
I created new device in to test which had error code -11.

Here is the .config file

SB_CONFIG_BOARD="nrf9160dk"

SB_CONFIG_BOARD_REVISION="0.14.0"

SB_CONFIG_BOARD_NRF9160DK=y

SB_CONFIG_BOARD_NRF9160DK_NRF9160_NS=y

SB_CONFIG_BOARD_QUALIFIERS="nrf9160/ns"

SB_CONFIG_SOC="nrf9160"

SB_CONFIG_SOC_SERIES="nrf91"

SB_CONFIG_SOC_FAMILY="nordic_nrf"

SB_CONFIG_SOC_FAMILY_NORDIC_NRF=y

SB_CONFIG_SOC_SERIES_NRF91X=y

SB_CONFIG_SOC_NRF9160=y

SB_CONFIG_SOC_NRF9160_SICA=y

#

# Sysbuild image configuration

#

#

# Modules

#

#

# Available modules.

#

SB_CONFIG_ZEPHYR_GOLIOTH_FIRMWARE_SDK_MODULE=y

SB_CONFIG_ZEPHYR_GOLIOTH_BOARDS_MODULE=y

SB_CONFIG_ZEPHYR_LIBOSTENTUS_MODULE=y

SB_CONFIG_ZEPHYR_NETWORK_INFO_MODULE=y

#

# nrf (/home/ashyvet3/golioth-reference-design-template/vtgwgit/reference-design-template/deps/nrf)

#

SB_CONFIG_PARTITION_MANAGER=y

SB_CONFIG_PM_MCUBOOT_PAD=0x200

# SB_CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY is not set

# SB_CONFIG_PM_OVERRIDE_EXTERNAL_DRIVER_CHECK is not set

SB_CONFIG_BUILD_OUTPUT_BIN=y

SB_CONFIG_BUILD_OUTPUT_HEX=y

SB_CONFIG_BOARD_IS_NON_SECURE=y

SB_CONFIG_APPCORE_REMOTE_BOARD_TARGET_CPUCLUSTER="cpuapp"

SB_CONFIG_APPCORE_REMOTE_DOMAIN="CPUAPP"

#

# Secure Bootloader

#

# SB_CONFIG_SECURE_BOOT_APPCORE is not set

# end of Secure Bootloader

#

# MCUboot configuration

#

# SB_CONFIG_MCUBOOT_HARDWARE_DOWNGRADE_PREVENTION is not set

SB_CONFIG_MCUBOOT_MAX_UPDATEABLE_IMAGES=4

SB_CONFIG_MCUBOOT_APPLICATION_IMAGE_NUMBER=0

SB_CONFIG_MCUBOOT_NETWORK_CORE_IMAGE_NUMBER=-1

SB_CONFIG_MCUBOOT_WIFI_PATCHES_IMAGE_NUMBER=-1

SB_CONFIG_MCUBOOT_QSPI_XIP_IMAGE_NUMBER=-1

SB_CONFIG_MCUBOOT_MCUBOOT_IMAGE_NUMBER=-1

SB_CONFIG_MCUBOOT_MIN_UPDATEABLE_IMAGES=1

SB_CONFIG_MCUBOOT_MIN_ADDITIONAL_UPDATEABLE_IMAGES=0

SB_CONFIG_MCUBOOT_UPDATEABLE_IMAGES=1

SB_CONFIG_MCUBOOT_ADDITIONAL_UPDATEABLE_IMAGES=0

SB_CONFIG_MCUBOOT_APP_SYNC_UPDATEABLE_IMAGES=y

# SB_CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAM is not set

# end of MCUboot configuration

# SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_BUILD is not set

SB_CONFIG_SUPPORT_QSPI_XIP=y

# SB_CONFIG_BT_FAST_PAIR is not set

SB_CONFIG_DFU_ZIP=y

SB_CONFIG_DFU_ZIP_APP=y

# SB_CONFIG_DFU_ZIP_BLUETOOTH_MESH_METADATA is not set

#

# Wi-Fi

#

# SB_CONFIG_WIFI_NRF70 is not set

# end of Wi-Fi

#

# SUIT

#

# SB_CONFIG_SUIT_ENVELOPE is not set

# SB_CONFIG_SUIT_BUILD_RECOVERY is not set

# SB_CONFIG_SUIT_BUILD_FLASH_COMPANION is not set

# end of SUIT

#

# SDP

#

# SB_CONFIG_SDP is not set

# end of SDP

# SB_CONFIG_APPROTECT_USE_UICR is not set

# SB_CONFIG_APPROTECT_LOCK is not set

# SB_CONFIG_APPROTECT_USER_HANDLING is not set

SB_CONFIG_APPROTECT_NO_SYSBUILD=y

# SB_CONFIG_SECURE_APPROTECT_USE_UICR is not set

# SB_CONFIG_SECURE_APPROTECT_LOCK is not set

# SB_CONFIG_SECURE_APPROTECT_USER_HANDLING is not set

SB_CONFIG_SECURE_APPROTECT_NO_SYSBUILD=y

# SB_CONFIG_LWM2M_CARRIER_DIVIDED_DFU is not set

SB_CONFIG_ZEPHYR_NRF_MODULE=y

# end of nrf (/home/ashyvet3/golioth-reference-design-template/vtgwgit/reference-design-template/deps/nrf)

SB_CONFIG_ZEPHYR_MCUBOOT_MODULE=y

SB_CONFIG_ZEPHYR_MBEDTLS_MODULE=y

SB_CONFIG_ZEPHYR_OBERON_PSA_CRYPTO_MODULE=y

SB_CONFIG_ZEPHYR_TRUSTED_FIRMWARE_M_MODULE=y

SB_CONFIG_ZEPHYR_CMSIS_MODULE=y

SB_CONFIG_ZEPHYR_HAL_NORDIC_MODULE=y

SB_CONFIG_ZEPHYR_SEGGER_MODULE=y

SB_CONFIG_ZEPHYR_TINYCRYPT_MODULE=y

SB_CONFIG_ZEPHYR_ZCBOR_MODULE=y

SB_CONFIG_ZEPHYR_NRFXLIB_MODULE=y

#

# Unavailable modules, please install those via the project manifest.

#

# end of Modules

# SB_CONFIG_WARN_EXPERIMENTAL is not set

SB_CONFIG_WARN_DEPRECATED=y

SB_CONFIG_SUPPORT_BOOTLOADER=y

SB_CONFIG_SUPPORT_BOOTLOADER_MCUBOOT_ZEPHYR=y

# SB_CONFIG_BOOTLOADER_NONE is not set

SB_CONFIG_BOOTLOADER_MCUBOOT=y

# SB_CONFIG_MCUBOOT_MODE_SINGLE_APP is not set

SB_CONFIG_MCUBOOT_MODE_SWAP_WITHOUT_SCRATCH=y

# SB_CONFIG_MCUBOOT_MODE_SWAP_SCRATCH is not set

# SB_CONFIG_MCUBOOT_MODE_OVERWRITE_ONLY is not set

# SB_CONFIG_MCUBOOT_MODE_DIRECT_XIP is not set

# SB_CONFIG_MCUBOOT_MODE_DIRECT_XIP_WITH_REVERT is not set

# SB_CONFIG_MCUBOOT_MODE_RAM_LOAD is not set

# SB_CONFIG_MCUBOOT_MODE_FIRMWARE_UPDATER is not set

SB_CONFIG_SIGNATURE_TYPE="ECDSA_P256"

# SB_CONFIG_BOOT_SIGNATURE_TYPE_NONE is not set

# SB_CONFIG_BOOT_SIGNATURE_TYPE_RSA is not set

SB_CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y

# SB_CONFIG_BOOT_SIGNATURE_TYPE_ED25519 is not set

SB_CONFIG_BOOT_SIGNATURE_KEY_FILE="/home/ashyvet3/golioth-reference-design-template/vtgwgit/reference-design-template/deps/bootloader/mcuboot/root-ec-p256.pem"

# SB_CONFIG_BOOT_ENCRYPTION is not set

#

# Build options

#

# SB_CONFIG_COMPILER_WARNINGS_AS_ERRORS is not set

# end of Build options

Hey @ash.vetchip,

Can you check if the device has an IP address by running the command net iface from the device shell and post the output here?

Using Reference Design Template

uart:~$ net i> net iface
face

Interface net0 (0x2000cfd4) () [1]

MTU : 1280
Flags : AUTO_START,IPv4,IPv6
Device : nrf9x_socket (0x60580)
IPv6 not enabled for this interface.
IPv4 unicast addresses (max 1):
10.155.249.192/0.0.0.0 manual preferred infinite
IPv4 multicast addresses (max 2):
224.0.0.1
IPv4 gateway : 0.0.0.0
[00:00:36.439,056] golioth_coap_client_zephyr: Failed to connect to socket: -22
[00:00:36.439,453] golioth_coap_client_zephyr: Failed to connect: -22
[00:00:36.439,453] golioth_coap_client_zephyr: Failed to connect: -22

Using Hello example (with hardcoded credentials)

*** Booting nRF Connect SDK v2.5.2 ***
[00:00:00.514,923] hello_zephyr: main: start hello sample
[00:00:00.515,075] golioth_samples: Bringing up network interface
[00:00:00.515,106] golioth_samples: Waiting to obtain IP address
[00:00:01.948,699] lte_monitor: Network: Searching
[00:00:06.170,928] lte_monitor: Network: Registered (roaming)
[00:00:06.171,966] golioth_mbox: Mbox created, bufsize: 1232, num_items: 10, item_size: 112
uart:~$ > net iface
net iface

Interface net0 (0x2000cd90) () [1]

MTU : 1280
Flags : AUTO_START,IPv4,IPv6
IPv6 unicast addresses (max 2):

IPv6 multicast addresses (max 3):

IPv6 prefixes (max 2):

IPv4 unicast addresses (max 1):
10.155.250.64 manual preferred infinite
IPv4 multicast addresses (max 1):

IPv4 gateway : 0.0.0.0
IPv4 netmask : 0.0.0.0

nRF Multi Cloud example

+CGEV: ME PDN ACT 0,0
+CNEC_ESM: 50,0
+CEREG: 5,“9001”,“0903B30C”,7,“00001010”,“11100000”
%XTIME: “23”,“42213240707523”,“00”
[00:00:05.802,337] cloud_connection: Network connectivity gained!
[00:00:06.802,459] cloud_connection: Network is ready
[00:00:06.802,490] cloud_connection: Connecting to nRF Cloud
[00:00:06.802,551] cloud_connection: Device ID: nrf-352656109831712