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

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

Muhammed — Thu, 06 Jun 2024 09:01:25 GMT

[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..

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

Didrik Rokhaug — Thu, 06 Jun 2024 08:50:40 GMT

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.

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

Muhammed — Thu, 06 Jun 2024 06:53:13 GMT

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

Didrik Rokhaug — Wed, 05 Jun 2024 08:25:09 GMT

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.

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

Muhammed — Fri, 31 May 2024 13:59:25 GMT

* 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

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

Didrik Rokhaug — Fri, 31 May 2024 11:28:31 GMT

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?

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

Muhammed — Wed, 29 May 2024 12:58:14 GMT

I triyed but not working.

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

Muhammed — Wed, 29 May 2024 12:57:18 GMT

...

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

Didrik Rokhaug — Wed, 29 May 2024 12:40:28 GMT

Can you try to set CONFIG_NET_IPV6=n?

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

irsad_kures — Wed, 29 May 2024 07:24:00 GMT

devzone.nordicsemi.com/.../trace_2D00_2024_2D00_05_2D00_29T07_2D00_13_2D00_45.407Z.mtrace

I tried again as you said. can you help again?

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

Didrik Rokhaug — Tue, 28 May 2024 12:31:22 GMT

Did you edit the application to enable modem traces?

https://docs.nordicsemi.com/bundle/nrf-connect-cellularmonitor/page/requirements.html#software-requirements

I also recommend that you reset the device after starting the trace, so that you are sure the trace captures everything from the start.

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

Muhammed — Tue, 28 May 2024 08:52:28 GMT

Mr. Irşad and I are together now. He flashed the FOTA code in Exercise 4. Then we took the trace from the Cellular Monitor screen. But when we take it, we see that it takes a low byte. Is there something we did wrong?

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

irsad_kures — Tue, 28 May 2024 08:45:56 GMT

devzone.nordicsemi.com/.../WhatsApp-Video-2024_2D00_05_2D00_28-saat-11.43.13_5F00_af97f015.mp4

we tried like this after flushing, is it correct?

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

Didrik Rokhaug — Tue, 28 May 2024 08:18:14 GMT

Unfortunately, that trace file is not valid.

All bytes in it is 0. Besides, I would expect a proper trace that captures this situation to be around a couple hundred kilobytes, not just 256 bytes.

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

irsad_kures — Tue, 28 May 2024 07:04:35 GMT

devzone.nordicsemi.com/.../trace_2D00_2024_2D00_05_2D00_28T06_2D00_59_2D00_30.130Z.mtrace

Trace is here , I wait for your response.

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

Didrik Rokhaug — Wed, 22 May 2024 14:32:56 GMT

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