The embedded tools company

Search FAQs

PDF document ( 47KB / 09-Apr-2019 )

Freeze timers in debug halted state

Ref: 0416
The SYStem.Option.FREEZE setting seems not to have any influence on the timers/counters. Is it possible to let the timers/counters run even when a breakpoint is hit or the cores are halted?

The SYStem.Option.FREEZE setting just uses the debug related registers to influence the timer / counter behavior when the target enters the debug halted state.
QorIQ CPUs typically offer an additional register in the RCPM, called CTBHLTCRL.
If the corresponding bit for a specific core in this register
  • is set to 1, the SYStem.Option.FREEZE setting can handle both: To let the timers run or to freeze them during the core is in the debug halted state.
  • is set to 0, the timers will always be frozen in the debug halted state, regardless of the SYStem.Option.FREEZE setting.

ISO 14001

Ref: 0358
Are the TRACE32 products in compliance with "ISO 14001"?

Lauterbach GmbH doesn't need to establish such additional control system. The "International Environmental Management Standard ISO 14001" is a weaker regulation than the European "REACH" directive followed by Lauterbach. For details on our "REACH" compliance please refer to our FAQ regarding "REACH" (Registration, Evaluation, Authorisation and Restriction of Chemicals).

Plugged debug cable is not suitable for CPU

Ref: 0448
Why do I get the error message "Plugged debug cable is not suitable for CPU" ?

In general you get the error message "Plugged debug cable is not suitable for CPU", when the started TRACE32 application is not supported by the debug cable plugged to your PowerDebug.
E.g. The "PowerPC-4xx Debug Cable" is not suitable for "TRACE32 for ARM" (t32marm.exe)
Please start the correct TRACE32 application or connect the correct debug cable to your PowerDebug.

As a special case, you also get the error message "Plugged debug cable is not suitable for CPU" if you use TRACE32 R.2018.02 or older and you use a new debug cable that is not yet supported by that version:
  • If your ARM debug cable has a serial number starting with "C18" or higher, it is the new "ARM Debug Cable V5" (shipped since 2018). Please ensure you use TRACE32 version R.2017.02 or higher.
  • If you use the Automotive PRO cable (LA-2707), ensure you use TRACE32 R.2018.02 or higher.
You can download a suitable version of TRACE32 at https://www.lauterbach.com/7373

Power Debug PRO and Power Trace PX

Ref: 0427
Why does not work my TRACE32 software version with Power Debug Pro or Power Trace PX?

If you get an error message like
"Fatal error: This software is too old to use this Lauterbach Hardware. Use more recent software!"
"FATAL ERROR from PODBUS-driver: TRACE32 USB device not connected".
Please check whether the used TRACE32 software fulfills the requirements below.

PowerDebug PRO is the successor of PowerDebug-II.
This kind of new hardware module requires at least TRACE32 software revision 58927 from 11/2014.

PowerTrace PX is the successor of PowerTrace.
This kind of new hardware module requires at least TRACE32 software revision 59808 from 11/2014.

The TRACE32 USB driver must be updated too.

REACH Statement

Ref: 0309
Are the TRACE32 products in compliance with the European Regulation "REACH"?

Lauterbach GmbH is a so called "downstream user" and delivers only manufactured products. We do not provide chemical substances or preparations. The key features of Lauterbach products are their form and function, not their chemical composition.

TRACE32 products contain no substances to be intentionally released under proper conditions especially no hazardous substances. We do not use substances on the candidate list of substances of very high concern at all during production. There are no chemicals or preparations used exceeding 1 ton a year.

Consequently, no registration of chemical substances is necessary for Lauterbach and Lauterbach is currently not affected by REACH.

The statement above is provided in utmost good faith, no representations or warranties are made with regards to its completeness or accuracy and no liability will be accepted for damages of any nature whatsoever resulting from the use of or reliance on the information.

t32.cmm is not executed

Ref: 0447
Why does TRACE32 no longer start the script t32.cmm ?

TRACE32 build 99519 (August 2018) and newer start the following scripts automatically after the application start:
  1. TRACE32 first executes the file autostart.cmm from the TRACE32 system directory (usually C:\T32).
  2. autostart.cmm normally starts then the following scripts:
    • system-settings.cmm (from the TRACE32 system directory)
    • user-settings.cmm (from the user settings directory (on Windows %APPDATA%\TRACE32 or ~/.trace32 otherwise))
    • work-settings.cmm (from the current working directory)
  3. Finally TRACE32 executes additionally the file specified on the command line (or in T32Start).
If the file autostart.cmm does not exist in the TRACE32 system directory, TRACE32 build 99519 (and later) will fallback to the previous autostart-mechanism and start t32.cmm (if no start script was specified on the command line (or in T32Start))

The file autostart.cmm will be provided by Lauterbach and should not be changed, because every software update from Lauterbach will restore the file.

Individual settings should be added in the files system-settings.cmm, user-settings.cmm and work-settings.cmm (which will not be changed by Lauterbach).

Read more on https://www.lauterbach.com/2018

WEEE Statement

Ref: 0365
Are the TRACE32 products in compliance with the European "WEEE" directive?

Statement of Compliance:
The product group TRACE32 of Lauterbach GmbH, Germany is in compliance to the European Community directive 2002/96/EC Waste Electrical and Electronic Equipment Directive, dated January 27th 2003. (In Germany the WEEE Directive is called "Richtlinie 2002/96/EG über Elektro- und Elektronik-Altgeräte").

TRACE32 tools are capital goods with a typical useful lifetime of more than 10 years. They are used as professional devices only in other than private households (so-called "business-to-business devices - B2B"). The tools demonstrate their B2B characteristics and nature of no doubt by their usage and purpose as well as the group of buyers and the price.

TRACE32 tools are included in the device category 9 ("monitoring and control instruments") to the section "Equipment for measuring in the laboratory".

The responsibility for disposal will be transferred with the purchase of a TRACE32 tools to the buyer according to the general terms and conditions of Lauterbach GmbH.

The text of the European WEEE Directive 2002/96lEC can be found at:
or in German language:

TRACE32 HELP Command Abbreviations (HELP)

Ref: 0403
What's the long form and meaning of abbreviated TRACE32 commands in CMM scripts? Which shorter syntax is available?

Options to find out details on command abbreviations and the meaning of abbreviated commands in scripts:
  • 1. In the documentation only the long form is used to show the meaning. But the possible abbreviation is shown by the capital letters. It is NOT possible to search abbreviated commands by "Find" (CTRL-F) in a manual. The manual "commandlist.pdf" uses the long form but if you look for e.g. "D" you find Data has the capital D (and no other command on this "1st" command level/position).

  • 2. Quick: If looking for "D"_something (or "S" like sYmbol_something) directly open "general_ref_?.pdf". (? = 1st character)

  • 3. Automatic: You can open in the TRACE32 menu "Help - Index" (or press F1-Key, register card "Index"). In the offered field abbreviations work.

  • 4. Simple option even without opening a PDF: Check the soft-keys. Click on the position and watch for capital letters. If wanted - press F1-Key (behind a separator like dot or white-space). The PDF will typically open at the correct location in the PDF.

TRACE32 HELP Easy & Quick (HELP)

Ref: 0399
How to use the TRACE32 Help easiest and quickest?

It's probably best to read the main.pdf first because it gives you an overview of how the help system and its structure. Here is the executive summary of the main.pdf:

There are only a few PDF files you should know by name: (You will also find a few illustrated suggestions here: http://www.lauterbach.com/help.html )

Very first steps:

Very basic start guide:

More comprehensive debug guide:

Functions to get information related to the host system:

Functions to get information related to the target system:

If you have a trace extension or an on-chip trace:

List of commands (leading to specific PDFs from A to Z):

Commands from A to Z (e.g. D):

And last but not least the processor architecture manual:
debugger_<architecture>.pdf ;in case of a debugger
like debugger_arm.pdf

The rest is mostly nice to have or most likely not appropriate to your situation or tool HW.

PDF documentation can be found in the installation folder T32\PDF or on DVD\files\PDF or Internet:

And here is a reference card regarding the flexible and powerful script programming language PRACTICE (CMM scripts).

Copyright © 2019 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany   Impressum     Privacy Policy
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 13-Aug-2019