GRMON3-UM
June 2019, Version 3.1.0
43 www.cobham.com/gaisler
Associate a setting with a CPU by clicking the cell that intersect the setting and the CPU and tick the check box.
Untick the check-box to reverse the association. Some settings can occur more than one time for the same CPU (i.e.
Symbol file), meaning that several symbol files can be supplied. If an incompatible or unsupported combination
of settings is associated to a CPU, then the background of the cells for the settings are set to bright red.
To edit the value of a setting click the cell in the Value column. Different settings are edited in different ways. If
the cell after clicking it shows a button with "...", this button opens a dialog to change the value. For example the
Image setting is edited by choosing a file from a dialog.
If any of the settings are invalid, then the dialog shows an error message at the top, and the button Launch Target
Image are disabled. Once the invalid settings are corrected, the button becomes enabled and the Target Image
can be launched.
A Target Image Configuration can be launched automatically at connect to the system. This can be selected in the
System configuration dialog option named Launch Target Image Configuration when connected.
4.4.2. Launch properties
A simple launch configuration typicaly consists of only the Image and Run Mode properties. Additional properties
can be added as required. The following list describes all available properties.
Properties:
Image
File name of an image file to load. More than one image can be added and each image can be assigned
to any number of CPUs.
Command: load
Verify Image
Verify each image after load to memory. The property is not CPU specific. Only one Verify Image property
can be specified.
Command: verify
Symbol file
File name of a symbol file to load. The symbols will be loaded into GRMON but no content from the file
will be loaded into the target memory. More than one image can be added and each image can be assigned
to any number of CPUs.
Command: symbols
Run Mode
• Run - Reset GRMON drivers and start the execution from the beginning of the application.
• Go - Start the execution from the beginning of the application with the current system CPU state.
At most one Run Mode can be specified. The recommended mode is Run for most applications. Go is useful
when the application itself is initilizing the target, such as a boot loader. The property is not CPU specific.
Note that it is also possible to omit the Run Mode property. In that case, the application could be started
with the run command in a shell.
Command: run, go
Break at Application
Inserts a breakpoint at application start. The breakpoint location is OS dependent, for example main() in a
bare-metal application and Init() in an RTEMS application. At most one Break at Application property
can be specified.
Command: bp
Break at Entry
Inserts a breakpoint at the entry point of the loaded image. At most one Break at Application property can
be specified.
To Next Page
Loading...