I have a suggestion for an additional feature to nRF Connect for Desktop:
When doing DFU with a zip package that contains a bootloader + softdevice -combo and an application, nRF Connect tries to update everything that is in the zip package. It would be useful to have the option to only update the application, even if the zip package contains the other parts as well.
Background: We are going to release the firmware updates to our products as 'complete' DFU zip packages that always have the latest bootloader and softdevice also included. Our iOS and Android apps can ask the device for installed versions and then decide to only update the application if the latest bootloader and softdevice are already installed.
During development I often use nRF Connect for DFU. I have set up my build tools to generate these 'complete' zip packages, but I can't use them with nRF Connect. The update fails, as nRF Connect tries to update the bootloader to the same version that is already installed. This is expected, I have intentionally not allowed re-flashing the bootloader with the same or lower version. What's missing is the ability to tell nRF Connect to not try to update the bootloader.
This isn't a major issue, I have a workaround in the form of an additional post-build step that generates a DFU package with just the application. However I'd like to use the actual output files as much as possible.
