Adding MCUBOOT Bootloader to Peripheral UART example stops SES IDE RTT debug terminal output

RE: Adding MCUBOOT Bootloader to Peripheral UART example stops SES IDE RTT debug terminal output

Einar Thorsrud — Fri, 17 Sep 2021 11:25:48 GMT

Hi,

It should work if you disable RTT by adding this to your application's CMakeLists.txt:

set(mcuboot_CONF_FILE prj.conf ${CMAKE_CURRENT_LIST_DIR}/mcuboot.conf)

and create a file named mcuboot.conf in the same location (your application folder) which you populate with:

CONFIG_USE_SEGGER_RTT=n

RE: Adding MCUBOOT Bootloader to Peripheral UART example stops SES IDE RTT debug terminal output

MBradshaw — Thu, 16 Sep 2021 11:58:28 GMT

I am using the defaults in prj.conf for MCUBoot. I did not enable it in the prj.conf file for ncs/bootloader/mcuboot/boot/zephyr/

MCUBoot proj.conf Settings:

CONFIG_CONSOLE_HANDLER=y
CONFIG_SYSTEM_CLOCK_DISABLE=y
CONFIG_SYS_POWER_MANAGEMENT=n

CONFIG_MAIN_STACK_SIZE=10240
CONFIG_MBEDTLS_CFG_FILE="mcuboot-mbedtls-cfg.h"

CONFIG_BOOT_SWAP_SAVE_ENCTLV=n
CONFIG_BOOT_ENCRYPT_RSA=n
CONFIG_BOOT_ENCRYPT_EC256=n
CONFIG_BOOT_ENCRYPT_X25519=n

CONFIG_BOOT_UPGRADE_ONLY=n
CONFIG_BOOT_BOOTSTRAP=n

### mbedTLS has its own heap
# CONFIG_HEAP_MEM_POOL_SIZE is not set

### We never want Zephyr's copy of tinycrypt. If tinycrypt is needed,
### MCUboot has its own copy in tree.
# CONFIG_TINYCRYPT is not set
# CONFIG_TINYCRYPT_ECC_DSA is not set
# CONFIG_TINYCRYPT_SHA256 is not set

CONFIG_FLASH=y
CONFIG_FPROTECT=y

### Various Zephyr boards enable features that we don't want.
# CONFIG_BT is not set
# CONFIG_BT_CTLR is not set
# CONFIG_I2C is not set

CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=y # former CONFIG_MODE_MINIMAL
### Ensure Zephyr logging changes don't use more resources
CONFIG_LOG_DEFAULT_LEVEL=0
### Decrease footprint by ~4 KB in comparison to CBPRINTF_COMPLETE=y
CONFIG_CBPRINTF_NANO=y

RE: Adding MCUBOOT Bootloader to Peripheral UART example stops SES IDE RTT debug terminal output

Einar Thorsrud — Thu, 16 Sep 2021 11:52:13 GMT

Hi,

Do you by any chance use RTT logging in MCUBoot as well as in your application? If so, that could cause problems. In that case, the easiest fix is to disable RTT logging in MCUBoot.