From the Disassembly View

To set a trigger in the Disassembly view:

1. In the CodeWarrior Projects view, expand the Sources folder of your project.
2. Double-click the source file, for example, main.c to display its contents in the editor area. Replace the source code in the main.c file with the source code shown below.
   Listing: Source code 3

   #include <hidef.h> /* for EnableInterrupts macro */
   #include "derivative.h" /* include peripheral declarations */
   
   volatile int a, b, i;
   
   void f(){}
   
   void f1()
   {
     b=1;
     b=2;
     b=3;
   }
   
   void f2()
   {
     a=1;
     a=2;
     a=3;
   }
   
   void main(void)
   {
     EnableInterrupts;
     /* include your code here */
     for(i=1;i<10;i++)
     {
       f();
     }
   
     f2();
     
     for(;;)
     {
       __RESET_WATCHDOG(); /* feeds the dog */
       f1();
       f2();
     } /* loop forever */
   }
   

3. Save and build the project.
4. Open the Debug Configurations dialog box, and select your project in the tree structure.
5. Click the Trace and Profile tab, and check the Enable Trace and Profile checkbox.
6. Select the Collect Program Trace option in the Trace Mode Options group.
7. Select the Automatically option.
8. Select the Collect Trace From Trigger in the Trace Start/Stop Conditions group.
9. Check the Break on FIFO Full checkbox.
10. Select the Instruction at Address A is Executed option from the Trigger Type drop-down list.
11. Click Apply to save the settings.
12. Click Debug to debug the application.
13. In the Disassembly view, right-click the marker bar corresponding to the address line of the function, f2() before _RESET_WATCHDOG().
    Figure 1. Disassembly View
    
    
14. Select Trace Triggers > Toggle Trace Trigger A from the context menu.

    The trigger icon, A appears in green color on the marker bar, in the editor area and the Disassembly view.

15. Click Resume to continue collecting trace.
    Note: Because you selected the Break on FIFO Full check box in the Trace and Profile tab, the application will stop automatically after the trigger hit. You do not need to stop it manually by clicking Suspend.
16. Open the Trace Data viewer following the steps explained in the topic Viewing Data to view the collected data.

The figure below shows the data files and the timeline graph that is generated by the application in which the data has been collected after setting trigger A. You can see Figure 3 to view the data files that are generated before setting tracepoints. The Trace Data viewer in the figure below shows that trace starts collecting from where you set the trigger, and when the trace buffer gets full, the application stops collecting trace. That is, application starts collecting trace from f2() as highlighted in the figure, and continues till buffer trace gets full.

Figure 2. Trace Data After Setting From Trigger in Automatically Mode