<?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>FOTA upgrade MCUboot image with new signing key and app image simultaneously?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120571/fota-upgrade-mcuboot-image-with-new-signing-key-and-app-image-simultaneously</link><description>I am preparing to make our first firmware release on our custom board, which is equipped with the nRF9160 SICA B1 , modem fw version 1.3.4 . Our application is based on the Asset Tracker v2 and uses NCS v2.6.1 , with AWS as the cloud provider. 
 The firmware</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Apr 2025 12:10:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120571/fota-upgrade-mcuboot-image-with-new-signing-key-and-app-image-simultaneously" /><item><title>RE: FOTA upgrade MCUboot image with new signing key and app image simultaneously?</title><link>https://devzone.nordicsemi.com/thread/531518?ContentTypeID=1</link><pubDate>Fri, 11 Apr 2025 12:10:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d289bc3e-87dc-40ef-b9ce-7ad7409e6277</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Yes, your understanding is correct. Therefore it is important that the private key is kept securely stored&amp;nbsp;(on signing server, etc.) Only the public key will be embedded in the MCUBoot FW image.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FOTA upgrade MCUboot image with new signing key and app image simultaneously?</title><link>https://devzone.nordicsemi.com/thread/531503?ContentTypeID=1</link><pubDate>Fri, 11 Apr 2025 11:01:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0005d37-4c41-4dc5-bd00-5c512696bf3e</guid><dc:creator>jeremy.olson</dc:creator><description>&lt;p&gt;Alright, so that means that MCUboot is effectively not updatable with a new firmware signing key for new application firmware with the current implementation of the &lt;code&gt;aws_fota&lt;/code&gt; and &lt;code&gt;fota_download&lt;/code&gt; (and also likely the &lt;code&gt;mcuboot&lt;/code&gt; implementation) libraries. Do I understand correctly?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FOTA upgrade MCUboot image with new signing key and app image simultaneously?</title><link>https://devzone.nordicsemi.com/thread/531488?ContentTypeID=1</link><pubDate>Fri, 11 Apr 2025 09:16:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75c56e5d-e033-44f7-a291-81f3512b7066</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Sorry for the delay. By updating both the application and MCUboot simultaneously as discussed in the linked ticket you would be able to update the public key in the bootloader. Unfortunately, simultaneous&amp;nbsp;update of these two images is not supported in the current implementation/design.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FOTA upgrade MCUboot image with new signing key and app image simultaneously?</title><link>https://devzone.nordicsemi.com/thread/531478?ContentTypeID=1</link><pubDate>Fri, 11 Apr 2025 07:54:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92f89eaf-b047-4161-9ff5-ba168652d449</guid><dc:creator>jeremy.olson</dc:creator><description>&lt;p&gt;I saw an engineer was assigned to this post in the last two days. Any movement on this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>