<?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>Unable to use TFM_PROFILE_LARGE with FIRMWARE_UPDATE config</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/100904/unable-to-use-tfm_profile_large-with-firmware_update-config</link><description>I want to enable CONFIG_TFM_PROFILE_TYPE_LARGE with CONFIG_TFM_PARTITION_FIRMWARE_UPDATE from prj.conf 
 As per dependencies needed enabled below configs on tfm_hello_world sample program: 
 
 CONFIG_BUILD_WITH_TFM =y 
 CONFIG_TFM_PROFILE_TYPE_LARGE </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 21 Jun 2023 11:20:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/100904/unable-to-use-tfm_profile_large-with-firmware_update-config" /><item><title>RE: Unable to use TFM_PROFILE_LARGE with FIRMWARE_UPDATE config</title><link>https://devzone.nordicsemi.com/thread/432283?ContentTypeID=1</link><pubDate>Wed, 21 Jun 2023 11:20:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:747b8c4a-b7ee-4c93-ab2a-bee779112942</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Unfortunately we don&amp;#39;t support&amp;nbsp;CONFIG_TFM_PARTITION_FIRMWARE_UPDATE yet. Our TF-M does not use the built in bootloader for TF-M but uses MCU boot and NSIB. You can check the example &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/tfm/tfm_psa_template/README.html"&gt;pfm_psa_template &lt;/a&gt;on how we do DFU with TF-M and this blogpost&amp;nbsp;&amp;nbsp;&lt;a title="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/an-introduction-to-trusted-firmware-m-t-m" href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/an-introduction-to-trusted-firmware-m-t-m" rel="noopener noreferrer" target="_blank"&gt;An Introduction to Trusted Firmware-M (TF-M)&lt;/a&gt; on &amp;quot;Immutable Bootloader and Second Stage Bootloader&amp;quot;&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to use TFM_PROFILE_LARGE with FIRMWARE_UPDATE config</title><link>https://devzone.nordicsemi.com/thread/431472?ContentTypeID=1</link><pubDate>Fri, 16 Jun 2023 11:37:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f70c153e-5c20-4402-ab63-78b694f738e4</guid><dc:creator>skirti</dc:creator><description>&lt;p&gt;I want to identify the tfm_secure.hex size when I enable&amp;nbsp;&lt;span&gt;CONFIG_TFM_PROFILE_TYPE_LARGE&amp;nbsp; with firmware update functionality.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;To enable firmware updates, we need to enable config&amp;nbsp;&lt;/span&gt;&lt;a href="https://docs.zephyrproject.org/latest/kconfig.html#CONFIG_TFM_PARTITION_FIRMWARE_UPDATE"&gt;CONFIG_TFM_PARTITION_FIRMWARE_UPDATE&lt;/a&gt;&amp;nbsp;which selects config&amp;nbsp;&lt;a href="https://docs.zephyrproject.org/latest/kconfig.html#CONFIG_TFM_MCUBOOT_DATA_SHARING"&gt;CONFIG_TFM_MCUBOOT_DATA_SHARING&lt;/a&gt;&amp;nbsp;&lt;span&gt;which is dependent on&amp;nbsp;&lt;a href="https://docs.zephyrproject.org/latest/kconfig.html#CONFIG_TFM_BL2"&gt;CONFIG_TFM_BL2&lt;/a&gt;. So&amp;nbsp;final prj.conf looks like below&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BUILD_WITH_TFM&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_TFM_PROFILE_TYPE_LARGE&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_TFM_PARTITION_FIRMWARE_UPDATE&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_TFM_BL2&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;Sample program used: tfm_hello_world&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;With this configuration I get an error as stated above. (&amp;quot;BL2 not supported&amp;quot;)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;My question is what should I do to build CONFIG_TFM_PROFILE_TYPE_LARGE with firmware updates config on?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to use TFM_PROFILE_LARGE with FIRMWARE_UPDATE config</title><link>https://devzone.nordicsemi.com/thread/431467?ContentTypeID=1</link><pubDate>Fri, 16 Jun 2023 11:28:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de908bfb-f6e1-42e1-8b4e-95d5911b5132</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This is a bit outside my normal wheelhouse, so could you explain what your end goal here is?&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t think we support the BL2, but you can still have two bootloader stages with our &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.0/nrf/samples/bootloader/README.html"&gt;nRF Secure Immutable Bootloader&lt;/a&gt; and MCUBoot. To see how they can be used, you can look at the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.0/nrf/samples/tfm/tfm_psa_template/README.html"&gt;PSA template sample&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Didrik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>