<?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>i.MX Processors中的主题 Issue with Hardware timestamp</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Issue-with-Hardware-timestamp/m-p/856117#M130916</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Hi All,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;we can feed 125MHz clock to ENET_REF_Clk in three ways&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Through EXTERNAL oscillator&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Through PHY&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Through GPIO_16&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;As per my hardware design ENET_REF_CLK(V22) is already connected to PHY(KSZ9031) CLK125_NDO/LED_MODE pin,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;and Phy(KSZ9031) is generating 125 MHz clock and forwarding it to ENET_REF_CLK(V22).&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;KSZ9031 having some errata#2&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;SPAN style="border: 0px; font-weight: inherit;"&gt;&lt;EM&gt;The 125MHz reference clock (CLK125_NDO pin) output has duty cycle variation when the KSZ9031RNX links up in 1000Base-T Slave mode, resulting in wide variation on the falling clock edge.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;BR /&gt;for workaround, I had applied a patch from below link which Set KSZ9031RNX to always link up in 1000Base-T Master mode by setting register 9h, bits [12:11] to ‘11’.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;A class="" data-content-finding="Community" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fpatchwork.ozlabs.org%2Fpatch%2F912742%2F" rel="nofollow" style="color: #3d9ce7; border: 0px; font-weight: inherit; text-decoration: none; padding: 0px calc(12px + 0.35ex) 0px 0px;" target="_blank"&gt;https://patchwork.ozlabs.org/patch/912742/&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;But still I'm not able to sync the clock with hardware timestamp using ptp.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Am i missing some thing or ENET_REF_CLK(v22) needs any configurations to be done?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Unfortunately ENET_REF_CLk(V22) ball didn't came out&amp;nbsp; in my design to check whether clock is coming on to this ball.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Is there a way to check whether the clock is coming to ENET mac through software?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Sankar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Jan 2019 06:00:45 GMT</pubDate>
    <dc:creator>sankarsalla</dc:creator>
    <dc:date>2019-01-07T06:00:45Z</dc:date>
    <item>
      <title>Issue with Hardware timestamp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Issue-with-Hardware-timestamp/m-p/856117#M130916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Hi All,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;we can feed 125MHz clock to ENET_REF_Clk in three ways&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Through EXTERNAL oscillator&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Through PHY&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Through GPIO_16&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;As per my hardware design ENET_REF_CLK(V22) is already connected to PHY(KSZ9031) CLK125_NDO/LED_MODE pin,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;and Phy(KSZ9031) is generating 125 MHz clock and forwarding it to ENET_REF_CLK(V22).&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;KSZ9031 having some errata#2&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;SPAN style="border: 0px; font-weight: inherit;"&gt;&lt;EM&gt;The 125MHz reference clock (CLK125_NDO pin) output has duty cycle variation when the KSZ9031RNX links up in 1000Base-T Slave mode, resulting in wide variation on the falling clock edge.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;BR /&gt;for workaround, I had applied a patch from below link which Set KSZ9031RNX to always link up in 1000Base-T Master mode by setting register 9h, bits [12:11] to ‘11’.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;A class="" data-content-finding="Community" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fpatchwork.ozlabs.org%2Fpatch%2F912742%2F" rel="nofollow" style="color: #3d9ce7; border: 0px; font-weight: inherit; text-decoration: none; padding: 0px calc(12px + 0.35ex) 0px 0px;" target="_blank"&gt;https://patchwork.ozlabs.org/patch/912742/&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;But still I'm not able to sync the clock with hardware timestamp using ptp.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Am i missing some thing or ENET_REF_CLK(v22) needs any configurations to be done?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Unfortunately ENET_REF_CLk(V22) ball didn't came out&amp;nbsp; in my design to check whether clock is coming on to this ball.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Is there a way to check whether the clock is coming to ENET mac through software?&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Sankar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jan 2019 06:00:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Issue-with-Hardware-timestamp/m-p/856117#M130916</guid>
      <dc:creator>sankarsalla</dc:creator>
      <dc:date>2019-01-07T06:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with Hardware timestamp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Issue-with-Hardware-timestamp/m-p/856118#M130917</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;&amp;nbsp;&amp;nbsp; Please use Table 2-9 (Gigabit Ethernet Recommendations) of the recent release&lt;/P&gt;&lt;P class=""&gt;of the &lt;SPAN class=""&gt;Hardware Development Guide for i.MX6, where there are explanations how &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;the GPIO_16 ball must be used / configured for IEEE-1588 timestamp operation.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt; &lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;A href="http://cache.nxp.com/assets/documents/data/en/user-guides/IMX6DQ6SDLHDG.pdf"&gt;http://cache.nxp.com/assets/documents/data/en/user-guides/IMX6DQ6SDLHDG.pdf&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Yuri&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&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>Wed, 16 Jan 2019 09:42:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Issue-with-Hardware-timestamp/m-p/856118#M130917</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2019-01-16T09:42:01Z</dc:date>
    </item>
  </channel>
</rss>

