Exercise 4 – FOTA over LTE-M/NB-IoT

[irsad_kures]

Hi, I try to update firmware with nbiot. I flush 

Exercise 4 – FOTA over LTE-M/NB-IoT  sample in devacademy

�*** Booting nRF Connect SDK 3758bcbfa5cd ***
[00:00:00.251,678] <inf> cloud_connection: Enabling connectivity...
[00:00:00.527,587] <inf> cloud_connection: Setting up nRF Cloud library...
[00:00:00.529,479] <inf> nrf_cloud_fota_common: Saved job: , type: 6, validate: 0, bl: 0x0
[00:00:00.530,303] <inf> cloud_connection: Waiting for network ready...
Hello World! nrf9160dk_nrf9160
+CEREG: 2,"1600","00096967",9
+CSCON: 1
+CGEV: ME PDN ACT 0,0
+CNEC_ESM: 50,0
+CEREG: 1,"1600","00096967",9,,,"00010000","11100000"
[00:01:32.102,722] <inf> cloud_connection: Network connectivity gained!
%XTIME: "21","42501241520121","00"
[00:01:33.102,844] <inf> cloud_connection: Network is ready
[00:01:33.102,874] <inf> cloud_connection: Connecting to nRF Cloud
[00:01:33.102,935] <inf> cloud_connection: Device ID: nrf-351358811477337
[00:01:33.102,996] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING
[00:01:33.103,302] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECT_ERROR: -3
[00:01:33.103,332] <dbg> cloud_connection: clear_readiness_timeout: Stopping cloud connection readiness timeout
[00:01:33.103,332] <inf> cloud_connection: Disconnecting from nRF Cloud
[00:01:33.103,363] <dbg> cloud_connection: disconnect_cloud: Already disconnected from nRF Cloud
[00:01:33.103,393] <err> cloud_connection: Could not connect to nRF Cloud
[00:01:33.103,424] <inf> cloud_connection: Retrying in 60 seconds...

this is my output. actually when I flush asset trcker v2 , it does not matter. it is normal. I can connect to nrf cloud.

but in this example I can not connect to nrf cloud. what must I do? thank you.

[Didrik Rokhaug]

Hi,

What SIM card are you using?

Could it be that it is out of data?

From the log, it looks like the DNS lookup fails. Can you take a modem trace, so that we can see the communication between the modem and the network?

Best regards,

Didrik

[irsad_kures]

trace-2024-05-28T06-59-30.130Z.mtrace

Trace is here , I wait for your response.

[Muhammed]

...

[Muhammed]

I triyed but not working.

[Didrik Rokhaug]

I had another look at the modem trace, and while it originally looked similar to another recent ticket where the problem was that the application tried to use IPv6 while the network only supported IPv4, I saw now that the network doesn't provide you with a DNS server address.

You can provide a fallback DNS server to the modem with nrf_setdnsaddr().

Can you add a call to that function where you provide the IPv4 address of a DNS server?

[Muhammed]

/*

 * Copyright (c) 2012-2014 Wind River Systems, Inc.

 *

 * SPDX-License-Identifier: Apache-2.0

 */

#include <stdio.h>

#include "cloud_connection.h"

#include "nrf_socket.h"

#define CONNECTION_THREAD_STACK_SIZE 2048

/* Define, and automatically start the cloud connection thread. See cloud_connection.c */

K_THREAD_DEFINE(con_thread, CONNECTION_THREAD_STACK_SIZE, cloud_connection_thread_fn,

        NULL, NULL, NULL, 0, 0, 0);

int main(void)

{

    struct nrf_in_addr dns;

    dns.s_addr = 134744072; // Google DNS, 8.8.8.8

    const int err = nrf_setdnsaddr(2, &dns,8);

    printk("DNS set result %d\n", err);

  k_sleep(K_SECONDS(10));

    printf("Hello World! %s\n", CONFIG_BOARD);

    return 0;

}

I added but not working

[Didrik Rokhaug]

Did you get any errors from nrf_setdnsaddr?

nrf_setdnsaddr must be called after the modem library has been initilized (otherwise the modem isn't powered to receive the DNS server address), so it might be better to place it between the calls to conn_mgr_all_if_connect and setup_cloud in cloud_connection_thread_fn.

[Muhammed]

[Didrik Rokhaug]

I might have missed it, but is the return value from nrf_setdnsaddr shown in the log?

Another thing you can try is to set CONFIG_PDN=y and CONFIG_LEGACY_PCO=y. This will tell the modem to use the "legacy" PCO mode, rather than the new extended PCO. Not all networks supports ePCO yet, and it is the PCO configuration that provides the DNS server addresses to the devices.

[Muhammed]

[00:01:24.725,860] <inf> cloud_connection: Network is ready
[00:01:24.725,891] <inf> cloud_connection: Connecting to nRF Cloud
[00:01:24.725,952] <inf> cloud_connection: Device ID: nrf-351516172740011
[00:01:24.726,013] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING
[00:01:30.332,641] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED
[00:01:30.332,672] <inf> cloud_connection: Connected to nRF Cloud
[00:01:30.332,702] <dbg> cloud_connection: cloud_connection_thread_fn: Awaiting disconnection from nRF Cloud
[00:01:31.176,422] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_RX_DATA_SHADOW
[00:01:31.176,452] <dbg> cloud_connection: handle_shadow_event: Shadow: Accepted
[00:01:31.225,830] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED
[00:01:32.774,047] <dbg> cloud_connection: cloud_event_handler: NRF_CLOUD_EVT_READY
[00:01:32.774,078] <dbg> cloud_connection: clear_readiness_timeout: Stopping cloud connection readiness timeout

Yes. It worked THANKS..