<?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: S32K344 secureBoot in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K344-secureBoot/m-p/2081500#M47811</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please download the&lt;STRONG&gt; Secure Boot Application note v0.1.1.0&lt;/STRONG&gt; from secure file.&lt;/P&gt;
&lt;P&gt;The chapter "4.3.6. SMR core status" mentioned:&lt;BR /&gt;HSE system attribute service “HSE_SMR_CORE_BOOT_STATUS” request the SMR verification status and core boot status as Table 14 shows.&lt;/P&gt;
&lt;P&gt;Since this document requires signing an NDA, I won’t post the screenshots here.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You will also find the SMR and Core Boot status in struct &lt;STRONG&gt;hseAttrSmrCoreStatus_t&lt;/STRONG&gt; in &lt;STRONG&gt;S32K3X4_HSE_Service_API_Reference_Manual.pdf&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Robin&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
    <pubDate>Wed, 16 Apr 2025 07:41:36 GMT</pubDate>
    <dc:creator>Robin_Shen</dc:creator>
    <dc:date>2025-04-16T07:41:36Z</dc:date>
    <item>
      <title>S32K344 secureBoot</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-secureBoot/m-p/2081216#M47800</link>
      <description>&lt;P&gt;在ASB模式下实施postBoot，SMR关联app，CR为HSE_CR_SANCTION_DIS_ALL_KEYS时。由于是并行方式所以HSE会释放core 0，同时进行SMR验证。我理解此时app代码已经运行，那么app里能不能通过某个寄存器标志知道SMR的验证结果是成功还是失败呢？&lt;/P&gt;</description>
      <pubDate>Wed, 16 Apr 2025 02:11:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-secureBoot/m-p/2081216#M47800</guid>
      <dc:creator>liyongfeng</dc:creator>
      <dc:date>2025-04-16T02:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 secureBoot</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-secureBoot/m-p/2081500#M47811</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please download the&lt;STRONG&gt; Secure Boot Application note v0.1.1.0&lt;/STRONG&gt; from secure file.&lt;/P&gt;
&lt;P&gt;The chapter "4.3.6. SMR core status" mentioned:&lt;BR /&gt;HSE system attribute service “HSE_SMR_CORE_BOOT_STATUS” request the SMR verification status and core boot status as Table 14 shows.&lt;/P&gt;
&lt;P&gt;Since this document requires signing an NDA, I won’t post the screenshots here.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You will also find the SMR and Core Boot status in struct &lt;STRONG&gt;hseAttrSmrCoreStatus_t&lt;/STRONG&gt; in &lt;STRONG&gt;S32K3X4_HSE_Service_API_Reference_Manual.pdf&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Robin&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Wed, 16 Apr 2025 07:41:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-secureBoot/m-p/2081500#M47811</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2025-04-16T07:41:36Z</dc:date>
    </item>
  </channel>
</rss>

