<?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>Question about MCUboot version</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116099/question-about-mcuboot-version</link><description>Hello, 
 In my project, I have b0+mcuboot+app to be able to update the bootloader and the application. 
 I am contacting you because I have trouble understanding the difference between SB_CONFIG_SECURE_BOOT_MCUBOOT_VERSION, CONFIG_FW_INFO_FIRMWARE_VERSION</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 12 Feb 2026 11:14:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116099/question-about-mcuboot-version" /><item><title>RE: Question about MCUboot version</title><link>https://devzone.nordicsemi.com/thread/560990?ContentTypeID=1</link><pubDate>Thu, 12 Feb 2026 11:14:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2a28382-71e0-4e70-b764-d98e17adc034</guid><dc:creator>jasr93</dc:creator><description>&lt;p&gt;Just one question related to this topic:&lt;/p&gt;
&lt;p&gt;Every time we want to create an MCUBOOT update, we have to change SB_CONFIG_SECURE_BOOT_MCUBOOT_VERSION.&lt;/p&gt;
&lt;p&gt;But what should we do with CONFIG_FW_INFO_FIRMWARE_VERSION within b0? b0 is immutable, so it can&amp;#39;t be changed.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Question about MCUboot version</title><link>https://devzone.nordicsemi.com/thread/509163?ContentTypeID=1</link><pubDate>Tue, 05 Nov 2024 16:09:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:745e18d5-bd43-49e9-a6fa-e4e03c2f8d85</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When MCUboot updates are enabled, the firmware embeds the nRF Secure Immutable Bootloader version using the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a title="(in Kconfig reference v&amp;amp;nbsp;)" href="https://docs.nordicsemi.com/bundle/ncs-latest/page/kconfig/index.html#CONFIG_FW_INFO_FIRMWARE_VERSION"&gt;&lt;code&gt;&lt;span&gt;CONFIG_FW_INFO_FIRMWARE_VERSION&lt;/span&gt;&lt;/code&gt;&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;Kconfig option. However, during an update, MCUboot does not check this version; it only checks the MCUboot package version.&lt;/p&gt;
&lt;p&gt;You can set the MCUboot update package version in sysbuild with&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;&lt;span&gt;SB_CONFIG_SECURE_BOOT_MCUBOOT_VERSION&lt;/span&gt;&lt;/code&gt;. You must increase this version number when deploying an MCUboot update. If the version in the update is lower than the current version, MCUboot will reject the update and not transfer it to the opposing secure boot firmware slot.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Using a&amp;nbsp;&lt;/span&gt;&lt;code&gt;&lt;span&gt;VERSION&lt;/span&gt;&lt;/code&gt;&lt;span&gt;&amp;nbsp;file allows you to independently configure the version value for each build instance of the application.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;See&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/bootloaders_dfu/sysbuild_image_ids.html"&gt;MCUboot update package version&lt;/a&gt;, &lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/config_and_build/dfu/dfu_image_versions.html"&gt;Image versions&lt;/a&gt;, and &lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/zephyr/build/version/index.html"&gt;Application version management&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>