<?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>S32KのトピックRe: S32K322 MPU MemManage handler Exception Not Reaching</title>
    <link>https://community.nxp.com/t5/S32K/S32K322-MPU-MemManage-handler-Exception-Not-Reaching/m-p/2356326#M58203</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/248796"&gt;@Thiru2483&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;The root cause could be that another fault occurs during exception entry or stack usage. Even with MEMFAULTENA enabled, if the MPU violation happens while the core is stacking/unstacking registers (for example, when the stack pointer lies in or grows into a restricted SRAM MPU region), the Cortex‑M7 will force escalation directly to HardFault. In that case, MemManage_Handler is never entered.&amp;nbsp;Is the stack located in the same SRAM region that you are restricting with the MPU?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;
&lt;DIV style="font-family: 'Segoe UI'; font-size: 14px; font-style: normal; font-weight: 400; line-height: 20px;"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
    <pubDate>Mon, 27 Apr 2026 06:32:09 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2026-04-27T06:32:09Z</dc:date>
    <item>
      <title>S32K322 MPU MemManage handler Exception Not Reaching</title>
      <link>https://community.nxp.com/t5/S32K/S32K322-MPU-MemManage-handler-Exception-Not-Reaching/m-p/2355797#M58174</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I have configured the MPU memory partition.&lt;/P&gt;&lt;P&gt;I created a stub function to intentionally violate the SRAM address region.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Thiru2483_0-1777026529330.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/383480i88A1B41939DD2301/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Thiru2483_0-1777026529330.png" alt="Thiru2483_0-1777026529330.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Initially, I configured both read and write access to the SRAM region. After changing the region permissions to read-only and attempting to write to the TEST_SRAM_ADDRESS, a MemFault is triggered, and the location is updated as expected. However, it is entering the HardFault handler instead of the MemManage handler. I have attached the image below for your reference withe register details.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Thiru2483_1-1777026796118.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/383481iE9A9613A12D7CCC4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Thiru2483_1-1777026796118.png" alt="Thiru2483_1-1777026796118.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Thiru2483_0-1777027817170.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/383484iC5FBD766D1672BD3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Thiru2483_0-1777027817170.png" alt="Thiru2483_0-1777027817170.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have added the MCAL MPU option enabled similar is done for core 1.&lt;/P&gt;&lt;P&gt;Kindly let me know why this is happening and whether I am missing any configuration. Please provide your support on this.&lt;BR /&gt;&lt;BR /&gt;&lt;LI-PRODUCT title="S32K3" id="S32K3"&gt;&lt;/LI-PRODUCT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2026 10:51:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K322-MPU-MemManage-handler-Exception-Not-Reaching/m-p/2355797#M58174</guid>
      <dc:creator>Thiru2483</dc:creator>
      <dc:date>2026-04-24T10:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: S32K322 MPU MemManage handler Exception Not Reaching</title>
      <link>https://community.nxp.com/t5/S32K/S32K322-MPU-MemManage-handler-Exception-Not-Reaching/m-p/2356326#M58203</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/248796"&gt;@Thiru2483&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;The root cause could be that another fault occurs during exception entry or stack usage. Even with MEMFAULTENA enabled, if the MPU violation happens while the core is stacking/unstacking registers (for example, when the stack pointer lies in or grows into a restricted SRAM MPU region), the Cortex‑M7 will force escalation directly to HardFault. In that case, MemManage_Handler is never entered.&amp;nbsp;Is the stack located in the same SRAM region that you are restricting with the MPU?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;
&lt;DIV style="font-family: 'Segoe UI'; font-size: 14px; font-style: normal; font-weight: 400; line-height: 20px;"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Mon, 27 Apr 2026 06:32:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K322-MPU-MemManage-handler-Exception-Not-Reaching/m-p/2356326#M58203</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2026-04-27T06:32:09Z</dc:date>
    </item>
  </channel>
</rss>

