<?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>PowerQUICC Processors中的主题 MPC8548 eTSEC truncated Tx frame exceeds MAXFRM</title>
    <link>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607224#M1676</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;During MPC8548 Ethernet testing, we have observed that when a Tx frame is truncated, the eTSEC&amp;nbsp;&lt;SPAN style="font-size: 11.0pt;"&gt;always sends exactly (MAXFRM + 5) bytes. It doesn’t matter how many bytes over MAXFRM you were trying to send (1, 1000, etc…). Looking at the extra 5 bytes, the first one is an extra valid data byte from the transmit buffer (i.e. txbuf[MAXFRM]). The last 4 look random. They are not data and they are not a valid CRC.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;Is this the expected MPC8548 eTSEC behavior?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Oct 2016 23:25:53 GMT</pubDate>
    <dc:creator>robertbracero</dc:creator>
    <dc:date>2016-10-26T23:25:53Z</dc:date>
    <item>
      <title>MPC8548 eTSEC truncated Tx frame exceeds MAXFRM</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607224#M1676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;During MPC8548 Ethernet testing, we have observed that when a Tx frame is truncated, the eTSEC&amp;nbsp;&lt;SPAN style="font-size: 11.0pt;"&gt;always sends exactly (MAXFRM + 5) bytes. It doesn’t matter how many bytes over MAXFRM you were trying to send (1, 1000, etc…). Looking at the extra 5 bytes, the first one is an extra valid data byte from the transmit buffer (i.e. txbuf[MAXFRM]). The last 4 look random. They are not data and they are not a valid CRC.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;Is this the expected MPC8548 eTSEC behavior?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Oct 2016 23:25:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607224#M1676</guid>
      <dc:creator>robertbracero</dc:creator>
      <dc:date>2016-10-26T23:25:53Z</dc:date>
    </item>
    <item>
      <title>Re: MPC8548 eTSEC truncated Tx frame exceeds MAXFRM</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607225#M1677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Can you please provide the following information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Your&amp;nbsp; MPC8548 silicon revision.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. NXP SDK/BSP version you are working with, if at all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Is this a custom board or CDS? If custom, please specify the&lt;BR /&gt;&amp;nbsp;&amp;nbsp; model of the PHY &amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Do all eTSECs exhibit this behaviour or only one?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5. Please share a register dump of the problematic eTSEC,&lt;BR /&gt;&amp;nbsp;&amp;nbsp; taken after the problem manifests itself. Please include the&lt;BR /&gt;&amp;nbsp;&amp;nbsp; following areas: eTSEC general config registers(0x2_4000 to 0FF), &lt;BR /&gt;&amp;nbsp;&amp;nbsp; MAC registers (offset 0x2_4500 to 5BF)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Nov 2016 09:49:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607225#M1677</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2016-11-08T09:49:08Z</dc:date>
    </item>
    <item>
      <title>Re: MPC8548 eTSEC truncated Tx frame exceeds MAXFRM</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607226#M1678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1.      pvr=0x80210022&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.      Green Hills Software INTEGRITY BSP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.      This is a custom board with a TLK100 PHY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4.      Only one eTSEC is brought out on this board (eTSEC3)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5.      Attached is the raw memory dump of the eTSEC register block (0x2_6000 – 0x2_6FFF) immediately after sending a truncated Tx frame.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Nov 2016 14:00:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607226#M1678</guid>
      <dc:creator>robertbracero</dc:creator>
      <dc:date>2016-11-11T14:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: MPC8548 eTSEC truncated Tx frame exceeds MAXFRM</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607227#M1679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have tested this on the CDS8548 board as well and confirmed that 5 extra bytes always get sent when Tx truncation occurs. The pvr is&amp;nbsp;0x80210020, and in this case all 5 bytes are always 0x0e.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2017 23:16:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/MPC8548-eTSEC-truncated-Tx-frame-exceeds-MAXFRM/m-p/607227#M1679</guid>
      <dc:creator>robertbracero</dc:creator>
      <dc:date>2017-01-06T23:16:23Z</dc:date>
    </item>
  </channel>
</rss>

