Next: , Previous: About, Up: Top


1 OpenOCD Developer Resources

If you are interested in improving the state of OpenOCD's debugging and testing support, new contributions will be welcome. Motivated developers can produce new target, flash or interface drivers, improve the documentation, as well as more conventional bug fixes and enhancements.

The resources in this chapter are available for developers wishing to explore or expand the OpenOCD source code.

1.1 OpenOCD Subversion Repository

The “Building From Source” section provides instructions to retrieve and and build the latest version of the OpenOCD source code. See Building OpenOCD.

Developers that want to contribute patches to the OpenOCD system are strongly encouraged to base their work off of the most recent trunk revision. Patches created against older versions may require additional work from their submitter in order to be updated for newer releases.

1.2 Doxygen Developer Manual

During the development of the 0.2.0 release, the OpenOCD project began providing a Doxygen reference manual. This document contains more technical information about the software internals, development processes, and similar documentation:

http://openocd.berlios.de/doc/doxygen/index.html

This document is a work-in-progress, but contributions would be welcome to fill in the gaps. All of the source files are provided in-tree, listed in the Doxyfile configuration in the top of the repository trunk.

1.3 OpenOCD Developer Mailing List

The OpenOCD Developer Mailing List provides the primary means of communication between developers:

https://lists.berlios.de/mailman/listinfo/openocd-development

All drivers developers are enouraged to also subscribe to the list of SVN commits to keep pace with the ongoing changes:

https://lists.berlios.de/mailman/listinfo/openocd-svn