dfu checking bootloader version/revision?

RE: dfu checking bootloader version/revision?

Mike — Wed, 20 May 2015 11:53:00 GMT

Thanks for the comments!

RE: dfu checking bootloader version/revision?

Hung Bui — Tue, 12 May 2015 11:13:45 GMT

Just a comment, as Øyvind pointed, there is no bootloader version field on the initdata, so no information for the current bootloader to detect which version the new bootloader is coming.

The reason for that is that we want to do it on the master side and before we send the image. There is a DFU revision characteristic in the DFU service. The DFU master should read this characteristic to detect which version of the bootloader is on the target. The DFU master or the maker of .zip image file should take care of the match between softdevice and bootloader.

As far as I know there are following revision: 0x0001: DFU Application (the DFU service embedded in application to start the bootloader) 0x0005: Bootloader in SDK v7.x 0x0006: Bootloader in SDK v8.x

The bootloader in SDK earlier than SDK v7.x doesn't have this revision characteristic.

RE: dfu checking bootloader version/revision?

Øyvind Karlsen — Fri, 08 May 2015 09:07:37 GMT

Hi Mike,

While it is true that the bootloader version field is missing, note that the dfu_init_packet_t uses a very generous 32bits for the app_version. You could for example use the first 16bits in app_version for the bootloader version, and the last 16 for the actual application version.

Unfortunately there is currently no template example for checking the application version.

Hopefully this answers your question,

-Øyvind