Skip to main content
Contact Us
New to Lauterbach Support? Register for an account
Need a password reminder?

How to integrate TRACE32 with Jenkins? - Knowledgebase / TRACE32 PowerView - Lauterbach Support

This Article Category Knowledgebase

How to integrate TRACE32 with Jenkins?

Authors list
  • Last updated: Aug 13, 2026 by Khaled Jmal

TRACE32 can be integrated into a Jenkins build or test process by running TRACE32 PowerView in the background and controlling it either through a TRACE32 startup script or from an external application.

To run TRACE32 PowerView without displaying the user interface, set the SCREEN option to OFF in the TRACE32 configuration file (by default, config.t32).

Find the line starting with:

SCREEN=

and change it to:

SCREEN=OFF

You can then either:

  • Start TRACE32 PowerView with a startup script containing the actions you want to perform.

  • Control TRACE32 PowerView from an external application, such as a Python script or a C application.

TRACE32 PowerView can be closed using the QUIT command. The command can take the operating system return value as an argument, allowing Jenkins to determine whether the execution was successful.

For more information, refer to the TRACE32 Installation Guide and the API for Remote Control and JTAG Access in C.

Helpful Unhelpful

7 of 8 people found this page helpful

Comments (6)

Sudhakar
Good suggestion. With "SCREEN=OFF" mode (in CI machine), Can the commands like "PRinTer.FILE" & "WinPRT" be useful to collect the (invisible) screendump using scripting? or suggest ways to log in this mode?
Khaled Jmal
Hello, I need to correct my previous answer. Printing TRACE32 windows to a file using "PRinTer.FILE" & "WinPRinT" is also possible when using SCREEN=OFF
Sudhakar
1. You're right. It works in screen off mode as well... so it means that a t32 instance is running in the backend though GUI is disabled. Isn't it? 2. While using pyrcl library, is it required to open t32 instance (disabled GUI)? Because if a t32 instance isn't open, it gives socket timeout error though pyrcl config is in place in config.t32. Or could it be someother error?
Khaled Jmal
1. correct, the TRACE32 PowerView instance is running though the GUI is disabled. 2. It is required to start the TRACE32 PowerView instance with or without GUI to use pyrcl.
Sudhakar
In CI/Remote machine (where GUI isn't supported), How to close a/all T32 instance(s) [initiated with SCREEN=OFF mode] if the cmm/py(pyrcl) script executed have errors or don't have 'QUIT' command?
Khaled Jmal
> In CI/Remote machine (where GUI isn't supported), How to close a/all T32 instance(s) [initiated with SCREEN=OFF mode] if the >cmm/py(pyrcl) script executed have errors or don't have 'QUIT' command? The only solution in this case is to kill the instance. You should implement error handling in your cmm/py(pyrcl) script (e.g. using ON.ERROR in cmm) to always have the possibility to close the instance.

Add a comment

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

Labels

API
Date Created
Sep 17, 2021