User manual

Raisonance Tools for ARM 6. Debugging with hardware tools
6.3.2 Installing the Signum Systems USB driver for Ride7
To install the USB driver for JTAGjet:
1. Insert the Signum Systems CD-ROM into your CD drive.
2. Plug the JTAGjet into the USB port.
Normally, MS Windows detects and installs the required driver automatically. If the OS cannot find the
driver, direct it to the SigUSB.sys (SigUSB98.sys on Win98) file in the root folder of the Signum
Systems CD-ROM. The latest USB driver version is also available from the Download page at
www.signum.com.
For information on troubleshooting the USB driver installation process, refer to the “USB 2.0 Driver for
JTAGjet and ADM51” installation instructions on the Signum Systems Technical Documentation web
page at www.signum.com/tecdoc.htm.
6.3.3 Installing the RDI driver for third party debuggers
For instructions on installing the RDI driver for use with software tools other than those from
Raisonance or Signum Systems, see “RDI Drivers for Third Party Debuggers with JTAGjet & RLink”
installation instructions on the Signum Systems Technical Documentation web page at
www.signum.com/tecdoc.htm. The procedure incorporates the installation of the USB driver.
6.3.4 Using the JTAGJet/STR9 trace features (ETM) in Ride7
To use the trace capability of the STR9 with JTAGJet, you should use the ETM connector instead of
the 20-pin JTAG connector. See the ARM documentation for more information. You need a JTAGJet-
trace (not all JTAGJets can perform ETM tracing) and a target board featuring the ETM connector.
The programming and debugging interfaces are the same as with the RLink or the standard JTAGJet,
but, once the debug session has started, you will find additional commands in the menu Debug >
JTAGJet.
If you are using the REva board with an ETM connector, you MUST remove the enable jumpers for
LEDs D4, D5, D6 and D7, because they would interfere with the trace signals. These 4 LEDs cannot be
used by the application while using the trace.
• The JTAGJet trace window: Selecting option Open Trace Window enables trace and opens the
associated window. Refer to the Signum's Chameleon documentation for more information.
• The trace I/O configuration: The trace uses more pins than the simple JTAG debugging. See the
ARM documentation for more information. These pins must be configured correctly for trace to
work, and the user (debugged) application must not change this configuration.
When using a JTAGJet with trace capability and an STR9 device, Ride7 configures the I/Os for
the trace as described in a script file. Then, whenever the trace is enabled, and at every
execution of some user code while the trace is enabled, it checks if the configuration has not
been broken by the application. If it has, Ride7 notifies you and ask you if you want it to restore
the configuration for trace, or if you want to disable the trace. If you choose to restore the trace
settings, then Ride7 reconfigures the I/Os according to the data in the script file. This could
affect your application’s behavior.
The script is located in <Ride installation directory>\bin\STR9_ETM_IO_conf.txt. It is designed
for the STR9 REva daughterboard, but can be modified for other boards. It consists of a list of
entries containing Address, Value, InitMask and CheckMask. At reset, Ride7 writes the Value of
each entry at the associated Address, masked using the associated InitMask. When enabling
the trace or after some user code execution, Ride7 checks the value in the target device at each
entry’s Address against the associated Value, masked using the associated CheckMask.
Masks must be used to allow the user application to use some pins other than those used by the
trace but on the same I/O port.
Note: Be very careful when modifying the script. A wrong script prevents you from using the trace, and
could prevent you from debugging at all. Always make a copy of the original script before modifying it.
Make sure you have all the necessary information about ETM from the ARM documentation to avoid any
wrong manipulation.
- 31 -