https://devzone.nordicsemi.com/f/nordic-q-a/8608/dfu-signingI have had a look at you experimental implementation of DFU signing. I&#39;m very concerned about the code size. The old Bootloader used about 13KB and the new one with signing has allocated 25KB. Let&#39;s assume we use 4KB for MBR and 4KB for App-data, thisen-USTelligent Community 13Fri, 14 Aug 2015 05:05:36 GMThttps://devzone.nordicsemi.com/thread/31505?ContentTypeID=1Fri, 14 Aug 2015 05:05:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2716d572-6a06-42a9-9098-c8fd200187feLucas<p>The size has blown my bootloader start address estimation. If I understand correctly bootloader start address cannot be changed after the bootloader has been flashed. code size reduction would be nice for me as well.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/31504?ContentTypeID=1Wed, 12 Aug 2015 14:22:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:22256451-b204-43f2-97a5-a9931a1ae811Stefan Birnir Sverrisson<p>Hi Freddy</p> <p>Thank you for your feedback. I acknowledge your concern about the size when using bootloader with S130 softdevice. We will try for future development to decrease the size of the bootloader with signing. As I understand it, there is a size/speed tradeoff when doing the signing, where we have prioritized speed apparently. This experimental implementation of DFU signing has primarily been intended for application updates. Is it possible for you to update the softdevice and bootloader separately, in order to make everything fit within the 256k?</p><div style="clear:both;"></div>