BLE OTA using external flash, E: Image in the primary slot is not valid! E: Unable to find bootable imagehttps://devzone.nordicsemi.com/f/nordic-q-a/120384/ble-ota-using-external-flash-e-image-in-the-primary-slot-is-not-valid-e-unable-to-find-bootable-imageHi, I&#39;m trying to use BLE OTA with an external memory due to my application is too big to do it only with the internal memory. When I use OTA config with internal memory, all works ok, but when I try to use it with the external, I get the following erroren-USTelligent Community 13Thu, 03 Apr 2025 08:45:48 GMTRE: BLE OTA using external flash, E: Image in the primary slot is not valid! E: Unable to find bootable imagehttps://devzone.nordicsemi.com/thread/530397?ContentTypeID=1Thu, 03 Apr 2025 08:45:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fa61f088-e202-4bda-91e7-937cc89ae85fH&#229;kon Alseth<p>Glad to hear that it worked out!</p> <p>&nbsp;</p> <p>Kind regards,</p> <p>Håkon</p><div style="clear:both;"></div>RE: BLE OTA using external flash, E: Image in the primary slot is not valid! E: Unable to find bootable imagehttps://devzone.nordicsemi.com/thread/530329?ContentTypeID=1Wed, 02 Apr 2025 21:31:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e5049f3a-3ef9-4c0c-af6e-3b2782c36124Juandgarcia<p>Hi, it&#39;s fixed. I was selecting the wrong board at the build config.&nbsp;</p> <p>Thanks,</p><div style="clear:both;"></div>RE: BLE OTA using external flash, E: Image in the primary slot is not valid! E: Unable to find bootable imagehttps://devzone.nordicsemi.com/thread/530298?ContentTypeID=1Wed, 02 Apr 2025 14:59:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2c50ac4a-7206-41fc-9e35-105e702c401eJuandgarcia<p>Still the same.</p> <p></p> <p><img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1743605912422v1.png" alt=" " /></p> <p></p> <p>Maybe I&#39;m missing something in the prj build??&nbsp;</p> <p></p> <p><img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1743605967530v2.png" alt=" " /></p> <p><img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1743605987521v3.png" alt=" " /></p><div style="clear:both;"></div>RE: BLE OTA using external flash, E: Image in the primary slot is not valid! E: Unable to find bootable imagehttps://devzone.nordicsemi.com/thread/530292?ContentTypeID=1Wed, 02 Apr 2025 14:32:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d382f4b8-4da9-439d-bb85-b096828655c3H&#229;kon Alseth<p>Hi,</p> <p>&nbsp;</p> <p>Thanks for sharing. It looks like the configuration is not picked up for your board.</p> <p>Try renaming &quot;child_image/mcuboot/boards/mcuboot.conf&quot; to &quot;<span>child_image/mcuboot/boards/nrf52840dk_nrf52840.conf&quot; and see if this now works better.</span></p> <p><span>&nbsp;</span></p> <p><span>Kind regards,</span></p> <p><span>Håkon</span></p><div style="clear:both;"></div>RE: BLE OTA using external flash, E: Image in the primary slot is not valid! E: Unable to find bootable imagehttps://devzone.nordicsemi.com/thread/530281?ContentTypeID=1Wed, 02 Apr 2025 14:09:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5f9d4186-5193-4b15-9b44-f18cc99b9484Juandgarcia<p>Hi, removed the withspace and deleted the build, but still have the same error. I&#39;m attaching my tree, if maybe there is something wrong.</p> <p><img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1743603699678v2.png" alt=" " /></p> <p>Thanks</p><div style="clear:both;"></div>RE: BLE OTA using external flash, E: Image in the primary slot is not valid! E: Unable to find bootable imagehttps://devzone.nordicsemi.com/thread/530268?ContentTypeID=1Wed, 02 Apr 2025 13:31:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5cafd0bd-90b1-47b3-bbfb-3ac5a9ce5c4eH&#229;kon Alseth<p>Hi,</p> <p>&nbsp;</p> <p>The run-time output here:</p> [quote user=""]W: Failed reading sectors; BOOT_MAX_IMG_SECTORS=128 - too small?<br />[/quote] <p>does not align with the configuration that you shared here:</p> [quote user=""]<div><span></span></div> <div><span>CONFIG_BOOT_MAX_IMG_SECTORS</span><span>= 256</span></div>[/quote] <p>This also has a whitespace after the equal sign, which will cause a problem when configuring your project.</p> <p>&nbsp;</p> <p>Could you double-check that your mcuboot child image indeed has this configuration set? It might be relevant to delete the build and reconfigure the project to ensure everything is reloaded properly.</p> <p>&nbsp;</p> <p>Kind regards,</p> <p>Håkon</p><div style="clear:both;"></div>