<?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: S32K3XX HSE Firmware in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K3XX-HSE-Firmware/m-p/1788053#M30603</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/228036"&gt;@KadirY&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The HSE firmware is placed to internal flash but this flash is not accessible for user after installation of HSE firmware. Part(s) of flash used for HSE firmware are removed from the memory map and HSE has exclusive access to this flash. So, there are no security concerns. It is ensured by internal design / internal features that user can't access it.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Fri, 12 Jan 2024 13:49:56 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2024-01-12T13:49:56Z</dc:date>
    <item>
      <title>S32K3XX HSE Firmware</title>
      <link>https://community.nxp.com/t5/S32K/S32K3XX-HSE-Firmware/m-p/1787202#M30542</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;Within the "S32K3XX SECURITY OVERVIEW AND BRING UP" document, there is a figure showing the locations of the HSE Firmware. For the S32K3 series, the HSE Firmware is located in the internal flash, while for the more secure S32G2 and S32R41 series chips, it is situated in secure external flash. You can view the figure and the document in the attachments. Since the internal flash is accessible during runtime, I am concerned that it can be edited, raising concerns over the Secure Boot of the platform.&lt;/P&gt;&lt;P&gt;1-) Is the placement of HSE Firmware in the internal flash a drawback?&lt;/P&gt;&lt;P&gt;2-) Can it be tampered with in any way?&lt;/P&gt;&lt;P&gt;3-) Is there a method to detect such tampering and halt the MCU boot (this is needed for Secure Boot) ?&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;4-) What precautions can be implemented to address security concerns related to this issue?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;KadirY&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jan 2024 12:27:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3XX-HSE-Firmware/m-p/1787202#M30542</guid>
      <dc:creator>KadirY</dc:creator>
      <dc:date>2024-01-11T12:27:40Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3XX HSE Firmware</title>
      <link>https://community.nxp.com/t5/S32K/S32K3XX-HSE-Firmware/m-p/1788053#M30603</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/228036"&gt;@KadirY&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The HSE firmware is placed to internal flash but this flash is not accessible for user after installation of HSE firmware. Part(s) of flash used for HSE firmware are removed from the memory map and HSE has exclusive access to this flash. So, there are no security concerns. It is ensured by internal design / internal features that user can't access it.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2024 13:49:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3XX-HSE-Firmware/m-p/1788053#M30603</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2024-01-12T13:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: S32K3XX HSE Firmware</title>
      <link>https://community.nxp.com/t5/S32K/S32K3XX-HSE-Firmware/m-p/2125395#M50379</link>
      <description>then we need to get access to secure files first before firmware flashing onto the board right ?</description>
      <pubDate>Mon, 30 Jun 2025 06:55:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K3XX-HSE-Firmware/m-p/2125395#M50379</guid>
      <dc:creator>Sanjana_k</dc:creator>
      <dc:date>2025-06-30T06:55:54Z</dc:date>
    </item>
  </channel>
</rss>

