Hi @vareddy_Amzn and @WWarne ,
First, can you confirm the board part number revision you are using? There are two revisions, and they use different 10/100M Ethernet PHYs. The Zephyr default is the latest MIMXRT1170-EVKB. The older part number was MIMXRT1170-EVK, which Zephyr calls Rev A. Also, I assume you are using the 10/100M Ethernet connection for this, which is J32 on EVKB (or J3 on EVK(A)).
Your log shows you are not using the latest Zephyr release, but using an older commit fdd02c5105d2. I tested the dhcpv4_client sample with that commit, and I also see issues on the EVKB revision, and the board never gets an IP address:
[00:00:00.051,000] <inf> phy_mii: PHY (0) ID 1CC816
[00:00:00.053,000] <err> eth_nxp_enet_mac: phy_configure_link failed with error0
[00:00:00.054,000] <inf> eth_nxp_enet_mac: Link is down
[00:00:00.054,000] <err> eth_nxp_enet_mac: phy_configure_link failed with error0
*** Booting Zephyr OS build v4.2.0-rc1-129-gfdd02c5105d2 ***
[00:00:00.055,000] <inf> net_dhcpv4_client_sample: Run dhcpv4 client
[00:00:00.055,000] <inf> net_dhcpv4_client_sample: Start on ethernet: index=1
[00:00:03.155,000] <inf> phy_mii: PHY (0) Link speed 100 Mb, full duplex
[00:00:03.155,000] <inf> eth_nxp_enet_mac: Link is up
But using the latest upstream Zephyr release v4.2 resolves that issue for me:
[00:00:00.051,000] <inf> phy_mii: PHY (0) ID 1CC816
[00:00:00.054,000] <inf> eth_nxp_enet_mac: Link is down
*** Booting Zephyr OS build v4.2.0 ***
[00:00:00.055,000] <inf> net_dhcpv4_client_sample: Run dhcpv4 client
[00:00:00.055,000] <inf> net_dhcpv4_client_sample: Start on ethernet: index=1
[00:00:03.155,000] <inf> phy_mii: PHY (0) Link speed 100 Mb, full duplex
[00:00:03.155,000] <inf> eth_nxp_enet_mac: Link is up
[00:00:06.423,000] <inf> net_dhcpv4: Received: 192.168.86.165
[00:00:06.423,000] <inf> net_dhcpv4_client_sample: Address[1]: 192.168.86.165
[00:00:06.423,000] <inf> net_dhcpv4_client_sample: Subnet[1]: 255.255.255.0
[00:00:06.423,000] <inf> net_dhcpv4_client_sample: Router[1]: 192.168.86.1
[00:00:06.423,000] <inf> net_dhcpv4_client_sample: Lease time[1]: 86400 seconds
Can you please try updating to v4.2 and see if that resolves your issue? Thank you