Difference between revisions of "Openocd-setup"

Revision as of 06:39, 16 April 2021

On the Linux side, openocd set up on Debian type distros follows more or less the 2021 Q1 'getting started' instructions for the toolchain needed by Oresat firmware developers. There were some small differences getting full working cross-compiling and debugging toolchain installed on an Ubuntu 20.04 LTS system, to be documented here soon. One of the more difficult pieces was to obtain a version of arm-none-eabi-gcc which did not produce warnings about a known bug with ticket in the 86000 range.

Alternately on Windows 10 hosts, a similar toolchain can be installed via the following steps, and not strictly in the order of these steps:

• install 'Git for Windows', provides 'gitbash'
• install arm-none-eabi-gcc toolchain

  ( https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads )

• install chocolatey package manager for Windows
• install GNU 'make' for Windows ( https://community.chocolatey.org/packages/make )
• install openocd

Key download sites include:

https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/download
https://chocolatey.org/
https://community.chocolatey.org/packages/make
https://gnutoolchains.com/arm-eabi/openocd/

This short notes page a work in progress and more to come.

openocd use

• http://openocd.org/doc/html/Debug-Adapter-Configuration.html