Bootloader MCUBoot and dfu serial

[MatthiasJ]

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

[Amanda Hsieh]

Hi, 

Try to add the following config into child_image/mcuboot.conf:

CONFIG_USB_DEVICE_VID=0x1915
CONFIG_USB_DEVICE_PID=0x5300

-Amanda H.

[MatthiasJ]

Thank you for answering. But maybe I missed some points for details. I tried to use the nrfutil dfu via serial, no USB.

I'm using a FTDI 3V3 UART converter.

Maybe you have also some comments.

Kind regards,

Matthias

[MatthiasJ]

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)

[Amanda Hsieh]

Hi, 

From the team, the nRF Util currently only supports known Nordic kits/samples like thingy:53 etc for DFU updates via UART. We are working to support more use cases in the next release. Sorry for the inconvenience. 

-Amanda H.

[MatthiasJ]

Hi,

so it's possible to use the "old" nrf sdk DFU in the new nrfconnect MCUboot bootloader. That support the SMP DFU protocol and the nrf DFU? It's only not possible to test with the command line tool?

Kind regards,

Matthias

[Amanda Hsieh]

Hi, 

MatthiasJ said:

so it's possible to use the "old" nrf sdk DFU in the new nrfconnect MCUboot bootloader. That support the SMP DFU protocol and the nrf DFU?

The current nRF Util can support only known Nordic kits/samples like thingy:53. 

MatthiasJ said:

It's only not possible to test with the command line tool?

No, nRF Command Line Tool cannot support updating DFU. 

-Amanda H.

[MatthiasJ]

Hi,

my question was more about the MCUBoot and not the nRF Util.

Does the MCUBoot support also the "old" nrf sdk DFU protocol. So that its behaving like the bootloader examples from the nrf sdk 17 or older?

[Amanda Hsieh]

Hi,

MatthiasJ said:

Does the MCUBoot support also the "old" nrf sdk DFU protocol.

The mcuboot doesn't support the nRF5 SDK DFU protocol. Their roles are the same, but they are different protocols. The nRF5 SDK bootloader cannot support SMP DFU, and the mcuboot cannot support nRF5 SDK DFU. 

-Amanda