Toggle the state of the assertion mode.
To activate or suspend assertion mode, select the Breakpoints | Assertions... menu item, and enable or disable the Assertion Mode Active check box.
The command line syntax is:
Activate (A a) or suspend (A s) overall state of the assertion mechanism. If no operand is given, toggle the state.
To activate the assertion mechanism, type:
A a
To suspend the assertion mechanism, type:
A s
To toggle the state of the assertion mechanism, simply type:
A
Define or modify an assertion.
Select the Breakpoints | Assertions... menu item to view the Assertions dialog box. Click the New... button to define an assertion. Select an assertion and click the Edit... button to modify an assertion.
The command line syntax is:
The a command is used to invoke two different commands. The syntax for each command is distinct. The first version allows modification of the state of the assertion specified by the expression exp. (The assertion can be activated (a a), deleted (a d) or suspended (a s).) The second version creates a new assertion with the given command list cmds. Using the mouse, you can create a new assertion or toggle the state of an existing one from the Assertions dialogue box.
Suspended assertions continue to exist, but are not active. Deleted assertions must be explicitly redefined in order to be made active again.
The commands for every active assertion are executed after every source statement is executed. The x command in an assertion command list forces an exit from assertion mode.
This command is not allowed when the target runs in the background.
To suspend assertion 3, type:
3 a s
To delete assertion 1, type:
1 a d
To set an assertion to stop the program when global variable myvar exceeds 3, type:
a if (myvar > 3) {x}
List all of the currently defined breakpoints.
Select the Breakpoints | Breakpoints.. menu item to view the Breakpoints dialog box.
The command line syntax is:
Breakpoints are listed with numbers associated with them. These numbers can be used to delete individual breakpoints.
break
,
b
,
bb
,
bB
,
bi
,
bI
,
bu
,
bU
,
R
,
C
,
D
,
l
Set a code breakpoint.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select
Code Breakpoint... to open the Add Code Breakpoint dialog.
Enter the name of the source module or click the Break At... button to select a source module and enter a line number.
Alternatively, you can set a code breakpoint directly in the source by clicking on a green breakpoint toggle next to the source line.
The command line syntax is:
You can attach a list of CrossView Pro commands with the breakpoint. If no line is given, set the breakpoint at the current viewing position.
When the breakpoint is hit execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next, any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the b command.
To set a breakpoint at the current line, type:
b
To set a breakpoint at line 10 that will list all global variables and halt execution, type:
10 b {l g}
break
,
bd
,
bD
,
bdis
, bena
,
bb
,
bB
,
bi
,
bI
,
bt
,
bti
,
btI
,
bu
,
bU
,
Q
Set a temporary breakpoint at the beginning of a function.
In the Stack Window, click on the desired function and
select the Breakpoints | Stack Breakpoint | At Function Entry menu item.
The command line syntax is:
The function is designated by the stack level stack. If no function is specified, CrossView Pro uses the current function (stack level 0), and associates the list of CrossView Pro commands cmds with the breakpoint.
Breakpoints set in the Stack Window are always temporary, meaning they will be deleted after the first time you reach them. A breakpoint set in this manner will not be visible in the Source Window.
When the breakpoint is hit, execution is halted; the breakpoint is then removed. By default the current execution position, function, line number, and source statement are displayed. Next, any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bB command.
This command is not allowed when the target runs in the background.
To set a temporary breakpoint at the beginning of the current function which prints a stack trace, type:
bB {T}
To set a temporary breakpoint at the beginning of the function whose stack number is 2, type:
2 bB
break
,
b
,
bb
,
bd
,
bD
,
bi
,
bI
,
bt
,
bti
,
btI
,
bu
,
bU
,
Q
Set a permanent breakpoint at the beginning of a function.
In the Stack Window, click on the desired function and select the Breakpoints | Stack Breakpoint | At Function Entry menu item. To make the stack breakpoint permanent,
select the Breakpoints | Breakpoints... menu item, select the desired breakpoint and click on the Edit... button. The Edit Code Breakpoint dialog appears. Click on the Advanced>> button and disable the Remove when hit check box.
The command line syntax is:
Set a breakpoint at the beginning of the function designated by the stack level stack. Otherwise, use the current function (stack level 0), and associate the list of CrossView Pro commands cmds with the breakpoint.
When the breakpoint is hit, execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next, any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bb command.
This command is not allowed when the target runs in the background.
To set a breakpoint at the beginning of the current function, which prints a stack trace, type:
bb {T}
To set a breakpoint at the beginning of a function whose stack number is 2, type:
2 bb
break
,
b
,
bB
,
bd
,
bD
,
bi
,
bI
,
bt
,
bti
,
btI
,
bu
,
bU
,
Q
Set a breakpoint's count and reset count.
Select the Breakpoints | Breakpoint... menu item, select the breakpoint for which you want to set the count and reset
count and click on the Edit... button. The Edit Code Breakpoint dialog appears. Click on the Advanced button and enter a breakpoint count.
The command line syntax is:
Set the count and reset_count for the breakpoint with breakpoint number number. When no arguments are given, the breakpoint at the current viewing position is set to a count of 1 and a reset count of 1. If no breakpoint is present at the current viewing position, the message "No such breakpoint" appears.
Each time a breakpoint is hit, CrossView Pro decrements the count. When the count reaches 0, execution is halted and the count is reset to the reset_count.
This command is not allowed when the target runs in the background.
To set a breakpoint's count and reset count to 1 for the breakpoint at the current viewing position, type:
bc
To set the count to 3 and the reset count to 4 for the breakpoint whose breakpoint number is 2, type:
2 bc 3 4
Set a temporary cycle count breakpoint.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select Cycle Breakpoint... to open the Add Cycle Breakpoint dialog. Click the Advanced
button and enable the Remove when hit check box.
The command line syntax is:
Set a temporary breakpoint after the specified cycle count. count can be any expression evaluating to a number. The list of CrossView Pro commands cmds are executed when the breakpoint is hit.
When the breakpoint is hit, execution is halted; the breakpoint is then removed. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bCYC command.
To set a temporary breakpoint after 4 clock cycles and list all global variables, type:
4 bCYC {l g}
break
,
b
, bcyc
, bINST
, binst
, bTIM
, btim
,
D
Set a permanent cycle count breakpoint.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select Cycle Breakpoint... to open the Add Cycle Breakpoint dialog. Enter a cycle count and click the OK button.
The command line syntax is:
Set a permanent breakpoint after the specified cycle count. count can be any expression evaluating to a number. The list of CrossView Pro commands cmds are executed when the breakpoint is hit.
When the breakpoint is hit, execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bcyc command.
To set a cycle count breakpoint after 4 clock cycles and list all global variables, type:
4 bcyc {l g}
break
,
b
, bCYC
, bINST
, binst
, bTIM
, btim
,
D
Set a read and/or write data breakpoint over a range of addresses.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select Data Breakpoint... to open the Add Data Breakpoint dialog. Enter an address or click the Address... button to select a symbol to use as the address. Click the Advanced button. Enter an address in the
End adress field or click the Browse... button to select a symbol to use as the end address. Click the OK button to add the data breakpoint.
The command line syntax is:
Set a read, write, or both (read and write) data breakpoint in the address range exp1 to exp2 and associate the list of CrossView Pro commands cmds with the breakpoint.
When the breakpoint is hit, execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next, any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bD command.
If exp1 is the address of a local (stack) variable, the function in which it was declared must be currently active on the stack. If the local variable corresponding to a data breakpoint goes out of scope due to a return from the function in which it is currently active, the data breakpoint will be removed and a message will be printed telling the user that the variable is no longer active.
Not available for all execution environments.
To set a data breakpoint that includes the entire structure rec1, type:
&rec1 bD r (int)&rec1+sizeof(rec1)-1
This breakpoint will be hit only if any address in the range of addresses is read from.
To set a data breakpoint for the address range 10 to 10f hex (256 bytes) that will list all global variables, type:
0x10 bD b 0x10f {l g;}
This breakpoint will be hit if any memory locations within the range 10-10f hex are either read from or written to.
break
,
b
,
bb
,
bB
,
bd
,
bi
,
bI
,
bt
,
bti
,
btI
,
bu
,
bU
,
Q
Set a read and/or write data breakpoint at an address.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select Data Breakpoint... to open the Add Data Breakpoint dialog. Enter an address or click the Address... button to select a symbol to use as the address. Click the OK button to add the data breakpoint.
The command line syntax is:
Set a read, write or both (read and write) data breakpoint at the address specified by exp and associate the list of CrossView Pro commands cmds with the breakpoint.
When the breakpoint is hit, execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bd command.
If exp corresponds to a local (stack) variable, the function in which it was declared must be currently active on the stack. If the local variable corresponding to a data breakpoint goes out of scope due to a return from the function in which it is currently active, the data breakpoint will be removed and a message will be printed telling you that the variable is no longer active.
Not available for all execution environments.
To set a breakpoint at the variable count which will all be hit only if the variable is read from memory, type:
&count bd r
Note that the breakpoint only acts on the lowest byte
in memory of this variable.
To set a breakpoint at address 10 hex that will list all global variables, type:
0x10 bd b {l g}
This breakpoint will be hit if address 10 hex is either read from or written to.
break
,
b
,
bb
,
bB
,
bD
,
bi
,
bI
,
bt
,
bti
,
btI
,
bu
,
bU
,
Q
Disable code breakpoint.
Select the Breakpoints | Breakpoint... menu item. On Windows toggle the check box in front of the breakpoint to enable
or disable the breakpoint. On UNIX select the breakpoint and click the Enable or
Disable button
The command line syntax is:
Disable the code breakpoint associated with the given number.
This does not delete the code breakpoint. It disables the code breakpoint until you enable it again with the bena command.
This command does not work on data breakpoints, only on code breakpoints
To disable code breakpoint number 3, type:
3 bdis
Enable code breakpoint.
Select the Breakpoints | Breakpoint... menu item. On Windows toggle the check box in front of the breakpoint to enable
or disable the breakpoint. On UNIX select the breakpoint and click the Enable or
Disable button
The command line syntax is:
Enable the code breakpoint associated with the given numbe., which was previously disabled by the bdis command.
This command does not work on data breakpoints, only on code breakpoints
To enable code breakpoint number 3, type:
3 bena
Set a temporary low-level breakpoint at a machine instruction.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select
Code Breakpoint... to open the Add Code Breakpoint dialog.
Edit the Break At... field. In the Advanced dialog enable the Remove when hit check box.
The command line syntax is:
Set a temporary breakpoint at the machine instruction at address addr, or the current viewing position's address if addr is not specified; the list of CrossView Pro commands cmds are executed when the breakpoint is hit.
Make sure that addr is the start address of a machine instruction, otherwise the results are unpredictable. When the breakpoint is hit execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bI command.
To set a temporary breakpoint at the current viewing position's address, type:
bI
To set a temporary breakpoint at address 100 that will print the addresses of the next five source statements, type:
100 bI {P 5}
break
,
b
,
bb
,
bB
,
bd
,
bD
,
bi
,
bt
,
bti
,
btI
,
bu
,
bU
,
Q
Set a permanent low-level breakpoint at a machine instruction.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select
Code Breakpoint... to open the Add Code Breakpoint dialog.
Edit the Break At... field. In the Advanced dialog disable the Remove when hit check box.
Alternatively, you can place a breakpoint in the intermixed window or assembly window by double clicking on the desired instruction.
The command line syntax is:
Set a permanent breakpoint at the machine instruction at address addr, or the current viewing position's address if addr is not specified; the list of CrossView Pro commands cmds are executed when the breakpoint is hit.
Make sure that addr is the start address of a machine instruction, otherwise the results are unpredictable. When the breakpoint is hit execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bi command.
To set a breakpoint at the current viewing position's address, type:
bi
To set a breakpoint at address 100 that will print the addresses of the next five source statements, type:
100 bi {P 5}
break
,
b
,
bb
,
bB
,
bd
,
bD
,
bI
,
bt
,
bti
,
btI
,
bu
,
bU
,
Q
Set a temporary instruction count breakpoint.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select Instruction Breakpoint... to open the Add Instruction Breakpoint dialog. Type a value in the Instruction count field and enable the
Remove when hit check box in the Advanced dialog.
The command line syntax is:
Set a temporary breakpoint after the specified count number of machine instructions have been executed. count can be any expression evaluating to a number. The list of CrossView Pro commands cmds are executed when the breakpoint is hit.
When the breakpoint is hit, execution is halted; the breakpoint is then removed. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bINST command.
To set a temporary breakpoint after execution of 5 instructions and list all global variables, type:
5 bINST {l g}
break
,
b
, bCYC
, bcyc
, binst
, bTIM
, btim
,
D
Set a permanent instruction count breakpoint.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select Instruction Breakpoint... to open the Add Instruction Breakpoint dialog. Type a value in the Instruction count field and disable the
Remove when hit check box in the Advanced dialog.
The command line syntax is:
Set a permanent breakpoint after the specified count number of machine instructions have been executed. count can be any expression evaluating to a number. The list of CrossView Pro commands cmds are executed when the breakpoint is hit.
When the breakpoint is hit, execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the binst command.
To set a permanent breakpoint after execution of 5 instructions and list all global variables, type:
5 binst {l g}
break
,
b
, bCYC
, bcyc
, bINST
, bTIM
, btim
,
D
Universal breakpoint command.
Select the Breakpoints | Breakpoints... menu item to add/remove/enable/disable breakpoints.
The general command line syntax is:
This is a universal breakpoint command.
type can be one of: code | data | instructions | cycles | time | sequence | set | delete | enable | disable. The type can be abbreviated. So, t|ti|tim|time are the same. When the type field is not specified the type defaults to code.
Depening on the type field the where field will evaluate to an address, count, name, breakpoint number or a sequence.
The available options are listed below.
Syntax:
address can be any expression evaluating to an address.
Syntax:
address can be any expression evaluating to an address.
Syntax:
count can be any expression evaluating to the number of instructions.
Syntax:
count can be any expression evaluating to the number of cycles.
Syntax:
time can be any expression evaluating to a time value. Depending on the setting of the timer_unit option this value is in seconds or timer ticks (default is in seconds).
Syntax:
sequence is a combination of breakpoints.
Syntax:
bp_number is the breakpoint number. If the breakpoint has a name (bp_name) you can use this name instead of a number.
Syntax:
bp_number is the breakpoint number. If the breakpoint has a name (bp_name) you can use this name instead of a number.
Syntax:
bp_number is the breakpoint number. If the breakpoint has a name (bp_name) you can use this name instead of a number.
name=str
temporary[=bool]
enabled[=bool]
curr_count=expr
reset_count=expr
count=expr
access_type=r | w | rw
addr=expr
value=expr
method=hardware | software | none
probe_point[=bool]
size=expr
end_addr=expr
end_value=expr
value_is_absolute[=bool]
commands={ commands }
timer_unit=seconds | ticks
bool
expr
To set a code breakpoint at an address range, type:
break code code:0x10, end_addr=code:0x1f
To set a code breakpoint at an address range by specifying a size, type:
break code:0x10, size=0x10
To set a code breakpoint with a name, type:
break code:0x10, name=brk_1
To disable the breakpoint with name brk_1, type:
break dis brk_1
To set a cycle count breakpoint and treat the value as an absolute count, type:
break cycles 1000, value_is_absolute
Chapter 7
, Breakpoints.
Set a task aware code breakpoint.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select
Code Breakpoint... to open the Code Breakpoint dialog. Fill
in the Task ID field.
The command line syntax is:
Set a task aware code breakpoint at the specified source line and associate the list of CrossView Pro commands cmds with the breakpoint. If no line is given, set the breakpoint at the current viewing position. The TaskId is the identification of the task as displayed in the Tasks Window or specified by the l k command.
When the breakpoint is hit, execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next, any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bt command.
To set a breakpoint for task 4 at the current viewing position, type:
bt "4"
To set a breakpoint for task 4 at line 10, which lists all global variables, type:
10 bt "4" {l g}
break
,
b
,
bb
,
bB
,
bd
,
bD
,
bi
,
bI
,
bti
,
btI
,
bu
,
bU
,
l
,
Q
Set a temporary low-level task aware breakpoint at a machine instruction.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select
Code Breakpoint... to open the Code Breakpoint dialog. Edit
the Break At... field and fill in the Task ID field. In the Advanced dialog enable the Remove when hit check box.
The command line syntax is:
Set a temporary task aware breakpoint at the machine instruction at address addr, or the current viewing position's address if addr is not specified; the list of CrossView Pro commands cmds are executed when the breakpoint is hit. The TaskId is the identification of the task as displayed in the Tasks Window or specified by the l k command.
Make sure that addr is the start address of a machine instruction, otherwise the results are unpredictable. When the breakpoint is hit execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the btI command.
To set a temporary breakpoint for task 4 at the current viewing position's address, type:
btI "4"
To set a temporary breakpoint for task 4 at address 0xF00 and print the message, type:
0xF00 btI "4" {"breakpoint triggered: address 0xF00, task 4"}
break
,
b
,
bb
,
bB
,
bd
,
bD
,
bi
,
bI
,
bt
,
bti
,
bu
,
bU
,
l
,
Q
Set a permanent low-level task aware breakpoint at a machine instruction.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select
Code Breakpoint... to open the Code Breakpoint dialog. Edit
the Break At... field and fill in the Task ID field. In the Advanced dialog disable the Remove when hit check box.
The command line syntax is:
Set a permanent task aware breakpoint at the machine instruction at address addr, or the current viewing position's address if addr is not specified; the list of CrossView Pro commands cmds are executed when the breakpoint is hit. The TaskId is the identification of the task as displayed in the Tasks Window or specified by the l k command.
Make sure that addr is the start address of a machine instruction, otherwise the results are unpredictable. When the breakpoint is hit execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bti command.
To set a breakpoint for task 4 at the current viewing position's address, type:
bti "4"
To set a breakpoint for task 4 at address 0xF00 and print the message, type:
0xF00 bti "4" {"breakpoint triggered: address 0xF00, task 4"}
break
,
b
,
bb
,
bB
,
bd
,
bD
,
bi
,
bI
,
bt
,
btI
,
bu
,
bU
,
l
,
Q
Set a temporary time breakpoint.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select Timer Breakpoint... to open the Add Timer Breakpoint dialog. Enter a value in the Time field and enable the Remove when hit check box in the Advanced
dialog.
The command line syntax is:
Set a temporary breakpoint after the specified time (in seconds). time can be any expression evaluating to a number. The list of CrossView Pro commands cmds are executed when the breakpoint is hit.
When the breakpoint is hit, execution is halted; the breakpoint is then removed. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bTIM command.
To set a temporary breakpoint after 0.5 seconds and list all global variables, type:
0.5 bTIM {l g}
break
,
b
, bCYC
, bcyc
, bINST
, binst
, btim
,
D
Set a permanent time breakpoint.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click the Add > button and select Timer Breakpoint... to open the Add Timer Breakpoint dialog. Enter a value in the Time field and disable the Remove when hit check box in the Advanced
dialog.
The command line syntax is:
Set a permanent breakpoint after the specified time (in seconds). time can be any expression evaluating to a number. The list of CrossView Pro commands cmds are executed when the breakpoint is hit.
When the breakpoint is hit, execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the btim command.
To set a permanent breakpoint after 0.5 seconds and list all global variables, type:
0.5 bTIM {l g}
break
,
b
, bCYC
, bcyc
, bINST
, binst
, bTIM
,
D
Set a temporary up-level breakpoint (to finish the function at a specific stack level).
In the Stack Window, double-click on the desired function. Alternately, you can click on the desired function in the Stack Window and select the Breakpoints | Stack Breakpoint | After Call to Function menu item.
The command line syntax is:
This command sets a temporary up-level breakpoint immediately after the call to the function designated by the stack number stack, otherwise the currently viewed function is used. Associate the list of CrossView Pro commands commands with the breakpoint.
When the breakpoint is hit execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bU command.
Breakpoints set in the Stack Window are always temporary, meaning they will be deleted after the first time you reach them. A breakpoint set in this manner will not be visible in the Source Window.
This command is not allowed when the target runs in the background.
To set a temporary up-level breakpoint immediately after the call to the currently viewed function, type:
bU
To set a temporary up-level breakpoint immediately after the call to the function at stack level 2, type:
2 bU {1}
After stopping, this command will cause CrossView Pro to print out the function's local variables and arguments.
break
,
b
,
bb
,
bB
,
bd
,
bD
,
bi
,
bI
,
bt
,
bti
,
btI
,
bu
,
Q
Set a permanent up-level breakpoint (to finish the function at a specific stack level).
Click on the desired function in the Stack Window and
select the Breakpoints | Stack Breakpoint | After Call to Function menu item. To make the stack breakpoint permanent,
select the Breakpoints | Breakpoints... menu item, select the desired stack breakpoint and click on the Edit... button. The Edit Code Breakpoint dialog appears. Click on the Advanced>> button and disable the Remove when hit check box.
The command line syntax is:
Set a permanent up-level breakpoint immediately after the call to the function designated by the stack number stack, otherwise the currently viewed function is used. Associate the list of CrossView Pro commands commands with the breakpoint.
When the breakpoint is hit execution is halted. By default the current execution position, function, line number, and source statement are displayed. Next any commands associated with the breakpoint are executed. The Q command can be used to suppress the output from the bu command.
This command is not allowed when the target runs in the background.
To set a temporary up-level breakpoint immediately after the call to the currently viewed function, type:
bu
To set an up-level breakpoint immediately after the call to the function at stack level 2 and, after stopping, print out the local variables and arguments of that function, type:
2 bu {l}
break
,
b
,
bb
,
bB
,
bd
,
bD
,
bi
,
bI
,
bt
,
bti
,
btI
,
bU
,
Q
Append the contents of one buffer to another buffer.
The command line syntax is:
Add the contents of buffer added_buffer_name to buffer target_buffer_name. If size_limit is specified, buffer target_buffer_name will be trimmed down to the specified size (keeping size_limit elements of the tail of the buffer).
To append the contents of $buffer to buffer $all_data, and keep the last 1024 elements, type:
bufa $all_data,$buffer,1024
bufd
, graph
, memget
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Free a used buffer.
The command line syntax is:
Discard the specified buffer (if the target data is not to be used anymore).
To discard buffer $buffer, type:
bufd $buffer
bufa
, graph
, memget
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Continue using the current value of the program counter.
In the Source Window, click on the
Run/Continue
button. You can also select the Run | Run menu item.
The command line syntax is:
If exp is specified and you are stopped at a breakpoint, then the breakpoint count is set to this value. If line is specified, a temporary breakpoint is set at that line number. Note that this temporary breakpoint will overwrite any existing breakpoint at that line.
The C command can be used in the command lists of breakpoints to resume execution automatically.
This command is not allowed when the target runs in the background.
To continue execution from the current target program counter, type:
C
To set the breakpoint's count to 4 and continue, type:
4 C
To set a temporary breakpoint at line 52 and continue, type:
C 52
Continue execution in background using the current value of the target program counter.
The command line syntax is:
If exp is specified and you are stopped at a breakpoint, then the breakpoint count is set to this value. If line is specified, a temporary breakpoint is set at that line number. Note that this temporary breakpoint will overwrite any existing breakpoint at that line.
The CB command can be used in the command lists of breakpoints to resume execution automatically.
This command is not allowed when the target runs in the background.
Not available for all execution environments.
To continue execution from the current target program counter, type:
CB
To set the breakpoint's count to 4 and continue, type:
4 CB
To set a temporary breakpoint at line 52 and continue, type:
CB 52
Disable, turn off, gathering of coverage data.
Select the Tools | Coverage menu item if this item was set.
The command line syntax is:
If coverage is supported by your version of CrossView Pro, this command disables the coverage system. Normally, you should disable coverage if you are not interested in the coverage results, as this will often improve the performance of the execution environment.
To disable coverage, type:
cd
Enable, turn on, gathering of coverage data.
Select the Tools | Coverage menu item if this item was not set.
The command line syntax is:
If coverage is supported by your version of CrossView Pro, this command enables the coverage system. Normally, you should disable coverage if you are not interested in the coverage results, as this will often improve the performance of the execution environment.
To enable coverage, type:
ce
Clear the Command Output Window.
The command line syntax is:
Use this command if you want to clear the output window part of the Command Window.
To clear the Command Output Window, type:
clear
List coverage information.
Select the Tools | Code Coverage... menu item, make your changes and select the Update button.
The command line syntax is:
If coverage is supported by your version of CrossView Pro and coverage is enabled, this command lists the coverage information. Without arguments (same as all) this command lists the coverage information of all modules and functions.
Instead of listing the results you can also save the results in a file with extension .cov.
Normally, you should disable profiling if you are not interested in the profiling results, as this will often improve the performance of the execution environment.
To list the coverage information of all modules and functions to the output window, type:
ce covinfo
To list coverage information of function main to the output window, type:
covinfo main
To list coverage information of all modules and functions in file hello.cov, type:
covinfo all,hello.cov
List cumulative profiling results or add or remove functions from the list of profiled functions.
Select the Tools | Cumulative Profiling Setup... menu item, make your changes and click the OK button. Select Tools | Cumulative Profiling Report... to see the cumulative
profiling report.
The command line syntax is:
If profiling is supported by your version of CrossView Pro and profiling is enabled, this command lists the cumulative profiling results. Without arguments (same as all) this command lists the cumulative profiling information of all functions.
Instead of listing the results you can also save the results in a file with extension .cpr.
Normally, you should disable profiling if you are not interested in the profiling results, as this will often improve the performance of the execution environment.
To list the cumulative profiling results of all functions to the output window, type:
pe cproinfo
To dump cumulative profile information of all functions in file hello.cpr, type:
cproinfo all,hello.cpr
To add function main to the list of profiled functions, type:
cproinfo add main
To remove function main from the list of profiled functions, type:
cproinfo remove main
Display a C-execution trace.
Select the View | Trace | Source Level menu item. The Trace Window displays the most recently executed lines of code
every time program execution is stopped. CrossView Pro automatically
updates the Trace Window each time execution is halted, as long as the window
is open.
The command line syntax is:
Display a C-execution trace in the Command window, corresponding to the last number of machine instructions executed. Since the ct command relies on the emulator's trace buffer, the ct command will not be implemented on some emulators.
For each executed line of code, the Trace Window displays:
The window shows all the code executed since the the last time the program halted.
This command is not allowed when the target runs in the background.
Not available for all execution environments.
To display, in the Command window, the last C statements (corresponding to the last ten machine instructions) executed, type:
10 ct
Display a disassembled trace.
Select the View | Trace | Instruction Level menu item. The Trace Window displays the most recently executed lines of
code every time program execution is stopped. CrossView Pro automatically updates the Trace Window each time execution is halted, as long as
the window is open.
The command line syntax is:
Display a disassembled trace in the Command window, corresponding to the last number of machine instructions executed.
Since the ct i command relies on the emulator's trace buffer, the ct i command will not be implemented on some emulators.
This command is not allowed when the target runs in the background.
Not available for all execution environments.
To display in the Command window the last 20 disassembled instructions executed, type:
20 ct i
Display a raw trace.
Select the View | Trace | Raw menu item. The Trace Window displays the most recently executed lines of code every time program execution is stopped. CrossView Pro automatically
updates the Trace Window each time execution is halted, as long as the window
is open.
The command line syntax is:
Display a raw trace in the Command window, corresponding to the last number of trace frames. This command merely shows the contents of the emulator's trace buffer.
Since the ct r command relies on the emulator's trace buffer, the ct r command will not be implemented on some emulators.
This command is not allowed when the target runs in the background.
Not available for all execution environments.
To display in the Command window the last 20 trace frames, type:
20 ct r
Delete all currently defined breakpoints.
Select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Click on the Remove All button.
The command line syntax is:
D deletes all currently defined breakpoints. Dy does not ask for confirmation.
Delete a specific breakpoint.
To delete a code breakpoint directly from the C source,
click on the red breakpoint toggle next to the corresponding, source line
in the Source Window.
Otherwise, select the Breakpoints | Breakpoints... menu item to view the Breakpoints dialog box. Select the breakpoint you want to remove and click on the Remove button.
The command line syntax is:
Delete the breakpoint associated with the given number. If no number is given, delete the breakpoint at the current line. If there is no breakpoint at the current line, a B command will be executed to display all breakpoints.
Whenever a breakpoint is deleted the remaining breakpoints are renumbered starting at 0.
To delete a breakpoint at the current line, type:
d
To delete breakpoint number 3, type:
3 d
break
,
b
,
bb
,
bB
,
bd
,
bD
,
bi
,
bI
,
bt
,
bti
,
btI
,
bu
,
bU
,
B
,
D
Compare a file with the downloaded application.
Select the File | Compare Application... menu item. Specify an application file and click on the Compare button.
The command line syntax is:
Compare an application file with the memory contents and display differing memory addresses or addresses and values. If you have already loaded an application you can invoke this command without specifying a file name. You can limit the number of differences by specifying a number_of_hits. The value 0 means there is no limit on the number of differences.
This command is not allowed when the target runs in the background.
To compare the currently loaded application, there is no limit on the number of differences and the contents of differing memory addresses are not displayed, type:
dcmp
To compare the currently loaded application and stop when the number of differences equals 10, type:
dcmp ,10
To compare the currently loaded application there is no limit on the number of differences and display the contents of differing memory addresses, type:
dcmp ,,d
To compare file test.abs, stop if the number of differences equals 5 and display the contents of differing memory addresses, type:
dcmp "test.abs",5,d
Open, save/restore, close a debug instrument state.
Select the Target | Save/Restore Target State... menu item.
The command line syntax is:
Before a state can be saved, restored or closed it must be opend first. To open a state use the di_state open state_name command. When opened successfully the name is added to the available state names list.
With the di_state save command you can now save the state of the debug instrument with the specified state_name and number. With di_state restore you can restore a previously saved state of the debug instrument with the specified state_name and number.
Use di_state close to close a state. The delete flag can be 1 to delete the state or use 0 to keep the state.
This feature is only available when it is supported by the debug instrument.
To open and save a state, type:
di_state open S1 di_state save S1, 0
To restore a state, type:
di_state restore S1, 0
Disassemble a range of memory.
Select the View | Source | Disassembly or View | Source | Source and Disassembly menu item to open the Disassembly or Source and Disassembly window respectively.
The command line syntax is:
Disassemble a range of memory. The output is interleaved with source lines when i is specified. You can enter valid expressions as well for address and count.
To disassemble 4 instructions starting at 3 bytes behind the start address of the function main., type:
dis main+3,#4
To disassemble memory for (initval+1) instructions, starting at the address of the function main., type:
dis main+3,#initval+1
To disassemble from 0x2000 up to and including the instruction at 0x2100 and also interleave C source lines of any function resident in that memory range, type:
dis 0x2000,0x2100,i
Download a file.
Select the File | Download Application... menu item to download the image part of the file to the execution environment.
The command line syntax is:
Download the image part of the specified file to the execution environment. If no file is specified, use the file specified when CrossView Pro was invoked, and from which the symbolic information was read during startup, or the file specified in either the N command or the Load Symbolic Debug Info dialog.
Downloading a file only copies an image part into target memory. It will not cause CrossView Pro to re-read symbolic information.
This command is not allowed when the target runs in the background.
To download the current file, type
dn
To download the IEEE file demo.abs, type:
dn demo.abs
To download the hex file test.hex, type:
dn test.hex
Download a file into a specific memory space
Select the File | Download Image menu item to download the image part of the file to the execution environment.
Select a memory space in the Into mem. list selection box.
The command line syntax is:
Download the image part of the specified file to the execution environment into the specified memory space mem_space. The file must contain data in hexadecimal format, that is, Intel Hex, Motorola S-records, Tektronix Hex and Extended Tektronix Hex formats are supported. If no file is specified, use the file specified when CrossView Pro was invoked, or the file specified in either the N command or the Load Symbolic Debug Info dialog.
This command is not allowed when the target runs in the background.
To download the current file into memory space CODE, type
dnm CODE
To download the IEEE file demo.abs into memory space CODE, type:
dnm CODE demo.abs
Dump a range of memory.
Select the View | Memory | New menu item to open a Memory Window.
The command line syntax is:
The dump command can dump memory as hexadecimal data or as C variables. You can enter valid C expressions as well for address and count. You can also dump Motorola S records or Intel hex records. Also, you can specify a filename in which the dump is to be written or appended.
style can be one of:
a c D O U X d o u x E F G e f g n P p R r s t I M
Style I dumps Intel hex and style M specifies Motorola S records output. See Chapter 6, Accessing Code and Data, and section 3.5, Formatting Expressions, in Chapter 3, Command Language, for details on each of the other format styles. The R and r style are only available for targets that support the fractional type.
Mind the following:
To dump the first byte of the function main., type:
dump main
To dump the first 10 bytes of the function main as Motorola S records in the file main.sre, type:
dump main,main+10,M,main.sre
To dump the first 5 bytes of the function main. as 1 string, type:
dump main,main+10,M,main.sre,a
To append the first 5 bytes of the function main. as 1 string, type:
dump main,,c5
To dump the resulting value bytes of 'the address of main binary anded with 3', type:
dump main+1,#main&3
Establish viewing position
Select the File | Open Source... menu item to view a file. In the Source Window, click on the Find Symbol button to find a function, or select the Edit | Find Symbol... menu item.
In the Stack Window click once on the function to be examined.
The command line syntax is:
The e option invokes two distinct commands. The first version establishes the viewing position to be the first line of file, the first executable line of the function function or the current viewing position if no argument is given.
The second version establishes the viewing position to be the line at stack level stack in the stack trace. (See the t command.)
The stack e command is not allowed when the target runs in the background.
The L command is equivalent to 0 e.
To view the function main, type:
e main
To view the test file test.c, type:
e test.c
To view the call site of the current function, type:
0 e
To view the line at stack level 3, type:
3 e
Start execution on current CPU and switch to another CPU.
The command line syntax is:
Start execution on the current CPU and switch to CPU cpu_number.
This command can only be issued when the currently selected CPU is in debug mode.
To start execution on the current CPU and select the CPU indicated by number 1, type:
1 eC
Select a CPU or show current CPU number.
The command line syntax is:
The ec command allows you to select a CPU in your current Execution Environment if your target has multi-CPU support.
This command can only be issued when the currently selected CPU is in debug mode.
To view the current CPU selection, type:
ec
To select the CPU indicated by number 1, type:
1 ec
Display the definition of a macro name without executing the macro.
You can view the definition of a macro by selecting the Tools | Macro Definitions... menu item to view the Macro Definitions dialog box.
The command line syntax is:
Perform macro expansion on text without executing. This allows you to see how a macro is expanded. It is particularly informative when macros call other macros.
If you type:
echo macro(3)
CrossView Pro will display the expansion of macro(3).
Establish viewing position at a specified address.
Select the Edit | Find Address... menu item.
The command line syntax is:
The ei command establishes the viewing position to be at the instruction specified.
This command is useful for viewing some code in the assembly window, without changing the program counter, since the execution position is not changed.
To view the current viewing position, type:
ei
To view the instruction at address 0x100, type:
0x100 ei
Select the specified task's context.
In the Tasks Window click once on the task to be examined.
The command line syntax is:
Select the specified task's context. The TaskId is the identification of the task as displayed in the Tasks Window or specified by the l k command.
The current execution position, function, line number, and source statement are displayed. All other windows, except for the Kernel Windows, are updated accordingly.
Subsequent CrossView Pro commands use the context of the selected task. For example, the t command shows a stack trace of the selected task.
To select task 4, type:
et "4"
Set default address printing format
The command line syntax is:
Set the default address printing format, using a printf format specification.
If there is no argument, the format defaults to %x, which prints an address in hexadecimal.
This command is intended to allow users to see memory addresses in decimal, octal or a format of their choosing.
To display addresses in octal, type:
f "%o"
To display addresses in hex, type:
f
File System Simulation redirection.
The command line syntax is:
Redirect a File System Simulation stream to a file or another stream. Redirection to a file can be needed when a stream is only mapped to a window and you want it to be mapped to a file also.
To redirect the output of stream 2 to stream 1, type:
FSS 2>&1
To retrieve input for stream 1 from stream 4, type:
FSS 1<&4
To retrieve input for stream 4 from file "data.txt", type:
FSS 4<"data.txt"
To redirect the output of stream 3 to file "data.txt", type:
FSS 3>"data.txt"
Section 10.3
, File System Simulation
in Chapter I/O Simulation.
Close a stream previously opened by FSS_stdio_open.
The command line syntax is:
Close the stream indicated by streamnumber.
To close stream 1, type:
FSS_stdio_close 1
FSS_stdio_open.
Section 10.3,
File System Simulation
in Chapter I/O Simulation.
Redirect the output of a stream to a file.
The command line syntax is:
Redirect the stream indicated by streamnumber to the file filename. rwdirection can be an r for read-only, w for writable, or rw for read/write.
To redirect stream 1 (output, so w for writable) to the file myfile.out, type:
FSS_stdio_open myfile.out,w,1
The following command is used to close the stream.
FSS_stdio_close 1
FSS_stdio_close.
Section 10.3,
File System Simulation
in Chapter I/O Simulation.
Change the program counter to a new execution position.
Click on a source line and select the
Run | Jump to Cursor menu item.
The command line syntax is:
This command changes the program counter so that line becomes the current execution position. Line must be a line in the current function.
This command changes only the program counter. It does not cause the target to begin execution.
Exercise caution when changing the execution position. Oftentimes, each line of C source code is compiled into several machine language instructions. Moving the program counter to a new address in the middle of a series of related assembly instructions is sometimes risky. Moreover, even though you change the program counter, registers and variables may not have the expected values if parts of the code are bypassed.
This command is not allowed when the target runs in the background.
To change the program counter so that the next instruction to be executed corresponds to line 127, type:
g 127
Change the program counter to a new execution position.
Click on a source line and select the
Run | Jump to Cursor menu item.
The command line syntax is:
This command changes the program counter so that address becomes the current execution position.
This command changes only the program counter. It does not cause the target to begin execution.
Exercise caution when changing the execution position. The Jump to Cursor menu item is not available in the source lines window mode to prevent problems by skipping pieces of C code which are required to be executed. Moving the program counter to a new address in the middle of a series of related assembly instructions is sometimes risky. Moreover, even though you change the program counter, registers and variables may not have the expected values if parts of the code are bypassed.
This command is not allowed when the target runs in the background.
To change the program counter so that the next instruction to be executed corresponds to address 0x0800, type:
0x0800 gi
Create Data Analysis window and execute CXL script.
The command line syntax is:
Create Data Analysis window window and execute CXL script script. The display list produced by the script is shown in the specified window. Arguments arg are passed as global variables to the script. Each argument is treated as an expression. Arguments starting with a "$" refer to an acquisition buffer. In all other cases arg is evaluated as an expression and will be casted to type double.
If for example register $R1 should be passed as argument to the script you must write "0+$R1" to avoid that $R1 is recognized as an acquisition buffer.
To transform the contents of buffer $buffer to displayable data in window demo using CXL script x_t.cxl, type:
graph "demo","x_t.cxl",$buffer,0,1
bufa
, graphm
, graphp
, memget
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Add a command to the sequence of update commands.
For the supplied scripts only. Select the
Settings | Data Analysis Window Setup... menu item. Enter a new window
name and click New. Click Configure... to open the Data Analysis Window Setup dialog.
The command line syntax is:
Set the sequence of update commands for Data Analysis window window manually. These update commands are executed when the Update button on the Data Analysis window is pressed or when the update command is issued.
Prior to adding update commands, you have to remove all update commands with the graph_clear_updates command.
To retrieve data and show it in window demo, type:
graph_clear_updates "demo" graph_add_update "demo",memget data[$i],100,$buffer graph_add_update "demo",graphm "demo","show_x_t.cxl" graph_add_update "demo",graph "demo","x_t.cxl",$buffer,0,1 update "demo"
graph_clear_updates, update
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Clear the sequence of update commands.
The command line syntax is:
Clear the sequence of update commands for Data Analysis window window. This is needed prior to adding new update commands with the graph_add_update command.
To retrieve data and show it in window demo, type:
graph_clear_updates "demo" graph_add_update "demo",memget data[$i],100,$buffer graph_add_update "demo",graphm "demo","show_x_t.cxl" graph_add_update "demo",graph "demo","x_t.cxl",$buffer,0,1 update "demo"
graph_add_update, update
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Close a Data Analysis window.
The command line syntax is:
With the graph_close command you can close the named window.
To close window demo, type:
graph_close "demo"
graph
, graphm
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Debug Data Analysis graph window.
The command line syntax is:
If expression evaluates to a non-zero value, this value is an ORed value of two flags:
Other bits (when value & 3 equals zero, for example 4) are ignored and treated like zero. No parameters result in value 1. A value of zero turns off all debugging.
graph
, graphm
, graphmn.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Set Data Analysis window display mode.
The command line syntax is:
The graphm command sets the representation script for the specified window. Depending on the script, the arguments may vary.
Several scripts are supplied with the product that you can use with the graphm command. See section Supplied Data Analysis Window Scripts in Chapter Special Features for more information.
To set the display mode for window demo using CXL script show_x_t.cxl and show "demo" in the title bar of the window, type:
graphm "demo","show_x_t.cxl"
bufa
, graph
, graphp
, memget
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Set Data Analysis window display mode.
The command line syntax is:
The graphmn command works similar to the graphm command, but it does not update the graph window. This can be useful where a graph and a graphm command are followed by each other, preventing the redrawing of the same graphics twice.
To set the display mode for window demo using CXL script show_x_t.cxl and show "demo" in the title bar of the window, type:
graphmn "demo","show_x_t.cxl"
bufa
, graph
, graphp
, memget
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Position Data Analysis window on the screen.
The command line syntax is:
With the graphp command you can position the named window at the specified screen coordinates.
To put window demo at position (0,0) on the screen with a size of 100x100, type:
graphp "demo",0,0,100,100
graph
, graphm
.
Section 11.5,
Data Analysis,
in Chapter Special Features.
Suppress or reactivate window updating.
The command line syntax is:
With gus on the GUI updating suppress feature is enabled. This means that the graphical windows are no longer updated. To reactivate the window updating use the gus off command.
To suppress the updating of CrossView windows, type:
gus on
Other commands:
expression - ^
I - Z