https://devzone.nordicsemi.com/f/nordic-q-a/56996/sdk-15-3-0-bootloader-bugs-nrf_bootloadercHello ... Our product uses a secure bootloader based on the SDK 15.3.0 secure_bootloader dfu example. I&#39;ve found a few posts eluding to bugs and would like to confirm whether or not fixed in 15.3. This one appears to be fixed: https://devzone.nordicsemien-USTelligent Community 13Mon, 27 Jan 2020 22:20:39 GMThttps://devzone.nordicsemi.com/thread/231268?ContentTypeID=1Mon, 27 Jan 2020 22:20:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:413287d9-8903-46a4-a149-6b8eba27985aTim<p>Thank you&nbsp;Einar. Very helpful.</p> <p>Tim</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/231064?ContentTypeID=1Mon, 27 Jan 2020 09:55:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:791bce74-6251-4d46-ba7c-b8be21dbfac1Einar Thorsrud<p>Hi Tim,</p> <ul> <li>The reported issue about how GPREGRET is checked in&nbsp;dfu_enter_check() is not fixed. So the current implementation will start DFU mode if any of the bits in&nbsp;BOOTLOADER_DFU_START are set. This is clearly a bug and has been reported, but I do not see it having any practical consequences. The suggested fix is appropriate and can be used if you want to fix it.</li> <li>The reported bug about clearing all of GPREGRET when clearing BOOTLOADER_DFU_START in&nbsp;dfu_enter_flags_clear() is fixed in SDK 15.3.</li> </ul> <p>These GPREGRET related bugs are only relevant if you use the GPREGRET register for something else in addition to the bootloader. If you do not, you can ignore it. If you do, you should implement the suggested fix.</p><div style="clear:both;"></div>