I’m afraid it is not possible to query the thread name from the TID.
For this particular problem I suspect that a floating signal is generating interrupts and thus loads the CPU. The UART driver is a candidate. Have a look at the following issues in the release history:
- #25340 System Hang on SerialPort Open while receiving data
- #25075 Added “NumberOfLines” registry setting for UART to specify number of used lines
If my guess is correct, updating to the latest OS image would solve the problem.
Regards, Andy