
GRMON3-UM
June 2019, Version 3.1.0
10
www.cobham.com/gaisler
3. Operation
This chapter describes how GRMON can be controlled by the user in a terminal based interactive debug session
and how it can be automated with scripts for batch execution. The first sections describe and exemplifies typical
operations for interactive use. The later sections describe automation concepts. Most interactive commands are
applicable also for automated use.
GRMON graphical user interface is described in Chapter 4, Graphical user interface.
3.1. Overview
An interactive GRMON debug session typically consists of the following steps:
1. Starting GRMON and attaching to the target system
2. Examining the hardware configuration
3. Uploading application program
4. Setup debugging, for example insert breakpoints and watchpoints
5. Executing the application
6. Debugging the application and examining the CPU and hardware state
Step 2 though 6 is performed using the GRMON terminal interface or by attaching GDB and use the standard
GDB interface. The GDB section describes how GRMON specific commands are accessed from GDB.
The following sections will give an overview how the various steps are performed.
3.2. Starting GRMON
On a Linux host, GRMON is started by giving the grmon command together with command line options in a
terminal window. It can run either the GUI or a commandline interface depending on if a debug link option is
provided or not.
On Windows hosts, there are two executable provided. The file grmon.exe is intended to be started in a Windows
command prompt (cmd.exe). It can run either the GUI or a commandline interface depending on if a debug link
option is provided or not. The executable grmon-gui.exe will always spawn a gui.
Command line options are grouped by function as indicated below.
• The debug link options: setting up a connection to GRLIB target
• General options: debug session behavior options
• Debug driver options: configure the hardware, skip core auto-probing etc.
NOTE: If any debug-link option is given to grmon or grmon.exe, then the GRMON command line interface
will be started.
If no debug-link option is given to grmon or grmon.exe, then the GRMON graphical user interface will be started.
For more information, see Chapter 4, Graphical user interface.
Below is an example of GRMON connecting to a GR712 evaluation board using the FTDI USB serial interface,
tunneling the UART output of APBUART0 to GRMON and specifying three RAM wait states on read and write:
$ grmon -ftdi -u -ramws 3
To connect to a target using the AHBUART debug link, the following example can be used:
$ grmon -uart -u
The
-uart
option uses the first UART of the host (ttyS0 or COM1) with a baud rate of 115200 baud by default.
3.2.1. Debug link options
GRMON connects to a GRLIB target using one debug link interface, the command line options selects which
interface the PC uses to connect to the target and optionally how the debug link is configured. All options are
described in Chapter 5, Debug link.
Содержание GRMON3
Страница 56: ...GRMON3 UM June 2019 Version 3 1 0 56 www cobham com gaisler...
Страница 114: ...GRMON3 UM June 2019 Version 3 1 0 114 www cobham com gaisler...
Страница 123: ...GRMON3 UM June 2019 Version 3 1 0 123 www cobham com gaisler dcache...
Страница 156: ...GRMON3 UM June 2019 Version 3 1 0 156 www cobham com gaisler SEE ALSO Section 6 13 On chip logic analyzer driver...
Страница 208: ...GRMON3 UM June 2019 Version 3 1 0 208 www cobham com gaisler SEE ALSO Section 3 5 Tcl integration...