<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/113100/nrf5340-mcuboot-issue-with-multi-image-update-when-sb_config_secure_boot_appcore-is-enabled</link><description>Hi. I had a working MCUboot configuration that I used in order to update both the app core and the net core as follows: 
 - Upload the app core image using mcumgr - Upload the net core image using mcumgr - Activate the app core image using mcumgr ( https</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 08 Jul 2025 10:30:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/113100/nrf5340-mcuboot-issue-with-multi-image-update-when-sb_config_secure_boot_appcore-is-enabled" /><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/541775?ContentTypeID=1</link><pubDate>Tue, 08 Jul 2025 10:30:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b12717d-f040-4db4-81a6-549ded2ca597</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This API is used for sending:&lt;/p&gt;
&lt;p&gt;&lt;a title="https://github.com/nordicsemiconductor/android-nrf-connect-device-manager/blob/fc9b6091de37a19e913d90ff87b3a181c616a66f/mcumgr-core/src/main/java/io/runtime/mcumgr/dfu/mcuboot/firmwareupgrademanager.java#l332" href="https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/fc9b6091de37a19e913d90ff87b3a181c616a66f/mcumgr-core/src/main/java/io/runtime/mcumgr/dfu/mcuboot/FirmwareUpgradeManager.java#L332" rel="noopener noreferrer" target="_blank"&gt;https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/fc9b6091de37a19e913d90ff87b3a181c616a66f/mcumgr-core/src/main/java/io/runtime/mcumgr/dfu/mcuboot/FirmwareUpgradeManager.java#L332&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;And here set is created&lt;/p&gt;
&lt;p&gt;&lt;a title="https://github.com/nordicsemiconductor/android-nrf-connect-device-manager/blob/fc9b6091de37a19e913d90ff87b3a181c616a66f/mcumgr-core/src/main/java/io/runtime/mcumgr/dfu/mcuboot/model/imageset.java#l60" href="https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/fc9b6091de37a19e913d90ff87b3a181c616a66f/mcumgr-core/src/main/java/io/runtime/mcumgr/dfu/mcuboot/model/ImageSet.java#L60" rel="noopener noreferrer" target="_blank"&gt;https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/fc9b6091de37a19e913d90ff87b3a181c616a66f/mcumgr-core/src/main/java/io/runtime/mcumgr/dfu/mcuboot/model/ImageSet.java#L60&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;And here zip is unpacked:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a title="https://github.com/nordicsemiconductor/android-nrf-connect-device-manager/blob/main/sample/src/main/java/io/runtime/mcumgr/sample/utils/zippackage.java" href="https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/main/sample/src/main/java/io/runtime/mcumgr/sample/utils/ZipPackage.java" rel="noopener noreferrer" target="_blank"&gt;&lt;span&gt;https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager/blob/main/sample/src/main/java/io/runtime/mcumgr/sample/utils/ZipPackage.java&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Another comment is that&amp;nbsp;but seems that the easiest way for you will be to change the order in manifest.json file for DFU package, i.e manually&amp;nbsp;&lt;span&gt;change the order in this file (netcore first and then app core) and it should be enough&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Let me know if this works,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kind regards,&lt;br /&gt;Andreas&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/541758?ContentTypeID=1</link><pubDate>Tue, 08 Jul 2025 09:19:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:211709b7-dae9-42b0-8183-738ec01abadf</guid><dc:creator>Hayden Ball</dc:creator><description>&lt;p&gt;Thank you &lt;a href="https://devzone.nordicsemi.com/members/ahaug"&gt;AHaug&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Are you able to provide an example of how to do this using the Android and iOS libraries at&amp;nbsp;&lt;a id="" href="https://github.com/nordicSemiconductor/Android-nRF-Connect-Device-Manager"&gt;https://github.com/nordicSemiconductor/Android-nRF-Connect-Device-Manager&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a id="" href="https://github.com/NordicSemiconductor/IOS-nRF-Connect-Device-Manager"&gt;https://github.com/NordicSemiconductor/IOS-nRF-Connect-Device-Manager&lt;/a&gt;&amp;nbsp;please&amp;nbsp;- this issue continues to block our product launch.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/541414?ContentTypeID=1</link><pubDate>Fri, 04 Jul 2025 08:20:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:627bede1-1da0-47a7-b87f-c3722fec054c</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi again,&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s an update from internally. There&amp;#39;s a workaround that you can use below. W.r.t for a PR for a fix for this issue, I&amp;#39;m afraid it will take some time, specially since the workaround seems to work. Please report back if the suggestion does not work as intended.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Changing the update sequence from:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Upload the app core image using mcumgr&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Upload the net core image using mcumgr&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Activate the app core image using mcumgr&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Activate the net core image using mcumgr&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Reboot&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span&gt;to:&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Upload the net core image using mcumgr&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Upload the app core image using mcumgr&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Activate the net core image using mcumgr&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Activate the app core image using mcumgr&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Reboot&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span&gt;fixes the problem and MCUboot updates both the app core and the net core once again, even with&amp;nbsp;SB_CONFIG_SECURE_BOOT_APPCORE=y.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/538367?ContentTypeID=1</link><pubDate>Fri, 06 Jun 2025 08:19:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef918c47-da71-4934-8db8-8accde997b09</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Initial comment (without testing): &amp;quot;It looks like the PR is overall ok, except for the lack of nrf tag&amp;quot;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/538354?ContentTypeID=1</link><pubDate>Fri, 06 Jun 2025 07:25:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:684695d4-59e1-4ead-9ffd-53e8f652b90b</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thanks for letting me know. I&amp;#39;ve let the developers know about the urgency&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/538291?ContentTypeID=1</link><pubDate>Thu, 05 Jun 2025 16:03:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:546ee178-0def-4a86-8a0c-a47357ad7943</guid><dc:creator>Hayden Ball</dc:creator><description>&lt;p&gt;Thanks &lt;a href="https://devzone.nordicsemi.com/members/ahaug"&gt;AHaug&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the team have any feedback I&amp;#39;d really appreciate it - this is blocking our product beta launch.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/537998?ContentTypeID=1</link><pubDate>Wed, 04 Jun 2025 09:06:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03024e32-8787-4eb8-a52a-5342913ef8ad</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Alexander let me know you had commented here&lt;/p&gt;
[quote user="Hayden Ball"]This feels like there is a deeper problem, as &lt;a href="https://devzone.nordicsemi.com/members/bogdan-marinescu"&gt;Bogdan Marinescu&lt;/a&gt;&amp;nbsp;has mentioned, and this solution masks the actual problem.[/quote]
&lt;p&gt;There still could be a problem indeed. I see the reviewers are on it and I&amp;#39;ve reached out to them and asked for some input and shared the context of this case with them. If it becomes relevant, I will relay any info from them to you through here&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/537714?ContentTypeID=1</link><pubDate>Mon, 02 Jun 2025 15:40:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:51cefcfb-b193-40e6-882a-6938e4566c9a</guid><dc:creator>Hayden Ball</dc:creator><description>&lt;p&gt;I _think_ this is fixed by&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-mcuboot/pull/444"&gt;github.com/.../444&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/537541?ContentTypeID=1</link><pubDate>Fri, 30 May 2025 14:37:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:333dfa7d-fae3-4ab6-8f4e-b825692ef06c</guid><dc:creator>Hayden Ball</dc:creator><description>&lt;p&gt;To add, this is easily reproducible&amp;nbsp;following&amp;nbsp;&lt;a id="" href="https://academy.nordicsemi.com/simultaneous-updates-for-both-cores-of-the-nrf5340/"&gt;https://academy.nordicsemi.com/simultaneous-updates-for-both-cores-of-the-nrf5340/&lt;/a&gt;, then setting `SB_CONFIG_SECURE_BOOT_APPCORE=y`&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The resulting diff is the following:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;diff --git a/applications/ipc_radio/VERSION b/applications/ipc_radio/VERSION
new file mode 100644
index 000000000..5d04d4847
--- /dev/null
+++ b/applications/ipc_radio/VERSION
@@ -0,0 +1,5 @@
+VERSION_MAJOR = 5
+VERSION_MINOR = 0
+PATCHLEVEL = 2
+VERSION_TWEAK = 0
+EXTRAVERSION =
diff --git a/samples/bluetooth/peripheral_lbs/VERSION b/samples/bluetooth/peripheral_lbs/VERSION
index 5e193c5dc..5d04d4847 100644
--- a/samples/bluetooth/peripheral_lbs/VERSION
+++ b/samples/bluetooth/peripheral_lbs/VERSION
@@ -1,4 +1,4 @@
-VERSION_MAJOR = 3
+VERSION_MAJOR = 5
 VERSION_MINOR = 0
 PATCHLEVEL = 2
 VERSION_TWEAK = 0
diff --git a/samples/bluetooth/peripheral_lbs/app.overlay b/samples/bluetooth/peripheral_lbs/app.overlay
new file mode 100644
index 000000000..fcc2e240f
--- /dev/null
+++ b/samples/bluetooth/peripheral_lbs/app.overlay
@@ -0,0 +1,5 @@
+/ {
+       chosen {
+               nordic,pm-ext-flash = &amp;amp;mx25r64;
+       };
+};
diff --git a/samples/bluetooth/peripheral_lbs/prj.conf b/samples/bluetooth/peripheral_lbs/prj.conf
index 63a681872..a5e69d03e 100644
--- a/samples/bluetooth/peripheral_lbs/prj.conf
+++ b/samples/bluetooth/peripheral_lbs/prj.conf
@@ -15,3 +15,5 @@ CONFIG_BT_LBS_POLL_BUTTON=y
 CONFIG_DK_LIBRARY=y

 CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
+
+CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y
diff --git a/samples/bluetooth/peripheral_lbs/sysbuild.conf b/samples/bluetooth/peripheral_lbs/sysbuild.conf
new file mode 100644
index 000000000..88e9d7a29
--- /dev/null
+++ b/samples/bluetooth/peripheral_lbs/sysbuild.conf
@@ -0,0 +1,11 @@
+SB_CONFIG_BOOTLOADER_MCUBOOT=y
+SB_CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y
+
+SB_CONFIG_SECURE_BOOT_NETCORE=y
+SB_CONFIG_MCUBOOT_UPDATEABLE_IMAGES=2
+SB_CONFIG_NETCORE_APP_UPDATE=y
+SB_CONFIG_MCUBOOT_NRF53_MULTI_IMAGE_UPDATE=y
+SB_CONFIG_MCUBOOT_MODE_OVERWRITE_ONLY=y
+
+SB_CONFIG_SECURE_BOOT_APPCORE=y
+SB_CONFIG_SECURE_BOOT_NETCORE=y
diff --git a/samples/bluetooth/peripheral_lbs/sysbuild/ipc_radio.conf b/samples/bluetooth/peripheral_lbs/sysbuild/ipc_radio.conf
new file mode 100644
index 000000000..7fd7b3d06
--- /dev/null
+++ b/samples/bluetooth/peripheral_lbs/sysbuild/ipc_radio.conf
@@ -0,0 +1,3 @@
+CONFIG_SERIAL=y
+CONFIG_UART_CONSOLE=y
+CONFIG_LOG=y
diff --git a/samples/bluetooth/peripheral_lbs/sysbuild/mcuboot.conf b/samples/bluetooth/peripheral_lbs/sysbuild/mcuboot.conf
new file mode 100644
index 000000000..a567d5488
--- /dev/null
+++ b/samples/bluetooth/peripheral_lbs/sysbuild/mcuboot.conf
@@ -0,0 +1,2 @@
+CONFIG_NORDIC_QSPI_NOR=y
+CONFIG_BOOT_MAX_IMG_SECTORS=256
diff --git a/samples/bluetooth/peripheral_lbs/sysbuild/mcuboot.overlay b/samples/bluetooth/peripheral_lbs/sysbuild/mcuboot.overlay
new file mode 100644
index 000000000..fcc2e240f
--- /dev/null
+++ b/samples/bluetooth/peripheral_lbs/sysbuild/mcuboot.overlay
@@ -0,0 +1,5 @@
+/ {
+       chosen {
+               nordic,pm-ext-flash = &amp;amp;mx25r64;
+       };
+};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Flashing this to a nRF5340 DK, then changing the version numbers in both version files, rebuilding, and attempting an OTA update, you see that the app core version changes in the banner, but the net core does not.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/537533?ContentTypeID=1</link><pubDate>Fri, 30 May 2025 13:53:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f226402d-7317-4cc5-9f7c-2d7d06a57eb1</guid><dc:creator>Hayden Ball</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/members/ahaug"&gt;AHaug&lt;/a&gt;&amp;nbsp;&amp;nbsp;please can you advise how to achieve this using&amp;nbsp;&lt;a href="https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager"&gt;https://github.com/NordicSemiconductor/Android-nRF-Connect-Device-Manager &lt;/a&gt;and&amp;nbsp;&lt;a href="https://github.com/NordicSemiconductor/IOS-nRF-Connect-Device-Manager"&gt;https://github.com/NordicSemiconductor/IOS-nRF-Connect-Device-Manager?&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;m seeing the same problem,&amp;nbsp;and both of the above always upload the app core image first.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;This feels like there is a deeper problem, as &lt;a href="https://devzone.nordicsemi.com/members/bogdan-marinescu"&gt;Bogdan Marinescu&lt;/a&gt;&amp;nbsp;has mentioned, and this solution masks the actual problem.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Is there a way to fix this in firmware such that the &amp;quot;normal&amp;quot; order of app core, net core can be followed?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/494365?ContentTypeID=1</link><pubDate>Wed, 17 Jul 2024 12:50:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c31ac0f8-2018-4438-b6ea-20f81a7a4e25</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;I&amp;#39;m not sure why you&amp;#39;re having issues when doing it the initial way, but if your solution works then it&amp;#39;s a proper fix.&lt;/p&gt;
&lt;p&gt;Let me know if you find any issues with this method after a while and we&amp;#39;ll look closer into it.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340: MCUBoot issue with multi image update when SB_CONFIG_SECURE_BOOT_APPCORE is enabled</title><link>https://devzone.nordicsemi.com/thread/494177?ContentTypeID=1</link><pubDate>Tue, 16 Jul 2024 13:47:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:edd24d37-01b9-4273-afdf-f927b87796bd</guid><dc:creator>Bogdan Marinescu</dc:creator><description>&lt;p&gt;I found a fix for this, although probably not the best one. Turns out that changing the update sequence from:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;- Upload the app core image using mcumgr&lt;/span&gt;&lt;br /&gt;&lt;span&gt;- Upload the net core image using mcumgr&lt;/span&gt;&lt;br /&gt;&lt;span&gt;- Activate the app core image using mcumgr&lt;/span&gt;&lt;br /&gt;&lt;span&gt;- Activate the net core image using mcumgr&lt;/span&gt;&lt;br /&gt;&lt;span&gt;- Reboot&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;to:&lt;/p&gt;
&lt;p&gt;&lt;span&gt;- Upload the net core image using mcumgr&lt;br /&gt;- Upload the app core image using mcumgr&lt;br /&gt;- Activate the net core image using mcumgr&lt;/span&gt;&lt;br /&gt;&lt;span&gt;- Activate the app core image using mcumgr&lt;/span&gt;&lt;br /&gt;&lt;span&gt;- Reboot&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;fixes the problem and MCUboot updates both the app core and the net core once again, even with&amp;nbsp;&lt;span&gt;SB_CONFIG_SECURE_BOOT_APPCORE&lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt;y. Pretty sure that this &amp;quot;fix&amp;quot; only masks the main issue, but for now it does the job.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>