<?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 Linker File Memory Segregation Issue triggers Hardfault</title>
    <link>https://community.nxp.com/t5/S32K/S32k322-Linker-File-Memory-Segregation-Issue-triggers-Hardfault/m-p/2008287#M43937</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/244188"&gt;@Lisha&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I understand this is a MemManage fault.&lt;/P&gt;
&lt;P&gt;You should be able to find the memory address and the PC address of the fault instruction, refer to these documents:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K312-HARDFAULT-Handling-Interrupt-DS3-5-RTD300/ta-p/1806259" target="_blank"&gt;https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K312-HARDFAULT-Handling-Interrupt-DS3-5-RTD300/ta-p/1806259&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/How-To-Debug-A-Fault-Exception-On-ARM-Cortex-M-V7M-MCU-S32K3XX/ta-p/1595570" target="_blank"&gt;https://community.nxp.com/t5/S32K-Knowledge-Base/How-To-Debug-A-Fault-Exception-On-ARM-Cortex-M-V7M-MCU-S32K3XX/ta-p/1595570&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447" target="_blank"&gt;https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway, this is caused by the MPU that is configured in system.c&lt;/P&gt;
&lt;P&gt;Please check the starting address, size and all the attributes of each descriptor.&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;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Dec 2024 14:44:15 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2024-12-05T14:44:15Z</dc:date>
    <item>
      <title>S32k322 Linker File Memory Segregation Issue triggers Hardfault</title>
      <link>https://community.nxp.com/t5/S32K/S32k322-Linker-File-Memory-Segregation-Issue-triggers-Hardfault/m-p/2006887#M43872</link>
      <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Hii,&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;I am facing an issue in my linker file. As soon as I add a section under int_flash_safeos_c0 and&amp;nbsp;I enabled the MPU (Memory Protection Unit) and divided it into two sections: OsROM and OsRAM. When using it, I encounter a HardFault.&amp;nbsp;&amp;nbsp;I encounter a HardFault on the S32K322 in S32 Design Studio. I am not sure why this is happening. I have attached the Linker here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Lisha&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2024 09:54:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32k322-Linker-File-Memory-Segregation-Issue-triggers-Hardfault/m-p/2006887#M43872</guid>
      <dc:creator>Lisha</dc:creator>
      <dc:date>2024-12-04T09:54:24Z</dc:date>
    </item>
    <item>
      <title>Re: S32k322 Linker File Memory Segregation Issue triggers Hardfault</title>
      <link>https://community.nxp.com/t5/S32K/S32k322-Linker-File-Memory-Segregation-Issue-triggers-Hardfault/m-p/2008287#M43937</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/244188"&gt;@Lisha&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I understand this is a MemManage fault.&lt;/P&gt;
&lt;P&gt;You should be able to find the memory address and the PC address of the fault instruction, refer to these documents:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K312-HARDFAULT-Handling-Interrupt-DS3-5-RTD300/ta-p/1806259" target="_blank"&gt;https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K312-HARDFAULT-Handling-Interrupt-DS3-5-RTD300/ta-p/1806259&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/How-To-Debug-A-Fault-Exception-On-ARM-Cortex-M-V7M-MCU-S32K3XX/ta-p/1595570" target="_blank"&gt;https://community.nxp.com/t5/S32K-Knowledge-Base/How-To-Debug-A-Fault-Exception-On-ARM-Cortex-M-V7M-MCU-S32K3XX/ta-p/1595570&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447" target="_blank"&gt;https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway, this is caused by the MPU that is configured in system.c&lt;/P&gt;
&lt;P&gt;Please check the starting address, size and all the attributes of each descriptor.&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;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2024 14:44:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32k322-Linker-File-Memory-Segregation-Issue-triggers-Hardfault/m-p/2008287#M43937</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2024-12-05T14:44:15Z</dc:date>
    </item>
  </channel>
</rss>

