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
The Ride7 environment should look like this:
• Boot Mode option (visible in the Advanced ARM Options) determines the memory space
containing the image of the code that the target executes after a reset.
You can select FLASH, RAM, or External Memory. For information about boot modes, refer to
your device datasheet and the section Boot mode choices. For your first try, choose FLASH.
• Use Thumb Mode option allows you to choose between the Thumb or ARM modes, for ARM7
and ARM9 devices. See the device datasheet for more information. Thumb2 mode is
automatically selected when using a Cortex-M3 device.
• Enable Interwork option allows you to select a different ARM/Thumb mode for each source file
of the project (this option is not valid on Cortex microcontrollers).
You are now ready to add files to the project, build and debug it as explained in the Ride7 manual
(common to all targets). Click Help > View Documentation to see it.
You can also change the GNU configuration, to use the Ride7 libraries for example, as explained in
section 4.4.
- 12 -