
GRMON3-UM
June 2019, Version 3.1.0
52
www.cobham.com/gaisler
5. Debug link
GRMON supports several different links to communicate with the target board. However all of the links may not
be supported by the target board. Refer to the board user manual to see which links that are supported. There are
also boards that have built-in adapters.
NOTE: Refer to the board user manual to see which links that are supported.
The default communication link between GRMON and the target system is the host’s serial port connected to a
serial debug interface (AHBUART) of the target system. Connecting using any of the other supported link can
be performed by using the switches listed below. More switches that may affect the connection are listed at each
subsection.
-altjtag
Connect to the target system using Altera Blaster cable (USB or parallel).
-eth
Connect to the target system using Ethernet. Requires the EDCL core to be present in
the target system.
-digilent
Connect to the target system Digilent HS1 cable.
-ftdi
Connect to the target system using a JTAG cable based on a FTDI chip.
-gresb
Connect to the target system through the GRESB bridge. The target needs a SpW core
with RMAP.
-jtag
Connect to the target system the JTAG Debug Link using Xilinx Parallel Cable III or IV.
-usb
Connect to the target system using the USB debug link. Requires the GRUSB_DCL core
to be present in the target.
-xilusb
Connect to the target system using a Xilinx Platform USB cable.
-uart
<device>
Connect to the target system using a serial cable.
-user
Connect to the target system using a custom user defined library.
8-/16-bit access to the target system is only supported by the JTAG debug links, all other interfaces access sub-
words using read-modify-write. All links supports 32-bit accesses. 8-bit access is generally not needed. An exam-
ple of when it is needed is when programming a 8 or 16-bit flash memory on a target system without a LEON
CPU available. Another example is when one is trying to access cores that have byte-registers, for example the
CAN_OC core, but almost all GRLIB cores have word-registers and can be accessed by any debug link.
The speed of the debug links affects the performance of GRMON. It is most noticeable when loading large appli-
cations, for example Linux or VxWorks. Another case when the speed of the link is important is during profiling,
a faster link will increase the number of samples. See Table 5.1 for a list of estimated speed of the debug links.
Table 5.1. Estimated debug link application download speed
Name
Estimated speed
UART
~100 kbit/s
JTAG (Parallel port)
~200 kbit/s
JTAG (USB)
~1 Mbit/s
GRESB
~25 Mbit/s
USB
~30 Mbit/s
Ethernet
~35 Mbit/s
5.1. UART debug link
To attach GRMON using the AHBUART debug link, first connect a cable between the UART connectors on target
board and the host system. Then power-up and reset the target board and start GRMON with the
-uart
option.
Use the
-uart <device>
option in case the target is not connected to the first UART port of your host. On
some hosts, it might be necessary to lower the baud rate in order to achieve a stable connection to the target. In
Содержание 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...