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

4. Creating a project Raisonance Tools for ARM
• For the STR75x, the RAM is physically at 0x40000000 but it is also seen at 0x00000000.
• For the STR91x, the RAM is physically at 0x04000000. The reset and interrupt vectors are
placed in the Flash and jump to some RAM addresses.
• For the STM32, the RAM is physically at 0x20000000.
• For the LPCx, the RAM is physically at 0x40000000. The reset and interrupt vectors are placed
in the Flash and jump to some RAM addresses.
In this mode, the linker places the code and data segments in the RAM and the data initialization
values in the Flash.
The final application cannot use this mode because the RAM is volatile and has to be reloaded at every
power-up of the microcontroller. It can be used during debugging because Ride7 is able to load the
RAM at the beginning of every debug session. The constants and the initialization values for the global
variables are still stored in the Flash. Therefore, do not be surprised if Ride7 has to erase and program
the Flash when starting a debug session in RAM mode.
4.3.3 External memory mode
Use of this mode depends on the microcontroller and is for experienced users only, you must consult
the relevant datasheet for details. You can still use Ride7 as a project manager and software simulator,
but you cannot debug or program. It uses external memory for booting, the target external memory
space is seen at address 0. RLinks and JTAGjet do not work in this mode.
4.4 GNU GCC toolchain configuration
Ride7 Options Manager (Options > Project Properties) provides the most important options needed
to configure the GCC toolchain. The GNU options are separated into 3 sections:
• GCC Compiler
• AS Assembler
• LD Linker
Only the sections that apply to the selected project node and its children are displayed, for example:
• If a C source file is selected, only GCC Compiler section is visible
• If the application or project node is selected, all three sections are visible
Note: When you modify options on a child node (most probably a source file), you create a superset of
local options for this node and its children. If you want to globally modify an option (this is the case most
of the time), do not forget to verify that the application node is selected, and not a child node.
4.4.1 Compiler and Assembler options
Refer to the tools specific documentation for a detailed description of the GCC Compiler and
Assembler options.
As Ride7 provides additional libraries this is explained in more detail here.
- 16 -