Debugger Engine Environment Variables
Debugger Environment
843
Microcontrollers Debugger Manual
• If the tool is launched using a File Manager/Explorer, the current directory is the
location of the executable launched.
• If the tool is launched using an Icon on the Desktop, the current directory is the one
specified and associated with the Icon.
• If the tool is launched by dragging a file on the icon of the executable under
Windows 2000, the desktop is the current directory.
• If the tool is launched by another tool with its own current directory specified (for
example, WinEdit), the current directory is the one specified by the launching tool
(for example, current directory definition in WinEdit).
• For the Debugger tools, the current directory is the directory containing the local
project file. Changing the current project file also changes the current directory, if the
other project file is in a different directory. Note that browsing for a C file does not
change the current directory.
To overwrite this behavior, the environment variable
DEFAULTDIR: Default Current
Directory
may be used.
Global Initialization File
(MCUTOOLS.INI - PC
Only)
All tools may store global data in
MCUTOOLS.INI
. The tool first searches for this file in
the directory of the tool itself (path of executable). If there is no MCUTOOLS.INI file in
this directory, the tool looks for the file in the MS Windows installation directory (for
example,
C:\WINDOWS
).
Example:
C:\WINDOWS\MCUTOOLS.INI
D:\INSTALL\PROG\MCUTOOLS.INI
If a tool is started in the
D:\INSTALL\PROG\DIRECTORY
, the project file in the same
directory as the tool is used (
D:\INSTALL\PROG\MCUTOOLS.INI
).
If the tool is started outside the
D:\INSTALL\PROG
directory, the project file in the
Windows directory is used (
C:\WINDOWS\MCUTOOLS.INI
).
NOTE
For more information about
MCUTOOLS.INI
entries, see the compiler
manual.
Summary of Contents for Microcontrollers
Page 1: ...Microcontrollers Debugger Manual Revised 22 October 2007 ...
Page 20: ...Table of Contents 20 Microcontrollers Debugger Manual ...
Page 24: ...Book I Contents 24 Microcontrollers Debugger Manual ...
Page 60: ...Debugger Interface Highlights of the User Interface 60 Microcontrollers Debugger Manual ...
Page 156: ...Debugger Components Visualization Utilities 156 Microcontrollers Debugger Manual ...
Page 198: ...Real Time Kernel Awareness OSEK Kernel Awareness 198 Microcontrollers Debugger Manual ...
Page 236: ...Synchronized Debugging Through DA C IDE Troubleshooting 236 Microcontrollers Debugger Manual ...
Page 238: ...Book II Contents 238 Microcontrollers Debugger Manual ...
Page 332: ...HC08 Full Chip Simulation Configuration Procedure 332 Microcontrollers Debugger Manual ...
Page 348: ...MON08 Interface Connection Device Class Description 348 Microcontrollers Debugger Manual ...
Page 364: ...ICS MON08 Interface Connection Device Class Description 364 Microcontrollers Debugger Manual ...
Page 428: ...HC08 FSICEBASE Emulator Bus State Analyzer BSA 428 Microcontrollers Debugger Manual ...
Page 430: ...Book III Contents 430 Microcontrollers Debugger Manual ...
Page 466: ...HCS08 Full Chip Simulation Peripheral Modules Commands 466 Microcontrollers Debugger Manual ...
Page 544: ...HCS08 On Chip DBG Module HCS08 DBG V3 New Features 544 Microcontrollers Debugger Manual ...
Page 546: ...Book IV Contents 546 Microcontrollers Debugger Manual ...
Page 576: ...Book V Contents 576 Microcontrollers Debugger Manual ...
Page 698: ...Book VI Contents 698 Microcontrollers Debugger Manual ...
Page 714: ...Flash Programming NVMC Commands 714 Microcontrollers Debugger Manual ...
Page 730: ...Book VII Contents 730 Microcontrollers Debugger Manual ...
Page 840: ...Book VIII Contents 840 Microcontrollers Debugger Manual ...
Page 864: ...Book IX Contents 864 Microcontrollers Debugger Manual ...
Page 868: ...Legacy Target Interfaces Removed 868 Microcontrollers Debugger Manual ...