Hi all,
I'm using ThreadX with NetX Duo and running a Modbus TCP server on an STM32 platform. The system works fine under normal conditions, but I encounter a hang when the following sequence occurs:
- A Modbus TCP client is actively communicating with the board.
- The client is closed or a Telnet session is opened.
- The client reconnects — at this point, the system hangs.
From the ThreadX-aware debugger:
- Main Ip instance and Packet Monitor Thread are suspended, waiting on a mutex.
- The mutex is owned by my App Modbus TCP Thread, even though I don’t explicitly use any mutexes.
It seems like the NetX internal mutex is being held too long.
Can I trace or monitor the internal NetX mutex usage to better understand where the contention is happening?
