NRF52 Secure UART DFU SDK 13.0

RE: NRF52 Secure UART DFU SDK 13.0

rct42 — Fri, 23 Jun 2017 05:00:05 GMT

@Bjorn, thanks for the clarification. I'll manage with 9600 baud.

RE: NRF52 Secure UART DFU SDK 13.0

bjorn-spockeli — Thu, 22 Jun 2017 11:32:43 GMT

Q1: The bootloader was completely re-written from SKD 11 to SDK 12, so I thinks it because we're sending larger objects. Q2: No, we do not have a c library for the Host MCU side.

RE: NRF52 Secure UART DFU SDK 13.0

rct42 — Tue, 20 Jun 2017 21:40:39 GMT

Bjorn, do you also have a suggestion for my second question - is there a C library that allows another embedded device to send the DFU files via a serial port?

RE: NRF52 Secure UART DFU SDK 13.0

rct42 — Tue, 20 Jun 2017 21:38:51 GMT

Thanks Bjorn, the serial DFU is working at 9600 baud without flow control. Out of curiosity, what do you think the reason for having to reduce the baud rate to 9600 for this to work without flow control? The legacy bootloader worked fine for us at 38400 baud...

RE: NRF52 Secure UART DFU SDK 13.0

bjorn-spockeli — Fri, 16 Jun 2017 08:30:26 GMT

You should be able to run the Secure Serial Bootloader without Flow Control with the modifications described in this answer. Note: I think you only have to apply the changes in the secure serial bootloader project and not modify the nrfutil source code since you can set the baudrate and enable/disable flowcontrol, which was not possible in previous versions of nrfutil.

RE: NRF52 Secure UART DFU SDK 13.0

rct42 — Fri, 16 Jun 2017 02:48:30 GMT

I've since confirmed the secure bootloader works with hardware flow control (I needed to swap the control lines). However, I still have yet to get the bootloader working without flow control.

I've uploaded a log of RTT debug messages with flow control enabled here.

Meanwhile the log of RTT debug messages without flow control (here) also starts off with:

WARNING:Received unsupported OP code

but eventually gives the following errors:

ERROR:Error. Init command larger than expected

nrfutil also reports the following error:

pc_ble_driver_py.exceptions.NordicSemiException: Unexpected Executed OP_CODE
Expected: 0x03 Received: 0x31

Suggestions for getting the secure UART bootloader working without flow control?

RE: NRF52 Secure UART DFU SDK 13.0

rct42 — Fri, 16 Jun 2017 01:01:13 GMT

I've got a bit further with nrfutil. I had to supply "-fc 0" as an argument - I suspect that without this, it has flow control enabled by default (why!?!)? Anyway, the command I enter is:

nrfutil dfu serial -pkg dfu_test_app_hrm_s132.zip -p COM3 -fc 0 -b 115200

Meanwhile, the bootloader still reports "Received unsupported OP code", sends a response back ("Sending Response: [0x0, 0x3]"), then has a bunch of errors ("Error. Init command larger than expected" and "Failure to run packet write"), presumably because the nrfutil is trying to send the bootloader packets.

RE: NRF52 Secure UART DFU SDK 13.0

rct42 — Thu, 15 Jun 2017 23:56:46 GMT

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)