NRF52 Secure UART DFU SDK 13.0

[rct42]

Greetings,

I'm having trouble being able to perform a DFU with the secure serial DFU. My setup:

• Using PCA10040 (nRF52832) with the s132_nrf52_4.0.2_softdevice.hex
• SDK v13.0.0, Keil v5.20, on a Windows 8 PC
• nRFgo Studio 1.21.2.10
• experimental_bootloader_secure_serial without flow control, 115200 baud

I'm using the secure DFU example (v13.0.0\examples\dfu\experimental_bootloader_secure_serial\pca10040_debug). The only modification I have made is to disable flow control (by editing nrf_serial_dfu.c:371). After programming the bootloader, I look at the debug messages via RTT. If I try to upload the demo app (dfu_test_app_hrm_s132.zip) via nRF Studio, I get "Received unsupported OP code" (and the op code is 0 if I step through using the debugger). Serial data is being exchanged between the PC and the PCA10040, as observed on an oscilloscope.

Meanwhile, I've tried another way of performing a DFU using the command: "nrfutil dfu serial -pkg dfu_test_app_hrm_s132.zip -p COM3 -b 115200". However, I get the error "pc_ble_driver_py.exceptions.NordicSemiException: No ping response". There is also no activity on the TX/RX data lines. I am using nrfutil version 2.3.0.

Questions:

1. Can someone confirm they have been able to perform a DFU via UART with the bootloader and examples in provided SDK 13?
2. Is there an example how to get another embedded device to perform the DFU? The target application is one with two microcontrollers where the master will transmit the NRF52 firmware update via UART from a SD card. [I've got this feature working with the old/legacy serial bootloader on a NRF51 and SDK v9.0, just upgrading the system to a NRF52 and SDK v13.0 for the extra BLE features]

[rct42]

I've just noticed a very similar thread. In my case, I cannot use flow control and also require another embedded device to perform the DFU (but would like to get it working with nrfutil first)