Template:HowTo
This guide will walk you through connecting the {{{{{1}}}_PRODUCTLINK}} and the {{{{{2}}}_PRODUCTLINK}} to your Linux PC, and installing and running OpenOCD. This guide was written with Ubuntu 10.04.
{{{{{1}}}_{{{2}}}_CONNECT}}
{{{{{1}}}_{{{2}}}_COMPILEOCD|{{{1}}}|{{{2}}}}}
Contents
Running OpenOCD
Now you are ready to run OpenOCD. If you installed the OpenOCD Ubuntu package, open a terminal window and type the following from any directory:
openocd {{{{{1}}}_CFGRELPATH}} {{{{{2}}}_CFGRELPATH}}
If you compiled OpenOCD yourself, navigate to the openocd-bin directory you created in the compile guide and type:
cd ~/openocd-bin sudo ./openocd {{{{{1}}}_CFGRELPATH}} {{{{{2}}}_CFGRELPATH}}
{{{{{2}}}_RUNOCDBRIEF|{{{1}}}}}
Telnet Connection
You cannot enter commands directly to OpenOCD. Open a new terminal window and type:
telnet localhost 4444
You will should see this prompt:
You can give commands to OpenOCD through this prompt.
Common OpenOCD Commands
To see a full list of OpenOCD commands, enter help in the telnet window.
reset
Resets the {{{{{2}}}_DEVICENAME}}. The output of the Reset command should look like this:
{{{{{2}}}_IMG_OCDRESET}}
halt
Sends a halt request to the {{{{{2}}}_DEVICENAME}}. If the {{{{{2}}}_DEVICENAME}} halts, you will see text output in the telnet window. (If the {{{{{2}}}_DEVICENAME}} is already halted, you will see no output.)
{{{{{2}}}_IMG_OCDHALT}}
halt [timeout]
You can also use halt followed by a time in milliseconds. OpenOCD waits for the target to halt the specified amount of time, then gives up if the target has not halted. You can use this to avoid OpenOCD hanging because the {{{{{2}}}_DEVICENAME}} fails to halt. For example, to send a halt command with a timeout of one second, type:
halt 1000
resume
Enter resume to end a halt. You will not see any text output in the telnet window.
reg
Displays a numbered list of all of the {{{{{2}}}_DEVICENAME}}'s registers.
{{{{{2}}}_IMG_OCDREG}}
reg [entry]
Run reg with a register number to display the contents of a register, in hexadecimal. The register number corresponds to the output of the reg command with no arguments, above. You must run the halt command before reading registers.
{{{{{2}}}_IMG_OCDREG0}}
If you run reg while the {{{{{2}}}_DEVICENAME}} is not halted, you will still see the value stored in the register. However, registers change contents very quickly while the device is running; by the time you see the value, the value actually in the register may be different. If you try to run reg while the device is not halted, you will see this:
{{{{{2}}}_IMG_OCDREGNOTHALTED}}
reg [entry] [value]
Sets the value of a register. The register number corresponds to the output of the reg command with no arguments, above. Make sure the {{{{{2}}}_DEVICENAME}} is halted (with the halt command) before you change the value of a register!
You can enter registry values in either decimal, by typing a number by itself, or in hexadecimal, by prefacing the value with 0x.
{{{{{2}}}_IMG_OCDREGSET}}
GDB Debugger
GDB, the GNU Project Debugger is a debugging tool provided with the GNU Compiler Collection (GCC). GDB allows you to stop and start a running program, examine its functioning, and make changes. GDB is installed on Ubuntu 10.04 by default, but you will need a different version of GDB build for embedded targets. Follow the instructions on the GDB Debugger page below.
The GDB debugger page will walk you through installing GDB for use with OpenOCD, and loading and testing a simple program.