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?

  • Last updated: Nov 2, 2023 by Lauterbach

To disable the TRACE32 PowerView user interface, find the line starting with SCREEN= in your TRACE32 configuration file (default: config.t32) and change it to SCREEN=OFF. If there is no line starting with SCREEN= add a and empty line at the end of the file and then add the line SCREEN=OFF.
Then you can either start TRACE32 PowerView with a startup script which will contains the actions you want to perform or control the TRACE32 application from an external program (e.g. Python script or C application).
The TRACE32 application can be closed using the QUIT command, which can take the OS return value as argument.

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

Helpful Unhelpful

5 of 6 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