https://devzone.nordicsemi.com/f/nordic-q-a/89235/updating-bootloader-softdevice-fails-with-error-the-new-softdevice-is-of-a-different-family-than-the-present-softdevice-compatibility-cannot-be-guaranteedHi, I&#39;m trying to perform a Bootloader+Softdevice DFU over BLE. The image that I currently have in the NRF52 DK is BL+S112 and I&#39;m trying to perform a DFU with BL+S132. I&#39;m using the nRF5 SDK 17.1.0 and the soft devices versions are s112nrf52720 and s132nrf52720en-USTelligent Community 13Wed, 22 Jun 2022 11:27:12 GMThttps://devzone.nordicsemi.com/thread/373647?ContentTypeID=1Wed, 22 Jun 2022 11:27:12 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b439caee-184d-4b06-891b-5110bcd586c0Einar Thorsrud<p>Hi André,</p> <p>There is no fundamental reason that updating to a SoftDevice should not work, except from that check. The reason for the check is that we do not test it, and therefor it is not supported and prevented by the code snippet you have referred to. If you have devices you want to update to a different SoftDevice type via DFU that is still possible, but you would have to do it in two stages. First, update the bootloader to a temporary bootloader using the same old SoftDevice where you remove this test, so that updates to different SoftDevice types is not prevented. Then you can do a new DFU update with a new package that include the new SoftDevice and new bootloader built for that SoftDevice.</p> <p>Br,</p> <p>Einar</p><div style="clear:both;"></div>