Merge application_update and mqtt_simple

RE: Merge application_update and mqtt_simple

Thabet — Mon, 04 Apr 2022 16:17:55 GMT

Finally this is resolved, thanks @Hakon for showing me this command:

CONFIG_THREAD_NAME=y

After using it I noticed that the problem was related to the workqueue stack size!

Anyone who has this problem, know that the solution is to increase the stack through the configuration: CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE

RE: Merge application_update and mqtt_simple

Thabet — Mon, 04 Apr 2022 14:15:00 GMT

By default I already have this conf:

CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096

The sysworkq thread giving the assert!

RE: Merge application_update and mqtt_simple

Hakon — Mon, 04 Apr 2022 13:58:54 GMT

Also, try setting CONFIG_THREAD_NAME=y to display the thread name.

RE: Merge application_update and mqtt_simple

Hakon — Mon, 04 Apr 2022 13:54:11 GMT

What thread is giving the assert? If it's the download-thread, you can maybe try changing the stack size, CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096.

RE: Merge application_update and mqtt_simple

Thabet — Mon, 04 Apr 2022 12:36:17 GMT

Hello Hakon,

The error occurs inside http.c, on line 83, in the call below:

len = snprintf(client->buf,

CONFIG_DOWNLOAD_CLIENT_BUF_SIZE,

HTTP_GET_RANGE, file, host, client->progress, off);

Could someone from Nordic please help? 20 days of topic, 1 reply, 0 solution. This issue is delaying prototype assembly and field testing!

RE: Merge application_update and mqtt_simple

Thabet — Tue, 29 Mar 2022 13:10:42 GMT

In the link you mentioned, here, I can see that the library is dependent on NEWLIB_LIBC, does this refer to CONFIG_NEWLIB_LIBC_NANO? Isn't this referring to CONFIG_NEWLIB_LIBC?

NEWLIBC NANO isn't a shortened version of NEWLIBC? Wouldn't we have to have the resources present in LIBC NANO within the full LIBC?

I'm not able to track where this error comes from, the error occurs when the download is started, but according to the documentation the http_application_update sample uses the download client library to download the image, the same library used in the download_client sample, but in the download_client sample I can disable no problem to lib nano, doing this I don't get any errors!

So apparently the error is not in the download client library, but why does it occur when it is called in the application_update sample? I've tried tracking the source through "arm-none-eabi-addr2line -e build/zephyr/zephyr.elf 0x0003e0f6" but that doesn't get me anywhere. Could you please help me to track down this error?

RE: Merge application_update and mqtt_simple

Hakon — Tue, 29 Mar 2022 12:36:38 GMT

[quote user="Thabet"]Apparently the application_update example depends on this lib. But I need to disable this lib because of other things in the code. How could I account for this problem and eliminate this dependency on libc nano?[/quote]

The at_cmd parser depends on the CONFIG_NEWLIB_LIBC_NANO config, you need to somehow get rid of this first.

RE: Merge application_update and mqtt_simple

Thabet — Thu, 24 Mar 2022 14:03:38 GMT

I managed to track down what causes this error! I can't disable new libc nano:

CONFIG_NEWLIB_LIBC_NANO=n

Apparently the application_update example depends on this lib. But I need to disable this lib because of other things in the code. How could I account for this problem and eliminate this dependency on libc nano?

I already use the full libc, shouldn't that be enough and make it possible to disable libc nano without causing any problems?

CONFIG_NEWLIB_LIBC=y

Please give me tips on how to get around this, over 1 week and no response from Nordic!

RE: Merge application_update and mqtt_simple

Thabet — Mon, 21 Mar 2022 18:07:29 GMT

I only kept CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096.

My current application is already configured as follows:

# Memory

CONFIG_MAIN_STACK_SIZE=16384

CONFIG_HEAP_MEM_POOL_SIZE=16384

I tried to increase the size but without success!

CONFIG_MAIN_STACK_SIZE=32768

CONFIG_HEAP_MEM_POOL_SIZE=32768

RE: Merge application_update and mqtt_simple

Joao Dullius — Mon, 21 Mar 2022 17:38:15 GMT

Hi,

Have you tried to increase the Stack size?

I noticed the application_update uses higher value than the mqtt simple:

From application_update/proj.conf:

# Heap and stacks

CONFIG_HEAP_MEM_POOL_SIZE=2048

CONFIG_MAIN_STACK_SIZE=8192

From mqtt_simple/proj.conf:

# Memory

CONFIG_MAIN_STACK_SIZE=4096

CONFIG_HEAP_MEM_POOL_SIZE=2048

RE: Merge application_update and mqtt_simple

Thabet — Mon, 21 Mar 2022 17:14:35 GMT

Hello João,

I'm calling dfu_button_pressed(), this worked in the application_update example!

But in my custom application and in the mqtt_simple sample, I find the quoted error.

In the application_update sample and in the merge with the applications I kept the stack settings.

RE: Merge application_update and mqtt_simple

Joao Dullius — Mon, 21 Mar 2022 16:35:09 GMT

Hi Gabriel,

This appears to be a stack overflow on the update thread.

Which command are you calling when you het this stack overflow?

RE: Merge application_update and mqtt_simple

Thabet — Mon, 21 Mar 2022 16:30:03 GMT

I tried to call the function that starts the firmware update from several places, main, workqueue... I always get errors, for example when I call through a thread I get this error:

I: Configuring socket timeout (30 s)
I: Connecting to files.wnology.io
E: ***** USAGE FAULT *****
E:   Stack overflow (context area not valid)
E: r0/a1:  0x0004040a  r1/a2:  0x21040000  r2/a3:  0x0d0f8e00
E: r3/a4:  0x6207ccbf r12/ip:  0x2350734b r14/lr:  0x0000002c
E:  xpsr:  0x2001bc00
E: Faulting instruction address (r15/pc): 0xffffffd9
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x2000f338 (unknown)
E: Resetting system

Please give me tips on how to do this!

RE: Merge application_update and mqtt_simple

Thabet — Wed, 16 Mar 2022 11:38:05 GMT

[quote userid="109559" url="~/f/nordic-q-a/85862/merge-application_update-and-mqtt_simple"]If I remove CONFIG_MODEM_KEY_MGMT=y from prj.conf, the device stops rebooting but nothing works:[/quote]

Updating: By doing this I can now connect and maintain the functionality of the MQTT application, the problem I found in the sequence was related to CONFIG_NRF_MODEM_LIB_SYS_INIT=n, I was maintaining this configuration, but it was not initializing in the nrf_modem_lib_init code, as the idea is to act only in NORMAL MODE, I removed this config from prj.conf.

[quote userid="109559" url="~/f/nordic-q-a/85862/merge-application_update-and-mqtt_simple"]

First I was encountering errors related to the settings below prj.conf:

CONFIG_DOWNLOAD_HOST="nrfconnectsdk.s3.eu-central-1.amazonaws.com"

CONFIG_DOWNLOAD_FILE_V2="app_update.bin"

CONFIG_DOWNLOAD_FILE_V1="app_downgrade.bin"

[/quote]

I solved the problem above too, I just added the HTTP application update sample menu to Kconfig, that is, I merged the Kconfig of the two examples.

But I still don't understand why I should use CONFIG_MODEM_KEY_MGMT=y, and if necessary, what modification to make to be able to use this config. Is this only used if using HTTPS?

How can I modify update_sample_init so that FOTA is started via a call? For example a publish on a topic, I would like to start FOTA this way instead of using a push button!