<?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: i.MX6SoloX RGMII TX_CTL delay in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633300#M96326</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vadim&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reference designs are made when not all chip parameters are fully&lt;/P&gt;&lt;P&gt;validated and formally it is necessary to follow delays given in&lt;/P&gt;&lt;P&gt;Table 69. RGMII Signal Switching Specifications&amp;nbsp;i.MX6SX Datasheet &lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fcache.freescale.com%2Ffiles%2F32bit%2Fdoc%2Fdata_sheet%2FIMX6SXCEC.pdf" rel="nofollow" target="_blank"&gt;http://cache.freescale.com/files/32bit/doc/data_sheet/IMX6SXCEC.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Sep 2016 23:38:22 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2016-09-20T23:38:22Z</dc:date>
    <item>
      <title>i.MX6SoloX RGMII TX_CTL delay</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633299#M96325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;In &lt;A href="https://community.nxp.com/thread/384608"&gt;i.MX6SoloX RGMII1_TX_CTL delay to AR8035&lt;/A&gt;&amp;nbsp; it is recommended to implement 1.75ns TX_CTL delay as PCB trace delay and the following NXP PCB photo is presented as an example:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="circuit-board-traces.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/5626i07188838C8D1DB9C/image-size/large?v=v2&amp;amp;px=999" role="button" title="circuit-board-traces.jpg" alt="circuit-board-traces.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the reference for the SABRE Board (&lt;A class="link-titled" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.nxp.com%2Fproducts%2Fmicrocontrollers-and-processors%2Farm-processors%2Fi.mx-applications-processors-based-on-arm-cores%2Fi.mx-6-processors%2Fi.mx6qp%2Fsabre-board-for-smart-devices-reference-design-based-on-the-i.mx-6-series%3ARDIMX6SABREBRD" title="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.nxp.com%2Fproducts%2Fmicrocontrollers-and-processors%2Farm-processors%2Fi.mx-applications-processors-based-on-arm-cores%2Fi.mx-6-processors%2Fi.mx6qp%2Fsabre-board-for-smart-devices-reference-design-based-on-the-i.mx-6-series%3ARDIMX6SABREBRD"&gt;https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.nxp.com%2Fproducts%2Fmicrocontrollers-and-processors%2…&lt;/A&gt; isn't contain data.&lt;/P&gt;&lt;P&gt;The RGMII2 TX traces in the LAY-27962_C.brd have&amp;nbsp; the following lengths:&lt;/P&gt;&lt;P&gt;RGMII2_TXCLK: 1762.4mil&lt;/P&gt;&lt;P&gt;RGMII_TXD3: 2068.05mil&lt;/P&gt;&lt;P&gt;RGMII2_TXD2: 1899.02mil&lt;/P&gt;&lt;P&gt;RGMII2_TX1: 1835.57mil&lt;/P&gt;&lt;P&gt;RGMII2_TXD0: 1778.63mil&lt;/P&gt;&lt;P&gt;RGMII2_TXEN: 1710.34mil.&lt;/P&gt;&lt;P&gt;So actually the TXCLK is almost shortest trace in the RGMII2 TX group and no delay is implemented by the PCB clock trace.&lt;/P&gt;&lt;P&gt;How the recommended RGMII clock delays are implemented in the NXP reference boards/design?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Vadim Aleynikov&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Sep 2016 15:23:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633299#M96325</guid>
      <dc:creator>vadimaleynikov</dc:creator>
      <dc:date>2016-09-20T15:23:59Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6SoloX RGMII TX_CTL delay</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633300#M96326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vadim&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reference designs are made when not all chip parameters are fully&lt;/P&gt;&lt;P&gt;validated and formally it is necessary to follow delays given in&lt;/P&gt;&lt;P&gt;Table 69. RGMII Signal Switching Specifications&amp;nbsp;i.MX6SX Datasheet &lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fcache.freescale.com%2Ffiles%2F32bit%2Fdoc%2Fdata_sheet%2FIMX6SXCEC.pdf" rel="nofollow" target="_blank"&gt;http://cache.freescale.com/files/32bit/doc/data_sheet/IMX6SXCEC.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Sep 2016 23:38:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633300#M96326</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-09-20T23:38:22Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6SoloX RGMII TX_CTL delay</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633301#M96327</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;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Two fields&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;RXC_DLY and TXC_DLY &amp;nbsp;of ENETx_ECR register &amp;nbsp;were added&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;in the recent i.MX6SX RM.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yuri.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Oct 2016 04:37:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633301#M96327</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2016-10-04T04:37:32Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6SoloX RGMII TX_CTL delay</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633302#M96328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Thank you for the message. Do you mean RM Rev. 1, 6/2016? If these bits really control anything? What are values of these delays? The &lt;SPAN style="color: #51626f; background-color: #ffffff; border: 0px;"&gt; i.MX6SX&lt;/SPAN&gt; datasheets don't contain these data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Vadim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Oct 2016 08:57:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633302#M96328</guid>
      <dc:creator>vadimaleynikov</dc:creator>
      <dc:date>2016-10-05T08:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6SoloX RGMII TX_CTL delay</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633303#M96329</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 issue is under discussion yet :&amp;nbsp;&lt;A href="https://community.nxp.com/thread/435696"&gt;https://community.nxp.com/thread/435696&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yuri.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Oct 2016 02:02:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633303#M96329</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2016-10-06T02:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX6SoloX RGMII TX_CTL delay</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633304#M96330</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 class=""&gt;&amp;nbsp; Appears,&amp;nbsp; &lt;SPAN class=""&gt;i.MX6SX doesn't have that feature (&lt;SPAN style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;RXC_DLY and TXC_DLY &amp;nbsp;of ENETx_ECR register&lt;/SPAN&gt;).&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yuri.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Oct 2016 07:25:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX6SoloX-RGMII-TX-CTL-delay/m-p/633304#M96330</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2016-10-13T07:25:51Z</dc:date>
    </item>
  </channel>
</rss>

