Bootloader MCUBoot and dfu serial

I managed to setup a Demo App on the base on zephyr that uses MCUBoot as bootloader in multi image build, using the nRF Connect SDK.

Upload via SMP DFU with mcumgr is working.

But I would like to use nrfutil dfu  protocol via serial/uart. I found several CONFIG flags but none worked for me.

Any suggestions what CONFIG is missing or did I need to choose a other bootloader, the open_bootloader?

I'm using the nRF52 DK (PCA10040), nrf52dk_nrf52832.

I used this MCUBoot config child_image/mcuboot.conf

CONFIG_CONSOLE=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n

# Enable MCUboot Serial Recovery
CONFIG_MCUBOOT_SERIAL=y
# DT_ALIAS(mcuboot_button0) is been used to detect entrance, set in overlay
CONFIG_BOOT_SERIAL_ENTRANCE_GPIO=y
CONFIG_BOOT_SERIAL_DETECT_DELAY=200
CONFIG_BOOT_SERIAL_WAIT_FOR_DFU=y
CONFIG_BOOT_SERIAL_NO_APPLICATION=y

CONFIG_MAIN_STACK_SIZE=10240
CONFIG_NCS_MCUBOOT_IN_BUILD=y
CONFIG_PARTITION_MANAGER_ENABLED=y
CONFIG_FPROTECT=y
CONFIG_FLASH=y
CONFIG_CBPRINTF_NANO=y

CONFIG_LOG=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_MODE_IMMEDIATE=y

CONFIG_LOG_DEFAULT_LEVEL=4

Kind regards,

Matthias

Parents Reply
  • Ah, ok. Thanks I only used to know the pypi tool.

    The first with USB connected to the dev board. Second one only serial adapter connected, while chip is in bootloader serial recovery.

    dev@dev-virtual-machine:/home/dev/Downloads# ./nrfutil device list
    1050348880
    product         J-Link
    device version  NRF52832_xxAA_REV3
    board version   PCA10040
    ports           /dev/ttyACM0, vcom: 0
                    /dev/ttyACM1, vcom: 1
                    /dev/ttyUSB0, vcom: 2
    traits          jlink, seggerUsb, serialPorts, usb
    
    Found 1 supported device(s)
    
    dev@dev-virtual-machine:/home/dev/Downloads# ./nrfutil device list
    FT94TNNW
    product         TTL232R-3V3
    ports           /dev/ttyUSB0
    traits          serialPorts, usb
    
    Found 1 supported device(s)

Children
Related