<?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: How to debug HSE firmware RAM code in S32K</title>
    <link>https://community.nxp.com/t5/S32K/How-to-debug-HSE-firmware-RAM-code/m-p/2247172#M54764</link>
    <description>&lt;P&gt;It does not seem to be code executed fro SRAM as it reports different PC address. Rather you exception handlers in SRAM&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="davidtosenovjan_1-1763976976177.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/366958i05582ED4B8DE33EB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="davidtosenovjan_1-1763976976177.png" alt="davidtosenovjan_1-1763976976177.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 24 Nov 2025 09:37:23 GMT</pubDate>
    <dc:creator>davidtosenovjan</dc:creator>
    <dc:date>2025-11-24T09:37:23Z</dc:date>
    <item>
      <title>How to debug HSE firmware RAM code</title>
      <link>https://community.nxp.com/t5/S32K/How-to-debug-HSE-firmware-RAM-code/m-p/2234069#M54719</link>
      <description>&lt;P&gt;An exception is occurring in the HSE firmware.&lt;BR /&gt;The HSE appears to load code into RAM and execute it; however, an exception is raised while the RAM code is running.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Why is this exception occurring, and how should I proceed with debugging?&lt;BR /&gt;The attachment contains the register dump and exception details captured at the time of the fault.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="reg.png" style="width: 291px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/366810i7A42006218DB68A2/image-size/large?v=v2&amp;amp;px=999" role="button" title="reg.png" alt="reg.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="exception.png" style="width: 562px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/366811i2A6E0C82AF210649/image-size/large?v=v2&amp;amp;px=999" role="button" title="exception.png" alt="exception.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Nov 2025 13:19:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-debug-HSE-firmware-RAM-code/m-p/2234069#M54719</guid>
      <dc:creator>Hozumi</dc:creator>
      <dc:date>2025-11-21T13:19:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to debug HSE firmware RAM code</title>
      <link>https://community.nxp.com/t5/S32K/How-to-debug-HSE-firmware-RAM-code/m-p/2247172#M54764</link>
      <description>&lt;P&gt;It does not seem to be code executed fro SRAM as it reports different PC address. Rather you exception handlers in SRAM&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="davidtosenovjan_1-1763976976177.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/366958i05582ED4B8DE33EB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="davidtosenovjan_1-1763976976177.png" alt="davidtosenovjan_1-1763976976177.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 09:37:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/How-to-debug-HSE-firmware-RAM-code/m-p/2247172#M54764</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2025-11-24T09:37:23Z</dc:date>
    </item>
  </channel>
</rss>

