原文链接(Keil官方):Key Sequence for Tool Parameters
Use Key Sequences to pass arguments from µVision to external user programs. Key Sequences are combinations of a Key Code and a File Code. Key sequences can be used, for example, in the dialogsTools, SVCS, Options for Target — User, or from the command line. The following rules apply:
- Certain Key Codes have to be duplicated when used from the command line.
To use the symbols $, #, %, @, ~, ^
escape them with $$, ##, %%, @@, ~~, ^^. - Enclose Key Sequences within quotes (" ") when using folder names that might contain special characters (space, ~, or #).
Key Codes and File Codes are listed in the tables below:
Key Code | Description |
---|---|
% | File name with extension (PROJECT1.UVPROJ) |
# | File name with extension and complete path specification (C:\MYPROJECT\PROJECT1.UVPROJ) |
@ | File name without extension or path specification (PROJECT1) |
$ | Path name of a file. Path names get extended with a backslash. For example, $P could generate C:\MYPROJECT\. |
! | File name with extension and relative path specification to the current folder (.\SRC\TEST.C) |
~ 1 | Line number of the current cursor position |
^ 1 | Column number of the current cursor position |
File Code | Description |
---|---|
$D | Device name as selected from the Device Database. |
E | Editor file name currently in focus. |
F | Depending on the context, this File Code returns:
|
H | Application HEX file name (PROJECT1.H86). |
$J | Absolute compiler system include folder. Compiler base folders are listed in the fieldProject — Manage — Project Items — Folder/Extensions - ARMCC Folder. The include path depends on the compiler selected in Options for Target - Code Generation - ARM Compiler. |
K | Absolute root folder of the development toolchain, regardless of the Key Code used. |
L | Linker output file. Typically the executable file used for debugging (PROJECT1). |
$M | CPU mask revision number. |
P | Current project file name. |
X | µVision executable program file (..\UV4\UV4.EXE). Works for For Key Code %, # @. |
$X | XTAL clock frequency in MHz as specified in Options for Target — Target — XTAL. |
^X | XTAL clock frequency in kHz as specified in Options for Target — Target — XTAL. |
File Codes when using an SVCS | |
Q 2 | Name of the temporary file that contains comments (Comment). |
R 2 | Revision number (Revision). |
C 2 | Check point string (Check Point). |
I 2 | Project identification string (Project Ident). |
U 2 | User name (User Name). |
V 2 | Database file name string (Database). |
File Codes when using a merge tool | |
A merge tool gives you the opportunity to merge the application-specific configuration settings from the previous version into the current version. Specify a merge tool withTools - Configure Merge Tool. | |
$current | Is the file as copied from the PACK with default configuration options. |
$previous | Is the back-up file filename.increment number |
Environment Variables
You can use environment variables for passing paths to external programs. This is described explicitly in the respective dialog documentation. Environment variables must be enclosed by curly brackets ({ }). For example, you have defined an environment variable with
SET ProgramFiles(x86)=C:\Program Files (x86)
.
You can use the environment variable as
{ProgramFiles(x86)}
in dialog fields.
Note
- 1 only in combination with the File Code F.
- 2 only in combination with the Key Code %.
- Examples can be found in the sections: Start External Tools and Using the SVCS Menu.