You can use debugger commands in the macro body. If used, you must enclose the command with dollar signs ($) and end in a semi-colon (;), and the command must not be split across multiple lines, for example:

last_time = @cycle;
value = base[offset];
base[offset] = 0;
$printf "base offset value=%d\n",value$;

You can substitute the value of an integer variable in a CLI command before the command is executed. A format specifier can also be included:

The syntax for variable substitution is ${variable[:format]}.

For example:

define /R int tstMacro()
{
    int num;
    num = 1;
    $FOPEN 150, "C:\\myfiles\\myfile${num:d}.txt"$; // substitution
    $FPRINTF 150, "Test value: %d", num$;
    $VCLOSE 150$;
}
.

The filename in this example is myfile1.txt. The text written to the file is "Test value: 1".

You can also use macro arguments and local variables in RealView Debugger commands.

RealView Debugger prohibits the use of the following commands inside a macro:

Also you cannot use execution-type commands (for example, STEP) in a macro if you attach the macro to another entity, such as a breakpoint.