<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Advanced Secure Boot - SMR verification in S32K</title>
    <link>https://community.nxp.com/t5/S32K/Advanced-Secure-Boot-SMR-verification/m-p/1836351#M33518</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/222923"&gt;@anakha&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;there's some explanation in section "7.3. Implement secure boot" in the Secure boot application note.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lukaszadrapa_0-1711543271229.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/270695i7F460E82A1F7E486/image-size/medium?v=v2&amp;amp;px=400" role="button" title="lukaszadrapa_0-1711543271229.png" alt="lukaszadrapa_0-1711543271229.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;When you update your application, you load also new auth_tag to the passive block (auth_tag of your new application). After AB swap, still the same SMR will read still the same address of auth_tag in active block - the auth_tag corresponds to the new application now, so everything is ok a secure boot will pass. &lt;BR /&gt;If you don't do that in this way, it would be necessary to update the SMR.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Wed, 27 Mar 2024 12:42:09 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2024-03-27T12:42:09Z</dc:date>
    <item>
      <title>Advanced Secure Boot - SMR verification</title>
      <link>https://community.nxp.com/t5/S32K/Advanced-Secure-Boot-SMR-verification/m-p/1833800#M33355</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Advanced Secure Boot authentication proof is based on defined start address, size and config. (regarding to HSE Demo Advanced Secure Boot example and also Secure Boot App demo - SW745310)&lt;/P&gt;&lt;P&gt;The start address and the reserved SMR size for the application remains same for most of the time even the application updates.&amp;nbsp;&lt;SPAN&gt;Key catalog and the key values are also remain same.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;then, the TAG value and its address in flash remain same all the time even App changes.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What am I missing here? How Secure boot checks my app is secured?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Do I need to change keys or catalog each time I change app? But these values are defined in bootloader not in app.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Do I need to implement another signature (RSA or ECC) depend on the content of the App? if yes, how?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;regards,&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2024 14:20:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Advanced-Secure-Boot-SMR-verification/m-p/1833800#M33355</guid>
      <dc:creator>anakha</dc:creator>
      <dc:date>2024-03-22T14:20:54Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced Secure Boot - SMR verification</title>
      <link>https://community.nxp.com/t5/S32K/Advanced-Secure-Boot-SMR-verification/m-p/1836351#M33518</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/222923"&gt;@anakha&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;there's some explanation in section "7.3. Implement secure boot" in the Secure boot application note.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lukaszadrapa_0-1711543271229.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/270695i7F460E82A1F7E486/image-size/medium?v=v2&amp;amp;px=400" role="button" title="lukaszadrapa_0-1711543271229.png" alt="lukaszadrapa_0-1711543271229.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;When you update your application, you load also new auth_tag to the passive block (auth_tag of your new application). After AB swap, still the same SMR will read still the same address of auth_tag in active block - the auth_tag corresponds to the new application now, so everything is ok a secure boot will pass. &lt;BR /&gt;If you don't do that in this way, it would be necessary to update the SMR.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 12:42:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Advanced-Secure-Boot-SMR-verification/m-p/1836351#M33518</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2024-03-27T12:42:09Z</dc:date>
    </item>
    <item>
      <title>Re: Advanced Secure Boot - SMR verification</title>
      <link>https://community.nxp.com/t5/S32K/Advanced-Secure-Boot-SMR-verification/m-p/1836371#M33522</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/37795"&gt;@lukaszadrapa&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I am using full_mem right now, but will use AB_Swap soon.&lt;/P&gt;&lt;P&gt;Anyway, please correct me if I am wrong. I understand that you are saying to create a new TAG each time I update my App and write it to the same address. My problem/question is creating a different TAG.&lt;/P&gt;&lt;P&gt;KEY Catalog and and initial key is defined in bootloader not in APP and how can I crate different TAG if they remain same?&lt;/P&gt;&lt;P&gt;I only change App, bootloader config stays same, right?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 13:04:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Advanced-Secure-Boot-SMR-verification/m-p/1836371#M33522</guid>
      <dc:creator>anakha</dc:creator>
      <dc:date>2024-03-27T13:04:21Z</dc:date>
    </item>
  </channel>
</rss>

