https://devzone.nordicsemi.com/f/nordic-q-a/80808/ncs-mcuboot-chainload-failingI have the following pm_static.yml defined for my project (nrf52840 on a custom board, NCS v1.7-branch): west build -t partition_manager_report shows this is working as expected. west flash writes the amount of bytes I expect for my combined applicationen-USTelligent Community 13Wed, 20 Oct 2021 11:55:28 GMThttps://devzone.nordicsemi.com/thread/335081?ContentTypeID=1Wed, 20 Oct 2021 11:55:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:06e8143d-cb44-427a-91a0-4c47eef4b7d9Elfving<p>Hey Benjamin!</p> <p>I am glad you found the solution to your problem! Yes, that is correct. It needs to compatible with the alignment of the&nbsp;vector table.</p> <p>With partition manager <a href="https://github.com/nrfconnect/sdk-mcuboot/blob/master/boot/zephyr/Kconfig#L26">it is this value that is used.&nbsp;</a>&nbsp;You can also see it described a bit on <a href="https://developer.arm.com/documentation/dui0552/a/cortex-m3-peripherals/system-control-block/vector-table-offset-register?lang=en">ARMs developer pages</a>.</p> <p>Best regards,</p> <p>Elfving</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/334957?ContentTypeID=1Tue, 19 Oct 2021 23:57:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:340afcf0-a7f3-437c-b548-bc3d89400e54Benjamin<p>Upon further investigation into mcuboot&#39;s source, it seems that this padding size is also used for vector table offset (presumably because the interrupt vector table is at the beginning of the image) which must be appropriately aligned. For&nbsp;the nRF52840 the minimum size is thus 0x200.</p> <p>Neither the comment <a href="https://github.com/nrfconnect/sdk-mcuboot/blob/master/boot/zephyr/pm.yml#L40-L41">here</a> nor the comment for CONFIG_PM_PARTITION_SIZE_MCUBOOT_PAD reference the importance of this partition size.</p><div style="clear:both;"></div>