<?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: ETHERNET COMMUNICATION in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1667484#M25481</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/207121"&gt;@achal&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;What you marked in the screenshot is mac address. PHY address is defined in board.h&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/*! @brief The ENET PHY address. */
#define BOARD_ENET0_PHY_ADDRESS (0x02U) /* Phy address of enet port 0. */

&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jing&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 12 Jun 2023 09:26:33 GMT</pubDate>
    <dc:creator>jingpan</dc:creator>
    <dc:date>2023-06-12T09:26:33Z</dc:date>
    <item>
      <title>ETHERNET COMMUNICATION</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1667277#M25462</link>
      <description>&lt;P&gt;PLEAE TELL in this below example how the developed decided these phy address and mac address&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="achal_0-1686485445062.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/227092i89BD5BDE9F96D680/image-size/medium?v=v2&amp;amp;px=400" role="button" title="achal_0-1686485445062.png" alt="achal_0-1686485445062.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 11 Jun 2023 12:08:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1667277#M25462</guid>
      <dc:creator>achal</dc:creator>
      <dc:date>2023-06-11T12:08:52Z</dc:date>
    </item>
    <item>
      <title>Re: ETHERNET COMMUNICATION</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1667484#M25481</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/207121"&gt;@achal&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;What you marked in the screenshot is mac address. PHY address is defined in board.h&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/*! @brief The ENET PHY address. */
#define BOARD_ENET0_PHY_ADDRESS (0x02U) /* Phy address of enet port 0. */

&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jing&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2023 09:26:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1667484#M25481</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2023-06-12T09:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: ETHERNET COMMUNICATION</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1672608#M25585</link>
      <description>&lt;P&gt;Hi&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.nxp.com/t5/user/viewprofilepage/user-id/61241" target="_blank"&gt;@jingpan&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for responding, can you please tell why phy address is defined as&amp;nbsp; 0x02 only and why not something else like 0x03 or 0x04. Is there any document which mentions that if we have to work on this board then 0x02 has to be used as phy address.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please also tell that how this particular MAC address is chosen? same is it given in some document ?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 09:35:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1672608#M25585</guid>
      <dc:creator>achal</dc:creator>
      <dc:date>2023-06-20T09:35:02Z</dc:date>
    </item>
    <item>
      <title>Re: ETHERNET COMMUNICATION</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1675405#M25649</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/207121"&gt;@achal&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;PHY address is determined by PHY address config pins on the PHY chip. Please refer to the EVK board.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="jingpan_0-1687679001677.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/229141iDF929C8FD60C427A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="jingpan_0-1687679001677.png" alt="jingpan_0-1687679001677.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MAC address is random in the demo. Officially it is allocated by IEEE (Institute of Electrical and Electronics Engineers), the last three bytes, the hexadecimal number AE-3C-40 represents the serial number of a certain network product (such as network card) manufactured by the manufacturer.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jing&lt;/P&gt;</description>
      <pubDate>Sun, 25 Jun 2023 07:47:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/ETHERNET-COMMUNICATION/m-p/1675405#M25649</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2023-06-25T07:47:37Z</dc:date>
    </item>
  </channel>
</rss>

