nRF5340 + nRF7002: WiFi DNS timeouts and scanning issues

Dear Nordic Team,

I am currently working on a project that integrates your HTTPS client sample with your BLE provisioning sample, specifically on the nRF5340 with the 7002EK. The typical workflow involves provisioning the network via BLE from a mobile app, followed by several HTTPS requests.

I have encountered an issue where the board occasionally enters a state in which any call to getaddrinfo returns an error value of -101. Upon enabling DNS-related debug logs, I found that this is due to a DNS timeout. I can confirm this by executing net dns google.com, which also times out. I believe the DNS server is functioning correctly, as my computer can access it without issues, even when the board is in this problematic state. The only way to recover from this state is to restart the board.

Additionally, when in this state, any call to wifi scan returns zero results, despite the presence of multiple networks.

It appears that the Wi-Fi/networking subsystem may be entering an undefined state. I do not have specific steps to reproduce the issue, but it seems to occur in approximately 15% of cases when using Wi-Fi.

I am currently using SDK version 2.6.1 and have also tried version 2.7.0, with similar results. Unfortunately, I cannot test versions 2.8 or 2.9 at this time, as the migration would require more time than I currently have available.

Any advice on how to debug or resolve this issue would be greatly appreciated.

Thank you!

Parents Reply
  • Hi Ladivin,

    I tested the HTTP Client sample in NCS v2.9.1 on the nRF7002DK more than 10 times, and the domain was successfully resolved every time and the IP addresses are different some times.

    Looking up example.com
    Resolved 96.7.128.198 (AF_INET)

    How about your tests? Could you change the Wi-Fi AP, for example home or mobilephone host to try?

    Best regards,

    Charlie

Children
No Data
Related