<?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: S32K310 CAN MessageBuffer and HwObjectCount in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K310-CAN-MessageBuffer-and-HwObjectCount/m-p/2049255#M46152</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/213197"&gt;@Embedded_novice&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;According to the FlexCAN MCAL user manual, in case of&amp;nbsp;HRH, HwObjectCount is&amp;nbsp;number of&lt;BR /&gt;elements in the hardware FIFO.&lt;/P&gt;
&lt;P&gt;Regarding your question, yes, CAN&amp;nbsp;hardware objects defined as a PDU buffer.&amp;nbsp;The CAN RAM block can store message buffers in different configurations of sizes. According to the S32K3XX reference manual, the RAM block can store 32 messages of 8 bytes, 21 messages of 16 bytes, 12 messages of 32 bytes or 7 messages of 64 bytes. So, it is based on MB.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The CAN Interface (CanIf) is found between the low-level CAN drivers and the upper communication service layers from the AUTOSAR stack. It is not related to the Mailbox concept.&amp;nbsp;&lt;SPAN class=""&gt;The mailbox system is composed of a set of message buffers (MB) that store configuration and control data, time stamp, message ID, and data (see Message buffer structure).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Julin_AragnM_0-1740164337037.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/325196i6AED49E7866D5D0F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Julin_AragnM_0-1740164337037.png" alt="Julin_AragnM_0-1740164337037.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You can read the following article to know more about the CAN module:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/NXP-Model-Based-Design-Tools/Communicating-over-the-CAN-Bus/ta-p/1758456" target="_blank"&gt;Communicating over the CAN Bus - NXP Community&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2025 18:59:07 GMT</pubDate>
    <dc:creator>Julián_AragónM</dc:creator>
    <dc:date>2025-02-21T18:59:07Z</dc:date>
    <item>
      <title>S32K310 CAN MessageBuffer and HwObjectCount</title>
      <link>https://community.nxp.com/t5/S32K/S32K310-CAN-MessageBuffer-and-HwObjectCount/m-p/2047115#M46039</link>
      <description>&lt;P&gt;我在使用EB配置S32K310的MCAL的CAN模块时产生一些疑问：&lt;/P&gt;&lt;P&gt;1.我在手册中看到S32K310的MessageBuffer大小是64，那么HwObjectCount的最大配置数是否与MessageBuffer相关，如果不相关的话，我想知道HwObjectCount的最大配置数收什么因素的限制？MessageBuffer的最大个数64又会影响什么配置？（在我个人的理解中，FIFO的大小应该是由HwObjectCount决定的，且HwObjectCount不应该超过MessageBuffer的大小）&lt;/P&gt;&lt;P&gt;2.CAN模块是否一定要搭配CANIF组件使用，MailBox是在使用CANIF时才会用到的概念吗？MailBox的大小与什么有关？&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CANCFG.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/324721iB89605B51945C94D/image-size/large?v=v2&amp;amp;px=999" role="button" title="CANCFG.png" alt="CANCFG.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;感谢帮助！&lt;/P&gt;</description>
      <pubDate>Wed, 19 Feb 2025 08:36:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K310-CAN-MessageBuffer-and-HwObjectCount/m-p/2047115#M46039</guid>
      <dc:creator>Embedded_novice</dc:creator>
      <dc:date>2025-02-19T08:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: S32K310 CAN MessageBuffer and HwObjectCount</title>
      <link>https://community.nxp.com/t5/S32K/S32K310-CAN-MessageBuffer-and-HwObjectCount/m-p/2049255#M46152</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/213197"&gt;@Embedded_novice&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;According to the FlexCAN MCAL user manual, in case of&amp;nbsp;HRH, HwObjectCount is&amp;nbsp;number of&lt;BR /&gt;elements in the hardware FIFO.&lt;/P&gt;
&lt;P&gt;Regarding your question, yes, CAN&amp;nbsp;hardware objects defined as a PDU buffer.&amp;nbsp;The CAN RAM block can store message buffers in different configurations of sizes. According to the S32K3XX reference manual, the RAM block can store 32 messages of 8 bytes, 21 messages of 16 bytes, 12 messages of 32 bytes or 7 messages of 64 bytes. So, it is based on MB.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The CAN Interface (CanIf) is found between the low-level CAN drivers and the upper communication service layers from the AUTOSAR stack. It is not related to the Mailbox concept.&amp;nbsp;&lt;SPAN class=""&gt;The mailbox system is composed of a set of message buffers (MB) that store configuration and control data, time stamp, message ID, and data (see Message buffer structure).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Julin_AragnM_0-1740164337037.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/325196i6AED49E7866D5D0F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Julin_AragnM_0-1740164337037.png" alt="Julin_AragnM_0-1740164337037.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You can read the following article to know more about the CAN module:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/NXP-Model-Based-Design-Tools/Communicating-over-the-CAN-Bus/ta-p/1758456" target="_blank"&gt;Communicating over the CAN Bus - NXP Community&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2025 18:59:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K310-CAN-MessageBuffer-and-HwObjectCount/m-p/2049255#M46152</guid>
      <dc:creator>Julián_AragónM</dc:creator>
      <dc:date>2025-02-21T18:59:07Z</dc:date>
    </item>
  </channel>
</rss>

