Skip to main content

Error message: "FATAL ERROR from InterCom-driver: can not bind read socket" - Knowledgebase / TRACE32 PowerView - Lauterbach Support

Error message: "FATAL ERROR from InterCom-driver: can not bind read socket"

You are using InterCom communication for TRACE32 on your PC. This was activated by a setting in the active configuration for your TRACE32 PowerView software. Either by the InterCom setting in the T32Start configuration or inside your TRACE32 config file (default name config.t32).

The InterCom communication is typically needed if two or more TRACE32 PowerView instances shall communicate together (via UDP). This is for example needed for multicore debugging or debugging coprocessors like GTM.

The problem is caused by using the same InterCom port address by different applications (several TRACE32 executables or other applications). You can check the used ports by command: "netstat -a" on your PC.

For TRACE32, you can avoid this problem in the configuration of T32Start using the option "Use Auto Increment Port: Yes". If using a config file like config.t32 you need to set a different InterCom Port manually.

Helpful Unhelpful

13 of 16 people found this page helpful

Comments (2)

KEILY SUN
If using a config file like config.t32,how can I set a different InterCom Port manually? How do I describe it in config.t32?
Khaled Jmal
You can set the intercom port number in the IC=NETASSIST section in the config file. EXample: IC=NETASSIST PORT=12345 Refer for more information to installation.pdf

Add a comment

ID-0
To prove you are a human, please tell us the text you see in the CAPTCHA image