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
Example of trace with PC time stamp:
6.4.9.3 SWV error messages
Some error messages can occur in the Debug Output View, during an SWV session:
• SWV unknown trace received (check CPU frequency or reduce trace speed): the system
received data that it could not interpret. It may be a configuration or synchronization problem.
The SWV data flow depends on the CPU clock, so check that the CPU clock indicated in the
configuration dialog box equals the real CPU clock of your target.
If the frequency is correct, try to reduce the trace speed.
If the problem persists, stop the application for a while, and run it again.
If the problem still persists, end the debug session and restart it.
• SWV overrun: Ride7 is not able to treat all the data flow, and some data is lost. Reduce the
frequency of sending or quantity of data sent by the application software.
• SWV buffer full: the size of the acquisition buffer is limited to 100 KB. When it becomes full, this
message appears in the Debug Output View, and acquisition is stopped.
• SWV USB communication error. Please check that the dongle is connected.: some
communication errors occurred. Check the RLink connection.
Some special events can occur in the global trace view:
• Internal Cortex fifo OVERFLOW: the fifo of the CPU SWV module overruns. Reduce the
frequency of sending or quantity of data sent by the application software.
• RLink internal buffer OVERRUN: Ride7 is not able to treat all the data flow, and some data is
lost. Reduce the frequency of sending or quantity of data sent by the application software
• Unknown event: the system received data that it could not interpret. See the SWV unknown
trace received above.
6.4.9.4 SWV Limitations
Note: Remember that SWV is a low cost method for CPU tracing.
Clearly a single serial wire port cannot provide all trace information because of the high speed of the
Cortex M3 micro-controllers. In particular SWO and Ride7 are not capable of providing every program
counter value because of the high speed at which the STM32 runs.
The system is also unable to provide all exception or diagnostic counters events, depending on the
target CPU clock and the interrupt frequencies.
- 41 -