ARM Developement Environment from Macraigor Systems LLC
This installs a full GNU cross development system on a Windows host system that already has the Cygwin Linux emulation environment. The Macraigor JTAG interface software is installed. This includes OcdLibRemote along with necessary dll\'s. These utilies act as an interface between Insight/gdb and the remote target CPU target via a Macraigor Wiggler, Raven, or mpDemon, IE:
This file, README, is installed in / (root) of the Cygwin environment.
------------------------------------------------------------------- Debugging a Target using Insight/GDB and OcdLibRemote -------------------------------------------------------------------
1) Prior to running Insight/gdb first start OcdLibRemote. You specify the target processor with the first parameter. OcdLibRemote listens to a tcp/ip port and convert incoming gdb commands to JTAG signals.
Use the following command to start OcdLibRemote using a RAVEN interconnect device on LPT1 and using tcp/ip port 8888 to receive commands from gdb. It must be run from a second cygwin "bash" shell window:
/usr/local/bin/OcdLibRemote -c <CPU type>
The OcdLibRemote takes additional OPTIONAL parameters that allow you to modify their modes of operation:
2) Start Insight (gdb with a GUI interface) or GDB (arm in this example):
/usr/local/arm/bin/arm-elf-gdb
or this command to bring up the traditional gdb command line interface :
/usr/local/arm/bin/arm-elf-gdb -nw
gdb will execute initialization commands from a file called .gdbinit when it first starts. Running arm-elf-gdb with the -nw option displays each of the commands in the .gdbinit file and their execution status. This can be useful when debugging a .gdbinit file.
The example .gdbinit file included in this directory sets up gdb to control an Evalulation board using OcdLibRemote via tcp/ip port localhost:8888. It resets the board to initialize it\'s system configuration registers. Alternatively you could execute a series of "monitor char | short | long <address> = <value>" commands to setup the target CPU\'s memory mapped configuration registers. ("monitor help" will give you a full list of LibRemote\'s monitor commands) commands) It then loads "test" (the Elf format file created by make) into target RAM on the board
------------------------------------------------------------------- Some useful commands to to use with OCDemon arm-elf-gdb ------------------------------------------------------------------- monitor reset - reset CPU
monitor resetrun - reset CPU then start execution automatically
monitor halt - stops the CPU
monitor runfrom - <address> - starts CPU running starting at <address>
monitor reg - displays additional ARM registers
monitor hbreak set <address> | clear - controls the hardware breakpoint
monitor endian <big/little> - sets big or little endian for short/long command\'s <value>
monitor char <address> = <value> monitor short <address> = <value> monitor long <address> = <value> - writes a 8/16/32 bit value directly to the CPU\'s memory. This command is typically used in a .gdbinit file to setup the target CPU\'s memory mapped configuration registers prior to starting a gdb session. monitor help displays the monitor commands available from OcdLibRemote
s Step, single step a C source code line.
si Step Instruction, single step a machine code instruction.
c Continue, run the processor after a step or breakpoint.
b Breakpoint, set a breakpoint at specified location.
^C Control C, stop execution from the keyboard.
l List, show the source code being executed.
x Examine, show the contents of memory.
i r Info registers, show the contents of all registers.
set Set, change the contents of ram or a register.
The "run" command is not useful for a remotely connected target, you should use the "continue" command to cause the program to run even from the begining.
If you use Insight GUI the monitor commands can be executed from a command window, all the other commands are available using the pull downs or buttons.
Some target processors cannot run at full JTAG speed. This will generally be indicated by the failure of the "target" command. The selectable speed range is 1 thru 8. The JTAG speed is the last parameter in the invocation line of OcdLibRemote. The default speed is 1 which is the fastest.
2) gdb fails to attach to OcdLibRemote;
GDB/Insight communicates through a daemon called OcdLibRemote which resides in /usr/local/bin. This daemon communicates through IP port 8888 by default. You can start it by entering the following command;
/usr/local/arm/OcdLibRemote -c <CPU type>
GDB should be able to attach to the daemon now.
3) Wiggler/template/JTAG DLLs not installed:
The Macraigor interface devices that use the parallel port depend on the presence of serveral dynamic link libraries (DLLs). These DLLs should be installed as:
