The old svn server has caused some unnecessary confusion lately and since nobody has responded to the message posted to the openocd development mailinglist as to whether there is a reason to keep it running, it will be shut down in the next few days.
The http://openocd.sourceforge.net/ git server has been the official development git repository for a few months now.
Øyvind Harboe
OpenOCD has released its first -rc packages for testing: 0.3.0-rc0.
This version has been tagged in Git as ‘v0.3.0-rc0′.
By posting these packages on SourceForge and BerliOS, we hope users will test them and report problems to this list, so the final 0.3.0 release do not have lingering issues that must be resolved with a quick 0.3.1.
Please download these packages from one of our mirrors and let us know what you think. Unless we hear reports of problems, this may be the only -rc release before we tag the final 0.3.0 and branch 0.4.0-dev.
Please take this opportunity to mention any outstanding issues, or send a work of thanks to the folks that contributed to release. Thanks!
The OpenOCD project has retired those BerliOS web site services that received insufficient attention from developers:
These steps simplify the OpenOCD infrastructure considerably, leaving the following services hosted on their systems:
The mailing list is the most reliable medium for reporting bug and feature requests to the project developers and maintainers, so we hope this action will improve the experience for all members of our community.
After a recent BerliOS service outage, the OpenOCD maintainers decided to switch the project version control system from Subversion to GIT. Development now proceeds in the GIT tree on SourceForge.net, which was created initially for the purpose of mirroring the Subversion tree. This change was made effective around 6:00pm PST on Oct 07, 2009, and this move should improve the availability of our repository. In addition to the main GIT tree on SF.net, we have created an official mirror on repo.or.cz for users behind firewalls.
The SF.net site now also provides copies of the source archives through their mirror network. Additional services may be deployed there in the future, so stay tuned for more news.
The OpenOCD Project has produced its 0.2.0 source code release. The summary of changes since the last release may be found in the NEWS file. You may download the source archives from the BerliOS website.
Beyond some new features and numerous bug fixes, this release reflects significant work by the community to clean up the code, documentation, and processes. Significantly, the 0.2.0 release served to test a nearly automated release process. That tool will help project maintainers deliver improvements and fixes to the user community more frequently and robustly.
Because the project will be producing regular releases, the maintainers hope that most users will avoid the potential build problems and instabilities that can be associated with the Subversion repository trunk. A regular cycle should encourage packaging of OpenOCD releases on more platforms and distributions, providing binaries for users on all supported systems.
Finally, the OpenOCD project will no longer distribute binary packages or installers. The OpenOCD 0.1.0 installer was removed due to licensing violations that were exposed while improving the documentation for the 0.2.0 release. These issues were discussed in depth on the mailing list, and the Software Freedom Law Center provided guidance and support for the OpenOCD community. Future GPL violations should be reported to the developer mailing list, the maintainers, or the SFLC.
We have finally got around to making our first release.
The src and binaries for this release can be found at the following url:
http://developer.berlios.de/project/showfiles.php?group_id=4148
A new section has been added to the website - Discussion
This should help users get info and help on using OpenOCD.
The OpenOCD manual is now available online in pdf and html formats - online docs
The docs are generated from the svn repository and will always relate to the latest version available.
OpenOCD is alive and well.
However, you won’t find any news here about OpenOCD. For that you have to go to the openocd development mailing list.
svn version 1000 was committed a while ago… In addition to new features such as improved scripting, new targets(MIPS particularly), there is a steady stream of patches that fix bugs and improve performance.
I’ll be cleaning up old and misleading information on this web site now…
Øyvind Harboe
It’s been over a year since I last posted to the OpenOCD website, but my posting frequency is by no means an indication of OpenOCD development activity. The mailinglist shows 184 posts for January ‘08, and we’ve already reached 87 messages within the first 11 days of februrary. The Windows binaries available from Michael Fischer were downloaded 1907 times during January. This number doesn’t include those using one of the packages available for various Linux distributions or the SVN checkouts used by users who compile the OpenOCD themselves. Thanks a lot to all OpenOCD users!
With this posting I primarily want to thank those people that keep the OpenOCD alive while I’m busy with other things.
Michael Fischer does an amazing job keeping up with all the patches that get posted on the OpenOCD mailinglist, getting new Windows binaries out on his Yagarto page, and testing all that new stuff on the boards and programmers he has access to. Thanks a lot Michael!
Øyvind Harboe is responsible for a huge number of patches aiming to make the OpenOCD more useable and stable. He fixed numerous bugs in the past, and made the OpenOCD a lot more portable to smaller, embedded hosts. Thanks a lot Øyvind!
Spencer Oliver has been an active supporter for a long time and keeps submitting patches all the time. Last but not least he catches the numerous times were I forget to “svn add” new files that come with a patch. Thanks a lot Spen!
This list is certainly not comprehensive, so thanks a lot to all who I’ve missed, too! All patches and suggestions are highly appreciated, even if you don’t get an immediate answer.
The best of way of getting patches integrated is sending them to the OpenOCD mailinglist, see https://lists.berlios.de/mailman/listinfo/openocd-development for instructions on how to subscribe.
The mailing list archive is available from that URL, too, so feel free to browse the past months to get an impression of the OpenOCD’s development progress.
Best regards,
Dominic Rath