<?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: Using KSZ8081RNA with RT1050 in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818217#M1252</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To make me able to accurately study the case, please provide some more information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's on the other side of the Ethernet link? You said that there is some activity oh the RX[1:0] signals, so, RT1050 should receive something. Does it? Does RT1050 output any log on the serial console?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, please provide the PHY data sheet and the complete schematic of your hardware.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Artur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Nov 2018 10:27:39 GMT</pubDate>
    <dc:creator>art</dc:creator>
    <dc:date>2018-11-30T10:27:39Z</dc:date>
    <item>
      <title>Solved: Using KSZ8081RNA with RT1050</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818216#M1251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi fellow engineers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are developing a board with RT1050 that uses the RNA physical chip instead than RNB version as in the EVKB.&lt;/P&gt;&lt;P&gt;So far we have had no success in making our board work. I hope someone has experience with this.&lt;/P&gt;&lt;P&gt;This is the scenario.&lt;/P&gt;&lt;P&gt;1) we modified the connections between the PHY and the MCU as shown in the image.&lt;/P&gt;&lt;P&gt;2) we are using the lwip_ping demo firmware that comes in MCUXpresso&lt;/P&gt;&lt;P&gt;3) the only change we did is setting BOARD_ENET0_PHY_ADDRESS to zero instead than 2. By doing so, the PHY recognizes a connection and negotiates a 100 Mbps link. The MCU correctly reads the status of the PHY.&lt;/P&gt;&lt;P&gt;We get traffic on the RX[0..1] lines, but TX_EN is low, and there is no traffic on TX[0..1].&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/78751i5C3B26D6C11A79D2/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;We connected ETH.RST and ETH.INT to GPIOs. When the board starts, there is a cycle reset.&lt;/P&gt;&lt;P&gt;REFCLOCK gets a 25 MHz from the MCU (pin B13 configured as REF_CLK)&lt;/P&gt;&lt;P&gt;CRS_DV is connected to pin G2, configured as RX_EN like in the EVK board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any hints?&lt;/P&gt;&lt;P&gt;:-)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2018 16:37:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818216#M1251</guid>
      <dc:creator>giuseppescarpi</dc:creator>
      <dc:date>2018-11-29T16:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: Using KSZ8081RNA with RT1050</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818217#M1252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To make me able to accurately study the case, please provide some more information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's on the other side of the Ethernet link? You said that there is some activity oh the RX[1:0] signals, so, RT1050 should receive something. Does it? Does RT1050 output any log on the serial console?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, please provide the PHY data sheet and the complete schematic of your hardware.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Artur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Nov 2018 10:27:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818217#M1252</guid>
      <dc:creator>art</dc:creator>
      <dc:date>2018-11-30T10:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: Using KSZ8081RNA with RT1050</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818218#M1253</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Artur, thank you for your answer.&lt;/P&gt;&lt;P&gt;It seems that the RT1050 does not receive anything. The firmware works in the EVK-B, but when ported to our board (changing some Ethernet pins assignment and the GPIOs for RST and INT), it does not.&lt;/P&gt;&lt;P&gt;Of course I have no problems to provide you the datasheet. For the schematic, I cannot publish it on the forum. If you want I can either send it to an NXP email address (we already have an NDA in place with NXP), or contact your FAE in Italy (Mr. Ferrari).&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://ww1.microchip.com/downloads/en/DeviceDoc/00002199A.pdf" title="http://ww1.microchip.com/downloads/en/DeviceDoc/00002199A.pdf"&gt;http://ww1.microchip.com/downloads/en/DeviceDoc/00002199A.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Nov 2018 13:27:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818218#M1253</guid>
      <dc:creator>giuseppescarpi</dc:creator>
      <dc:date>2018-11-30T13:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Using KSZ8081RNA with RT1050</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818219#M1254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the end I discovered the problem.&lt;/P&gt;&lt;P&gt;The hardware is perfectly OK, and you can use versione RNA of the physical with zero changes.&lt;/P&gt;&lt;P&gt;The problem was a settings in the reference clock pin. You have to enable the "Software Input On" flag in the pin configuration.&lt;/P&gt;&lt;P&gt;By default, this is set to Disabled. SDK projects override the value to Enabled, but when you relocate the signal to a different pin (this was our case) you lose the override.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/62363i83CACD57E176373E/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, &lt;EM&gt;caveat emptor!&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Once the flag is set, the lwip examples work with no problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2018 16:06:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Solved-Using-KSZ8081RNA-with-RT1050/m-p/818219#M1254</guid>
      <dc:creator>giuseppescarpi</dc:creator>
      <dc:date>2018-12-06T16:06:19Z</dc:date>
    </item>
  </channel>
</rss>

