Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, there is no specific information about TCP socket issues related to Torizon 6 or any changes from Torizon 5 to Torizon 6 that might affect TCP communication. However, here are a few general troubleshooting steps you might consider:
-
Firewall/Network Configuration: Ensure that there are no firewall rules or network configurations on either the Verdin board or the PC that might be blocking the TCP connection.
-
Port Availability: Double-check that the port you are trying to use is not being used by another service and is open for communication.
-
Software Changes: Since you mentioned that this issue did not occur with Torizon 5, consider any changes in the network stack or security settings in Torizon 6 that might affect socket communication.
-
Logs and Diagnostics: Check system logs on both the Verdin board and the PC for any error messages or warnings that might provide more insight into why the socket is not opening.
-
Network Tools: Use network diagnostic tools like
netstatorssto verify that the socket is indeed listening on the Verdin board and to check the state of the connection.
If these steps do not resolve the issue, further investigation into the specific differences between Torizon 5 and Torizon 6 regarding network handling might be necessary. Unfortunately, without more detailed context or documentation, I cannot provide a more specific solution.
Please, also check if these links can help you solve your problem: