Configure ColdFire V1 Target

To configure the launch configuration for the ColdFire V1 target:

  1. 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.

  2. 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-CFV1_FLASH_PnE U-MultiLink.
  3. On the Main tab page, verify that proj-CFV1 is displayed in the Project field. If it does not appear, click Browse and locate the project.
  4. If the application is not displayed in the Application field, click Search Project to select the application image.
    Figure 1. Debug Configurations - Main Page
    Debug Configurations - Main Page

To configure the launch configuration for measurement of data:

  1. Click the Trace and Profile tab.
  2. Check the Enable Trace and Profile checkbox to enable the disabled options on the page.
    Figure 2. Debug Configurations - Trace and Profile Page (ColdFire V1)
    Debug Configurations - Trace and Profile Page (ColdFire V1)

The table below describes the various Trace and Profile options.

Table 1. Trace and Profile Options for ColdFire V1
Group Options Descriptions
User Options 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.
  Configuration Set in User Code When checked, lets you configure trace registers from the application without using the Trace and Profile page. In this scenario, you can write the appropriate registers in the source code to configure the trace mode and triggers.

To understand how to configure trace registers in the application for the ColdFire V1 target, refer Configuring Trace Registers in Source Code.

Select Trace Mode Continuous When selected, collects the trace data continuously. It produces best possible trace and profile results because it captures all executed instructions. However, it is slow and intrusive as it stops the target in the background every about 500 cycles.
Automatic (One-buffer) When selected, captures only the last instructions executed before the target gets suspended. It is totally unintrusive.
Halt the Target when Trace Buffer Gets Full Appears only when the Automatic (One-Buffer) option is selected. It acts as a breakpoint for stopping the application. If selected, stops the application automatically when trace buffer gets full.
Profile-Only. Sample PC every cycles When selected, captures the PC address every N cycles, where N is 128/256/512.......16384. Trace is mostly irrelevant in this mode, but Profile Statistics will be fairly accurate for a long cyclic run. This method is a bit intrusive because it stops the target in the background every about 8*N cycles.
Expert When selected, enables the Configure Expert Settings button and lets you configure the ColdFire V1 trace and debug registers directly. To configure expert settings, download the processor specific manual from http://www.freescale.com/.
Trace Start/Stop Conditions   Includes various conditions of triggers, A, B, and C, for starting and stopping trace.

For more information, refer Conditions for Starting/Stopping Triggers.

Target PC Address 2 Bytes Select this option to save 5-30% trace-buffer space if your PC addresses never exceed 16-bits (64K). This results in less intrusiveness, or more instructions traced, depending on the trace mode you use.

This feature is not supported for the Expert trace mode.

3 Bytes Select this default and recommended option if the PC address length in your program exceeds 16-bits (64K).

This feature is not supported for the Expert trace mode.

Trace data values Read Data Traces the values of data operands being read from the memory.

This feature is not supported for the Profile-Only and Expert trace modes.

Write Data Traces the values of data operands being written to the memory.

This feature is not supported for the Profile-Only and Expert trace modes.