Since SDK15.3.0 the DFU example code has changed to require signed DFU commands.The DFU that we used is base very closely on the Nordic example. In our update process we have found that the check for the signature is failing. The information in the documentation seems outdated and does not address how to sign these commands. I'm running nRF Connect Bluetooth Low Energy v3.6.1 and it does not seem to sign the commands or have an option to do so. I cannot find in the DFU code a place that would signal the app to sign messages. I also have not found any questions in the DevZone that address DFU issues past SDK15.2.0. The whole signature check can be bypassed and the DFU will update itself, but we wish to not need to bypass this added security. Updating from an older DFU (pre SDK15.2.0) to a later (post SDK15.3.0) is possible, but as soon as we update the DFU to a late one, we loose the ability to update it again because of this check. How do we properly sign a DFU command?
We have a few projects running SDK16 and SDK17 that will need to migrate to this signed DFU command system, but we are unable to find the key to making that happen in the intended way.
We are developing using Segger Embedded Studio 5.40b on Windows 10 machines. nRF52832 is our SOC.
