-
Notifications
You must be signed in to change notification settings - Fork 142
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
Netxduo is "blocked" after an error occured #188
Comments
0x23 should not be returned from
|
Yes excatly you're right, with these functions, the nx_tcp_server_socket_relisten function works normaly. |
Do you mean 10 minutes delay by calling relisten? If not, could you describe the question again, thanks! |
I'm a little bit confused about the 'delay'. Where does it occur? In |
After getting "Host disconnect" from TCP socket, i tried to nx_tcp_socket_disconnect()/nx_tcp_server_socket_unaccept()/nx_tcp_server_socket_relisten() as you said and that's working (no more error). But i don't have any interrupts from clients even if i try many times before 29 mins. |
And secondly, how can i trigger ux_slave_class_cdc_ecm_instance_activate and ux_slave_class_cdc_ecm_instance_deactivate from a software point of view? |
@xiaocq2001 , can you help with USBX questions? |
Closing as duplicate with eclipse-threadx/usbx#114 |
LPC55S69
6.1
arm-none-eabi-* + WSL
Hi,
I use Azure RTOS with the netxduo layer to manage TCP/IP sockets. The application exchanges a set of commands through netcat via "Windows sub Linux" on different ports (32071 to 32076) with an ethernet over USB protocol.
In my application, there are different communication buses, wifi / BLE / cellular network / IOT (through cellular or WIFI). When there is an error in one of the nx functions, for example in the "nx_tcp_server_socket_relisten" function, I get an error 0x23 which is NX_PORT_UNAVAILABLE. After that, it was impossible to continue exchanging through netcat on WSL, whatever the port. After a timeout of about 10 minutes, everything worked normally again.
In fact, the various communication buses are totally multi-threaded but they all seem to refer to the same instance of Netxduo since all the ports are blocked simultaneously and then unblocked at the same time.
Do you have any idea which parameter I can change to avoid this problem?
Best regards,
Antoine
The text was updated successfully, but these errors were encountered: