<?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 LP2387 ENET_REF_CLK specs in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LP2387-ENET-REF-CLK-specs/m-p/549751#M13885</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by eeckenrode on Thu Feb 25 09:04:56 MST 2016&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We have a two board design where we connect a LAN8720A daughter board to a third party LPC2387 main board that we purchase.&amp;nbsp; We have noticed some radiated emission issues to the point we cannot pass emission certifications for our product.&amp;nbsp; The ENET_REF_CLK passes through a connect between the boards.&amp;nbsp; This is the source of our emissions issue.&amp;nbsp; We have been able to reduce emissions significantly by slowing the edges on the ENET_REF_CLK with a capacitor.&amp;nbsp; We are looking for LPC2387 timing requirements for the MAC interface (in particular the ENET_REF_CLK) because we need to determine if we are violating any timing requirements.&amp;nbsp; We are most curious if rounding the ENET_REF_CLK signal is a major concern?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-notes-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Placed a 47pF cap on ENET_REF_CLK.&amp;nbsp; This essentially makes the clock signal mostly sinusoidal.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Trace lengths on Daughter Card - 0.25 inches (impedance matched)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Trace lengths on Main Board - 0.375 inches&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Connector between boards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;As tested with additional capacitor, signal integrity seems good and data transmission seems OK in the lab.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Eric&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 19:51:54 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T19:51:54Z</dc:date>
    <item>
      <title>LP2387 ENET_REF_CLK specs</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LP2387-ENET-REF-CLK-specs/m-p/549751#M13885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by eeckenrode on Thu Feb 25 09:04:56 MST 2016&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We have a two board design where we connect a LAN8720A daughter board to a third party LPC2387 main board that we purchase.&amp;nbsp; We have noticed some radiated emission issues to the point we cannot pass emission certifications for our product.&amp;nbsp; The ENET_REF_CLK passes through a connect between the boards.&amp;nbsp; This is the source of our emissions issue.&amp;nbsp; We have been able to reduce emissions significantly by slowing the edges on the ENET_REF_CLK with a capacitor.&amp;nbsp; We are looking for LPC2387 timing requirements for the MAC interface (in particular the ENET_REF_CLK) because we need to determine if we are violating any timing requirements.&amp;nbsp; We are most curious if rounding the ENET_REF_CLK signal is a major concern?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-notes-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Placed a 47pF cap on ENET_REF_CLK.&amp;nbsp; This essentially makes the clock signal mostly sinusoidal.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Trace lengths on Daughter Card - 0.25 inches (impedance matched)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Trace lengths on Main Board - 0.375 inches&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Connector between boards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;As tested with additional capacitor, signal integrity seems good and data transmission seems OK in the lab.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Eric&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:51:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LP2387-ENET-REF-CLK-specs/m-p/549751#M13885</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:51:54Z</dc:date>
    </item>
    <item>
      <title>Re: LP2387 ENET_REF_CLK specs</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LP2387-ENET-REF-CLK-specs/m-p/549752#M13886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by DF9DQ on Wed Mar 02 00:24:03 MST 2016&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi Eric,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;A big issue will probably be the drift of the actual 0-&amp;gt;1/1-&amp;gt;0 thresholds of the clock input due to component variations and in particular temperature. Small changes of the threshold result in large timing uncertainties if the clock slopes are slow.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've seen cases where adding much smaller caps (up to 10p) was beneficial, but then the intended delay due to the slowed down slope was only moderate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My worries are that your positive lab results may not be reliably repeatable in production.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Rolf&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:51:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LP2387-ENET-REF-CLK-specs/m-p/549752#M13886</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:51:55Z</dc:date>
    </item>
  </channel>
</rss>

