<?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 FRDM-S32K144 CAN port header incorrect in S32K</title>
    <link>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1201700#M9310</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;While woking on the Example project "can_pal_s32k144" on the evaluation board I find that communication is happening on pins at CAN1 header instead of CAN0.&lt;/P&gt;&lt;P&gt;I wonder if the CAN headers are incorrectly tagged on the board. Could someone from NXP confirm?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saurabh_mehta_2-1608280210241.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133043i6DF5CA8F501D76CC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh_mehta_2-1608280210241.png" alt="saurabh_mehta_2-1608280210241.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="saurabh_mehta_3-1608280464361.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133044iB942CC00D9CD69A4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh_mehta_3-1608280464361.png" alt="saurabh_mehta_3-1608280464361.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The project is attached - simpler version of "can_pal_s32k144".&lt;/P&gt;&lt;P&gt;And here the snapshot of CAN messages sent out from other side which are successfuly received through CAN1 header but not from CAN0.&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="can_msg.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133047i5F7F836B7CBC2152/image-size/large?v=v2&amp;amp;px=999" role="button" title="can_msg.png" alt="can_msg.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;IDE version:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saurabh_mehta_0-1608279814551.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133040iB474DEFF94BF6CAC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh_mehta_0-1608279814551.png" alt="saurabh_mehta_0-1608279814551.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;SDK version:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saurabh_mehta_1-1608280004650.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133041i269E643EE125D9F2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh_mehta_1-1608280004650.png" alt="saurabh_mehta_1-1608280004650.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 18 Dec 2020 08:49:10 GMT</pubDate>
    <dc:creator>saurabh_mehta</dc:creator>
    <dc:date>2020-12-18T08:49:10Z</dc:date>
    <item>
      <title>FRDM-S32K144 CAN port header incorrect</title>
      <link>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1201700#M9310</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;While woking on the Example project "can_pal_s32k144" on the evaluation board I find that communication is happening on pins at CAN1 header instead of CAN0.&lt;/P&gt;&lt;P&gt;I wonder if the CAN headers are incorrectly tagged on the board. Could someone from NXP confirm?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saurabh_mehta_2-1608280210241.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133043i6DF5CA8F501D76CC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh_mehta_2-1608280210241.png" alt="saurabh_mehta_2-1608280210241.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="saurabh_mehta_3-1608280464361.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133044iB942CC00D9CD69A4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh_mehta_3-1608280464361.png" alt="saurabh_mehta_3-1608280464361.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The project is attached - simpler version of "can_pal_s32k144".&lt;/P&gt;&lt;P&gt;And here the snapshot of CAN messages sent out from other side which are successfuly received through CAN1 header but not from CAN0.&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="can_msg.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133047i5F7F836B7CBC2152/image-size/large?v=v2&amp;amp;px=999" role="button" title="can_msg.png" alt="can_msg.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;IDE version:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saurabh_mehta_0-1608279814551.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133040iB474DEFF94BF6CAC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh_mehta_0-1608279814551.png" alt="saurabh_mehta_0-1608279814551.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;SDK version:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saurabh_mehta_1-1608280004650.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133041i269E643EE125D9F2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh_mehta_1-1608280004650.png" alt="saurabh_mehta_1-1608280004650.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Dec 2020 08:49:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1201700#M9310</guid>
      <dc:creator>saurabh_mehta</dc:creator>
      <dc:date>2020-12-18T08:49:10Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM-S32K144 CAN port header incorrect</title>
      <link>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1201734#M9313</link>
      <description>&lt;P&gt;Hi&amp;nbsp;saurabh_mehta,&lt;/P&gt;
&lt;P&gt;These SDK is for&amp;nbsp;&lt;A href="https://www.nxp.com/design/development-boards/automotive-development-platforms/s32k-mcu-platforms/s32k144-evaluation-board:S32K144EVB" target="_self"&gt;S32K144EVB: S32K144 Evaluation Board&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;The board on your hand seems to be: FRDM KFA Board&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Robin&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Fri, 18 Dec 2020 09:31:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1201734#M9313</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2020-12-18T09:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM-S32K144 CAN port header incorrect</title>
      <link>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1201813#M9315</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/57959"&gt;@Robin_Shen&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To my understanding SDK is for the S32K microcontroller, irrespective of the development kit -- or am i mistaken?&lt;/P&gt;&lt;P&gt;and from &lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/FRDM-S32K144-EVB/ta-p/1121816?attachment-id=3523" target="_self"&gt;FRDM KFA Board.pdf,&lt;/A&gt;&amp;nbsp;the PTE4/PTE5 should map to CAN0&lt;/P&gt;&lt;P&gt;Then why does communication happens over header marked as CAN1 instead of CAN0?&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="uC.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133064iC40EB2BB8103C422/image-size/large?v=v2&amp;amp;px=999" role="button" title="uC.png" alt="uC.png" /&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="CAN.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133065i7319966D439A1291/image-size/large?v=v2&amp;amp;px=999" role="button" title="CAN.png" alt="CAN.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 18 Dec 2020 12:30:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1201813#M9315</guid>
      <dc:creator>saurabh_mehta</dc:creator>
      <dc:date>2020-12-18T12:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM-S32K144 CAN port header incorrect</title>
      <link>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1202123#M9326</link>
      <description>&lt;P&gt;saurabh_mehta,&lt;/P&gt;
&lt;P&gt;Sorry for my previous inaccurate reply!&lt;BR /&gt;SDK is for the S32K microcontroller, irrespective of the development kit.&lt;BR /&gt;But the Examples and Demos of SDK are developed on Supported Boards. For example: S32K144EVB and S32K144-MB are supported by this application(can_pal_s32k144).&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Boards supported.png" style="width: 572px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/133144i6B262197FB03F168/image-size/large?v=v2&amp;amp;px=999" role="button" title="Boards supported.png" alt="Boards supported.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;If you want to use Examples and Demos on FRDM KFA Board, you need to modify the software configuration according to the difference between S32K144EVB and FRDM KFA Board.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes. You are correct. The header name on the board is the opposite of the actual circuit connection.&amp;nbsp;&lt;BR /&gt;Thank you for the report!&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Robin&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2020 02:11:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/FRDM-S32K144-CAN-port-header-incorrect/m-p/1202123#M9326</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2020-12-21T02:11:32Z</dc:date>
    </item>
  </channel>
</rss>

