RE: Secure serial DFU example question

Andres — Thu, 04 Mar 2021 19:17:49 GMT

Hi Einar,

I figured this out.

The DFU of the Blinky example was in the middle of the Softdevice area. As you noted, the Blinky example does not need the Softdevice. However, I recompiled the Blinky example to start at flash address 0x26000 and I added the Softdevice ID (0x101) to the DFU package for the Blinky.

And now I can go back and forth between the DFU of the Blinky example and the DFU of the HRS example.

In summary the bootloader is working fine. But I had to properly build and compile the examples keeping an eye on their flash locations and assuming there is a Softdevice installed.

Perhaps a warning for future DFU users is to be cautious of using the examples provided in \nRF5_SDK_17.0.2_d674dde\examples\dfu\secure_dfu_test_images\uart\nrf52832, e.g., blinky_mbr.zip and hrs_application_s132.zip since they are incompatible. I guess you can tell right away from their names "_mbr" and "_s132" that they make different assumptions. I learned the hard way :)

Thank you.

RE: Secure serial DFU example question

Einar Thorsrud — Thu, 04 Mar 2021 13:19:48 GMT

Hi,

I see from step 4 that you have programmed the SoftDevice. However this is not used by the serial bootloader so that in itself does not show that it is correctly programmed (other than the MBR, which is the first page in the SoftDevice hex and is needed by the bootloader). Can you double check that the correct SoftDevice is programmed?

On the same note, the Blinky example has no dependency on the SoftDevice. The HRS example on the other hand, has. Can you double check that you have build the HRS example for the exact same SoftDevice version? And can you check that it work with that SoftDevice if you program only the SoftDevice and HRS app, but not bootloader via nRF Connect Programmer?

Lastly, can you explain in what way it fails (when you write" Not OK XXXXXXXX")? Any logs or error messages?

Einar