To configure the launch configuration for the ColdFire V2-V4 targets:
- In the CodeWarrior Projects view, right-click the project and select Debug As > Debug Configurations from the context menu.
The Debug Configurations dialog box appears.
- In the Debug Configurations dialog box, expand the CodeWarrior Download configuration in the tree structure on the left, and select the launch configuration corresponding to the project you are using. For example, select proj-cfv2_RAM_PnE U-MultiLink.
To configure the launch configuration for the measurement of data:
- Click the Trace and Profile tab.
- Check the Enable Trace and Profile checkbox.
The table below describes the various Trace and Profile options for ColdFire V2-V4 targets.
| Group | Option | Description |
|---|---|---|
| Enable Trace and Profile | Enables tracing and profiling for the application. | |
| User Options | Keep all trace buffers | Lets you keep all the data received from the probe. On Coldfire V2-V4 targets, you can collect trace with external buffer only using Tracelink probes. The Tracelink (or multilink trace) probes cannot collect trace continuously, but they have a very large buffer. So suspending the application repeatedly with this option enabled will append the trace buffers, as if each buffer was collected alone, resulting in a very large trace collection. |
| Enable Logging | Creates a log file that keeps details of the actions that took place in the application. For example, when the debug session terminated, when the target execution resumed or stopped. | |
| Target Configuration | Target PC Address | Specifies the number of bytes that the trace hardware uses to store the addresses in the raw trace. The value is currently fixed at 4 bytes. |
| Trace data values | Read Data | Traces the values of data operands being read from the memory. |
| Write Data | Traces the values of data operands being written to the memory. |