Hello everyone!
I have recently started exploring possibility of controlling SEGGER SystemView app in a single instance mode with TCP/IP socket. I have been connecting to SystemView and sending commands from Windows PowerShell using telnet and Python scripts with socket library. In both cases, I can successfully set parameters of recorder or target device, and communicate with SystemView application - start/stop a recording, save data to SVDat file, load a previously recorded SVDat file, export a recording to CSV file or quit. However, the only response I receive from SystemView is:
SEGGER SystemView V3.58 Command Server
After this initial message is sent from SystemView, the application does not respond to commands sent by user.
Below is an example of TCP/IP communication. To start SystemView and establish a connection over TCP/IP I use these commands in PowerShell:
And communication looks like this:
SEGGER SystemView V3.58 Command Server
start
stop
quit
Connection to host lost.
While controlling SystemView over TCP/IP I am able to see SystemView's GUI and how different commands affect application's behavior (e.g. start command starts recording), but none of GUI's popup windows are reported via command line interface (e.g. an error occurred, or recording was successfully exported to CSV file).
Is this the expected behavior of SEGGER SystemView when app is controlled over TCP/IP? Or maybe, does it require some extra steps to enable the full functionality of the app?
Thanks in advance for your support!
My environment:
I have recently started exploring possibility of controlling SEGGER SystemView app in a single instance mode with TCP/IP socket. I have been connecting to SystemView and sending commands from Windows PowerShell using telnet and Python scripts with socket library. In both cases, I can successfully set parameters of recorder or target device, and communicate with SystemView application - start/stop a recording, save data to SVDat file, load a previously recorded SVDat file, export a recording to CSV file or quit. However, the only response I receive from SystemView is:
SEGGER SystemView V3.58 Command Server
After this initial message is sent from SystemView, the application does not respond to commands sent by user.
Below is an example of TCP/IP communication. To start SystemView and establish a connection over TCP/IP I use these commands in PowerShell:
And communication looks like this:
SEGGER SystemView V3.58 Command Server
start
stop
quit
Connection to host lost.
While controlling SystemView over TCP/IP I am able to see SystemView's GUI and how different commands affect application's behavior (e.g. start command starts recording), but none of GUI's popup windows are reported via command line interface (e.g. an error occurred, or recording was successfully exported to CSV file).
Is this the expected behavior of SEGGER SystemView when app is controlled over TCP/IP? Or maybe, does it require some extra steps to enable the full functionality of the app?
Thanks in advance for your support!
My environment:
- OS: Windows 11 Enterprise version 23H2,
- PowerShell: 5.1.22621.4391,
- SEGGER SystemView V3.58.