User manual

6. Debugging with hardware tools Raisonance Tools for ARM
• Speed of the JTAG clock: specifies the clock speed.
If your CPU’s clock is slow, then you must tell Ride7 to use a slow JTAG clock. If the JTAG
clock is too fast compared with the target CPU’s clock, then communication fails. This section of
the debugging options allows you to specify the JTAG clock speed:
Reducing the JTAG clock does not have very much influence on the programming and
debugging speed because the USB is the bottleneck for most operations. Therefore, don’t be
afraid to use this option and enter the value of your target’s clock speed in KHz.
Note: The RLink clock has a limited number of possible clock speeds. Ride7 selects the closest possible
value that is less than the value you required. The minimum value is 400KHz. If your clock is slower than
this, RLink might not be able to program and/or debug it. You must then purchase JTAGjet, or develop
your application using a faster clock.
6.2.3 Hints and troubleshooting
6.2.3.1 Example projects
The examples in the REva folder of the Ride7 directory are configured for use with the REva
evaluation board, which includes the RLink. For standard installations they are found at
<Ride>\EXAMPLES\ARM\REva. These examples can also be used with other demonstration and
evaluation boards with a standard JTAG connector and the RLink. Before using an example, look at it
and make sure that the jumpers on the REva evaluation board are set correctly (Enable switches for
the LEDs, buttons, SCI, EEPROM, etc). Usually, there is some important information in comments at
the beginning of the main file (I.e. the file that contains the "main" function).
The examples in the Primer folder of the Ride7 directory are configured for use with the Primer
evaluation boards, such as the STM32-Primer, which includes the RLink. For standard installations
they are found at:
<Ride>\EXAMPLES\ARM\Primer(\STM32).
These examples can also be used with other demonstration and evaluation boards with a standard
JTAG connector and the RLink. Usually, there is some important information in comments at the
beginning of the main file (I.e. the file that contains the "main" function).
6.2.3.2 Testing USB driver, connections and power supplies
Connect to RLink tests the USB driver installation and RLink operation. The RLink appears in
Windows' device manager under the Jungo section when it is correctly recognized.
Check connection to target tests the connections and power of the target board and ARM CPU. This
operation requires RLink to connect to the target ARM, ensuring that it is powered, correctly connected
to RLink, and that the rest of the application board does not interfere with the communication between
RLink and the ARM CPU (see below). It also checks that the target CPU is of the correct type.
6.3 JTAGjet programming and debugging features
Ride7 for ARM supports the JTAGjet emulator from Signum Systems Corp. Even though very similar in
concept and usage, the JTAGjet is considerably faster than the RLink and offers a real-time trace
(ETM) capability.
The user interface and advanced options for both emulators are the same and have the same
functions.
JTAGjet is allowed full access to the STRx. This means that it can be used for programming and
debugging, in Flash or in RAM, without limitation.
6.3.1 Signum Systems USB driver installation
The JTAGjet emulator requires installation of the Signum Systems USB driver. The installation process
differs depending on whether you work in the Ride7 environment or use a third party debugger. In both
instances, the driver is the same. The required driver files are on the CD-ROM disk that comes with the
JTAGjet.
- 30 -