DFU example for NRF_DFU_OP_FIRMWARE_VERSION

Question

Is there any code example for Android or iOS on how to build / send a DFU request for NRF_DFU_OP_FIRMWARE_VERSION and then how to interpret the response that comes back? 
 Does it not make sense for the DFU module from inside the nRF Toolbox to also have a way to send this request to a device in DFU mode for instance to check the existing values that are programmed in the device? (and then show a popup to the user for instance to let him know if he needs to update things)?

Aleksander Nowakowski · Answer

Hi @Catalin, @mrono, 
 Both Legacy (since SDK 7.1) and Secure DFU provide a security check to prevent wrong firmware to be flashed on your device. In the init packet there is hardware identifier. IDs of required softdevice(s). 
 Secure DFU and late Legacy DFU (optinally) prevent also from flashing modified fw by checking the hash and signature (although Legacy DFU does it incorrectly and device still can be bricked, even having a valid fw file). 
 The following requests: 
 NRF_DFU_OP_MTU_GET = 0x07, //!< Retrieve MTU size.
NRF_DFU_OP_OBJECT_WRITE = 0x08, //!< Write selected object.
NRF_DFU_OP_PING = 0x09, //!< Ping.
NRF_DFU_OP_HARDWARE_VERSION = 0x0A, //!< Retrieve hardware version.
NRF_DFU_OP_FIRMWARE_VERSION = 0x0B, //!< Retrieve firmware version.
NRF_DFU_OP_ABORT = 0x0C 
 were added to the DFU for the sake of the new nRF52840 Dongle, which uses DFU to flash firmware. On BLE such requests should either return the requested value, or return NOT SUPPORTED status code. 
 However, as I tested it out, the bootloader replies with 0x60-[Command ID]-01 (success), but the value is empty. According to me it's a bug and I reported it to the SDK team. I don't know which way they decide to go.

DFU example for NRF_DFU_OP_FIRMWARE_VERSION

Top Replies