Application read the DFU Revision Number.

RE: Application read the DFU Revision Number.

Hung Bui — Mon, 26 Oct 2015 09:57:27 GMT

Hi Cook,

The need for bootloader update is not that big, since it's pretty stable. We usually update the bootloader only when we update the softdevice that makes it not compatible with the bootloader.

If you really want to have the bootloader version when in application mode, you can modify bootloader_settings_t struct, to add uint16_t bootloader_version in, for example. In the bootloader, you keep update the bootloader_version with the correct version when you save the bootloader setting (when calling bootloader_settings_save() ).

Then in the application, you can read in flash at page BOOTLOADER_SETTINGS_ADDRESS (0x0003FC00), to read the bootloader_settings_t struct out.

RE: Application read the DFU Revision Number.

c cook — Fri, 23 Oct 2015 15:00:49 GMT

"I assume that you want to know the bootloader version before you enter bootloader mode. You may have to modify the bootloader in order to do this. I am thinking of simply writing additional information to bootloader setting page on flash and then in your application you can read this information out. If it's what you wanted, could you let me know the reason of that ? "
Hung - This is exactly what I want to do. We have a custom iOS and Android application that connects to our BLE device. On connection it reads the version number of the DFU, Soft Device, and Application. If updates are available, or needed for any of them, the user is prompted to perform a firmware update. We would prefer not to have to start to the DFU to get the actual DFU version number. Updating the settings page should work, but I'm not sure how to accomplish this.

RE: Application read the DFU Revision Number.

Hung Bui — Fri, 23 Oct 2015 10:44:08 GMT

Hi CCook,

Please be noted that the DFU_REVISION in the application code is set as 0x01 (and is fixed as 0x01) to tell the DFU master that it's the application, not the DFU bootloader. And by that knows what to do to put the device in DFU mode.

We may have different DFU_REVISION for DFU bootloader depends on the SDK version, but we will try to keep the DFU_REVISION of the application at 0x01.

The DFU_REVISION mainly made for the DFU master (running on phone or PC) to know which bootloader version is running on the device.

I assume that you want to know the bootloader version before you enter bootloader mode. You may have to modify the bootloader in order to do this. I am thinking of simply writing additional information to bootloader setting page on flash and then in your application you can read this information out.

If it's what you wanted, could you let me know the reason of that ?