<?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: S32K344 HardFault</title>
    <link>https://community.nxp.com/t5/S32K/S32K344-HardFault/m-p/1389993#M13319</link>
    <description>&lt;P&gt;Glad to hear that you can find the root cause. It's indeed that you need to enable the Clock in MC_ME partition before starting using the CAN peripheral.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Nam&lt;/P&gt;</description>
    <pubDate>Tue, 21 Dec 2021 08:35:08 GMT</pubDate>
    <dc:creator>namnguyenviet</dc:creator>
    <dc:date>2021-12-21T08:35:08Z</dc:date>
    <item>
      <title>S32K344 HardFault</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-HardFault/m-p/1388772#M13289</link>
      <description>&lt;P&gt;Hi, NXP&lt;/P&gt;&lt;P&gt;I configured a project in EB tresos, but when I try to initialize the CAN module, it occurs the hardfault.&lt;/P&gt;&lt;P&gt;I doubt it that there are faults in MCU clock configuration, but I could not find out the way to deal with it.&lt;/P&gt;&lt;P&gt;Could you please help me?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="KILLERzheng_2-1639736608432.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/165542iD2EBF2F4FBA153DD/image-size/medium?v=v2&amp;amp;px=400" role="button" title="KILLERzheng_2-1639736608432.png" alt="KILLERzheng_2-1639736608432.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;KILLERzheng_2-1639736608432.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="KILLERzheng_1-1639736575351.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/165541iC2F3DB5072BD61EF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="KILLERzheng_1-1639736575351.png" alt="KILLERzheng_1-1639736575351.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;KILLERzheng_1-1639736575351.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Dec 2021 10:25:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-HardFault/m-p/1388772#M13289</guid>
      <dc:creator>KILLERzheng</dc:creator>
      <dc:date>2021-12-17T10:25:14Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 HardFault</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-HardFault/m-p/1389714#M13311</link>
      <description>&lt;P&gt;I found the reason of the HardFault, just because the CAN clock has not been enable in the mcumodesetconf of MCU module&lt;/P&gt;</description>
      <pubDate>Tue, 21 Dec 2021 01:08:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-HardFault/m-p/1389714#M13311</guid>
      <dc:creator>KILLERzheng</dc:creator>
      <dc:date>2021-12-21T01:08:12Z</dc:date>
    </item>
    <item>
      <title>Re: S32K344 HardFault</title>
      <link>https://community.nxp.com/t5/S32K/S32K344-HardFault/m-p/1389993#M13319</link>
      <description>&lt;P&gt;Glad to hear that you can find the root cause. It's indeed that you need to enable the Clock in MC_ME partition before starting using the CAN peripheral.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Nam&lt;/P&gt;</description>
      <pubDate>Tue, 21 Dec 2021 08:35:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K344-HardFault/m-p/1389993#M13319</guid>
      <dc:creator>namnguyenviet</dc:creator>
      <dc:date>2021-12-21T08:35:08Z</dc:date>
    </item>
  </channel>
</rss>

