<?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: Ehernet interface not up in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/Ehernet-interface-not-up/m-p/880150#M4073</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The kernel informs you that it is unable read certain registers in &lt;BR /&gt;the PHY and/or the PHY stops responding while being initialized. &lt;BR /&gt;This can be a Device Tree or a hardware issue. Suggestions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Make sure you properly specified the PHY connection to the processor&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MDIO and the PHY management addresses in the Device Tree. Take&lt;BR /&gt;&amp;nbsp;&amp;nbsp; fsl-ls1088a-rdb.dts as a reference.&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;2. Monitor MDIO/MDC interface with a scope, make sure the signal shapes&lt;BR /&gt;&amp;nbsp;&amp;nbsp; meet the requirements of the processor and the PHY Hardware&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Specifications.&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Platon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 09 Apr 2019 17:44:08 GMT</pubDate>
    <dc:creator>bpe</dc:creator>
    <dc:date>2019-04-09T17:44:08Z</dc:date>
    <item>
      <title>Ehernet interface not up</title>
      <link>https://community.nxp.com/t5/Layerscape/Ehernet-interface-not-up/m-p/880149#M4072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Team&lt;/P&gt;&lt;P&gt;We are using custom LS2088A board in which, we are using&amp;nbsp;F104S8A Ethernet PHY for QSGMII interface.&lt;/P&gt;&lt;P&gt;We are getting the following error:&lt;/P&gt;&lt;P&gt;getting below&amp;nbsp; kernel logs.&lt;/P&gt;&lt;P&gt;libphy: Freescale XGMAC MDIO Bus: probed&lt;BR /&gt; mdio_bus 8b96000: Error while reading PHY16 reg at 2.2&lt;BR /&gt; mdio_bus 8b96000: Error while reading PHY16 reg at 3.3&lt;BR /&gt; mdio_bus 8b96000: MDIO device at address 16 is missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no Ethernet interface is created.&lt;/P&gt;&lt;P&gt;&amp;nbsp;ifconfig -a&lt;BR /&gt;docker0: flags=4098&amp;lt;BROADCAST,MULTICAST&amp;gt;&amp;nbsp; mtu 1500&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inet 172.17.0.1&amp;nbsp; netmask 255.255.0.0&amp;nbsp; broadcast 172.17.255.255&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ether 02:42:cd:a0:f6:7e&amp;nbsp; txqueuelen 0&amp;nbsp; (Ethernet)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RX packets 0&amp;nbsp; bytes 0 (0.0 B)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RX errors 0&amp;nbsp; dropped 0&amp;nbsp; overruns 0&amp;nbsp; frame 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TX packets 0&amp;nbsp; bytes 0 (0.0 B)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TX errors 0&amp;nbsp; dropped 0 overruns 0&amp;nbsp; carrier 0&amp;nbsp; collisions 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;lo: flags=73&amp;lt;UP,LOOPBACK,RUNNING&amp;gt;&amp;nbsp; mtu 65536&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inet 127.0.0.1&amp;nbsp; netmask 255.0.0.0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inet6 ::1&amp;nbsp; prefixlen 128&amp;nbsp; scopeid 0x10&amp;lt;host&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; loop&amp;nbsp; txqueuelen 1000&amp;nbsp; (Local Loopback)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RX packets 0&amp;nbsp; bytes 0 (0.0 B)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RX errors 0&amp;nbsp; dropped 0&amp;nbsp; overruns 0&amp;nbsp; frame 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TX packets 0&amp;nbsp; bytes 0 (0.0 B)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TX errors 0&amp;nbsp; dropped 0 overruns 0&amp;nbsp; carrier 0&amp;nbsp; collisions 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sit0: flags=128&amp;lt;NOARP&amp;gt;&amp;nbsp; mtu 1480&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; sit&amp;nbsp; txqueuelen 1000&amp;nbsp; (IPv6-in-IPv4)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RX packets 0&amp;nbsp; bytes 0 (0.0 B)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RX errors 0&amp;nbsp; dropped 0&amp;nbsp; overruns 0&amp;nbsp; frame 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TX packets 0&amp;nbsp; bytes 0 (0.0 B)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TX errors 0&amp;nbsp; dropped 0 overruns 0&amp;nbsp; carrier 0&amp;nbsp; collisions 0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2019 13:02:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Ehernet-interface-not-up/m-p/880149#M4072</guid>
      <dc:creator>jagadiswar_rao</dc:creator>
      <dc:date>2019-04-04T13:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: Ehernet interface not up</title>
      <link>https://community.nxp.com/t5/Layerscape/Ehernet-interface-not-up/m-p/880150#M4073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The kernel informs you that it is unable read certain registers in &lt;BR /&gt;the PHY and/or the PHY stops responding while being initialized. &lt;BR /&gt;This can be a Device Tree or a hardware issue. Suggestions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Make sure you properly specified the PHY connection to the processor&lt;BR /&gt;&amp;nbsp;&amp;nbsp; MDIO and the PHY management addresses in the Device Tree. Take&lt;BR /&gt;&amp;nbsp;&amp;nbsp; fsl-ls1088a-rdb.dts as a reference.&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;2. Monitor MDIO/MDC interface with a scope, make sure the signal shapes&lt;BR /&gt;&amp;nbsp;&amp;nbsp; meet the requirements of the processor and the PHY Hardware&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Specifications.&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Platon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt; Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Apr 2019 17:44:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Ehernet-interface-not-up/m-p/880150#M4073</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2019-04-09T17:44:08Z</dc:date>
    </item>
  </channel>
</rss>

