<?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>S32GのトピックRe: S32G secure boot issue</title>
    <link>https://community.nxp.com/t5/S32G/S32G-secure-boot-issue/m-p/1621885#M2628</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;HSE related information is confidential, for which we recommend opening a ticket under NXP online service or contacting your local NXP representative for more information.&lt;/P&gt;
&lt;P&gt;As to the "BOOT_SEQ", it is a flag that is tell the system if the HSE FW is to be run or not. The Key is to be managed inside the HSE FW, BOOT_SEQ just tells the system that it will follow the secure boot using HSE.&lt;/P&gt;
&lt;P&gt;Please, let us know.&lt;/P&gt;</description>
    <pubDate>Fri, 24 Mar 2023 19:53:56 GMT</pubDate>
    <dc:creator>Daniel-Aguirre</dc:creator>
    <dc:date>2023-03-24T19:53:56Z</dc:date>
    <item>
      <title>S32G secure boot issue</title>
      <link>https://community.nxp.com/t5/S32G/S32G-secure-boot-issue/m-p/1621551#M2617</link>
      <description>&lt;P&gt;For previous board, like IMX6/P4080/T2080, when secure boot enabled, the hash value of the public key&amp;nbsp; which is used to verify bootloader would be burned to the fuse, so that attacker cannot use its own key pair to tamper with it.&lt;/P&gt;&lt;P&gt;I can't find similar operation for S32G board, how should the public key be protected ？&lt;/P&gt;&lt;P&gt;And the secure boot switch "BOOT_SEQ" is stored in IVT table, I assume it is protected by the GMAC vlaue of IVT table ,but where is the key which used to generate GMAC value stored，is it burn to fuse ? could you please help to clarify it, thank you very much.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2023 09:05:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G-secure-boot-issue/m-p/1621551#M2617</guid>
      <dc:creator>liyan</dc:creator>
      <dc:date>2023-03-24T09:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: S32G secure boot issue</title>
      <link>https://community.nxp.com/t5/S32G/S32G-secure-boot-issue/m-p/1621885#M2628</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;HSE related information is confidential, for which we recommend opening a ticket under NXP online service or contacting your local NXP representative for more information.&lt;/P&gt;
&lt;P&gt;As to the "BOOT_SEQ", it is a flag that is tell the system if the HSE FW is to be run or not. The Key is to be managed inside the HSE FW, BOOT_SEQ just tells the system that it will follow the secure boot using HSE.&lt;/P&gt;
&lt;P&gt;Please, let us know.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2023 19:53:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G-secure-boot-issue/m-p/1621885#M2628</guid>
      <dc:creator>Daniel-Aguirre</dc:creator>
      <dc:date>2023-03-24T19:53:56Z</dc:date>
    </item>
  </channel>
</rss>

