You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Problem
When an AP is connected using the MXCHIP chip, the log shows that the AP has been successfully connected, but the IP address has not been obtained correctly.
Host
Host OS: FreeRTOS
Net Stack: Lwip
Emw3080 FW ver: V2.1.11
Screenshots
Describe
I used Wireshark and did not find any DHCP packets from the MXCHIP chip.
The text was updated successfully, but these errors were encountered:
this log is the trace of the EMW3080 Wi-FI module configured in stack-bypass mode.
The module reports it successfully joined the "321" SSID with "12345678" password.
Since the TCP-IP stack runs on the host rather than on the module, it is expected that the module does not report the IP configuration of the device.
If the DHCP client fails to start, the LwIP instance running on the should be investigated.
In case you forked and modified the host application, it would be worth testing with the latest release tag.
Describe the Problem
When an AP is connected using the MXCHIP chip, the log shows that the AP has been successfully connected, but the IP address has not been obtained correctly.
Host
Screenshots
Describe
I used Wireshark and did not find any DHCP packets from the MXCHIP chip.
The text was updated successfully, but these errors were encountered: