User manual
Table Of Contents
- 1. Introduction
- 2. Raisonance tools for ARM overview
- 3. How to register the new Raisonance tools for ARM
- 4. Creating a project
- 5. Debugging with the simulator
- 6. Debugging with hardware tools
- 6.1 Selecting hardware debugging tools
- 6.2 RLink-ARM programming and debugging features
- 6.3 JTAGjet programming and debugging features
- 6.4 Cortex Serial Wire Viewer (SWV) debugging features (Open4 RLink only)
- 6.4.1 Introduction
- 6.4.2 Hardware requirements
- 6.4.3 Configure Ride7 to use the SWV
- 6.4.4 Modify your application to use SWV software traces
- 6.4.5 Configure Ride7 to use SWV software traces
- 6.4.6 Configuring Ride7 to use the SWV hardware traces
- 6.4.7 Configuring Ride7 to use the SWV watchpoint traces
- 6.4.8 Start / Stop the trace
- 6.4.9 Visualizing SWV traces with Ride7
- 7. Raisonance solutions for ARM upgrades
- 8. Conformity
- 9. Glossary
- 10. Index
- 11. History

Raisonance Tools for ARM 6. Debugging with hardware tools
6.2.2.3 Instant actions
This allows you to carry out various instant actions without leaving this dialog box - useful for testing
connections and retrieving information from the RLink and your ARM, and for programming the ARM
and its configuration.
• View RLink REva jumpers configuration for ARM shows how you must set the jumpers on
RLink for using it for programming and debugging ARM. You must be sure that the jumpers are
correctly set before launching a debug session, or using any of the instant actions below.
• Connect to RLink and read serial number is useful for checking that RLink is working and
properly connected and that the USB driver is correctly installed. It also allows you to read the
RLink serial number, which you will be asked for if you contact our support team. When Ride7
checks the RLink serial number, the resulting serial number message includes information
about your RLink’s capabilities and limitations for the currently selected target microcontroller.
• Check connection to target allows you to read the JTAG IdCode of the chip. Use this to test
the connections and power of the target ARM CPU.
• Erase target now! allows you to completely erase the target CPU's Flash (writing 0xFF).
• Write target FLASH now! programs the Flash with the current application's hex file generated
by the linker. Then, launches the execution.
• Dump target FLASH to hex file reads the contents of the Flash and writes it in a file in hex
format whose name is derived from the current application's name with the extension .hex
(<application name>.hex).
6.2.2.4 JTAG parameters
• Single Device: specifies if there are several JTAG devices chained or only one device.
The JTAG standard makes it possible to chain JTAG devices (JTAG chaining is a complex
process and should only be done if you have a good knowledge of the JTAG protocol). This
section of the debugging options allows you to configure Ride7 to access an ARM
microcontroller that is chained with other JTAG devices.
The checkbox should remain checked if there is no other device in the chain. Otherwise, you
should uncheck it and enter the four parameters that the software needs to access the correct
target in the chain. You need to know how many devices are in the chain, what order they are in,
and the size of the IR register of each of them. Then, you must tell Ride7 how many devices are
before (and after) the target in the chain. You must also tell it the sum of the lengths of the IR
registers of the devices before and after the target.
- 29 -