<?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: Incorrect behavior when send/received small Ethernet frame in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040894#M153355</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use the i.MX 8QuadXPlus.&lt;/P&gt;&lt;P&gt;We don't use bsp, we use it bare metal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regard&lt;/P&gt;&lt;P&gt;Alexandre&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Le lun. 22 juin 2020 à 15:51, jimmychan &amp;lt;admin@community.nxp.com&amp;gt; a écrit :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE level="1"&gt;&lt;P&gt;NXP Community&lt;/P&gt;&lt;P&gt;&amp;lt;https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg&amp;gt;&lt;/P&gt;&lt;P&gt;Re: Incorrect behavior when send/received small Ethernet frame&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reply from jimmychan&lt;/P&gt;&lt;P&gt;&amp;lt;https://community.nxp.com/people/jimmychan?et=watches.email.thread&amp;gt; in *i.MX&lt;/P&gt;&lt;P&gt;Processors* - View the full discussion&lt;/P&gt;&lt;P&gt;&amp;lt;https://community.nxp.com/message/1330247?commentID=1330247&amp;amp;et=watches.email.thread#comment-1330247&amp;gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Jun 2020 14:37:24 GMT</pubDate>
    <dc:creator>alex_froissard</dc:creator>
    <dc:date>2020-06-23T14:37:24Z</dc:date>
    <item>
      <title>Incorrect behavior when send/received small Ethernet frame</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040892#M153353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a behavior than I don't understand, I send a Ethernet frame for ENET0 to ENET1 (they are connected together by a wire). When I send a frame bigger or equal to 88&amp;nbsp;Bytes everything work correctly, but if I try to send a frame smaller, at the reception the RxBD data length&amp;nbsp;field is equal to&amp;nbsp;1520 bytes (value of the MRBR register).&lt;/P&gt;&lt;P&gt;The ENETs are in store and forward mode, the FIFO threshold are the default value.&lt;/P&gt;&lt;P&gt;The Ethernet configuration is RGMII 100Mbits/s.&lt;/P&gt;&lt;P&gt;I use the legacy buffer descriptor and the option to compute the CRC and send it by the MAC is activated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is someone has an idea about why I have this behavior?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Jun 2020 17:56:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040892#M153353</guid>
      <dc:creator>alex_froissard</dc:creator>
      <dc:date>2020-06-12T17:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect behavior when send/received small Ethernet frame</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040893#M153354</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;which product/chip are you using? &lt;/P&gt;&lt;P&gt;which bsp (and version) are you using?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jun 2020 19:51:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040893#M153354</guid>
      <dc:creator>jimmychan</dc:creator>
      <dc:date>2020-06-22T19:51:16Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect behavior when send/received small Ethernet frame</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040894#M153355</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use the i.MX 8QuadXPlus.&lt;/P&gt;&lt;P&gt;We don't use bsp, we use it bare metal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regard&lt;/P&gt;&lt;P&gt;Alexandre&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Le lun. 22 juin 2020 à 15:51, jimmychan &amp;lt;admin@community.nxp.com&amp;gt; a écrit :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE level="1"&gt;&lt;P&gt;NXP Community&lt;/P&gt;&lt;P&gt;&amp;lt;https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg&amp;gt;&lt;/P&gt;&lt;P&gt;Re: Incorrect behavior when send/received small Ethernet frame&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reply from jimmychan&lt;/P&gt;&lt;P&gt;&amp;lt;https://community.nxp.com/people/jimmychan?et=watches.email.thread&amp;gt; in *i.MX&lt;/P&gt;&lt;P&gt;Processors* - View the full discussion&lt;/P&gt;&lt;P&gt;&amp;lt;https://community.nxp.com/message/1330247?commentID=1330247&amp;amp;et=watches.email.thread#comment-1330247&amp;gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jun 2020 14:37:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040894#M153355</guid>
      <dc:creator>alex_froissard</dc:creator>
      <dc:date>2020-06-23T14:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect behavior when send/received small Ethernet frame</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040895#M153356</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is still persistent, I will describe what I did, and the result I get. On the image below you can see the configuration of both ENET and&amp;nbsp;buffer descriptor for Tx and Rx.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ENET0 is loop to the ENET1 with a cable. (Problem is present also in internal loopback)&lt;/P&gt;&lt;P&gt;The buffer descriptor are in enhanced&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Tx BD (AS_ENET0_TXBD) : Length is set to 60 (0x3C)&amp;nbsp;and option L (Last in frame), TC (Transmit CRC) and R (ready) are set&lt;/P&gt;&lt;P&gt;- Rx BD &lt;SPAN&gt;(AS_ENET1_RXBD)&amp;nbsp;&lt;/SPAN&gt;: Only the option E (empty) is set&lt;/P&gt;&lt;P&gt;- The transmission and reception are configured in store and forward&lt;/P&gt;&lt;P&gt;- Then the register&amp;nbsp;ENET_TDAR is set to 0x01000000 to inform the MAC to start the transmission&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt; The field R of the TX BD is clear&amp;nbsp;and the&amp;nbsp;BDU (Last buffer descriptor update done.) is set by the MAC&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt; No error flag are raised in the Tx BD&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt; No interrupt flag are raised&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt; ENET_RMON_T_PACKETS is equal to 1 (one packet has been send)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_RMON_T_P64 is equal to 1 (one packet of 64 bytes has been send)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_RMON_T_OCTETS is equal to 0x40 (64 bytes has been send)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_IEEE_T_FRAME_OK is equal to 1 (one packet transmitted OK)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_IEEE_T_OCTETS_OK is equal to 0x40 (64 bytes transmitted without error)&lt;/P&gt;&lt;P&gt;- Then the register ENET_RDAR is set to 0x01000000 to received the data&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt; The field E of the Rx BD is clear, &lt;EM&gt;the field L set no set&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt; &lt;STRONG&gt;The data length of the Rx BD is set to 0x05F0 (Value of MRBR register)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;-&amp;gt; No error flag are raised in the Rx BD&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt; No interrupt flag are raised&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_RMON_R_PACKETS is equal to 1 (one packet received)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_RMON_R_P64 is equal to 1 (one packet of 64 Bytes received)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_RMON_R_OCTETS is equal to 0x40 (64 Bytes received)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_IEEE_R_FRAME_OK is equal to 1 (one frames received OK)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;-&amp;gt;&amp;nbsp;ENET_IEEE_R_OCTETS_OK is equal to 0x40 (&lt;STRONG&gt;64 Bytes received without error&lt;/STRONG&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pb_small_msg.JPG"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/114886iF980464D994C4531/image-size/large?v=v2&amp;amp;px=999" role="button" title="pb_small_msg.JPG" alt="pb_small_msg.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that If a second message is send, the transmission will work but not the reception, it's like it's stuck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't understand why the value write in the field Data length in the Rx BD is the value of the MRBR register whereas the counter show the reception of 1 frame of 64 bytes and no error are detected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Alexandre&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jul 2020 19:22:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040895#M153356</guid>
      <dc:creator>alex_froissard</dc:creator>
      <dc:date>2020-07-07T19:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect behavior when send/received small Ethernet frame</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040896#M153357</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This behavior is really similar to errata ERR050395 "ENET: Ethernet RX hang when receiving traffic through multiple queues" except that Alexandre is using a single ring... So we do not understand how we could fall into this errata...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Étienne&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jul 2020 18:05:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1040896#M153357</guid>
      <dc:creator>EAlepins</dc:creator>
      <dc:date>2020-07-08T18:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect behavior when send/received small Ethernet frame</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1319760#M178028</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have found the origin of the problem, the value that was in the register MRBR was not divisibly by 64 like asking by the reference manual.&lt;/P&gt;&lt;P&gt;After we respect this constraint the problem disappear.&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Alexandre&lt;/P&gt;</description>
      <pubDate>Fri, 06 Aug 2021 15:39:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Incorrect-behavior-when-send-received-small-Ethernet-frame/m-p/1319760#M178028</guid>
      <dc:creator>AFR89</dc:creator>
      <dc:date>2021-08-06T15:39:06Z</dc:date>
    </item>
  </channel>
</rss>

