How to debug using CCS?

How to debug using CCS?

In summary:

1. Switch to the CCS Debug perspective.
2. Connect to the Debug Probe.
3. Prompt for which core the program needs to be loaded (this is usually done only once if the device has multiple cores of the same ISA).
4. Automatically connect to the core/device.

How do you set a breakpoint in CCS?

Configure a Hardware Breakpoint

1. Configure CCS for a C28x target and launch a debug session.
2. In the Debug Perspective, open the breakpoint dialog from menu View → Breakpoints.
3. Use the pull-down menu to select Hardware Breakpoint.
4. In the Location field, specify the address where the breakpoint should be set.

How to work breakpoint?

Set breakpoints in source code To set a breakpoint in source code, click in the far left margin next to a line of code. You can also select the line and press F9, select Debug > Toggle Breakpoint, or right-click and select Breakpoint > Insert breakpoint. The breakpoint appears as a red dot in the left margin.

What is CC debug?

The CC Debugger is a small programmer and debugger for the TI Low Power RF System-on-Chips. It can be used together with IAR Embedded Workbench for 8051 (version 7.51A or later) for debugging and SmartRF Flash Programmer for flash programming.

What is target configuration?

Overview. The Code Composer Studio Target Configuration tool provides a way for users to create and modify target configuration (*. ccxml) files for use by the debugger. It is recommended to use the General Setup to specify a custom target when possible.

How to make CCS aware of the debug environment?

To properly make CCS aware of the physical aspects of the debugging environment, a Target Configuration File must be created. This file is populated with the appropriate Debug Probe type (XDS, ICDI or MSP-FET) and host interface (USB or Ethernet).

How does the CCS debugger split the information of an executable?

If loading an executable, the CCS debugger splits the information of the executable file: – The contents of both code and data sections are sent through JTAG and stored in the appropriate memory locations of the device/board. The placement of this code follows the directives on the Linker Command File .

How does CCS connect to the JTAG debugger?

CCS then parses the Target Configuration File, creates a Debug Configuration and uses the information in these two files to connect to the JTAG debugger and communicate to the device in the target.

Where to find debug file in Code Composer Studio?

The file can be placed in an arbitrary directory in the system. By default it is the subdirectory ti/CCSTargetConfigurations inside the user area. The location may be changed from CCS menu Window → Preferences → Code Composer Studio → Debug.