https://devzone.nordicsemi.com/f/nordic-q-a/100810/mcuboot-headerHi, I&#39;m using MCUBoot in my application but this last would hardfault all the time. I figured that the a MCUBoot header was inserted at the beginning of the code partition and that this header is considered as a partition by MCUBoot . Therefore, whenen-USTelligent Community 13Thu, 15 Jun 2023 08:42:41 GMThttps://devzone.nordicsemi.com/thread/431174?ContentTypeID=1Thu, 15 Jun 2023 08:42:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f775ca49-8b50-4906-8642-2945acc75600Hieu<p>Hi Hugo,</p> <p>If you are using the nRF Connect SDK, then</p> <ul> <li><a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.0/nrf/app_dev/multi_image/index.html">MCUboot is built as a child image of the application</a>.</li> <li><a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.0/nrf/scripts/partition_manager/partition_manager.html#partition-manager">The Partition Manager (PM)</a> is in effect, completely superseding any partitioning made in the Devicetree. <ul> <li>The PM will make sure the partition information is shared well between the different images, as well as MCUboot having access to all the data it needs properly.</li> </ul> </li> </ul> <p>Therefore, in almost all cases, you don&#39;t have to do anything special and MCUboot will&nbsp;have proper access to its data.</p> <p>Regards,</p> <p>Hieu</p><div style="clear:both;"></div>