why FOTA (application and modem) wasn't downloading the firmware updates when RTT logging was enabled and the debugger was removed

RE: why FOTA (application and modem) wasn't downloading the firmware updates when RTT logging was enabled and the debugger was removed

Kenneth — Tue, 07 Mar 2023 08:42:06 GMT

In terms of why enabling RTT can be problematic I think this is relevant:
https://devzone.nordicsemi.com/f/nordic-q-a/90178/rtt-presence-not-properly-detected

I think the problem may be that the code is hanging because it's not able to flush RTT log. Maybe also some of your child images use RTT?

[quote user="Praveen Deshmane"]3) when CONFIG_LOG_BACKEND_RTT=y and CONFIG_LOG_BACKEND_RTT_MODE_DROP=y, enabled and CONFIG_SHELL_BACKEND_RTT=n, even though fota update was successfully downloaded and why it is reverting to previous version?[/quote]

Do I understand it correctly that everything works if you completely disable RTT (also for child images)?

You have checked that you have called boot_write_img_confirmed()?

Kenneth

RE: why FOTA (application and modem) wasn't downloading the firmware updates when RTT logging was enabled and the debugger was removed

Praveen Deshmane — Mon, 06 Mar 2023 09:17:40 GMT

Hi Kenneth,

Any update?

Best Regards

Praveen Deshmane

RE: why FOTA (application and modem) wasn't downloading the firmware updates when RTT logging was enabled and the debugger was removed

Praveen Deshmane — Fri, 03 Mar 2023 05:01:43 GMT

Hello Kenneth,

I tried to add CONFIG_LOG_BACKEND_RTT_MODE_DROP=y, since it is dependent on

CONFIG_LOG_BACKEND_RTT, I needed to enable this too in prj.conf.

During build process, I encountered below problem.

C:\Users\ift_praveen\ncs\v1.9.1\zephyr\include\toolchain\gcc.h:61:36: error: static assertion failed: "Conflicting log RTT backend enabled on the same channel"
   61 | #define BUILD_ASSERT(EXPR, MSG...) _Static_assert(EXPR, "" MSG)
      |                                    ^~~~~~~~~~~~~~
C:\Users\ift_praveen\ncs\v1.9.1\zephyr\subsys\shell\backends\shell_rtt.c:12:1: note: in expansion of macro 'BUILD_ASSERT'
   12 | BUILD_ASSERT(!(IS_ENABLED(CONFIG_LOG_BACKEND_RTT) &&
      | ^~~~~~~~~~~~
[102/387] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/shell/shell.c.obj
ninja: build stopped: subcommand failed.

Due to "Conflicting log RTT backend enabled on the same channel", I commented out the following configurations in my prj.conf

# CONFIG_SHELL_BACKEND_RTT=y
# CONFIG_SHELL_RTT_INIT_LOG_LEVEL_WRN=y
# CONFIG_SHELL_RTT_LOG_LEVEL_DBG=y

I was successfuly able to build and run the application.

Scenario 1

The device was able to download fota updates when the "debugger is disconnected and RTT enabled". But cannot able to enter shell commands.

After restart, during the bootup the device trying to install the updates, but it is reverted to pevious version.

Scenario 2

The device was able to download fota updates when the "debugger is connected and RTT enabled".

After restart, during the bootup the device trying to install the updates, but it is reverted to pevious version.

MY OBSERVATIONS

I have followed this ticket

ERROR: FOTA download reverted to the previous version nRF9160.

and made sure that

1. boot_write_img_confirmed() is called in the top of main.

2. overall flash layout is equal on both original image and new image

RTT log

[04:45:33.993,700] <dbg> download_client: http_parse: Copying 71 payload bytes
[04:45:33.993,800] <inf> download_client: Downloaded 447559/447559 bytes (100%)
[04:45:33.993,800] <inf> download_client: Download complete
[04:45:34.092,600] <inf> dfu_target_mcuboot: MCUBoot image upgrade scheduled. Reset device to apply
[04:45:34.094,800] <dbg> UPDATE_TH: fota_dl_event_handler: FOTA DOWNLOAD FINISHED
[04:45:34.094,800] <dbg> UPDATE_TH: fota_dl_event_handler: FOTA_DOWNLOAD_EVT_FINISHED
messages dropped:   1 
[04:45:34.095,100] <dbg> UPDATE_TH: fota_dl_event_handler: App download is complete!

MY QUESTIONS

1) when i was using CONFIG_SHELL_BACKEND_RTT=y is enabled and debugger is connected, the device was able to downoad fota and updated to new version. why cant now?

2) when CONFIG_SHELL_BACKEND_RTT=y is enabled and debugger is disconnected
why fota was not able to download the updates?

3) when CONFIG_LOG_BACKEND_RTT=y and CONFIG_LOG_BACKEND_RTT_MODE_DROP=y, enabled and CONFIG_SHELL_BACKEND_RTT=n, even though fota update was successfully downloaded and why it is reverting to previous version?

NOTE

I am not calling LOG_PANIC() anywhere in my application.

Best Regards

Praveen Deshmane

RE: why FOTA (application and modem) wasn't downloading the firmware updates when RTT logging was enabled and the debugger was removed

Kenneth — Thu, 02 Mar 2023 11:38:23 GMT

Hi,

You should use CONFIG_LOG_BACKEND_RTT_MODE_DROP=y, so please add that in any case.

Can you check if you are calling LOG_PANIC() anywhere? I do believe this call is blocking until log buffer is empty, so you may need to comment this one out.

Kenneth

RE: why FOTA (application and modem) wasn't downloading the firmware updates when RTT logging was enabled and the debugger was removed

Praveen Deshmane — Thu, 02 Mar 2023 09:50:36 GMT

Hello Kenneth,

Thank you for your reply.

Here is the complete prf.conf file

CONFIG_TRUSTED_EXECUTION_NONSECURE=y


# General config
CONFIG_REBOOT=y
CONFIG_RING_BUFFER=y

# LOGGNG
CONFIG_LOG=y
CONFIG_LOG_BUFFER_SIZE=2048
CONFIG_LOG2_MODE_DEFERRED=y
CONFIG_CBPRINTF_FP_SUPPORT=y
CONFIG_LOG_DEFAULT_LEVEL=4

# Console
CONFIG_PRINTK=y
CONFIG_UART_CONSOLE=n
CONFIG_SHELL=y
CONFIG_KERNEL_SHELL=y
CONFIG_DEVICE_SHELL=y
CONFIG_POSIX_CLOCK=y
CONFIG_DATE_SHELL=y
CONFIG_SHELL_STACK_SIZE=1536
CONFIG_SHELL_BACKEND_SERIAL=n
CONFIG_SHELL_LOG_BACKEND=y
CONFIG_SHELL_RTT_LOG_LEVEL_DBG=y
CONFIG_SHELL_RTT_INIT_LOG_LEVEL_WRN=y

CONFIG_THREAD_MONITOR=y
CONFIG_INIT_STACKS=y
CONFIG_BOOT_BANNER=n
CONFIG_THREAD_NAME=y

#enable RTT shell
CONFIG_USE_SEGGER_RTT=y
CONFIG_SHELL_BACKEND_RTT=y
CONFIG_SEGGER_RTT_BUFFER_SIZE_DOWN=32

# UART
CONFIG_UART_ASYNC_API=y

# Modem library
CONFIG_NRF_MODEM_LIB=y
CONFIG_MODEM_INFO=y

CONFIG_MODEM_KEY_MGMT=y
CONFIG_DOWNLOAD_CLIENT=y


CONFIG_NEWLIB_LIBC=y

CONFIG_NEWLIB_LIBC_NANO=n

# LTE link control
CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_NETWORK_MODE_LTE_M=y
CONFIG_LTE_AUTO_INIT_AND_CONNECT=n

CONFIG_LTE_LOCK_BANDS=y
CONFIG_LTE_LOCK_BAND_MASK="0000000001000000000000000000"

# Network
CONFIG_NETWORKING=y
CONFIG_NET_NATIVE=n
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_OFFLOAD=y

# PDN library
CONFIG_PDN=y
CONFIG_PDN_SYS_INIT=n
CONFIG_PDN_DEFAULTS_OVERRIDE=y
CONFIG_PDN_DEFAULT_APN="myapn"
CONFIG_PDN_DEFAULT_FAM_IPV4=y
CONFIG_PDN_DEFAULT_AUTH_CHAP=y
CONFIG_PDN_DEFAULT_USERNAME="username"
CONFIG_PDN_DEFAULT_PASSWORD="password"


CONFIG_AGPS_OFFLINE_FLG=y


CONFIG_HEAP_MEM_POOL_SIZE=29696

# for debug
CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_DEBUG_THREAD_INFO=y

CONFIG_OPENOCD_SUPPORT=y
CONFIG_MAIN_STACK_SIZE=8192
CONFIG_PRIVILEGED_STACK_SIZE=1024
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096


# Flash
CONFIG_SPI=y
CONFIG_FLASH=y

# I2C
CONFIG_I2C_NRFX=y
CONFIG_I2C=y

#IMU
CONFIG_SENSOR=y
CONFIG_ICM42605=y
CONFIG_ICM42605_TRIGGER_NONE=y


# json
CONFIG_JSON_LIBRARY=y

CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y

# for Zmod library
CONFIG_FPU=y
CONFIG_FPU_SHARING=y
CONFIG_FP_HARDABI=y

CONFIG_CPU_LOAD=y

CONFIG_DATE_TIME=y


CONFIG_APP_VERSION="v0.0.4"

CONFIG_DEVELOP_MODE=y

CONFIG_CJSON_LIB=y
CONFIG_FOTA_DOWNLOAD=y
CONFIG_FOTA_SOCKET_RETRIES=5

#DFU 
CONFIG_DFU_TARGET=y

# MCUBOOT
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUBOOT_IMG_MANAGER=y

# Image manager
CONFIG_IMG_MANAGER=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y

# Download client
CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096
CONFIG_DOWNLOAD_CLIENT_BUF_SIZE=2048
CONFIG_DOWNLOAD_CLIENT_HTTP_FRAG_SIZE_1024=y
CONFIG_DOWNLOAD_CLIENT_RANGE_REQUESTS=n
CONFIG_DOWNLOAD_CLIENT_LOG_LEVEL_DBG=y
CONFIG_DOWNLOAD_CLIENT_LOG_HEADERS=y
CONFIG_DOWNLOAD_CLIENT_TCP_SOCK_TIMEO_MS=600000 


# DFU Target
CONFIG_DFU_TARGET_STREAM=y
CONFIG_DFU_TARGET_FULL_MODEM=y

# Full modem firmware from external flash support
CONFIG_FMFU_FDEV=y
CONFIG_CDDL_GEN=y

#SPI NOR
CONFIG_SPI_NOR=y

#Stream flash
CONFIG_STREAM_FLASH=y
CONFIG_STREAM_FLASH_ERASE=y

#libmodem
CONFIG_NRF_MODEM_LIB_SYS_INIT=n

#Prevalidation is not yet supported by the modem firmware, so skip it for now.
CONFIG_FMFU_FDEV_SKIP_PREVALIDATION=n

CONFIG_NO_OPTIMIZATIONS=y
CONFIG_EXTRA_EXCEPTION_INFO=y
CONFIG_NCS_SAMPLES_DEFAULTS=n

# Crypto
CONFIG_OBERON_BACKEND=y
CONFIG_NORDIC_SECURITY_BACKEND=y
# Disable all non-used crypto
CONFIG_NRF_SECURITY_RNG=n
CONFIG_MBEDTLS_AES_C=n
CONFIG_MBEDTLS_CHACHA20_C=n
CONFIG_MBEDTLS_POLY1305_C=n
CONFIG_MBEDTLS_ECP_C=n
CONFIG_MBEDTLS_RSA_C=n
CONFIG_MBEDTLS_DHM_C=n
CONFIG_MBEDTLS_SHA1_C=n
CONFIG_MBEDTLS_SHA384_C=n
CONFIG_MBEDTLS_SHA512_C=n
CONFIG_MBEDTLS_GCM_C=n
# This is the one we need
CONFIG_MBEDTLS_SHA256_C=y

I tried adding CONFIG_LOG_BACKEND_RTT_MODE_DROP

It doesnt worked.

Best regards

Praveen Deshmane

RE: why FOTA (application and modem) wasn't downloading the firmware updates when RTT logging was enabled and the debugger was removed

Kenneth — Wed, 01 Mar 2023 16:58:15 GMT

Hello,

Can you make sure you are using CONFIG_LOG_BACKEND_RTT_MODE_DROP=y instead of BLOCK:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_LOG_BACKEND_RTT_MODE

Best regards,
Kenneth