OpenOCD Config Files

This page contains OpenOCD config files created by TinCanTools. OpenOCD reads config files to configure itself for different hardware. OpenOCD is packaged with config files for many devices; the files on this page add support for new devices or replacements for obsolete config files.

=Installing Config Files=

To download a config file from this page, right-click the link and select "Save As." Save the file somewhere in OpenOCD's search path. If you're not sure what directories OpenOCD searches and you compiled OpenOCD yourself, save the config file to the same directory as your OpenOCD executable. If you have installed the OpenOCD Ubuntu Package, save the config file to \usr\local\share\openocd\scripts.

You can run OpenOCD with the script like this:

openocd -f yourconfigfile.cfg -f yourotherfile.cfg

By convention, config files for processors go in a folder called /target, files for target boards go in /board, and files for interface devices go in /interface. Many config files for boards search in \target for the file for their processor, so always save files for processor to /target. You aren't required to save your config files to \interface or /board, but it may help you keep your files organized. Just remember to include the folder in the file path when you run OpenOCD:

openocd -f interface/yourconfigfile.cfg -f board/yourotherfile.cfg

For a more in-depth discussion of how to use config files and how OpenOCD searches for them, see OpenOCD Config File Paths.

=Flyswatter Config Files=

These files add support for different versions of the TinCanTools Flyswatter. Flyswatter config files usually go in the OpenOCD's /interface folder, although this is not required.

[[Media:flyswatter2.cfg|flyswatter2.cfg]]
This is the config file for the TinCanTools Flyswatter2. OpenOCD does not currently support the Flyswatter2; you will need to compile OpenOCD yourself to use it with the Flyswatter2. This file is included in the OpenOCD 0.5.0 Patch and the OpenOCD 0.4.0 Flyswatter 2/3 Patch.

Full text of flyswatter2.cfg:

[[Media:flyswatter.cfg|flyswatter.cfg]] with JTAG Clock Speed
This file replaces flyswatter.cfg for the original Flyswatter. The new file sets the JTAG clock speed. This is required for OpenOCD 0.5.0 or any build based on OpenOCD 0.4.0 development code. It is not required for the 0.4.0 release. This file is included in the OpenOCD 0.5.0 Patch.

This file uses the jtag_khz command rather than the new adapter_khz command for compatibility with OpenOCD-0.4.0.

Full text of flyswatter.cfg:

=Board Config Files=

These files add support for different target boards. Board config files usually go in the OpenOCD's /board folder, although this is not required.

[[Media:hammer.cfg|hammer.cfg]]
This is the config file for the TinCanTools board. This is file replaces the hammer.cfg file provided with OpenOCD. It corrects the JTAG Tap Unexpected error with the old hammer.cfg by correctly setting the JTAG tap ID. This file is included in the OpenOCD 0.5.0 Patch.

Full text of hammer.cfg:

[[Media:olimex_pic32mx.cfg|olimex_pic32mx.cfg]]
This is the config file for the. This very short file sets the JTAG clock speed and tap ID for the board, then calls the config file for the CPU. The CPU config file target/pic32mx.cfg is provided with OpenOCD. This file is included in the OpenOCD 0.5.0 Patch and the OpenOCD 0.4.0 Flyswatter 2/3 Patch.

This file should be used in place of the pic-p32mx.cfg file provided with OpenOCD.

Full text of olimex_pic32mx.cfg:

=Target Config Files=

Target config files must go in a folder called /target somewhere in OpenOCD's search path.

[[Media:amdm37x.cfg|amdm37x.cfg]]
This is the config file for the am37x and dm37x processors, used with the in the Flyswatter2 Beagleboard XM How To. This file is almost identical to the [[Media:amdm37x_orig.cfg |original amdm37x.cfg file]] provided with OpenOCD 0.5.0. The only change is to line 32, to support JTAG TAP id 0x2b89102f. This file is included in the OpenOCD 0.5.0 Patch v0.12.

[[Media:omap3530_norclk.cfg|omap3530_norclk.cfg]]
OpenOCD sometimes has issues initializing the Beagleboard's JTAG with the Flyswatter2 adaptive clocking enabled. Adaptive clocking is enabled in the config file omap3530.cfg, called from ti_beagleboard.cfg. This is a modified config file that doesn't enable adaptive clocking. This file is intended only for use with the Beagleboard. For more information, see Beagleboard Troubleshooting: JTAG Tap Unexpected 0x000000ff.