<?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: External Boot S32k in S32K</title>
    <link>https://community.nxp.com/t5/S32K/External-Boot-S32k/m-p/2415027#M61134</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/254751"&gt;@CTCoder1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, S32K344 contains SBAF code which is executed after reset. However, this should not be considered a configurable bootloader that can directly load an application from an arbitrary external memory.&amp;nbsp;External boot is not supported.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The normal S32K3 boot flow expects the boot information/application in the internal code flash only. For example, a user bootloader can be placed at the beginning of internal flash (IVT at 0x00400000) and then execute whatever update/loading mechanism is required.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, if the intention is to store an application in an external flash, the usual solution is to have user bootloader in internal flash. This bootloader initializes the required peripheral/external memory interface, reads the image from the external device and then either programs it into internal flash or handles it according to the application's requirements.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is no SBAF (or we can say BootROM) configuration where you simply specify an external flash address/device and have the S32K344 SBAF boot the application directly from there. This needs to be managed completely by your software.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
    <pubDate>Mon, 21 Sep 2026 16:31:40 GMT</pubDate>
    <dc:creator>lukaszadrapa</dc:creator>
    <dc:date>2026-09-21T16:31:40Z</dc:date>
    <item>
      <title>External Boot S32k</title>
      <link>https://community.nxp.com/t5/S32K/External-Boot-S32k/m-p/2415010#M61130</link>
      <description>&lt;P class=""&gt;&lt;SPAN&gt;Does the S32k344 device initially execute an immutable first-stage bootloader from internal ROM? If so, can this ROM bootloader be configured to load a secondary bootloader (or application image) from an external source, such as external flash?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If external boot is supported, how would this be configured so the initial bootloader knows where to pull from?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Sep 2026 14:17:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/External-Boot-S32k/m-p/2415010#M61130</guid>
      <dc:creator>CTCoder1</dc:creator>
      <dc:date>2026-09-21T14:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: External Boot S32k</title>
      <link>https://community.nxp.com/t5/S32K/External-Boot-S32k/m-p/2415027#M61134</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/254751"&gt;@CTCoder1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, S32K344 contains SBAF code which is executed after reset. However, this should not be considered a configurable bootloader that can directly load an application from an arbitrary external memory.&amp;nbsp;External boot is not supported.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The normal S32K3 boot flow expects the boot information/application in the internal code flash only. For example, a user bootloader can be placed at the beginning of internal flash (IVT at 0x00400000) and then execute whatever update/loading mechanism is required.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, if the intention is to store an application in an external flash, the usual solution is to have user bootloader in internal flash. This bootloader initializes the required peripheral/external memory interface, reads the image from the external device and then either programs it into internal flash or handles it according to the application's requirements.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is no SBAF (or we can say BootROM) configuration where you simply specify an external flash address/device and have the S32K344 SBAF boot the application directly from there. This needs to be managed completely by your software.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Mon, 21 Sep 2026 16:31:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/External-Boot-S32k/m-p/2415027#M61134</guid>
      <dc:creator>lukaszadrapa</dc:creator>
      <dc:date>2026-09-21T16:31:40Z</dc:date>
    </item>
  </channel>
</rss>

