TRACE32 AutoStart Mechanism


The embedded tools company



After starting the TRACE32 application some PRACTICE scripts will be executed automatically.  
TOP

Autostart of old TRACE32 build 99518 and earlier


Until build 99518 TRACE32 started only one script on startup.
  • If an individual start script is specified on the command line (or in T32Start), only this script is executed (while t32.cmm was not executed)
  • If no start script is specified, the file t32.cmm from the current working directory is executed.
  • If no start script is specified and there is no t32.cmm in the working directory, the file t32.cmm from the TRACE32 system directory (usually C:\T32) is executed.
    Starting from August 2017 Lauterbach shipped a variant of t32.cmm, which started the scripts system-settings.cmm (from the TRACE32 system directory), user-settings.cmm (from the user settings directory (on Windows %APPDATA%\TRACE32 or ~/.trace32 otherwise)) and work-settings.cmm (from the current working directory)
 
TOP

Autostart since TRACE32 build 99519 and later (August 2018)


Since build 99519 TRACE32 starts the following script on startup:
  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))

You can easily switch back to the old autostart-mechanism by deleting the file autostart.cmm from the TRACE32 system directory. However be aware that every software update from Lauterbach will restore the file autostart.cmm.

The file autostart.cmm is provided by Lauterbach and should not be changed. Every software update will overwrite autostart.cmm.
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).





Copyright © 2018 Lauterbach GmbH, Altlaufstr.40, D-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: 08-Aug-2018