<?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 IMXRT1171 Flexcan MassageBox Filter (range filter function?) in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2001609#M32713</link>
    <description>&lt;P&gt;Hello,&lt;BR /&gt;I have a question regarding FlexCAN filtering.&lt;/P&gt;&lt;P&gt;I am currently using CAN FD, and with the FD configuration, the number of available Message Buffers (MBs) is limited to a maximum of 13.&lt;/P&gt;&lt;P&gt;When looking at settings from the MCUXpresso Config Tool or in code such as:&lt;/P&gt;&lt;P&gt;const flexcan_rx_mb_config_t CAN1_rx_mb_config_0 = {&lt;BR /&gt;.id = FLEXCAN_ID_STD(291UL),&lt;BR /&gt;.format = kFLEXCAN_FrameFormatStandard,&lt;BR /&gt;.type = kFLEXCAN_FrameTypeData&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;It seems that a single Message Box is mapped to a single CAN ID filter.&lt;/P&gt;&lt;P&gt;In the previous MCUs I used, there were filtering functions that allowed for range-based filtering.&lt;BR /&gt;Is there a similar way to implement this in the current setup?&lt;BR /&gt;For example, receiving only CAN IDs within the range of 0x100 to 0x200.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Tue, 26 Nov 2024 05:20:32 GMT</pubDate>
    <dc:creator>Seunghyup</dc:creator>
    <dc:date>2024-11-26T05:20:32Z</dc:date>
    <item>
      <title>IMXRT1171 Flexcan MassageBox Filter (range filter function?)</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2001609#M32713</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I have a question regarding FlexCAN filtering.&lt;/P&gt;&lt;P&gt;I am currently using CAN FD, and with the FD configuration, the number of available Message Buffers (MBs) is limited to a maximum of 13.&lt;/P&gt;&lt;P&gt;When looking at settings from the MCUXpresso Config Tool or in code such as:&lt;/P&gt;&lt;P&gt;const flexcan_rx_mb_config_t CAN1_rx_mb_config_0 = {&lt;BR /&gt;.id = FLEXCAN_ID_STD(291UL),&lt;BR /&gt;.format = kFLEXCAN_FrameFormatStandard,&lt;BR /&gt;.type = kFLEXCAN_FrameTypeData&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;It seems that a single Message Box is mapped to a single CAN ID filter.&lt;/P&gt;&lt;P&gt;In the previous MCUs I used, there were filtering functions that allowed for range-based filtering.&lt;BR /&gt;Is there a similar way to implement this in the current setup?&lt;BR /&gt;For example, receiving only CAN IDs within the range of 0x100 to 0x200.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 05:20:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2001609#M32713</guid>
      <dc:creator>Seunghyup</dc:creator>
      <dc:date>2024-11-26T05:20:32Z</dc:date>
    </item>
    <item>
      <title>Re: IMXRT1171 Flexcan MassageBox Filter (range filter function?)</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2001787#M32714</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;For FlexCAN filtering with CAN FD, you can use global masking to filter a range of CAN IDs. Set a global mask to accept the desired range, for example, IDs from 0x100 to 0x200. Use FLEXCAN_SetRxMbGlobalMask to apply this mask and configure individual masks for each message buffer accordingly&amp;nbsp;&lt;A href="https://www.litebluelite.com" target="_self"&gt;&lt;FONT color="#FFFFFF"&gt;LiteBlue&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Nov 2024 08:41:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2001787#M32714</guid>
      <dc:creator>eva78mason</dc:creator>
      <dc:date>2024-11-26T08:41:19Z</dc:date>
    </item>
    <item>
      <title>Re: IMXRT1171 Flexcan MassageBox Filter (range filter function?)</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2003445#M32753</link>
      <description>&lt;P&gt;Testing Based on Your Response:&lt;/P&gt;&lt;P&gt;MB0: RX 0x64&lt;BR /&gt;MB1: TX&lt;BR /&gt;MB2: RX 0x67&lt;BR /&gt;RXMGMASK = 0x1FF3FFFF&lt;/P&gt;&lt;P&gt;When testing with this configuration, I confirmed that MB0 could receive IDs ranging from 0x64 to 0x67 in its buffer.&lt;/P&gt;&lt;P&gt;I understood that the setting for the RXMGMASK is based on configuring '0' bits for the range between criterion A and criterion B, which defines the allowed IDs.&lt;/P&gt;&lt;P&gt;However, I have set 0x64 and 0x67 as MB0 and MB2, respectively, but is there any specific criterion for assigning MB (Message Buffer) numbers?&lt;/P&gt;&lt;P&gt;If I add another criterion to a different MB, how would it behave?&lt;BR /&gt;For example: MB3: RX 0x70&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2024 07:03:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2003445#M32753</guid>
      <dc:creator>Seunghyup</dc:creator>
      <dc:date>2024-11-28T07:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: IMXRT1171 Flexcan MassageBox Filter (range filter function?)</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2004290#M32772</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/240126"&gt;@Seunghyup&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thank you so much for your interest in our products and for using our community.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;RXMGMASK: RXMGMASK is used to mask the filter fields of all Rx MBs, excluding MBs 14-15,&lt;BR /&gt;which have individual mask registers.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please pay attention&amp;nbsp;MCR[IRMQ] setting.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mayliu1_0-1732875758077.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/313298i3050702A428E8E95/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mayliu1_0-1732875758077.png" alt="mayliu1_0-1732875758077.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;RXIMR0~63: These can allow&amp;nbsp; more fine-grained filtering settings for each available Rx mailbox.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mayliu1_1-1732876122044.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/313299iE9A9A458EEF2BB7C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mayliu1_1-1732876122044.png" alt="mayliu1_1-1732876122044.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wish it helps you.&lt;BR /&gt;If you still have question about it, please kindly let me know.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;mayliu&lt;/P&gt;</description>
      <pubDate>Fri, 29 Nov 2024 10:30:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/IMXRT1171-Flexcan-MassageBox-Filter-range-filter-function/m-p/2004290#M32772</guid>
      <dc:creator>mayliu1</dc:creator>
      <dc:date>2024-11-29T10:30:20Z</dc:date>
    </item>
  </channel>
</rss>

