<?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: RT1050 ENET_INT pin direction in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1776165#M28070</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Pavel,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1) In example&amp;nbsp;evkbimxrt1050_lwip_ping_freertos, except to change ENET_INT as input, what else should I do?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2) Where can I find example&amp;nbsp;evkbimxrt1050_lwip_ping_freertos in the mcuxpresso github&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/nxp-mcuxpresso/mcux-sdk/tree/main/boards/evkbimxrt1050" target="_blank"&gt;https://github.com/nxp-mcuxpresso/mcux-sdk/tree/main/boards/evkbimxrt1050&lt;/A&gt;&amp;nbsp;?&lt;/P&gt;</description>
    <pubDate>Mon, 18 Dec 2023 07:58:12 GMT</pubDate>
    <dc:creator>felix1</dc:creator>
    <dc:date>2023-12-18T07:58:12Z</dc:date>
    <item>
      <title>RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1773686#M27986</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;according to RT1050 EVK, pin ENET_INT pin is input,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="felix1_0-1702452481698.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/254125i6B26310E9E69BC20/image-size/medium?v=v2&amp;amp;px=400" role="button" title="felix1_0-1702452481698.png" alt="felix1_0-1702452481698.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;In SDK example evkbimxrt1050_lwip_ping_freertos and other lwip examples,&lt;/P&gt;&lt;P&gt;the ENET_INT (GPIO_AD_B0_10) seems output, do I miss something?&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;int main(void)
{
    gpio_pin_config_t gpio_config = {kGPIO_DigitalOutput, 0, kGPIO_NoIntmode};

    BOARD_ConfigMPU();
    BOARD_InitBootPins();
    BOARD_InitBootClocks();
    BOARD_InitDebugConsole();
    BOARD_InitModuleClock();

    IOMUXC_EnableMode(IOMUXC_GPR, kIOMUXC_GPR_ENET1TxClkOutputDir, true);

    GPIO_PinInit(GPIO1, 9, &amp;amp;gpio_config);
    GPIO_PinInit(GPIO1, 10, &amp;amp;gpio_config);
    /* Pull up the ENET_INT before RESET. */
    GPIO_WritePinOutput(GPIO1, 10, 1);
    GPIO_WritePinOutput(GPIO1, 9, 0);
    SDK_DelayAtLeastUs(10000, CLOCK_GetFreq(kCLOCK_CpuClk));
    GPIO_WritePinOutput(GPIO1, 9, 1);&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 07:39:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1773686#M27986</guid>
      <dc:creator>felix1</dc:creator>
      <dc:date>2023-12-13T07:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1774227#M27998</link>
      <description>&lt;P&gt;Hello, my name is Pavel, and I will be supporting your case, I will review it, and in case the error reporting is right, I will need the information on the version of the schematic. Could you share more information about where you see this?&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Pavel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 22:38:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1774227#M27998</guid>
      <dc:creator>Pavel_Hernandez</dc:creator>
      <dc:date>2023-12-13T22:38:47Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1774319#M28004</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;Pavel,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You can see the schematic in the attached file.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In the reference manual, it also set as input, so I doubt the example do this operation for some purpose.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="felix1_0-1702519348173.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/254299i14071EBD8E926A66/image-size/medium?v=v2&amp;amp;px=400" role="button" title="felix1_0-1702519348173.png" alt="felix1_0-1702519348173.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 02:08:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1774319#M28004</guid>
      <dc:creator>felix1</dc:creator>
      <dc:date>2023-12-14T02:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1775157#M28028</link>
      <description>&lt;P&gt;Hello, I made the report, and the team confirmed the issue was reported before,&amp;nbsp;they will update this in the next release.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 23:12:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1775157#M28028</guid>
      <dc:creator>Pavel_Hernandez</dc:creator>
      <dc:date>2023-12-14T23:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1775197#M28031</link>
      <description>Hi Pavel,&lt;BR /&gt;Can you tell me ENET_INT should be input or output first? I need this information to correct my code.</description>
      <pubDate>Fri, 15 Dec 2023 01:37:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1775197#M28031</guid>
      <dc:creator>felix1</dc:creator>
      <dc:date>2023-12-15T01:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1775812#M28057</link>
      <description>&lt;P&gt;Hello, sorry it should be as input, how is mentioned in the RM.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Sat, 16 Dec 2023 00:18:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1775812#M28057</guid>
      <dc:creator>Pavel_Hernandez</dc:creator>
      <dc:date>2023-12-16T00:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1776165#M28070</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Pavel,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1) In example&amp;nbsp;evkbimxrt1050_lwip_ping_freertos, except to change ENET_INT as input, what else should I do?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2) Where can I find example&amp;nbsp;evkbimxrt1050_lwip_ping_freertos in the mcuxpresso github&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/nxp-mcuxpresso/mcux-sdk/tree/main/boards/evkbimxrt1050" target="_blank"&gt;https://github.com/nxp-mcuxpresso/mcux-sdk/tree/main/boards/evkbimxrt1050&lt;/A&gt;&amp;nbsp;?&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2023 07:58:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1776165#M28070</guid>
      <dc:creator>felix1</dc:creator>
      <dc:date>2023-12-18T07:58:12Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1777457#M28104</link>
      <description>&lt;P&gt;Wait, hold up, I've run into this issue before in my testing. ENET_INT actually is an output pin, in a way.&amp;nbsp; The reason is, the ENET_INT pin actually does double duty as the NAND_TREE strapping pin on the PHY&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MultipleMonomials_0-1703030488622.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/255136i9368B8F948B95026/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MultipleMonomials_0-1703030488622.png" alt="MultipleMonomials_0-1703030488622.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This means that when reset is released for the phy, the ENET_INT line needs to be logic high so that the phy doesn't go into NAND_TREE test mode (which makes it basically inert).&lt;/P&gt;&lt;P&gt;If you wish to use the ENET_INT line to get interrupts from the phy, you can use it as an input, you just have to reconfigure it to input after the phy has been reset and has booted up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, you may run into issues because of an error in the schematic that I noticed: the ENET_INT line is both pulled up and pulled down by resistors!&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MultipleMonomials_1-1703030854416.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/255137iC22E8E1563A8A826/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MultipleMonomials_1-1703030854416.png" alt="MultipleMonomials_1-1703030854416.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MultipleMonomials_2-1703030868468.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/255138iC8F7D81E94E87133/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MultipleMonomials_2-1703030868468.png" alt="MultipleMonomials_2-1703030868468.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This means it will quite possibly be stuck at 1.6V unless you remove the pulldown resistor from your eval kit. This screenshot is from the 1060 EVK rev B, unsure if other EVKs have the same issue.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Dec 2023 00:08:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1777457#M28104</guid>
      <dc:creator>MultipleMonomials</dc:creator>
      <dc:date>2023-12-20T00:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1778614#M28146</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/219813"&gt;@MultipleMonomials&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Thanks for your information.&lt;/P&gt;&lt;P&gt;My customer board solder both the pull-up and pull-down resistors for ENET_INT pin as EVK, so it output 1.65V to PHY.&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to your test, any problem you meet?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Dec 2023 09:20:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1778614#M28146</guid>
      <dc:creator>felix1</dc:creator>
      <dc:date>2023-12-21T09:20:37Z</dc:date>
    </item>
    <item>
      <title>Re: RT1050 ENET_INT pin direction</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1783462#M28331</link>
      <description>&lt;P&gt;It seems like, on the EVK board, we do get away with it and the phy recognizes it as a logic high.&amp;nbsp; But I'm not sure I'd trust that on a production board.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2024 07:50:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT1050-ENET-INT-pin-direction/m-p/1783462#M28331</guid>
      <dc:creator>MultipleMonomials</dc:creator>
      <dc:date>2024-01-05T07:50:50Z</dc:date>
    </item>
  </channel>
</rss>

