This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
openocd:start [2018/08/24 14:53] – mgehrig2 | openocd:start [2021/01/14 16:37] (current) – [OpenOCD] ursgraf | ||
---|---|---|---|
Line 2: | Line 2: | ||
OpenOCD is the software part of a debugger. Together with a hardware adapter | OpenOCD is the software part of a debugger. Together with a hardware adapter | ||
OpenOCD is a complete debugger and can be used as a replacement for an expensive debugger such as the BDI3000 from Abatron. | OpenOCD is a complete debugger and can be used as a replacement for an expensive debugger such as the BDI3000 from Abatron. | ||
+ | * [[: | ||
+ | * [[openocd: | ||
+ | * [[openocd: | ||
- | The adapter forms the electrical interface to the processor and must also be matched to the processor. The adapter is already integrated on the Zybo board. | + | The hardware |
- | To install | + | ===== The OpenOCD |
+ | OpenOCD starts running as a server and waits for connections from clients (telnet, GDB) and processes the commands issued through those channels. OpenOCD will launch the GDB and telnet server even if it cannot establish a connection with the target. In general, it is possible for the JTAG controller to be unresponsive until the target is set up correctly via e.g. GDB monitor commands in a GDB init script. | ||
+ | ==== Using Telnet Connection ==== | ||
+ | [{{: | ||
- | ===== The OpenOCD-toolchain ===== | + | Make sure to have the necessary plugin installed, see [[:installation# |
- | {{:openocd: | + | |
- | //Picture 1: The OpenOCD-toolchain// | + | |
- | The same graphical debugger interface can be used with the OpenOCD toolchain as with the PowerPC and the BDI-3000. OpenOCD and the FT2232 on the Zybo take over the function of the BDI-3000. | ||
- | The Eclipse Plugin can be downloaded from [[https://github.com/MarcelGehrig/openOCDInterface.git | this ]] repository. This toolchain can also be used to download a compiled deep application to the ARM target. | + | ===== Using GDB Connection ===== |
+ | [{{:openocd:gdbopenocdtoolchain.png|//OpenOCD toolchain using GDB connection//}}] | ||
- | To use this toolchain, OpenOCD | + | This toolchain |
+ | === Installation of the GDB === | ||
+ | The "GNU Arm Embedded Toolchain" | ||
- | ===== The gdb-OpenOCD-toolchain ===== | + | === How to Use the GDB === |
- | {{:openocd: | + | [[.:how_to_use_gdb|Using the GDB with deep]] |
- | //Picture 2: The gdb-toolchain// | + | |
- | This toolchain uses OpenOCD in combination with the GNU debugger, the gdb. | ||
- | The gdb can be used to load a deep application onto the target if it has been packed in an ELF format. | ||
- | |||
- | If debug information in STABS or DWARF format is also provided, the debugger can also be used to debug the deep application directly to the target. | ||
- | |||
- | More information under [[.: | ||
- | |||
- | To use this toolchain, [[openocd: | ||