• State Not Answered
  • Replies 4 replies
  • Subscribers 72 subscribers
  • Views 89 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 342707
Options

No DHCP offer with W5500 and nRF5340

Amira R.

Hello,

I'm working with a custom board, using an nRF5340 (NCS v2.7.0 but also tested with version 2.9.0) and a W5500. I'm trying to run the DHCPv4 client test just to verify that an ethernet connection can be obtained, but haven't been able to get it working (btw my prj.conf is unchanged from the test, aside from enabling the W5500 driver and some debug logs).

The logs show a "Link up" from the W5500 driver, followed by DHCP discover packets being sent at increasing intervals (I verified they are indeed being sent with Wireshark). But I don't see any offer being returned.

I tried setting a static IP address (CONFIG_NET_CONFIG_MY_IPV4_ADDR) and performing a simple SNTP sync to see if it was just a problem with the DHCP server, but that failed (couldn't resolve address). I also tried setting the DNS IP address (CONFIG_DNS_SERVER_IP_ADDRESSES=y, CONFIG_DNS_SERVER1), manually setting the gateway address (CONFIG_NET_CONFIG_MY_IPV4_GW), and different combinations of those configurations, all to no avail.

Since the packets are indeed getting sent, I was initially inclined to believe it's a network/router security configuration possibly blocking it, or maybe a subnet issue, but I'm not sure. I'm inexperienced with networking and the person who set everything up at my work no longer works here (it's a startup, so they have yet to be replaced). I also tried on my home network and saw the same result.

I'm now at a point where I have no clue what else to try or what the issue could be. I've posted to the Zephyr discord channel multiple times but never received a response. Any assistance and/or suggestions would be greatly appreciated. Thank you!

Parents
  • 0

    Hi Amira,

    Thanks for reaching out regarding your issue.

    Unfortunately, the W5500 is not a Nordic product, so we do not provide official support for it.

    However, I found a similar discussion in the following ticket where a developer shared their solution. Could you take a look and see if it helps resolve your issue?

    (+) DHCPv4 client + Ethernet (W5500) Fails to work in SDK 2.4 - Nordic Q&A - Nordic DevZone - Nordic DevZone

    Let me know if you need further assistance.

    Best regards,

    Charlie

  • 0 in reply to Charlie

    Hi Charlie,

    Thank you for getting back to me! I did come across that post early on in my debugging efforts, but unfortunately their solution didn't work for me.

    I figured support would be limited on this end, given that neither the W5500 nor its driver are Nordic products, but it was worth a shot! I also tried posting to the Zephyr github, but I was only redirected here since I'm using NCS, and I was offered no assistance unless I could recreate the problem with only upstream Zephyr. So your assistance (and patience) is appreciated.

    I'm just gonna keep trying things and see if I can at least get some more information on what's happening, and I'll post here again if I find anything. I don't think there's much else I can ask from you, but again, thank you!

Reply
  • 0 in reply to Charlie

    Hi Charlie,

    Thank you for getting back to me! I did come across that post early on in my debugging efforts, but unfortunately their solution didn't work for me.

    I figured support would be limited on this end, given that neither the W5500 nor its driver are Nordic products, but it was worth a shot! I also tried posting to the Zephyr github, but I was only redirected here since I'm using NCS, and I was offered no assistance unless I could recreate the problem with only upstream Zephyr. So your assistance (and patience) is appreciated.

    I'm just gonna keep trying things and see if I can at least get some more information on what's happening, and I'll post here again if I find anything. I don't think there's much else I can ask from you, but again, thank you!

Children
Related
Terms of service