Configure DSC Target

To configure the launch configuration for the DSC target:

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-dsc_FLASH_SDM_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.
Figure 1. Trace and Profile Tab Options of DSC

The table below describes the various Trace and Profile options for DSC target.

Table 1. Trace and Profile Options for DSC
Group	Option	Description
Enable Trace and Profile		Enables trace and profiling for the DSC application.
Enable Data Visualization		Enables data visualization. Data Visualization and tracing cannot be used simultaneously. For details, refer Data Visualization.
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.
Select Trace Mode	Continuous	When selected, collects the trace data continuously.
Select Trace Mode	Automatic (One-buffer)	When selected, captures only the last instructions executed before the target gets suspended.
Collect Trace		Collects trace with any of the following trigger conditions selected: Always — captures all executed instructions in the application From Trigger A Onward — starts trace collection from where trigger A is set in the application From Trigger B Onward — starts trace collection from where trigger B is set in the application Until Trigger A — collects trace till Trigger A is set in the application Until Trigger B — collects trace till Trigger B is set in the application

Note: On DSC platform, breakpoints and triggers are mutually exclusive. You may use only breakpoints or only triggers but never both during debugging a DSC application.

Note: The triggers set on the DSC target work on program prefetch and not on the program execution. Therefore, triggering occurs a bit earlier than the execution of the instruction on which the trigger has been set. To prevent this, if you don’t have sequential instructions (statements) before the line where you want to set a trigger, you can set it in the Disassembly view on the instructions following one or two sequential instructions so that beginning of the trace is not affected.

Note: The DSC hardware traces destinations for only a subset of the change of flow instructions (please see the EOnCE manual, section "11.6.1 Trace Buffer Control Register"). Indirect change of flow instructions, such as returns (rts), indirect calls (such as JSR R0), and some direct branches (such as BRA) are not traced. As a result, in some cases, the trace data collected for a DSC project may contain <no debug info> when a return address cannot be estimated, or entire functions may be missing when they are called by a return or a indirect call. Also, collecting data in the automatic mode or setting triggers in the middle of the program may result into more returns than calls, which makes processing break and display <no debug info> instead of an address or "Break in trace!" messages in the collected trace data. Because of the above limitations, the Call Tree and Performance hyperlinks do not appear in the Software Analysis view for DSC applications.