<< Chapter < Page Chapter >> Page >

Introduction to debug with cce

TI’s debugger generates an output file as a result of building the project. To debug a project after a build, it is only necessary to perform the following steps:

1. Select the project as active, or click Run>Debug Active Project . The debug perspective is open and it is possible to debug the code;

2. This resets and suspends the execution of code on the device. Running this command, the content of all status registers is modified to the power-up state defaults in accordance with the device specifications. The reset command is enabled by > Reset CPU ;

3. To start a program execution, once loaded into the device's memory, select the option Run>Run (F8). Program execution will take place until the program finds a breakpoint;

4. The program execution may be suspended at any time by using the command Run>Halt ;

5. To re-start the execution of the application use the command Run>Restart . This action does not modify the execution stage of the device. It only restores the PC to the application’s starting point loaded into memory;

6. The Set PC to Cursor feature moves the execution of the application to a particular point in program memory. The execution of this command only modifies the contents of the PC register. No instruction will be executed in order to reach this point. The command can be found in the context menu of the C/C++ perspective in Set PC to Cursor ;

7. There are several different ways to run the code until a specific point:

- Use a breakpoint to specify that when this point is reached the program execution must be halted;

- Use the command Run>Run to Line, available in the context menu of C/C++ perspective, to run the code until the specified location;

8. A special case is to run the code until the main function is reached. This feature enables a temporary breakpoint at the beginning of the main routine and starts the execution of the application. The breakpoint is removed and execution is suspended once the location is reached. This command provides a convenient method of starting C applications.

9. The stepping commands execute each instruction step-by-step. When a function is called, it is possible to move the execution to the function (step into) or perform the function and pass to the following instruction (step over). Once inside a function, the user can continue to execute each instruction individually, or run the rest of the function code until it ends (step out);

10. The execution of the next instruction is performed through Run>Step Into (F5). The next instruction is executed when this command is used. If the next statement is a function call, the debugger passes the execution to the first instruction of the function, and suspends execution at this point;

11. When the execution is on top of a function call, the step over operation can be enabled by selecting the Run>Step Over (F6). The debugger then performs the function and then suspends execution when it returns. If it finds a breakpoint somewhere in the function, the execution may be suspended at this point. If the Step Over is executed on an instruction that is not a function call, the debugger response will be the same as Step Into command;

Get Jobilize Job Search Mobile App in your pocket Now!

Get it on Google Play Download on the App Store Now




Source:  OpenStax, Teaching and classroom laboratories based on the “ez430” and "experimenter's board" msp430 microcontroller platforms and code composer essentials. OpenStax CNX. May 19, 2009 Download for free at http://cnx.org/content/col10706/1.3
Google Play and the Google Play logo are trademarks of Google Inc.

Notification Switch

Would you like to follow the 'Teaching and classroom laboratories based on the “ez430” and "experimenter's board" msp430 microcontroller platforms and code composer essentials' conversation and receive update notifications?

Ask