-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wifi_eswifi: Unable to start TCP/UDP client #25600
Comments
@nandojve if I'm correct, you have an esp shield, do you confirm this is working on the same board with esp shield (and eswifi deactivated ) ? |
In my case, Zephyr was acting as a TCP server and a client was able to successfully connect to it. However, the WiFi driver did not pass the client information to the application layer which caused NET stack to fail (whenever the application layer tried to send data to the client).. In this case, an AT command to the WiFi chip is failing. So this is different.. |
@loicpoulain can you have a check ? |
Hi @erwango I noted that when use more buffers UpdateHub client works. I think es-WIFI need more intensive tests because more buffers can delay the problem. ESP offload driver and frdm-k64 with ethernet are working fine using default buffer config. As requested, below logs from ESP offload driver. I hope it can help to identify the problem.
|
Hi @loicpoulain , I would like check but I'm stuck again with #25010. On Linux:
Than flash this new hello world
So, full erase + flash MCUboot + flash Hello World is not working. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
I'm wait an EVB board to isolate WiFi and create a Shield. |
@nandojve now that there's a shield for eswifi, have you been able to reproduce this issue on other board ? |
Hi @erwango , yes, I already tried UpdateHub and I got in trouble with frdm_k64f on early development using esWIFI with serial bus. Unfortunately I did not have enough time to look in deep but I've been suspecting that could be something related to UDP, after TagoIO's example start to work. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Describe the bug
After receive an wifi_eswifi: Unable to start TCP/UDP client the tcp/ip only works after restart the board.
To Reproduce
CONFIG_UPDATEHUB_WIFI_SSID="wifi network"
CONFIG_UPDATEHUB_WIFI_PSK="password"
~/<zephyr_home_dir>/bootloader/mcuboot/scripts/imgtool.py sign --key ~/<zephyr_home_dir>/bootloader/mcuboot/root-rsa-2048.pem --header-size 0x200 --align 8 --version 1.0.0 --slot-size 0x6C000 ~/<zephyr_home_dir>/zephyr/build/zephyr/zephyr.hex ~/<zephyr_home_dir>/zephyr/build/zephyr/zephyr-1.0.0.hex
Expected behavior
if for any reason devices have problems to create a TCP/IP client the future attempts must work.
Impact
Features stop to work.
Screenshots or console output
Environment (please complete the following information):
Additional context
CONFIG_NET_PKT_RX_COUNT=default
CONFIG_NET_PKT_TX_COUNT=default
CONFIG_NET_BUF_RX_COUNT=default
CONFIG_NET_BUF_TX_COUNT=default
The text was updated successfully, but these errors were encountered: