Connection
A Connection is used to specify with which hardware (e.g. USB-Debugger) or software (e.g. Simulator) to work for your debug session.
- class lauterbach.trace32.pystart._connection.USBConnection(device_name='', device_path='', connect_mode=ConnectMode.NORMAL, exclusive=False)
Connection class for USB hardware debugger.
This Connection is a subtype of PBIConnection.
- device_name: str = ''
A name is required if several debug modules are connected via USB and used simultaneously. The manufacturing default device name is the serial number of the debug module. e.g. NODE=E18110012345
- device_path: PathType = ''
Use this option to select the debug module to use if several debug modules are connected via USB.
- Type:
Linux only
- connect_mode: ConnectMode = 1
Specify reaction if debugger is already in use.
- exclusive: bool = False
If set no other TRACE32 executable can connect to this particular PowerDebug module.
- class lauterbach.trace32.pystart._connection.UDPConnection(node_name, port=0, host_port=0, max_udp_packet_size=1024, packet_burst_limitation=False, compression=False, delay=0, connect_mode=ConnectMode.NORMAL, exclusive=False)
Connection class for ethernet hardware debugger via UDP.
This Connection is a subtype of PBIConnection.
- node_name: str
The key value specifies the node name of the PowerDebug device to connect to. This should be either a DNS name or an IP address.
- port: int = 0
UDP Port to which PowerView should send its packets on debugger module. If 0, a default port is used.
- host_port: int = 0
Defines the UDP communication port from the debugger module to the host. If 0, an available port will be derived from your OS.
- max_udp_packet_size: int = 1024
Limit the maximum UDP packet size.
- packet_burst_limitation: bool = False
Sends only very small packets.
- compression: bool = False
If
Truereduces the packet size by compression.
- delay: int = 0
Delay UDP packets send from host by specifed time in milliseconds.
- connect_mode: ConnectMode = 1
Specify reaction if debugger is already in use.
- exclusive: bool = False
Tells TRACE32 that there can be only one TRACE32 PowerView instance to connect.
- class lauterbach.trace32.pystart._connection.CitrixConnection(node_name: str = '')
- node_name: str = ''
The key value specifies the node name of the PowerDebug device to connect to. This should be either a DNS name or an IP address.
- class lauterbach.trace32.pystart._connection.USBProxyConnection(node_name, port, device_name='', device_path='')
TRACE32 allows to communicate with a usb debug module from a remote PC.
In order to implement this communication, the command line tool
t32tcpusbhas to be started on the PC to which the debug module is connected.t32tcpusbcan be found in thebin/<target_os>directory of your TRACE32 installation (e.g.bin/windows64).- node_name: str
DNS name or IP address of PC that runs
t32tcpusb.
- port: int
Port number that was specified when
t32tcpusbwas started.
- device_name: str = ''
A name is required if several debug modules are connected via USB and used simultaneously. The manufacturing default device name is the serial number of the debug module. e.g.
NODE=E18110012345
- device_path: PathType = ''
Use this option to select the debug module to use if several debug modules are connected via USB.
- Type:
Linux only
- class lauterbach.trace32.pystart._connection.MCIServerConnection(node_name='localhost', port=30000, dedicated=False)
start a TRACE32 as a back-end using an MCI server (t32mciserver).
- node_name: str = 'localhost'
The key value specifies the node name of the PowerDebug device to connect to. This should be either a DNS name or an IP address.
- port: int = 30000
TCP-port number of MCI-Server. All started PowerView GUIs that belong to one target system must use the same PORT and NODE in order to connect to the same MCI-server. The used port of the dedicated MCI-Server is passed by a command line parameter of t32mciserver[.exe].
- dedicated: bool = False
Prohibits to start the integrated MCI-server when there is no response from an already started MCI-server at localhost. Use this option when t32mciserver shall be started explicitly at localhost.
- class lauterbach.trace32.pystart._connection.SimulatorConnection(license_connection: lauterbach.trace32.pystart._connection._PBIConnection | None = None)
- license_connection: _PBIConnection | None = None
Specifies a hardware-based TRACE32 debugger connection to use its license
- Available are:
USBConnectionUDPConnectionTCPConnectionCitrixConnectionUSBProxyConnection
- class lauterbach.trace32.pystart._connection.GDBConnection
TRACE32 as GDB Front-End.
- class lauterbach.trace32.pystart._connection.HostConnection
TRACE32 as host process debugger.
- class lauterbach.trace32.pystart._connection.MCILibConnection
TRACE32 as a back-end using the Lauterbach debug driver library hostmci.
- class lauterbach.trace32.pystart._connection.SerialRomMonitorConnection(port: str = 'COM1', baudrate: int = 57600)
- class lauterbach.trace32.pystart._connection.MCDConnection(library_file)
TRACE32 to debug via the MultiCore Debug interface MCD.
Refer to “Virtual Targets User’s Guide” (virtual_targets.pdf) for more information.
- library_file: PathType
Required library file.
Please contact the manufacturer of the virtual target for the required .dll file.
- class lauterbach.trace32.pystart._connection.CADIConnection(library_file='')
Arm Cycle Accurate Debug Interface CADI.
- library_file: PathType = ''
Optional library file.
The library file is provided by Lauterbach and is installed together with TRACE32. Specifying a library file (.dll) is optional
- class lauterbach.trace32.pystart._connection.IRISConnection(library_file='')
TRACE32 to debug via the Arm Cycle Accurate Debug Interface.
Refer to “Virtual Targets User’s Guide” (virtual_targets.pdf) for more information.
- library_file: PathType = ''
Optional library file.
The library file is provided by Lauterbach and is installed together with TRACE32. Specifying a library file (.dll) is optional
- class lauterbach.trace32.pystart._connection.ARCINTConnection
TRACE32 for debugging using the ARCINT interface.
Refer to “Simulator for ARC” (simulator_arc.pdf) for more information.
- class lauterbach.trace32.pystart._connection.GDIConnection(library_file='')
TRACE32 to debug via the Generic Debug Instrument Interface GDI.
Refer to “Virtual Targets User’s Guide” (virtual_targets.pdf) for more information.
- library_file: PathType = ''
Required library file.
Please contact the manufacturer of the virtual target for the required .dll file.
- class lauterbach.trace32.pystart._connection.MDIConnection
TRACE32 to debug via MDI (MIPS Debug Interface) simulator.
Refer to “Virtual Targets User’s Guide” (virtual_targets.pdf) for more information.
- class lauterbach.trace32.pystart._connection.SCSConnection
TRACE32 to debug via the SCS StarCore simulator.
- class lauterbach.trace32.pystart._connection.SIMTSIConnection
TRACE32 to debug via the Target Server from Texas Instruments.
Refer to “Virtual Targets User’s Guide” (virtual_targets.pdf) for more information.
- class lauterbach.trace32.pystart._connection.ViewerConnection
Connection to perform off-line analysis of memory dumps and trace recordings
Available since TRACE32 build 158910.
- class lauterbach.trace32.pystart._connection.TCPConnection(node_name, port=0, compression=False, connect_mode=ConnectMode.NORMAL, exclusive=False)
Connection class for ethernet hardware debugger via TCP.
This Connection is a subtype of PBIConnection and is only available for debugger from the X-Series.
- node_name: str
The key value specifies the node name of the PowerDebug device to connect to. This should be either a DNS name or an IP address.
- port: int = 0
TCP Port to which PowerView should send its packets on debugger module. If 0, a default port is used.
- compression: bool = False
If
Truereduces the packet size by compression.
- connect_mode: ConnectMode = 1
Specify reaction if debugger is already in use.
- exclusive: bool = False
Tells TRACE32 that there can be only one TRACE32 PowerView instance to connect.
- class lauterbach.trace32.pystart._connection.InteractiveConnection
Start TRACE32 PowerView into the Interactive Connection Mode. In this mode, the connection to a debug module, simulator or other solutions is done in the GUI or per script after starting PowerView.
Available since TRACE32 build 167333.