0% found this document useful (0 votes)
2 views1 page

Using JTAG With The UCD3138 Using The CCS JTAG Debugger - Transcript

The CCS JTAG debugger allows users to step through programs, set breakpoints, and view memory and registers. To use it, connect to the target device, load the appropriate symbols, and utilize various controls for execution and debugging. Users can also view memory allocation and manage breakpoints through the interface.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views1 page

Using JTAG With The UCD3138 Using The CCS JTAG Debugger - Transcript

The CCS JTAG debugger allows users to step through programs, set breakpoints, and view memory and registers. To use it, connect to the target device, load the appropriate symbols, and utilize various controls for execution and debugging. Users can also view memory allocation and manage breakpoints through the interface.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Now, I will give a brief demonstration of the CCS JTAG debugger.

This allows you to


step through the program, set breakpoints, interrogate memory, and so on. For the
debugger to run correctly, the code should already be executing. Here, I take a
device that has just been programmed and use the PMBus device GUI to start code
execution.

In CCS, open the appropriate configuration and connect to the target via the JTAG
emulator. Now, you need to load the symbols associated with the code executing on
the device. Select Run, Load, Load Symbols. And select the .out file that matches
the code that is executing on the UCD device.

You should now see the see source code corresponding to the location of the program
counter in the ARM core. To resume execution, click on the Resume button on the
task bar, or press F8. To pause execution, click on the Suspend button on the task
bar, our press ALT and F8 together. To stop, click the Stop button.

There are also buttons for Step Into, which single-steps the program and keeps
descending down the program hierarchy, if able to do so, Step Over, which single-
steps the program counter, while remaining at the current hierarchy level, and Step
Return, which steps up to the next highest level of program hierarchy. All of these
have short keys, which can be seen when you hover your mouse over the task bar
buttons.

To set a breakpoint, the processor must be halted. Right-click on the line at which
you want to set the breakpoint, select Breakpoint, Code Composer Studio, Hardware
Breakpoint. Resume execution, and the program counter will stop at the breakpoint.

To view the contents of memory, select View, Memory, Browser. For example, to view
the contents at address 0, type 0 into the Address field. Here is the contents at
address 0. Here is the contents at address 4. Here is the contents at address 8, at
address [? C, ?] at address 10, and so on.

To view the contents of the registers, click View, Registers. Here are the ARM core
registers. To view global variables, click View, Variables. To view the code at the
assembler level, click View, Disassembly. Here, I'm stepping through the code at
the assembler level.

Click View, Breakpoints, to see the breakpoints. Right-click on a breakpoint, and


select Remove to delete it. To view how the memory is allocated, click View,
Memory, Allocation. Here, you can see that 13% of the program flash, or 4350 bytes,
are being used to store this particular program.

You might also like