https://devzone.nordicsemi.com/f/nordic-q-a/111178/mcuboot-bootloader-infoHi, TLDR: Tried the new BLINFO feature on an existing app, upgrading to 2.6.1 SDK (Zephyr 3.5.99). App does not boot after merged.hex flashed. So we are updating our project to NRF SDK 2.6.1. I saw that this version of the sdk use a version of Zephyren-USTelligent Community 13Wed, 15 May 2024 13:44:11 GMThttps://devzone.nordicsemi.com/thread/483529?ContentTypeID=1Wed, 15 May 2024 13:44:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3cb0f61c-c04c-4418-aebe-32638ded2cf7Einar Thorsrud<p>Hi,</p> <p>nRF Connect SDK 2.6.x includes a Zephyr &quot;version&quot; between 3.5 and 3.6 (see <a href="https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/nrf/releases_and_maturity/releases/release-notes-2.6.1.html#zephyr">release notes</a> for details), and that inclues <a href="https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/zephyr/services/retention/blinfo.html">bootloader information</a>. It was new at that time though and there may be issues.</p> <p>I have not used this feature though, nor found any examples of anyone usig it, but I will look into it and get back to you.</p><div style="clear:both;"></div>