GRMON3-UM
June 2019, Version 3.1.0
61
www.cobham.com/gaisler
Figure 5.5.
5.5. GRESB debug link
Targets equipped with a SpaceWire core with RMAP support can be debugged through the GRESB debug link
using the GRESB Ethernet to SpaceWire bridge. To do so start GRMON with the
-gresb
switch and use the
any of the switches below to set the needed parameters.
For further information about the GRESB bridge see the GRESB manual.
Extra options for the GRESB connection:
-gresb
[
<ipnum>
]
Use the GRESB connection and optionally use
ipnum
for the target system IP number. Default is
192.168.0.50.
-link
<num>
Use link
linknum
on the bridge. Defaults to 0.
-dna
<dna>
The destination node address of the target. Defaults to 0xfe.
-sna
<sna>
The SpW node address for the link used on the bridge. Defaults to 32.
-dpa
<dpa1>
[,
<dpa2>
,
...
,
<dpa12>
]
The destination path address. Comma separated list of addresses.
-spa
<spa1>
[,
<spa2>
,
...
,
<spa12>
]
The source path address. Comma separated list of addresses.
-dkey
<key>
The destination key used by the targets RMAP interface. Defaults to 0.
-clkdiv
<div>
Divide the TX bit rate by div. If not specified, the current setting is used.
-gresbtimeout
<sec>
Timeout period in seconds for RMAP replies. Defaults is 8.
-gresbretry
<n>
Number of retries for each timeout. Defaults to 0.
5.5.1. AGGA4 SpaceWire debug link
It is possible to debug the AGGA4 via SpaceWire, using the GRESB Ethernet SpaceWire Bridge, by combining the
commandline switches '
-gresb
' and '
' when starting GRMON. In addition, the following options
can also be added:
-link
,
-clkdiv
,
-gresbtimeout
and
-gresbretry
.
The AGGA4 SpaceWire debug link does not use a regular SpaceWire packet protocol, therefore the GRESB must
be setup to tunnel all the packets as raw data. To achieve this the GRESB must be configured to use separate
routing tables, this setting can only be enabled via the web interface.
