Opens "qview" ( installed with pip) with the customization provided in the dpp.py script located in the current directory. The "qview" will attach to the QSPY utility running at localhost:7701. Opens "qview" ( installed with pip) with the customization provided in the dpp.py script located in the directory. Opens "qview" with the customization provided in the dpp.py script located in the current directory. Opens the generic (not customized) "qview". Linux/MacOS Hosts python3 $(QTOOLS)/qview/qview.py The "qview" will attach to the QSPY utility running remotely at IP address 192.168.1.100:7705. Windows Hosts python3 %QTOOLS%\qview\qview.py If not specified, the default is '0', which means that the operating system will choose an open port. local_port - optional local UDP port to be used by "qview".If not specified, the default is 'localhost:7701'. qspy_host - optional host-name/IP-address:port for the host running the QSPY host utility.If not specified, qview will provide only the generic user interface for interacting with the target (e.g., reset, setting QS filters, posting events, etc.). cust_script - optional customization Python script for your specific target system.If you are using QView™ as a standalone Python script, you invoke it as follows: python3 /qview.py ]]Īlternatively, if you've installed QView™ with pip, you invoke it as follows: qview ] Also, the QTools™ collection for Windows already includes Python (3.8), so you don't need to install anything extra.Īlternatively, you can use your own Python installation, into which you can install the latest QView™ with pip from the PyPi index by executing the following command: pip install qview Note The qview.py script is included in the QTools™ collection. The qview.py script can be used standalone, without any installation in your Python system (see Running QView™ below). Remarks Why UDP? The communication between QSPY and QView is based on UDP, because UDP is inherently packet-oriented (as opposed to TCP, which is stream-oriented) and preserves the packet boundaries. This communication ( blue arrows) uses the same packet structure as the QP/Spy Protocol, but without the HDLC framing, without transparency (escaping), and without the checksum. The QView™ (Python script) attaches to the QSPY host application by means of the UDP socket that QSPY opens specifically for attaching various "front-ends". Additionally, the QP/Spy implementation in the Target must support bi-directional communication with QSPY. Attention The Target must be running the "Spy" build configuration, in which the QP/Spy™ Software Tracing is enabled. This communication is based on the QP/Spy Protocol. The embedded Target is running an instrumented code that communicates with the QSPY Host application over the Target data link ( red arrows). The sequence diagram below shows the general structure of QView™. Note A visualization and monitoring system like QView™ can be used in all stages of development, during manufacturing, and also after deployment for in-field servicing of embedded devices.
0 Comments
Leave a Reply. |