DFU support in Fast pair locator tag on nRF52833-DK

[Jignesh shingala]

Hi every one,

If any body have been succeeded  in adding DFU support in Fast pair locator tag on nRF52833-DK, if so can you guide me for it?

I am getting configuration and partition manager error every time.

regards,

Jignesh

[Vidar Berg]

Hi,

DFU should be enabled by default if you select the "release" configuration. Did you try that? 

Best regards,

Vidar

[Jignesh shingala]

Hi Vidar,

With this change it build successful, but when i tried to do dfu with generated dfu_application.zip, it is failing in eneabling bootloader. I have tested with DFU and Device manager apps in both app it is failing in bootloader enable.

Also generated merged.hex file siae is 1214KB and dfu_application.zip size is 420KB.

i have build this code for nRF52833-DK, then how merged.hex file size is possible more than 512KB?

[Vidar Berg]

DFU is done via the app and not within the bootloader, and I'm not sure what "bootloader enable" is in this context. Can you please post the error and logs from the app?

The merged.hex file is using the intelhex format which has ASCII encoding for the data and address records that makes the file significantly larger than a raw binary.

Jignesh shingala said:

dfu_application.zip size is 420KB.

It is containing the application binary both for the first and secondary mcuboot slot, but you will only be uploading one of them (refer to the "direct-xip" bootloader feature for more details on how this works). So the size if your application is roughly 420k / 2 =210 kB

[Jignesh shingala]

Hi Vidar,

Please find attached screenshot of DFU and Device manager app.

 

It is failing in bootloader enable in both app.

[Vidar Berg]

The dfu app shown in the second picture is only supporting legacy dfu. You need to use either the device manager or nrf connect app. Also, the first image from det device manager app is not showing any attempts to upload the fw