http://openocd.org/2023-03-03T17:51:26+01:002023-03-03T17:51:26+01:002023-03-03T17:51:26+01:00fercerpavtag:openocd.org,2023-03-03:/openocd-0120-released.html

<p>I'm happy to announce the availability of OpenOCD version 0.12.0.</p> <p>Some major GNU/Linux distros (Debian, Fedora, Gentoo, OpenWrt), Homebrew for macOS and MSYS2 for Windows have already picked the release up. If your distro doesn't provide it yet, please ping your maintainer, and if any packaging issues …</p>

<p>I'm happy to announce the availability of OpenOCD version 0.12.0.</p> <p>Some major GNU/Linux distros (Debian, Fedora, Gentoo, OpenWrt), Homebrew for macOS and MSYS2 for Windows have already picked the release up. If your distro doesn't provide it yet, please ping your maintainer, and if any packaging issues arise the OpenOCD devs would be happy to help with that.</p> <p>The list of the most essential changes follows:</p> <dl class="docutils"> <dt>JTAG Layer:</dt> <dd><ul class="first last simple"> <li>add default to adapter speed when unspecified (100 kHz)</li> <li>AM335X gpio (BeagleBones) adapter driver</li> <li>BCM2835 support for SWD</li> <li>Cadence Virtual Debug (vdebug) adapter driver</li> <li>CMSIS-DAP support for SWO and SWD multidrop</li> <li>Espressif USB JTAG Programmer adapter driver</li> <li>Remote bitbang support for Windows host</li> <li>ST-LINK add TCP server support to adapter driver</li> <li>SWD multidrop support</li> </ul> </dd> </dl> <p>Boundary Scan:</p> <dl class="docutils"> <dt>Target Layer:</dt> <dd><ul class="first last simple"> <li>aarch64: support watchpoints</li> <li>arm: support independent TPIU and SWO for trace</li> <li>arm adi v5: support Large Physical Address Extension</li> <li>arm adi v6: support added, for jtag and swd transport</li> <li>cortex_a: support watchpoints</li> <li>elf 64bit load support</li> <li>Espressif: support ESP32, ESP32-S2 and ESP32-S3 cores</li> <li>semihosting: support user defined operations</li> <li>Xtensa: support Xtensa LX architecture via JTAG and ADIv5 DAP</li> </ul> </dd> <dt>Flash Layer:</dt> <dd><ul class="first last simple"> <li>Atmel/Microchip SAM E51G18A, E51G19A, R35J18B, LAN9255 support</li> <li>GigaDevice GD32E23x, GD32F1x0/3x0, GD32VF103 support</li> <li>Nuvoton NPCX series support</li> <li>onsemi RSL10 support</li> <li>Raspberry Pi Pico RP2040 support</li> <li>ST BlueNRG-LPS support</li> <li>ST STM32 G05x, G06x, G0Bx, G0Cx, U57x, U58x, WB1x, WL5x support</li> <li>ST STM32 G0, G4, L4, L4+, L5, WB, WL OTP support</li> </ul> </dd> <dt>Board, Target, and Interface Configuration Scripts:</dt> <dd><ul class="first last simple"> <li>Ampere Computing eMAG8180, Altra (&quot;Quicksilver&quot;) and Altra Max (&quot;Mystique&quot;) board config</li> <li>Cadence KC705 FPGA (Xtensa Development Platform) via JTAG and ADIv5 DAP board config</li> <li>Digilent Nexys Video board config</li> <li>Espressif ESP32 ETHERNET-KIT and WROVER-KIT board config</li> <li>Espressif ESP32 via ESP USB Bridge generic board config</li> <li>Espressif ESP32-S2 Kaluga 1 board config</li> <li>Espressif ESP32-S2 with ESP USB Bridge board config</li> <li>Espressif ESP32-S3 example board config</li> <li>Kontron SMARC-sAL28 board config</li> <li>LambdaConcept ECPIX-5 board config</li> <li>Microchip ATSAMA5D27-SOM1-EK1 board config</li> <li>Microchip EVB-LAN9255 board config</li> <li>Microchip SAME51 Curiosity Nano board config</li> <li>NXP FRDM-K64F, LS1046ARDB and LS1088ARDB board config</li> <li>NXP RT6XX board config</li> <li>Olimex H405 board config</li> <li>Radiona ULX3S board config</li> <li>Raspberry Pi 3 and Raspberry Pi 4 model B board config</li> <li>Raspberry Pi Pico-Debug board config</li> <li>Renesas R-Car V3U Falcon board config</li> <li>ST BlueNRG-LPS steval-idb012v1 board config</li> <li>ST NUCLEO-8S208RB board config</li> <li>ST NUCLEO-G031K8, NUCLEO-G070RB, NUCLEO-G071RB board config</li> <li>ST NUCLEO-G431KB, NUCLEO-G431RB, NUCLEO-G474RE board config</li> <li>ST STM32MP13x-DK board config</li> <li>TI AM625 EVM, AM642 EVM and AM654 EVM board config</li> <li>TI J721E EVM, J721S2 EVM and J7200 EVM board config</li> <li>Ampere Computing eMAG, Altra (&quot;Quicksilver&quot;) and Altra Max (&quot;Mystique&quot;) target config</li> <li>Cadence Xtensa generic and Xtensa VDebug target config</li> <li>Broadcom BCM2711, BCM2835, BCM2836 and BCM2837 target config</li> <li>Espressif ESP32, ESP32-S2 and ESP32-S3 target config</li> <li>Microchip ATSAMA5D2 series target config</li> <li>NanoXplore NG-Ultra SoC target config</li> <li>NXP IMX8QM target config</li> <li>NXP LS1028A, LS1046A and LS1088A target config</li> <li>NXP RT600 (Xtensa HiFi DSP) target config</li> <li>onsemi RSL10 target config</li> <li>Raspberry Pi Pico RP2040 target config</li> <li>Renesas R8A779A0 V3U target config</li> <li>Renesas RZ/Five target config</li> <li>Renesas RZ/G2 MPU family target config</li> <li>Rockchip RK3399 target config</li> <li>ST BlueNRG-LPS target config</li> <li>ST STM32MP13x target config</li> <li>TI AM625, AM654, J721E and J721S2 target config</li> <li>Ashling Opella-LD interface config</li> <li>Aspeed AST2600 linuxgpiod based interface config</li> <li>Blinkinlabs JTAG_Hat interface config</li> <li>Cadence Virtual Debug (vdebug) interface config</li> <li>Espressif ESP32-S2 Kaluga 1 board's interface config</li> <li>Espressif USB Bridge jtag interface config</li> <li>Infineon DAP miniWiggler V3 interface config</li> <li>PLS SPC5 interface config</li> <li>Tigard interface config</li> <li>Lattice MachXO3 family FPGA config</li> </ul> </dd> <dt>Server Layer:</dt> <dd><ul class="first last simple"> <li>GDB: add per-target remote protocol extensions</li> <li>GDB: more 'Z' packets support</li> <li>IPDBG JtagHost server functionality</li> <li>semihosting: I/O redirection to TCP server</li> <li>telnet: support for command's autocomplete</li> </ul> </dd> <dt>RTOS:</dt> <dd><ul class="first last simple"> <li>'none' rtos support</li> <li>Zephyr rtos support</li> </ul> </dd> </dl> <p>Documentation:</p> <dl class="docutils"> <dt>Build and Release:</dt> <dd><ul class="first last simple"> <li>Add json extension to jimtcl build</li> <li>Drop dependency from libusb0</li> <li>Drop repository repo.or.cz for submodules</li> <li>Move gerrit to <a class="reference external" href="https://review.openocd.org/">https://review.openocd.org/</a></li> <li>Require autoconf 2.69 or newer</li> <li>Update jep106 to revision JEP106BF.01</li> <li>Update jimtcl to version 0.81</li> <li>Update libjaylink to version 0.3.1</li> <li>New configure flag '--enable-jimtcl-maintainer' for jimtcl build</li> </ul> </dd> </dl> <p>This release also contains a number of other important functional and cosmetic bugfixes. For more details about what has changed since the last release, see the git repository history:</p> <p><a class="reference external" href="http://sourceforge.net/p/openocd/code/ci/v0.12.0/log/?path=">http://sourceforge.net/p/openocd/code/ci/v0.12.0/log/?path=</a></p> <p>Hooray for the developers!</p> <div class="highlight"><pre><span></span>407 Antonio Borneo &lt;borneo.antonio@gmail.com&gt; 100 Tomas Vanek &lt;vanekt@fbl.cz&gt; 96 Tarek BOCHKATI &lt;tarek.bouchkati@gmail.com&gt; 76 Marc Schink &lt;dev@zapb.de&gt; 34 Erhan Kurubas &lt;erhan.kurubas@espressif.com&gt; 22 Tim Newsome &lt;tim@sifive.com&gt; 17 Jan Matyas &lt;matyas@codasip.com&gt; 17 Nishanth Menon &lt;nm@ti.com&gt; 15 Ian Thompson &lt;ianst@cadence.com&gt; 13 Paul Fertser &lt;fercerpav@gmail.com&gt; 13 Steve Marple &lt;stevemarple@googlemail.com&gt; 11 Yasushi SHOJI &lt;yashi@spacecubics.com&gt; 10 Sean Anderson &lt;sean.anderson@seco.com&gt; 9 R. Diez &lt;rdiezmail-openocd@yahoo.de&gt; 8 Kevin Burke &lt;kevinb@os.amperecomputing.com&gt; 5 Daniel Anselmi &lt;danselmi@gmx.ch&gt; 4 Adrian Negreanu &lt;adrian.negreanu@nxp.com&gt; 4 Andreas Fritiofson &lt;andreas.fritiofson@gmail.com&gt; 4 Daniel Goehring &lt;dgoehrin@os.amperecomputing.com&gt; 4 Florian Fainelli &lt;f.fainelli@gmail.com&gt; 4 Markus Reiter &lt;me@reitermark.us&gt; 4 Oleksij Rempel &lt;o.rempel@pengutronix.de&gt; 4 micbis &lt;michele.bisogno.ct@renesas.com&gt; 3 Ben McMorran &lt;bemcmorr@microsoft.com&gt; 3 Frank Dischner &lt;frank.dischner@gmail.com&gt; 3 Julien Massot &lt;julien.massot@iot.bzh&gt; 3 Marek Vasut &lt;marek.vasut@gmail.com&gt; 3 Matthew Mets &lt;matt@blinkinlabs.com&gt; 3 Sebastiaan de Schaetzen &lt;sebastiaan.de.schaetzen@gmail.com&gt; 3 Thomas Gleixner &lt;tglx@linutronix.de&gt; 3 Tim Nordell &lt;tnordell@airgain.com&gt; 2 Alex Crawford &lt;openocd@code.acrawford.com&gt; 2 Andreas Bolsch &lt;hyphen0break@gmail.com&gt; 2 Andreas Sandberg &lt;andreas@sandberg.uk&gt; 2 Andrew Wesie &lt;awesie@gmail.com&gt; 2 Antonio Borneo &lt;antonio.borneo@st.com&gt; 2 Christian Hoff &lt;christian.hoff@advantest.com&gt; 2 Doug Brunner &lt;doug.a.brunner@gmail.com&gt; 2 Evgeniy Didin &lt;didin@synopsys.com&gt; 2 Evgeniy Naydanov &lt;evgeniy.naydanov@syntacore.com&gt; 2 Hans-Erik Floryd &lt;hans-erik.floryd@rt-labs.com&gt; 2 Jacek Wuwer &lt;jacekmw8@gmail.com&gt; 2 Jae Hyun Yoo &lt;quic_jaehyoo@quicinc.com&gt; 2 Jian-Hong Pan &lt;chienhung.pan@gmail.com&gt; 2 Jiri Kastner &lt;cz172638@gmail.com&gt; 2 Koudai Iwahori &lt;koudai@google.com&gt; 2 Pavel Kirienko &lt;pavel.kirienko@gmail.com&gt; 2 Peter Lawrence &lt;majbthrd@gmail.com&gt; 2 Toms Stūrmanis &lt;toms.sturmanis@gmail.com&gt; 2 asier70 &lt;asier70@gmail.com&gt; 1 Adrien Grassein &lt;adrien.grassein@gmail.com&gt; 1 Adrien Grassein &lt;agrassein@nanoxplore.com&gt; 1 Alvin Šipraga &lt;alsi@bang-olufsen.dk&gt; 1 Anthony Ferranti &lt;ferranti@os.amperecomputing.com&gt; 1 Antony Pavlov &lt;antonynpavlov@gmail.com&gt; 1 Asier Llano &lt;allano@hubbell.com&gt; 1 Ben Bender &lt;benjbender@gmail.com&gt; 1 Bohdan Tymkiv &lt;bohdan200@gmail.com&gt; 1 Cheng-Shiun Tsai &lt;cheng.shiun.tsai@gmail.com&gt; 1 Chengyu Zheng &lt;chengyu.zheng@polimi.it&gt; 1 Dan Stahlke &lt;dan@stahlke.org&gt; 1 Diego Herranz &lt;diegoherranz@diegoherranz.com&gt; 1 Felipe Balbi &lt;balbi@kernel.org&gt; 1 Florian Meister &lt;florian.meister@advantest.com&gt; 1 Florian Zaruba &lt;florian@openhwgroup.org&gt; 1 Gabor Csapo &lt;gaborcsapo@google.com&gt; 1 George Voicu &lt;razvanvg@hotmail.com&gt; 1 Giulio Fieramosca &lt;giulio@glgprograms.it&gt; 1 Jaehoon Park &lt;52432979+jaehoon-sifive@users.noreply.github.com&gt; 1 Jan Matyas &lt;50193733+JanMatCodasip@users.noreply.github.com&gt; 1 Janco Kock &lt;janco@factorylab.nl&gt; 1 Jesse Sheridan &lt;jesse.sheridan@gmail.com&gt; 1 Jimmy &lt;nhminus@gmail.com&gt; 1 Joerg Wunsch &lt;openocd@uriah.heep.sax.de&gt; 1 Jonathan Bell &lt;jonathan@raspberrypi.com&gt; 1 Karl Palsson &lt;karlp@tweak.net.au&gt; 1 Keith Packard &lt;keithp@keithp.com&gt; 1 Laszlo Sitzer &lt;dlsitzer@gmail.com&gt; 1 Leonard Crestez &lt;leonard.crestez@nxp.com&gt; 1 Liming Sun &lt;lsun@mellanox.com&gt; 1 Luis de Arquer &lt;luis.dearquer@inertim.com&gt; 1 MadSquirrel &lt;benoit.forgette@ci-yow.com&gt; 1 Marcin Niestroj &lt;m.niestroj@emb.dev&gt; 1 Martin Hierholzer &lt;martin.hierholzer@desy.de&gt; 1 Mischa Studer &lt;mischa.studer@csa.ch&gt; 1 Nick Kraus &lt;nick@nckraus.com&gt; 1 Nima Palizban &lt;n.palizban@gmail.com&gt; 1 Oleksij Rempel &lt;linux@rempel-privat.de&gt; 1 Olivier DANET &lt;odanet@caramail.com&gt; 1 Patrick Stewart &lt;patrick@rfcreations.com&gt; 1 Piotr Kasprzyk &lt;ciri@ciri.pl&gt; 1 PoroCYon &lt;porocyon@titandemo.org&gt; 1 Ranjith Chandran &lt;ranjith.tc@ashling.com&gt; 1 Raúl Sanchez Siles &lt;rasasi78@gmail.com&gt; 1 Raúl Sánchez Siles &lt;rasasi78@gmail.com&gt; 1 Rene Kita &lt;git@rkta.de&gt; 1 Rocco Marco Guglielmi &lt;roccomarco.guglielmi@gmail.com&gt; 1 Rohit Singh &lt;rohit91.2008@gmail.com&gt; 1 Salvatore Giorgio PECORINO &lt;salvatore-giorgio.pecorino@st.com&gt; 1 Simon Johansson &lt;ampleyfly@gmail.com&gt; 1 Simon Smiganovski &lt;simon.smiganovski@fruitcore.de&gt; 1 Tarek BOCHKATI &lt;tarek.bouchkati@st.com&gt; 1 Thomas Hebb &lt;tommyhebb@gmail.com&gt; 1 Wealian Liao &lt;WHLIAO@nuvoton.com&gt; 1 Yun Liu &lt;liuyun.97@gmail.com&gt; 1 Zoltán Dudás &lt;zedudi@gmail.com&gt; 1 fatalc &lt;cnfatal@gmail.com&gt; 1 iysheng &lt;iyysheng@gmail.com&gt; 1 jihongbin &lt;longma@orbbec.com&gt; 1 root &lt;acalando@free.fr&gt; </pre></div> 2022-09-18T18:26:59+02:002022-09-18T18:26:59+02:00fercerpavtag:openocd.org,2022-09-18:/openocd-0120-rc1-release-candidate-is-out.html

<p>We are pleased to announce the first release candidate of the upcoming OpenOCD version.</p> <p>The source archives and release notes are available from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.12.0-rc1/">the usual SF download locations</a>.</p> <p>Please post all your feedback to the <a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-devel">openocd-devel mailing list</a>.</p>

<p>We are pleased to announce the first release candidate of the upcoming OpenOCD version.</p> <p>The source archives and release notes are available from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.12.0-rc1/">the usual SF download locations</a>.</p> <p>Please post all your feedback to the <a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-devel">openocd-devel mailing list</a>.</p> 2021-08-25T20:46:57+02:002021-08-25T20:46:57+02:00fercerpavtag:openocd.org,2021-08-25:/irc-channel-moved-to-liberachat.html

<p>Due to radical changes on Freenode we announce a move of our <a class="reference external" href="http://openocd.org/pages/irc.html">IRC</a> presence to <a class="reference external" href="https://libera.chat">Libera.Chat</a> network.</p> <p>You're always welcome to discuss OpenOCD and related topics there.</p>

<p>Due to radical changes on Freenode we announce a move of our <a class="reference external" href="http://openocd.org/pages/irc.html">IRC</a> presence to <a class="reference external" href="https://libera.chat">Libera.Chat</a> network.</p> <p>You're always welcome to discuss OpenOCD and related topics there.</p> 2021-03-07T19:14:00+01:002021-03-07T19:14:00+01:00fercerpavtag:openocd.org,2021-03-07:/openocd-0-11-0-released.html

<p>Finally! Final.</p> <p>I'm happy to announce the availability of OpenOCD version 0.11.0.</p> <p>So four years since the last release and probably three years overdue it's here. Chances are we'll be able to produce them more often thanks to the expansion of the core team by several amazingly productive …</p>

<p>Finally! Final.</p> <p>I'm happy to announce the availability of OpenOCD version 0.11.0.</p> <p>So four years since the last release and probably three years overdue it's here. Chances are we'll be able to produce them more often thanks to the expansion of the core team by several amazingly productive members. Please see the commit statistics at the end of this mail, and do not forget that also plenty of effort is going into reviewing and testing patches.</p> <p>Despite the seemingly large number of committers the project would still benefit from getting more help, so if you can review patches, improve documentation, provide support on the mailing lists and IRC or participate by other means please do not be too shy to stand up :)</p> <p>We expect this release to be picked up by the distro maintainers pretty soon, the release candidate testing was quite encouraging in this regard. If you're a distro maintainer and have any issues, please report and we'll try to help with sorting everything out.</p> <p>The list of the most essential changes follows:</p> <p>JTAG Layer:</p> <ul class="simple"> <li>add debug level 4 for verbose I/O debug</li> <li>bitbang, add read buffer to improve performance</li> <li>Cadence SystemVerilog Direct Programming Interface (DPI) adapter driver</li> <li>CMSIS-DAP v2 (USB bulk based) adapter driver</li> <li>Cypress KitProg adapter driver</li> <li>FTDI FT232R sync bitbang adapter driver</li> <li>Linux GPIOD bitbang adapter driver through libgpiod</li> <li>Mellanox rshim USB or PCIe adapter driver</li> <li>Nuvoton Nu-Link and Nu-Link2 adapter drivers</li> <li>NXP IMX GPIO mmap based adapter driver</li> <li>ST-Link consolidate all versions in single config</li> <li>ST-Link read properly old USB serial numbers</li> <li>STLink/V3 support (for ST devices only !)</li> <li>STM8 SWIM transport</li> <li>TI XDS110 adapter driver</li> <li>Xilinx XVC/PCIe adapter driver</li> </ul> <p>Target Layer:</p> <ul class="simple"> <li>64 bit address support</li> <li>ARCv2 target support</li> <li>ARM Cortex-A hypervisor mode support</li> <li>ARM Cortex-M fast PC sampling support for profiling</li> <li>ARM generic CTI support</li> <li>ARM generic mem-ap target support</li> <li>ARMv7-A MMU tools</li> <li>ARMv7m traces add TCP stream server</li> <li>ARMv8 AARCH64 target support and semihosting support</li> <li>ARMv8 AARCH64 disassembler support through capstone library</li> <li>ARMv8-M target support</li> <li>EnSilica eSi-RISC target support, including instruction tracing eSi-Trace support</li> <li>MIPS64 target support</li> <li>Motorola SREC S6 record image file support</li> <li>RISC-V target support</li> <li>SEGGER Real Time Transfer (RTT) initial support (for single target, Cortex-M only)</li> <li>ST STM8 target support</li> <li>Various MIPS32 target improvements</li> </ul> <p>Flash Layer:</p> <ul class="simple"> <li>Atheros (ath79) SPI interface support</li> <li>Atmel atmega128rfa1 support</li> <li>Atmel SAM D21, D51, DA1, E51, E53, E54, G55, R30 support</li> <li>Atmel SAMC2?N* support</li> <li>Cypress PSoC5LP, PSoC6 support</li> <li>EnSilica eSi-RISC support</li> <li>Foshan Synwit Tech SWM050 support</li> <li>Maxim Integrated MAX32XXX support</li> <li>Nordic Semiconductor nRF51822, nRF52810, nRF52832 support</li> <li>NXP Kinetis K27, K28, KE1x, KEAx, KL28, KL8x, KV5x, KWx support</li> <li>Renesas RPC HF support</li> <li>SH QSPI support</li> <li>SiFive Freedom E support</li> <li>Silicon Labs EFR-family, EZR32HG support</li> <li>ST BlueNRG support</li> <li>ST STM32 QUAD/OCTO-SPI interface support for Flash, FRAM and EEPROM</li> <li>ST STM32F72x, STM32F4x3, STM32H7xx support</li> <li>ST STM32G0xx, STM32G4xx, STM32L4x, STM32WB, STM32WL support</li> <li>ST STM32L5x support (non secure mode)</li> <li>TI CC13xx, CC26xx, CC32xx support</li> <li>TI MSP432 support</li> <li>Winner Micro w600 support</li> <li>Xilinx XCF platform support</li> <li>Various discrete SPI NOR flashes support</li> </ul> <p>Board, Target, and Interface Configuration Scripts:</p> <ul class="simple"> <li>8devices LIMA board config</li> <li>Achilles Instant-Development Kit Arria 10 board config</li> <li>Amazon Kindle 2 and DX board config</li> <li>Analog Devices ADSP-SC58x, ADSP-SC584-EZBRD board config</li> <li>Andes Technology ADP-XC7KFF676 board config</li> <li>Andes Technology Corvette-F1 board config</li> <li>ARM Musca A board config</li> <li>Arty Spartan 7 FPGA board config</li> <li>Atmel SAMD10 Xplained mini board config</li> <li>Atmel SAMD11 Xplained Pro board config</li> <li>Atmel SAM G55 Xplained Pro board config</li> <li>AVNET UltraZED EG StarterKit board config</li> <li>Blue Pill STM32F103C8 board config</li> <li>DP Busblaster v4.1a board config</li> <li>DPTechnics DPT-Board-v1 board config</li> <li>Emcraft imx8 SOM BSB board config</li> <li>Globalscale ESPRESSObin board config</li> <li>Kasli board config</li> <li>Kintex Ultrascale XCKU040 board config</li> <li>Knovative KC-100 board config</li> <li>LeMaker HiKey board config</li> <li>Microchip (Atmel) SAME54 Xplained Pro board config</li> <li>Microchip (Atmel) SAML11 Xplained Pro board config</li> <li>Nordic module NRF52 board config</li> <li>Numato Lab Mimas A7 board config</li> <li>NXP Freedom FRDM-LS1012A board config</li> <li>NXP IMX7SABRE board config</li> <li>NXP IMX8MP-EVK board config</li> <li>NXP MC-IMX8M-EVK board config</li> <li>QuickLogic QuickFeather board config</li> <li>Renesas R-Car E2, H2, M2 board config</li> <li>Renesas R-Car Salvator-X(S) board config</li> <li>Renesas RZ/A1H GR-Peach board config</li> <li>Rigado BMD-300 board config</li> <li>Sayma AMC board config</li> <li>Sifive e31arty, e51arty, hifive1 board config</li> <li>ST B-L475E-IOT01A board config</li> <li>ST BlueNRG idb007v1, idb008v1, idb011v1 board config</li> <li>ST STM32F412g discovery board config</li> <li>ST STM32F413h discovery board config</li> <li>ST STM32F469i discovery board config</li> <li>ST STM32F7 Nucleo board config</li> <li>ST STM32F723e discovery board config</li> <li>ST STM32F746g discovery board config</li> <li>ST STM32F769i discovery board config</li> <li>ST STM32H735g discovery board config</li> <li>ST STM32H743zi Nucleo board config</li> <li>ST STM32H745i discovery board config</li> <li>ST STM32H747i discovery board config</li> <li>ST STM32H750b discovery board config</li> <li>ST STM32H7b3i discovery board config</li> <li>ST STM32H7x_dual_qspi board config</li> <li>ST STM32H7x3i Eval boards config</li> <li>ST STM32L073 Nucleo board config</li> <li>ST STM32L476g discovery board config</li> <li>ST STM32L496g discovery board config</li> <li>ST STM32L4p5g discovery board config</li> <li>ST STM32L4r9i discovery board config</li> <li>ST STM32L5 Nucleo board config</li> <li>ST STM32MP15x DK2 board config</li> <li>ST STM32WB Nucleo board config</li> <li>ST STM8L152R8 Nucleo board config</li> <li>Synopsys DesignWare ARC EM board config</li> <li>Synopsys DesignWare ARC HSDK board config</li> <li>TI BeagleBone family boards config</li> <li>TI CC13xx, CC26xx, CC32xx LaunchPad board config</li> <li>TI MSP432 LaunchPad board config</li> <li>Tocoding Poplar board config</li> <li>TP-Link WDR4300 board config</li> <li>Allwinner V3s target config</li> <li>Andes Technology NDS V5 target config</li> <li>Atmel atmega128rfa1 target config</li> <li>ARM corelink SSE-200 target config</li> <li>Atheros_ar9344 target config</li> <li>Cypress PSoC5LP, PSoC6 target config</li> <li>EnSilica eSi-RISC target config</li> <li>Foshan Synwit Tech SWM050 target config</li> <li>GigaDevice GD32VF103 target config</li> <li>Hisilicon Hi3798 target config</li> <li>Hisilicon Hi6220 target config</li> <li>Infineon TLE987x target config</li> <li>Marvell Armada 3700 target config</li> <li>Maxim Integrated MAX32XXX target config</li> <li>Mellanox BlueField target config</li> <li>Microchip (Atmel) SAME5x, SAML1x target config</li> <li>NXP IMX6SX, IMX6UL, IMX7, IMX7ULP, IMX8 target config</li> <li>NXP Kinetis KE1xZ, KE1xF target config</li> <li>NXP LPC84x, LPC8Nxx, LS1012A, NHS31xx target config</li> <li>Qualcomm QCA4531 target config</li> <li>QuickLogic EOS S3 target config</li> <li>Renesas R-Car E2, H2, M2 target config</li> <li>Renesas R-Car Gen3 target config</li> <li>Renesas RZ/A1H target config</li> <li>Rockchip RK3308 target config</li> <li>ST BlueNRG target config</li> <li>ST STM32G0, STM32G4, STM32H7, STM32L0, STM32L5 target config</li> <li>ST STM32MP15x target config</li> <li>ST STM32WBx, STM32WLEx target config</li> <li>ST STM8L152, S003, S103, S105 target config</li> <li>Synopsys DesignWare ARC EM target config</li> <li>Synopsys DesignWare ARC HS Development Kit SoC target config</li> <li>TI CC13xx, CC26xx, CC32xx target config</li> <li>TI TNETC4401 target config</li> <li>Xilinx UltraScale+ target config</li> <li>Altera 5M570Z (MAXV family) CPLD config</li> <li>Xilinx Ultrascale, XCF CPLD config</li> <li>Intel (Altera) Arria10 FPGA config</li> <li>Cadence SystemVerilog Direct Programming Interface (DPI) interface config</li> <li>Cypress KitProg interface config</li> <li>Digilent SMT2 NC interface config</li> <li>DLN-2 example of Linux GPIOD interface config</li> <li>FTDI C232HM interface config</li> <li>HIE JTAG Debugger interface config</li> <li>In-Circuit's ICprog interface config</li> <li>isodebug isolated JTAG/SWD+UART interface config</li> <li>Mellanox rshim USB or PCIe interface config</li> <li>Nuvoton Nu-Link interface config</li> <li>NXP IMX GPIO mmap based interface config</li> <li>Steppenprobe open hardware interface config</li> <li>TI XDS110 interface config</li> </ul> <p>Server Layer:</p> <ul class="simple"> <li>64 bit address support</li> <li>default bind to IPv4 localhost</li> <li>gdb: allow multiple connections</li> <li>gdb: architecture element support</li> <li>gdb: vCont, vRun support</li> <li>telnet: handle Ctrl+A, Ctrl+E and Ctrl+K</li> </ul> <p>RTOS:</p> <ul class="simple"> <li>Chromium-EC rtos support</li> <li>hwthread pseudo rtos support</li> <li>NuttX rtos support</li> <li>RIOT rtos support</li> </ul> <p>Documentation:</p> <ul class="simple"> <li>Improve STM32 flash driver</li> <li>Various typo fix and improvements</li> </ul> <p>Build and Release:</p> <ul class="simple"> <li>Add libutil to support jimtcl version 0.80</li> <li>Clang warning fixes</li> <li>GitHub workflow for Win32 snapshot binaries</li> <li>Handle Tcl return values consistently</li> <li>Mitigation for CVE-2018-5704: Prevent some forms of Cross Protocol Scripting attacks</li> <li>Support for libftdi 1.5</li> <li>Travis-CI basic support</li> <li>Update libjaylink to version 0.2.0</li> <li>Update jimtcl to version 0.79</li> <li>Use external (optional) library capstone for ARM and AARCH64 disassembly</li> </ul> <p>This release also contains a number of other important functional and cosmetic bugfixes. For more details about what has changed since the last release, see the <a class="reference external" href="http://sourceforge.net/p/openocd/code/ci/v0.11.0/log/?path=">git repository history.</a></p> <p>Hooray for the developers!</p> <div class="highlight"><pre><span></span>392 Antonio Borneo 189 Tomas Vanek 135 Marc Schink 120 Matthias Welwarsky 85 Paul Fertser 74 Tarek BOCHKATI 47 Christopher Head 31 Marek Vasut 28 Oleksij Rempel 21 Tim Newsome 20 Edward Fewell 17 Salvador Arroyo 15 Andreas Fritiofson 15 Steven Stallion 14 Karl Palsson 14 Leonard Crestez 13 Evgeniy Didin 11 Jiri Kastner 10 Bohdan Tymkiv 10 Robert Jordens 9 Omair Javaid 8 Ake Rehnman 8 Moritz Fischer 7 Andreas Färber 7 David Ung 7 Florian Fainelli 6 Andreas Bolsch 6 Felipe Balbi 6 Jan Matyas 5 Hellosun Wu 5 Jonathan McDowell 4 Cody P Schafer 4 Jonas Norling 4 Laurent LEMELE 4 Liviu Ionescu 4 Peter Mamonov 4 Spencer Oliver 3 Alistair Francis 3 Armin van der Togt 3 Aurélien Martin 3 Diego Herranz 3 Dominik Peklo 3 Girts 3 Jan Kowalewski 3 Jean-Christian de Rivaz 3 Kevin Gillespie 3 Kevin Yang 3 Liming Sun 3 Mete Balci 3 Peter Lawrence 3 Slowcoder 3 Yasushi SHOJI 2 Adam Bass 2 Adrian Negreanu 2 Alexandre Torgue 2 Alexandru Gagniuc 2 Bas Vermeulen 2 Cody Schafer 2 Darius Rad 2 Forest Crossman 2 Freddie Chopin 2 Girts Folkmanis 2 Guido Günther 2 Jerome Forissier 2 Joakim Nohlgård 2 John Pham 2 Juha Niskanen 2 Kai Geissdoerfer 2 Kevin Burke 2 Khem Raj 2 Lars Poeschel 2 Michele Sardo 2 Mikhail Rasputin 2 Mirko Vogt 2 Piotr Kasprzyk 2 R. Diez 2 Seth LaForge 2 William D. Jones 2 luca vinci 2 pierre Kuo 2 tscn92 1 Al Dyrius 1 Alberto García Hierro 1 Aleksey Shargalin 1 Alex J Lennon 1 Alexander Kurz 1 Alexandre Bourdiol 1 Alexey Brodkin 1 Anders Westrup 1 Andrea Merello 1 Andreas Kemnade 1 Angus Ainslie 1 Anton V. Kirilchik 1 Antony Pavlov 1 Austin Morton 1 Austin Phillips 1 Benedikt-Alexander Mokroß 1 Boran Car 1 Brent Roman 1 Brian Brooks 1 Byron Kubert 1 Caleb Szalacinski 1 CezaryGapinski 1 Chengyu Zheng 1 Christian Meusel 1 Christopher Hoover 1 Cliff L. Biffle 1 Damyan Mitev 1 Daniel Glöckner 1 Daniel Goehring 1 Daniel Krebs 1 Daniel Kucera 1 Daniel Trnka 1 Dennis Ostermann 1 Diego Elio Pettenò 1 Dongxue Zhang 1 EMARD 1 Erwin Oegema 1 Evan Hunter 1 Fabio Utzig 1 Faisal Shah 1 Frank Hunleth 1 Frans-Willem Hardijzer 1 Grzegorz Kostka 1 Guillaume Revaillot 1 Han Hartgers 1 Icenowy Zheng 1 Ilya Kharin 1 James Jacobsson 1 James Marshall 1 Jan Vojtech 1 Jan Čapek 1 Jerome Lambourg 1 Jim Paris 1 Jimmy 1 Jānis Skujenieks 1 Kamal Dasu 1 Keir Fraser 1 Kevin Vermilion 1 Krzysztof Hockuba 1 Luca Dariz 1 Luca Lindhorst 1 Lucas 1 Mara Bos 1 Masatoshi Tateishi 1 Matej Kogovsek 1 Mateusz Manowiecki 1 Matthias Bock 1 Megan Wachs 1 Michael Betz 1 Michael Hope 1 Michael Schwingen 1 Michael Stoll 1 Michal Potrzebicz 1 Mickaël Thomas 1 Moritz &#39;Morty&#39; Strübe 1 Niklas Söderlund 1 Oleksandr Redchuk 1 Patrick Stewart 1 Paul Bartholomew 1 Peter Griffin 1 Philipp Tomsich 1 Pushpal Sidhu 1 Rahul Masurkar 1 Reto Schneider 1 Richard Watts 1 Robert Foss 1 Rocco Marco Guglielmi 1 Rod Boyce 1 Rohit Singh 1 Roman Elshin 1 Samuel Obuch 1 Sasha Kozaruk 1 Severin Junker 1 Simon Qian 1 Simon Schubert 1 Stafford Horne 1 Stefan Arnold 1 Svetoslav Enchev 1 Sylvain Chouleur 1 Tarek BOUCHKATI 1 Thomas Søhus 1 Tilman Sauerbeck 1 Tobias Diedrich 1 Tommy Vestermark 1 Ulrich-Lorenz Schlüter 1 Uwe Bonnes 1 YanLin Zhu 1 Zale Yu 1 barthess 1 bob 1 elmot 1 iosabi 1 xuguangxiao 1 Łukasz Misek </pre></div> 2018-11-01T10:40:00+01:002018-11-01T10:40:00+01:00ntfreaktag:openocd.org,2018-11-01:/beyond_simple_debugging.html

<p>A talk by Oleksij Rempel from Pengutronix on using OpenOCD for tasks other than debugging.</p> <iframe src="https://www.youtube.com/embed/lk2V0YkgN2A" frameborder="0" width="420" height="254"></iframe>

<p>A talk by Oleksij Rempel from Pengutronix on using OpenOCD for tasks other than debugging.</p> <iframe src="https://www.youtube.com/embed/lk2V0YkgN2A" frameborder="0" width="420" height="254"></iframe>2017-01-22T22:06:00+01:002017-01-22T22:06:00+01:00fercerpavtag:openocd.org,2017-01-22:/openocd-0-10-0-release-is-out.html

<p>Hello,</p> <p>I'm happy to announce the availability of <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.10.0/">OpenOCD version 0.10.0</a>, finally! For the important points regarding packaging please see <a class="reference external" href="https://sourceforge.net/p/openocd/mailman/message/35570895/">[1]</a>.</p> <p>It was a long release cycle but it was also a fruitful one. The list of the most important changes follows.</p> <p>OpenOCD is a community project and …</p>

<p>Hello,</p> <p>I'm happy to announce the availability of <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.10.0/">OpenOCD version 0.10.0</a>, finally! For the important points regarding packaging please see <a class="reference external" href="https://sourceforge.net/p/openocd/mailman/message/35570895/">[1]</a>.</p> <p>It was a long release cycle but it was also a fruitful one. The list of the most important changes follows.</p> <p>OpenOCD is a community project and I want to take this opportunity to say <em>thank you</em> to all the contributors, regular and occassional, hobbyists and professionals, corporate-supported and those doing the work on their spare time. Please keep the flow of the patches going, both by sending new code and by <a class="reference external" href="http://openocd.zylin.com">reviewing</a> other's contributions. It's you who really decide what new features OpenOCD is going to get.</p> <p>I also want to remind how important it is to communicate to the silicon vendors that you would like to see their devices supported upstream (or that you're happy that they're supported).</p> <div class="section" id="highlights-of-the-changes-made-in-the-openocd-source-archive-release"> <h2>Highlights of the changes made in the OpenOCD source archive release</h2> <p>JTAG Layer:</p> <ul class="simple"> <li>New driver for J-Link adapters based on libjaylink (including support for FPGA configuration, SWO and EMUCOM)</li> <li>FTDI improvements to work at 30MHz clock</li> <li>BCM2835 native driver SWD and Raspberry Pi2 support</li> <li>BCM2835 is set to 4ma drive, slow slew rate</li> <li>ixo-usb-jtag (emulation of an Altera Bus Blaster I on Cypress FX2 IC) support</li> <li>JTAG pass-through mode for CMSIS-DAP (including support for FPGA configuration)</li> <li>OpenJTAG support for Cypress CY7C65215</li> <li>connect_assert_srst support for SWD</li> <li>Xilinx Virtex-II Series7 bitstream loading support</li> <li>Use JEP106 data to decode IDs</li> <li>Deprecated &quot;ft2232&quot; driver removed (use &quot;ftdi&quot; instead)</li> <li>GPL-incompatible FTDI D2XX library support dropped (Presto, OpenJTAG and USB-Blaster I are using libftdi only now)</li> <li>ZY1000 support dropped (unmaintained since long)</li> <li>oocd_trace support dropped</li> </ul> <p>Target Layer:</p> <ul class="simple"> <li>ARMv7-A, Cortex-M, Cortex-A/R important fixes and improvements (allowing e.g. simultaneous debugging of A8 and M3 cores, JTAG WAIT support etc.)</li> <li>ARM Cortex-A,R allow interrupt disable during single-step (maskisr command)</li> <li>Semihosting support for ARMv7-A</li> <li>ARM Cortex-M7 support</li> <li>Intel Quark mcu D2000 support</li> <li>Freescale LS102x SAP support</li> <li>ThreadX RTOS support on ARM926E-JS</li> <li>Cortex-M RTOS stack alignment fixes</li> <li>FreeRTOS FPU support</li> <li>uC/OS-III RTOS support</li> <li>bridging semihosting to GDB's File-I/O support</li> <li>-defer-examine option added to target create command</li> <li>verify_image_checksum command added</li> </ul> <p>Flash Layer:</p> <ul class="simple"> <li>Atmel SAM4S, SAM4N, SAM4C support</li> <li>Atmel SAMV, SAMS, SAME (Cortex-M7) support</li> <li>Atmel AT91SAMD handle reset run/halt in DSU, other fixes</li> <li>Atmel AT91SAML21, SAML22, SAMC20/SAMC21, SAMD09 support</li> <li>ST STM32F4x support</li> <li>ST STM32F74x/76x/77x, STM32L4 support</li> <li>ST STM32L0 categories 1, 2 and 5 support</li> <li>Kinetis K02, K21, K22, K24, K26, K63, K64, K66 support</li> <li>Kinetis KE, KVx, K8x families support</li> <li>Kinetis FlexNVM handling</li> <li>Kinetis flash protection, security, mass_erase improvements</li> <li>Infineon XMC4xxx family support</li> <li>Infineon XMC1000 flash driver</li> <li>Energy Micro EFM32 Happy Gecko support</li> <li>Energy Micro EFM32 debug interface lock support</li> <li>Analog Devices ADuCM360 support</li> <li>Unified Nuvoton NuMicro flash driver</li> <li>NIIET K1921VK01T (Cortex-M4) support</li> <li>Nordic Semiconductor nRF51 improvements</li> <li>Spansion FM4 flash (including MB9BFx64/x65, S6E2DH) driver</li> <li>Ambiq Micro Apollo flash driver</li> <li>PIC32MX new device IDs, 17x/27x flash support</li> <li>read_bank() and verify_bank() NOR flash internal API to allow reading (and verifying) non-memory-mapped devices</li> <li>JTAGSPI driver to access SPI NOR flashes via a trivial FPGA proxy</li> <li>Milandr read/verify for Info memory support</li> <li>Various discrete SPI NOR flashes support</li> <li>CFI 16-bit flash reversed endianness support</li> </ul> <p>Board, Target, and Interface Configuration Scripts:</p> <ul class="simple"> <li>Digilent JTAG-HS2, JTAG-HS3 interfaces configs</li> <li>FTDI UM232H module as JTAG interface config</li> <li>100ask's OpenJTAG interface config</li> <li>MBFTDI interface config</li> <li>XDS100v3 interface config</li> <li>Freescale Vybrid VF6xx target config</li> <li>EmCraft VF6 SOM and baseboard configs</li> <li>Freescale SabreSD board config</li> <li>Freescale VF65GS10 tower board config</li> <li>Pipistrello Xilinx Spartan6 LX45 FPGA board config</li> <li>miniSpartan6+ board config</li> <li>Xilinx Kintex7 Development board config</li> <li>Parallella-I board config</li> <li>Digilent Atlys and Analog Discovery board configs</li> <li>Numato Opsis board config</li> <li>Xilinx Spartan 6 FPGA &quot;Device DNA&quot; reading support</li> <li>Altera 10M50 FPGA (MAX10 family) target config</li> <li>Altera EPM240 CPLD (MAXII family) target config</li> <li>Marsohod2, Marsohod3 FPGA, Marsohod CPLD boards configs</li> <li>Novena's integrated FPGA board config</li> <li>XMOS XS1-XAU8A-10's ARM core config</li> <li>XMOS xCORE-XA Core Module board config</li> <li>Exynos5250 target config</li> <li>Arndale board config</li> <li>FM4 MB9BFxxx family configs</li> <li>Spansion SK-FM4-U120-9B560 board config</li> <li>Diolan LPC4357-DB1 board config</li> <li>ST STM32F469 discovery board config</li> <li>ST STM32F7-DISCO, STM327[4|5]6G-EVAL boards configs</li> <li>ST STM32L4 discovery, NUCLEO L476RG, STM32F429I-DISC1 boards configs</li> <li>Atheros AR2313, AR2315 targets config</li> <li>Netgear WP102 board config</li> <li>La Fonera FON2200 board config</li> <li>Linksys WAG200G board config</li> <li>LPC-Link2 board config</li> <li>NXP LPC4370 target config</li> <li>Atmel SAMV, SAMS, SAME target configs</li> <li>Atmel SAM E70 Xplained, SAM V71 Xplained Ultra boards configs</li> <li>Nordic nRF52 target config</li> <li>Nordic nRF51-DK, nRF52-DK boards configs</li> <li>Infineon XMC4700 Relax Kit, XMC4800 Relax EtherCAT Kit, XMC4300 Relax EtherCAT Kit boards configs</li> <li>Renesas S7G2 target config</li> <li>Renesas DK-S7G2 board config</li> <li>Altera EP3C10 FPGA (Cyclone III family) target config</li> <li>TI MSP432P4xx target config</li> <li>Cypress PSoC 5LP target config</li> <li>Analog Devices ADSP-SC58x target config (Cortex-A5 core only)</li> </ul> <p>Server Layer:</p> <ul class="simple"> <li>tcl_trace command for async target trace output via Tcl RPC</li> </ul> <p>Build and Release:</p> <ul class="simple"> <li>Various fixes thanks to <a class="reference external" href="http://coccinellery.org">http://coccinellery.org</a></li> <li>libftdi is now autodetected with pkgconfig</li> <li>Releases should now support reproducible builds</li> <li>Conversion to non-recursive make, requires automake &gt;= 1.14</li> <li>Udev rules modified to add uaccess tag and moved to 60-openocd.rules</li> <li>Support searching for scripts relative to the openocd binary for all major architectures</li> </ul> <p>This release also contains a number of other important functional and cosmetic bugfixes. For more details about what has changed since the last release, see the <a class="reference external" href="http://sourceforge.net/p/openocd/code/ci/v0.10.0/log/?path=">git repository history</a>.</p> <p>Good luck, and happy hacking!</p> </div> 2017-01-15T16:33:00+01:002017-01-15T16:33:00+01:00fercerpavtag:openocd.org,2017-01-15:/openocd-0-10-0-rc2-release-candidate-is-available.html

<p>Few minor issues were fixed and now we are moving to the second release candidate. If everything goes nicely, we plan to produce the release during the next weekend.</p> <p>The source archives and release notes are available from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.10.0-rc2/">the usual SF download locations</a>.</p> <p>Please post all your feedback to the …</p>

<p>Few minor issues were fixed and now we are moving to the second release candidate. If everything goes nicely, we plan to produce the release during the next weekend.</p> <p>The source archives and release notes are available from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.10.0-rc2/">the usual SF download locations</a>.</p> <p>Please post all your feedback to the <a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-devel">openocd-devel mailing list</a>.</p> 2016-12-25T15:44:00+01:002016-12-25T15:44:00+01:00fercerpavtag:openocd.org,2016-12-25:/openocd-0-10-0-rc1-release-candidate-is-out.html

<p>We are pleased to announce the first release candidate of the upcoming OpenOCD version.</p> <p>The source archives and release notes are available from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.10.0-rc1/">the usual SF download locations</a>.</p> <p>Freddie Chopin has kindly provided windows binaries on his website:</p> <p><a class="reference external" href="http://www.freddiechopin.info/">http://www.freddiechopin.info/</a> &gt; Download &gt; Software &gt; OpenOCD dev &gt; openocd-0.10.0-rc1</p> <p>Please …</p>

<p>We are pleased to announce the first release candidate of the upcoming OpenOCD version.</p> <p>The source archives and release notes are available from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.10.0-rc1/">the usual SF download locations</a>.</p> <p>Freddie Chopin has kindly provided windows binaries on his website:</p> <p><a class="reference external" href="http://www.freddiechopin.info/">http://www.freddiechopin.info/</a> &gt; Download &gt; Software &gt; OpenOCD dev &gt; openocd-0.10.0-rc1</p> <p>Please post all your feedback to the <a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-devel">openocd-devel mailing list</a>.</p> 2015-05-18T22:42:00+02:002015-05-18T22:42:00+02:00fercerpavtag:openocd.org,2015-05-18:/openocd-0-9-0-release.html

<p>I'm happy to announce the release of OpenOCD version 0.9.0, finally!</p> <p>It tooks us a bit more than a year but the list of changes isn't a small one either. With 439 commits from 94 contributors, it's an impressive example of how the community can drive the project …</p>

<p>I'm happy to announce the release of OpenOCD version 0.9.0, finally!</p> <p>It tooks us a bit more than a year but the list of changes isn't a small one either. With 439 commits from 94 contributors, it's an impressive example of how the community can drive the project forward. As an active OpenOCD user, I really appreciate all your patches, bugreports, discussions and friendly chat on IRC, thank you folks! Special mention goes to those who tirelessly review the patches and keep the project afloat as a whole: the core maintainers team.</p> <p>We've also seen participation from the big semiconductor manufacturers, both nice and odd. Not everybody understands why it's important to provide the customers with free software cross-platform tools, so please, even if you're just a customer, you still have a voice, send your vendor an email explaining why it would be important for you to have support for their ICs in upstream OpenOCD (or if it's already there, how happy you're about it). The more examples they get, the more likely they'll listen and learn; and I hope those who have already tried collaborating with the OpenOCD project enjoyed it as much as we did.</p> <p>The release tarballs are available from the usual SF location: <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.9.0/">https://sourceforge.net/projects/openocd/files/openocd/0.9.0/</a> and the documentation can be easily reached from <a class="reference external" href="http://openocd.org/documentation/">http://openocd.org/documentation/</a> .</p> <p>Here follows a copy of the release NEWS for your convenience.</p> <p>Enjoy, and happy hacking!</p> <p>JTAG Layer:</p> <ul class="simple"> <li>SWD support with FTDI, Versaloon, J-Link, sysfsgpio</li> <li>CMSIS-DAP massive speed and stability improvements</li> <li>Versaloon driver ported to libusb-1.0</li> <li>STLink can reestablish communication with a target that was disconnected or rebooted</li> <li>STLink FAULT and WAIT SWD handling improved</li> <li>New hla_serial command to distinguish between several HLA adapters attached to a single machine</li> <li>Serial number support for CMSIS-DAP and J-Link adapters</li> <li>Support for more J-Link adapters</li> <li>TAP autoprobing improvements</li> <li>Big speedup for SVF playback with USB Blaster</li> </ul> <p>Boundary Scan:</p> <p>Target Layer:</p> <ul class="simple"> <li>Stability improvements for targets that get disconnected or rebooted during a debug session</li> <li>MIPS speed and reliability improvements</li> <li>MIPS 1.5/2.0 fixes</li> <li>ARMv7-R improvements</li> <li>Cortex-A improvements, A7, A15 MPCores support</li> <li>FPU support for ARMv7-M (Cortex-M4F)</li> <li>TPIU/ITM support (including SWO/SWV tracing), can be captured with external tools or STLink</li> <li>JTAG Serial Port (Advanced Debug System softcore) support</li> <li>Profiling support for OpenRISC</li> <li>ChibiOS/RT 3.0 support (with and without FPU)</li> <li>FreeRTOS current versions support</li> <li>Freescale MQX RTOS support</li> <li>GDB target description support for MIPS</li> <li>The last created target is auto-selected as the current</li> </ul> <p>Flash Layer:</p> <ul class="simple"> <li>nRF51 async loader to improve flashing performance and stability</li> <li>Cypress PSoC 41xx/42xx and CCG1 families flash driver</li> <li>Silabs SiM3 family flash driver</li> <li>Marvell Wireless Microcontroller SPI flash driver</li> <li>Kinetis mass erase (part unsecuring) implemented</li> <li>lpcspifi stability fixes</li> <li>STM32 family sync with reference manuals, L0 support, bugfixes</li> <li>LPC2000 driver automatically determines part and flash size</li> <li>NXP LPC11(x)xx, LPC13xx, LPC15xx, LPC8xx, LPC5410x, LPC407x support</li> <li>Atmel SAMD, SAMR, SAML21 devices support</li> <li>Atmel SAM4E16 support</li> <li>ZeroGecko family support</li> <li>TI Tiva C Blizzard and Snowflake families support</li> <li>Nuvoton NuMicro M051 support</li> <li>EZR32 support in EFM32 driver</li> </ul> <p>Board, Target, and Interface Configuration Scripts:</p> <ul class="simple"> <li>Normal target configs can work with HLA (STLink, ICDI) adapters</li> <li>STM32 discovery and Nucleo boards configs</li> <li>Gumstix AeroCore board config</li> <li>General Plus GP326XXXA target config</li> <li>Micrel KS869x target config</li> <li>ASUS RT-N66U board config</li> <li>Atmel SAM4E-EK board config</li> <li>Atmel AT91SAM4L proper reset handling implemented</li> <li>TI OMAP/AM 3505, 3517 target configs</li> <li>nRF51822-mKIT board config</li> <li>RC Module К1879ХБ1Я target config</li> <li>TI TMDX570LS20SUSB board config</li> <li>TI TMS570 USB Kit board config</li> <li>TI CC2538, CC26xx target configs</li> <li>TI AM437x major config improvements, DDR support</li> <li>TI AM437X IDK board config</li> <li>TI SimpleLink Wi-Fi CC3200 LaunchPad configs</li> <li>Silicon Labs EM357, EM358 target configs</li> <li>Infineon XMC1000, XMC4000 family targets and boards configs</li> <li>Atheros AR9331 target config</li> <li>TP-LINK TL-MR3020 board config</li> <li>Alphascale asm9260t target and eval kit configs</li> <li>Olimex SAM7-LA2 (AT91SAM7A2) board config</li> <li>EFM32 Gecko boards configs</li> <li>Spansion FM4 target and SK-FM4-176L-S6E2CC board configs</li> <li>LPC1xxx target configs were restructured</li> <li>IoT-LAB debug adapter config</li> <li>DP BusBlaster KT-Link compatible config</li> </ul> <p>Server Layer:</p> <ul class="simple"> <li>Polling period can be configured</li> <li>&quot;shutdown&quot; command has an immediate effect</li> <li>The &quot;program&quot; command doesn't lead to a shutdown by default, use optional &quot;exit&quot; parameter for the old behaviour</li> <li>Proper OS signal handling was implemented</li> <li>Async target notifications for the Tcl RPC</li> </ul> <p>Documentation:</p> <p>Build and Release:</p> <p>This release also contains a number of other important functional and cosmetic bugfixes. For more details about what has changed since the last release, see the git repository history: <a class="reference external" href="http://sourceforge.net/p/openocd/code/ci/v0.9.0/log/?path=">http://sourceforge.net/p/openocd/code/ci/v0.9.0/log/?path=</a></p> 2014-05-16T19:22:00+02:002014-05-16T19:22:00+02:00fercerpavtag:openocd.org,2014-05-16:/openocd-0-8-0-in-major-repositories.html

<p>A quick update on distro adoption status:</p> <p><strong>Debian</strong> unstable, <strong>Gentoo</strong>, <strong>Fedora</strong> devel and <strong>Arch GNU/Linux</strong> distributions provide their users with an up-to-date 0.8.0 package.</p> <p><strong>OS X</strong> users are covered as well: with <strong>Gentoo Prefix</strong> you can easily have either 0.8.0 or the current git version …</p>

<p>A quick update on distro adoption status:</p> <p><strong>Debian</strong> unstable, <strong>Gentoo</strong>, <strong>Fedora</strong> devel and <strong>Arch GNU/Linux</strong> distributions provide their users with an up-to-date 0.8.0 package.</p> <p><strong>OS X</strong> users are covered as well: with <strong>Gentoo Prefix</strong> you can easily have either 0.8.0 or the current git version (-9999); same about <strong>Homebrew</strong>: just update and <tt class="docutils literal">brew install <span class="pre">[--HEAD]</span> openocd</tt> (where the optional --HEAD parameter tells it to build the current git version).</p> <p>Thanks to everybody involved!</p> 2014-04-27T12:39:00+02:002014-04-27T12:39:00+02:00fercerpavtag:openocd.org,2014-04-27:/openocd-0-8-0-release.html

<p>Today I'm happy to announce the availability of OpenOCD 0.8.0 release.</p> <p>It's been almost a year since v0.7.0, and the amount of changes is impressive. The project gained 458 commits from 78 contributors all around the world; added to that countless hours that were spent on …</p>

<p>Today I'm happy to announce the availability of OpenOCD 0.8.0 release.</p> <p>It's been almost a year since v0.7.0, and the amount of changes is impressive. The project gained 458 commits from 78 contributors all around the world; added to that countless hours that were spent on reviewing, discussing, testing and bug-reporting. I'd like to take this opportunity to say &quot;thank you&quot; to everybody involved, your participation is sincerely appreciated.</p> <p>Of specific interest here were contributions directly from hardware manufacturers. During this development cycle OpenOCD received support from Andes Technology Corporation and Intel Corporation, and in both cases it was a fine collaboration following the best practices as established in the free software world. To help other manufacturers join the trend I propose we all start demanding out-of-the-box OpenOCD support from the vendors, educating them about Intel's experience.</p> <p>Please find the updated sources in the git repository and on the SF.net download area:</p> <p><a class="reference external" href="http://sourceforge.net/projects/openocd/files/openocd/0.8.0/">http://sourceforge.net/projects/openocd/files/openocd/0.8.0/</a></p> <p>Freddie Chopin has kindly provided windows binaries on his website:</p> <p><a class="reference external" href="http://www.freddiechopin.info/">http://www.freddiechopin.info/</a> &gt; Download &gt; Software &gt; OpenOCD, see <a class="reference external" href="http://www.freddiechopin.info/en/articles/34-news/92-openocd-w-wersji-080">http://www.freddiechopin.info/en/articles/34-news/92-openocd-w-wersji-080</a> for details.</p> <p>Good luck, and happy hacking!</p> <p>The release highlights are listed below:</p> <p>JTAG Layer:</p> <ul class="simple"> <li>New CMSIS-DAP driver.</li> <li>Andes AICE debug adapter support.</li> <li>New OpenJTAG driver.</li> <li>New BCM2835 (RaspberryPi) driver.</li> <li>JTAG VPI client driver (for OpenRISC Reference Platform SoC).</li> <li>Xilinx BSCAN_* for OpenRISC support.</li> <li>ST-LINKv2-1 support.</li> <li>ST-LINKv2 SWO tracing support (UART emulation).</li> <li>JLink-OB (onboard) support.</li> <li>Altera USB Blaster driver rewrite, initial Blaster II support.</li> <li>ULINK driver ported to libusb-1.0, OpenULINK build fixes.</li> <li>Support up to 64 bit IR lengths.</li> <li>SVF playback (FPGA programming) fixes.</li> <li>&quot;ftdi&quot; interface driver got extensive testing and is now recommended over the old ft2232 implementation.</li> </ul> <p>Boundary Scan:</p> <p>Target Layer:</p> <ul class="simple"> <li>New target: Andes nds32.</li> <li>New target: OpenRISC OR1K.</li> <li>New target: Intel Quark X10xx.</li> <li>MIPS EJTAG 1.5/2.0 support.</li> <li>MIPS speed improvements.</li> <li>Cortex-M, Cortex-A (MEM-AP, APB-AP) targets working with BE hosts now.</li> <li>XScale vector_catch support, reset fixes.</li> <li>dsp563xx ad-hoc breakpoint/watchpoint support.</li> <li>RTOS support for embKernel.</li> <li>Target profiling improvements.</li> <li>Memory access functions testbench.</li> </ul> <p>Flash Layer:</p> <ul class="simple"> <li>STM32 family sync with reference manuals, other bugfixes.</li> <li>STM32F401, STM32F07x support.</li> <li>Atmel SAM4L, SAMG5x support.</li> <li>Atmel AT91SAM3SD8[a,b], AT91SAM3S8[a,b,c], AT91SAM4S, AT91SAM3N0[a,b,0a,0b] support, bugfixes.</li> <li>Atmel SAMD support.</li> <li>Milandr 1986ВЕ* support.</li> <li>Kinetis KL, K21 support.</li> <li>Nuvoton NuMicro MINI5{1,2,4} support.</li> <li>Nuvoton NUC910 series support.</li> <li>NXP LPC43xx, LPC2000 fixes.</li> <li>NXP LPC800, LPC810 support.</li> <li>More ATmega parts supported.</li> <li>Fujitsu MB9Ax family support.</li> <li>EFM32 Wonder Gecko family support.</li> <li>Nordic nRF51 support.</li> </ul> <p>Board, Target, and Interface Configuration Scripts:</p> <ul class="simple"> <li>STM32W108xx generic target config.</li> <li>STM32F429 discovery board config.</li> <li>STM32 Nucleo boards configs.</li> <li>DENX M53EVK board config.</li> <li>Altera Cyclone V SoC, SoCkit config.</li> <li>New TI Launchpads board configs.</li> <li>TI am43xx devices, AM437x GP EVM, AM438x ePOS EVM board configs.</li> <li>Marvell Armada 370 family initial support.</li> <li>TI TMDX570LS31USB (TMS570, Cortex-R4) support scripts.</li> <li>Freescale FRDM-KL25Z, KL46Z board configs.</li> <li>Digilent Zedboard config.</li> <li>Asus RT-N16, Linksys WRT54GL, BT HomeHub board configs.</li> <li>Atmel Xplained initial support.</li> <li>Broadcom bcm28155_ap board config.</li> <li>TUMPA, TUMPA Lite interface configs.</li> <li>Digilent JTAG-SMT2 interface config.</li> <li>New RAM testing functions.</li> <li>Easy-to-use firmware recovery helpers targeting ordinary users with common equipment.</li> </ul> <p>Server Layer:</p> <ul class="simple"> <li>Auto-generation of GDB target description for ARMv7-M (XML support in GDB is mandatory for this architecture now), ARM4, nds32, OR1K, Quark.</li> <li>GDB File-I/O Remote Protocol extension support.</li> <li>Default GDB flashing events handlers to initialise and reset the target automatically when &quot;load&quot; is used.</li> </ul> <p>Documentation:</p> <ul class="simple"> <li>Extensive README* changes.</li> <li>The official User's Guide was proofread.</li> <li>Example cross-build script.</li> <li>RTOS documentation improvements.</li> <li>Tcl RPC documentation and examples added.</li> </ul> <p>Build and Release:</p> <ul class="simple"> <li>*BSD, OS X, clang, ARM, windows build fixes.</li> <li>New pkg-config support changes the way libusb (and other dependencies) are handled. Many adapter drivers are now selected automatically during the configure stage.</li> </ul> <p>PS: A next-release teaser: I know many people would like to see SWD support for FTDI-based adapters. It's already working really good but not yet ready for merging, the patches are available from Gerrit and it's likely they'll be ready by the next release.</p> 2014-03-31T06:40:00+02:002014-03-31T06:40:00+02:00fercerpavtag:openocd.org,2014-03-31:/openocd-0-8-0-rc1-release-candidate-is-out.html

<p>We are pleased to announce the first release candidate of the upcoming OpenOCD version.</p> <p>The source archives and release notes are available from <a class="reference external" href="http://sourceforge.net/projects/openocd/files/openocd/0.8.0-rc1/">the usual SF download locations</a>.</p> <p>Windows binary of OpenOCD 0.8.0-rc1 is kindly provided by Freddie Chopin and is available for download from his website: <a class="reference external" href="http://www.freddiechopin.info/en/download/category/10-openocd-dev/">www …</a></p>

<p>We are pleased to announce the first release candidate of the upcoming OpenOCD version.</p> <p>The source archives and release notes are available from <a class="reference external" href="http://sourceforge.net/projects/openocd/files/openocd/0.8.0-rc1/">the usual SF download locations</a>.</p> <p>Windows binary of OpenOCD 0.8.0-rc1 is kindly provided by Freddie Chopin and is available for download from his website: <a class="reference external" href="http://www.freddiechopin.info/en/download/category/10-openocd-dev/">www.freddiechopin.info</a>.</p> <p>Please post all your feedback to the <a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-devel">openocd-devel mailing list</a>.</p> 2014-01-16T20:28:00+01:002014-01-16T20:28:00+01:00ntfreaktag:openocd.org,2014-01-16:/openocd-and-gdb-for-openrisc-orconf-2013.html

<p>A talk by Franck Jullien on using OpenOCD and GDB for OpenRISC.</p> <iframe src="https://www.youtube.com/embed/zcDVcXE5-sE" frameborder="0" width="420" height="236"></iframe>

<p>A talk by Franck Jullien on using OpenOCD and GDB for OpenRISC.</p> <iframe src="https://www.youtube.com/embed/zcDVcXE5-sE" frameborder="0" width="420" height="236"></iframe>2013-05-05T20:31:00+02:002013-05-05T20:31:00+02:00freddie-chopintag:openocd.org,2013-05-05:/openocd-0-7-0-released.html

<p>After almost 7 months since previous 0.6.1 version, new 0.7.0 release is out! Source packages are available to download from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.7.0/">SourceForge</a>. If you use <em>Windows</em> and don't want to build the executable yourself,&nbsp;Freddie Chopin provides binaries on his personal <a class="reference external" href="http://www.freddiechopin.info/">website</a>.</p> <p>Here is the NEWS file …</p>

<p>After almost 7 months since previous 0.6.1 version, new 0.7.0 release is out! Source packages are available to download from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.7.0/">SourceForge</a>. If you use <em>Windows</em> and don't want to build the executable yourself,&nbsp;Freddie Chopin provides binaries on his personal <a class="reference external" href="http://www.freddiechopin.info/">website</a>.</p> <p>Here is the NEWS file for this release, which highlights the most important changes:</p> <p>This file includes highlights of the changes made in the OpenOCD source archive release. See the repository history for details about what changed, including bug fixes and other issues not mentioned here.</p> <p>JTAG Layer:</p> <ul class="simple"> <li>New TI ICDI adapter support.</li> <li>Support Latest OSBDM firmware.</li> <li>Improved MIPS EJTAG Support.</li> </ul> <p>Boundary Scan:</p> <p>Target Layer:</p> <ul class="simple"> <li>New ARMv7R and Cortex-R4 support.</li> <li>Added ChibiOS/RT support.</li> </ul> <p>Flash Layer:</p> <ul class="simple"> <li>New NXP LPC1850 support.</li> <li>New NXP LPC4300 support.</li> <li>New NXP SPIFI support.</li> <li>New Energy Micro EFM32 support.</li> <li>New ST STM32W support.</li> <li>New ST STM32f2 write protection and lock/unlock support.</li> <li>Ability to override STM32 flash bank size.</li> </ul> <p>Board, Target, and Interface Configuration Scripts:</p> <ul class="simple"> <li>Support Freescale i.MX6 series targets.</li> </ul> <p>Documentation:</p> <ul class="simple"> <li>New MIPS debugging info.</li> </ul> <p>Build and Release:</p> <p>For more details about what has changed since the last release, see the git repository history. With gitweb, you can browse that in various levels of detail.</p> <p>For older NEWS, see the NEWS files associated with each release (i.e. NEWS-&lt;version&gt;).</p> <p>For more information about contributing test reports, bug fixes, or new features and device support, please read the new Developer Manual (or the BUGS and PATCHES.txt files in the source archive).</p> 2013-01-28T15:26:00+01:002013-01-28T15:26:00+01:00ntfreaktag:openocd.org,2013-01-28:/openocd-hardware-debugging-and-more-elce-2012.html

<p>A talk from Peter Stuge on using OpenOCD to debug embedded systems.</p> <iframe width="420" height="236" src="https://www.youtube.com/embed/7ZgZplei6B4" frameborder="0"></iframe>

<p>A talk from Peter Stuge on using OpenOCD to debug embedded systems.</p> <iframe width="420" height="236" src="https://www.youtube.com/embed/7ZgZplei6B4" frameborder="0"></iframe>2012-11-16T10:24:00+01:002012-11-16T10:24:00+01:00ntfreaktag:openocd.org,2012-11-16:/sourceforge-upgrade.html

<p>We have upgraded OpenOCD to the new SourceForge platform(Allura), part of that change is a move in the git repo url.</p> <p><a class="reference external" href="https://sourceforge.net/p/openocd/code/">https://sourceforge.net/p/openocd/code/</a></p> <div class="line-block"> <div class="line">original url is:</div> <div class="line">git://openocd.git.sourceforge.net/gitroot/openocd/openocd</div> <div class="line">and this has changed to:</div> <div class="line">git://git.code.sf.net/p …</div></div>

<p>We have upgraded OpenOCD to the new SourceForge platform(Allura), part of that change is a move in the git repo url.</p> <p><a class="reference external" href="https://sourceforge.net/p/openocd/code/">https://sourceforge.net/p/openocd/code/</a></p> <div class="line-block"> <div class="line">original url is:</div> <div class="line">git://openocd.git.sourceforge.net/gitroot/openocd/openocd</div> <div class="line">and this has changed to:</div> <div class="line">git://git.code.sf.net/p/openocd/code</div> </div> <div class="line-block"> <div class="line">So you will either need to re-clone or manually update your .git/config</div> <div class="line">git config remote.origin.url git://git.code.sf.net/p/openocd/code should do the trick</div> </div> <p>Hopefully nothing has broken in the update.</p> 2012-10-07T14:25:00+02:002012-10-07T14:25:00+02:00freddie-chopintag:openocd.org,2012-10-07:/openocd-0-6-1-bugfix-release.html

<p>Today OpenOCD 0.6.1 bugfix release was published on <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.6.1/">project's download area on SourceForge</a>. Appropriate changes were also committed to GIT repository.</p> <p>This release addresses serious regression in 0.6.0 and 0.6.0-rc2 releases which caused some functionalities to work correctly only on the first run - all …</p>

<p>Today OpenOCD 0.6.1 bugfix release was published on <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.6.1/">project's download area on SourceForge</a>. Appropriate changes were also committed to GIT repository.</p> <p>This release addresses serious regression in 0.6.0 and 0.6.0-rc2 releases which caused some functionalities to work correctly only on the first run - all following operations would fail until OpenOCD would be restarted. Some of affected modules:</p> <ul class="simple"> <li>lpc2000 flash driver (for LPC2xxx and LPC17xx chips),</li> <li>mips_m4k fast data (for MIPS M4k chips),</li> <li>feroceon DCC,</li> <li>arm_io NAND flash driver,</li> <li>arm7_9 DCC.</li> </ul> <p>Last unaffected release (of course excluding 0.6.1) is 0.6.0-rc1. All users of affected releases are encouraged to update their version of OpenOCD.</p> <p>Additionally this release includes following fixes:</p> <ul class="simple"> <li>fix of handling Hi-Z state in direct connections in new ftdi driver,</li> <li>fix of handling RCLK in new ftdi driver,</li> <li>improvements to config files using new ftdi driver,</li> <li>fix for sector erase for AT91SAM4S chips,</li> <li>fix of TAPID in STM32F3 config script,</li> <li>support for STM32F3 Rev 2 flash,</li> <li>support for STM32F3-DISCOVERY board.</li> </ul> <p>As usual, Freddie Chopin has provided Window's binaries on <a class="reference external" href="http://www.freddiechopin.info/">his site</a>.</p> 2012-10-02T10:07:00+02:002012-10-02T10:07:00+02:00ntfreaktag:openocd.org,2012-10-02:/hackaday-arm-on-chip-debugging-demonstration.html

<iframe src="https://www.youtube.com/embed/NSVOuHToJ6c" frameborder="0" width="420" height="236"></iframe><p>Full article here - <a class="reference external" href="https://hackaday.com/2012/09/27/beginners-look-at-on-chip-debugging/">https://hackaday.com/2012/09/27/beginners-look-at-on-chip-debugging/</a>.</p>

<iframe src="https://www.youtube.com/embed/NSVOuHToJ6c" frameborder="0" width="420" height="236"></iframe><p>Full article here - <a class="reference external" href="https://hackaday.com/2012/09/27/beginners-look-at-on-chip-debugging/">https://hackaday.com/2012/09/27/beginners-look-at-on-chip-debugging/</a>.</p> 2012-09-07T10:35:00+02:002012-09-07T10:35:00+02:00freddie-chopintag:openocd.org,2012-09-07:/final-openocd-0-6-0-is-out.html

<p>It took 13 months without 2 days this time, but here it is! Packages with sourcecode of new stable release of OpenOCD - 0.6.0 - are available for you to download from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.6.0/">sourceforge's Download area</a>. If you're using Windows, you may check out <a class="reference external" href="http://www.freddiechopin.info">Freddie Chopin's website</a> to download binaries for …</p>

<p>It took 13 months without 2 days this time, but here it is! Packages with sourcecode of new stable release of OpenOCD - 0.6.0 - are available for you to download from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.6.0/">sourceforge's Download area</a>. If you're using Windows, you may check out <a class="reference external" href="http://www.freddiechopin.info">Freddie Chopin's website</a> to download binaries for this system.</p> <p>Here is the NEWS file for this release, which highlights most important changes:</p> <p>This file includes highlights of the changes made in the&nbsp;OpenOCD source archive release. See the&nbsp;repository history for details about what changed, including&nbsp;bugfixes and other issues not mentioned here.</p> <div class="line-block"> <div class="line"><strong>JTAG Layer:</strong></div> <div class="line">New STLINK V1/V2 JTAG/SWD adapter support.</div> <div class="line">New OSJTAG adapter support.</div> <div class="line">New Tincantools Flyswatter2 support.</div> <div class="line">Improved ULINK driver.</div> <div class="line">Improved RLINK driver.</div> <div class="line">Support for adapters based on FT232H chips.</div> <div class="line">New experimental driver for FTDI based adapters, using libusb-1.0 in asynchronous mode.</div> </div> <p><strong>Boundary Scan:</strong></p> <div class="line-block"> <div class="line"><strong>Target Layer:</strong></div> <div class="line">New Cortex-M0 support.</div> <div class="line">New Cortex-M4 support.</div> <div class="line">Improved Working area algorithm.</div> <div class="line">New RTOS support. Currently linux, FreeRTOS, ThreadX and eCos.</div> <div class="line">Connecting under reset to Cortex-Mx and MIPS chips.</div> </div> <div class="line-block"> <div class="line"><strong>Flash Layer:</strong></div> <div class="line">New SST39WF1601 support.</div> <div class="line">New EN29LV800BB support.</div> <div class="line">New async algorithm support for selected targets, stm32, stellaris and pic32.</div> <div class="line">New Atmel SAM3S, SAM3N support.</div> <div class="line">New ST STM32L support.</div> <div class="line">New Microchip PIC32MX1xx/2xx support.</div> <div class="line">New Freescale Kinetis K40 support.</div> </div> <div class="line-block"> <div class="line"><strong>Board, Target, and Interface Configuration Scripts:</strong></div> <div class="line">Support Dangerous Prototypes Bus Blaster.</div> <div class="line">Support ST SPEAr Family.</div> <div class="line">Support Gumstix Verdex boards.</div> <div class="line">Support TI Beaglebone.</div> </div> <div class="line-block"> <div class="line"><strong>Documentation:</strong></div> <div class="line">Improved HACKING info for submitting patches.</div> <div class="line">Fixed numerous broken links.</div> </div> <p><strong>Build and Release:</strong></p> <p>For more details about what has changed since the last release,&nbsp;see the git repository history. With gitweb, you can browse that&nbsp;in various levels of detail.</p> <p>For older NEWS, see the NEWS files associated with each release&nbsp;(i.e. NEWS-&lt;version&gt;).</p> <p>For more information about contributing test reports, bug fixes, or new&nbsp;features and device support, please read the new Developer Manual (or&nbsp;the BUGS and PATCHES.txt files in the source archive).</p> 2012-08-29T10:09:00+02:002012-08-29T10:09:00+02:00freddie-chopintag:openocd.org,2012-08-29:/openocd-v0-6-0-rc2-released.html

<p>Second release candidate for version 0.6.0 of OpenOCD was just released. Repository was updated and archives with source code uploaded for you to <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.6.0-rc2/">sourceforge</a>. As usually Windows users can find a suitable binary on <a class="reference external" href="http://www.freddiechopin.info/">Freddie Chopin's website</a>.</p> <p>Final 0.6.0 is scheduled to be released on 6th …</p>

<p>Second release candidate for version 0.6.0 of OpenOCD was just released. Repository was updated and archives with source code uploaded for you to <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.6.0-rc2/">sourceforge</a>. As usually Windows users can find a suitable binary on <a class="reference external" href="http://www.freddiechopin.info/">Freddie Chopin's website</a>.</p> <p>Final 0.6.0 is scheduled to be released on 6th of September 2012 - if no&nbsp;problems with -rc2 will be found. In case a need of extending this&nbsp;period appears, the final release would be possible after 23rd of September.</p> <p>Happy debugging! Remember to post info on potential problems to mailing list!</p> 2012-08-02T21:57:00+02:002012-08-02T21:57:00+02:00freddie-chopintag:openocd.org,2012-08-02:/openocd-v0-6-0-rc1-released.html

<p>We are pleased to announce that first release candidate for version 0.6.0&nbsp;of OpenOCD was released. Relevant changes have been done to the&nbsp;repository, the source packages can be downloaded from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.6.0-rc1/">sourceforge</a>.&nbsp;Windows binary is already available on <a class="reference external" href="http://www.freddiechopin.info">Freddie Chopin's website</a>.</p> <p>If no problems occur (no regressions / bugs …</p>

<p>We are pleased to announce that first release candidate for version 0.6.0&nbsp;of OpenOCD was released. Relevant changes have been done to the&nbsp;repository, the source packages can be downloaded from <a class="reference external" href="https://sourceforge.net/projects/openocd/files/openocd/0.6.0-rc1/">sourceforge</a>.&nbsp;Windows binary is already available on <a class="reference external" href="http://www.freddiechopin.info">Freddie Chopin's website</a>.</p> <p>If no problems occur (no regressions / bugs will be found), the rc1&nbsp;phase may be short, say 2 weeks. In case of problems the rc1 phase may&nbsp;be extended, or further rc phases may be done.</p> <p>So start testing and report back if you find any problems!</p> 2012-05-11T11:19:00+02:002012-05-11T11:19:00+02:00ntfreaktag:openocd.org,2012-05-11:/user-mailing-list.html

<p>To better help the user resolve issues with using OpenOCD, we have created a <a class="reference external" href="https://lists.sourceforge.net/mailman/listinfo/openocd-user">openocd-user</a> mailing list. Hopefully with user input we can make OpenOCD a smoother experience for all.</p> <p>For info other OpenOCD mailing lists can be found <a class="reference external" href="http://openocd.sourceforge.net/discussion/mailing-lists/">here</a>.</p>

<p>To better help the user resolve issues with using OpenOCD, we have created a <a class="reference external" href="https://lists.sourceforge.net/mailman/listinfo/openocd-user">openocd-user</a> mailing list. Hopefully with user input we can make OpenOCD a smoother experience for all.</p> <p>For info other OpenOCD mailing lists can be found <a class="reference external" href="http://openocd.sourceforge.net/discussion/mailing-lists/">here</a>.</p> 2012-05-11T10:45:00+02:002012-05-11T10:45:00+02:00ntfreaktag:openocd.org,2012-05-11:/using-openocd-with-the-beaglebone.html

<p>For those interested here is a new tutorial on using BeagleBone with OpenOCD.</p> <p><a class="reference external" href="http://www.mattlmassey.com/2012/04/26/using-openocd-with-the-beaglebone/">http://www.mattlmassey.com/2012/04/26/using-openocd-with-the-beaglebone/</a></p>

<p>For those interested here is a new tutorial on using BeagleBone with OpenOCD.</p> <p><a class="reference external" href="http://www.mattlmassey.com/2012/04/26/using-openocd-with-the-beaglebone/">http://www.mattlmassey.com/2012/04/26/using-openocd-with-the-beaglebone/</a></p> 2012-04-20T21:14:00+02:002012-04-20T21:14:00+02:00ntfreaktag:openocd.org,2012-04-20:/linaro-connect-q4-11-jtag-flyswatter-2-and-beacon-board-demo.html

<iframe width="420" height="243" src="https://www.youtube.com/embed/FhMhH5kEcGw" frameborder="0" allowfullscreen></iframe>

<iframe width="420" height="243" src="https://www.youtube.com/embed/FhMhH5kEcGw" frameborder="0" allowfullscreen></iframe>2012-04-20T20:56:00+02:002012-04-20T20:56:00+02:00ntfreaktag:openocd.org,2012-04-20:/kernel-debugging.html

<iframe width="420" height="243" src="https://www.youtube.com/embed/JzMj_iU4vxs" frameborder="0" allowfullscreen></iframe>

<iframe width="420" height="243" src="https://www.youtube.com/embed/JzMj_iU4vxs" frameborder="0" allowfullscreen></iframe>2012-01-03T10:13:00+01:002012-01-03T10:13:00+01:00ntfreaktag:openocd.org,2012-01-03:/mailing-lists-working.html

<p>All the mailing lists are back online now - all i can say is it took a lot longer than it should have (sf).</p>

<p>All the mailing lists are back online now - all i can say is it took a lot longer than it should have (sf).</p> 2011-11-29T10:49:00+01:002011-11-29T10:49:00+01:00ntfreaktag:openocd.org,2011-11-29:/mailing-list-issues.html

<div class="line-block"> <div class="line">We are currently having issues with our mailing lists hosted on SF:</div> <div class="line"><a class="reference external" href="https://sourceforge.net/mail/?group_id=274635">https://sourceforge.net/mail/?group_id=274635</a></div> </div> <p>For some reason they have been deleted, SF are looking into it and hopefully we will be back online soon.</p>

<div class="line-block"> <div class="line">We are currently having issues with our mailing lists hosted on SF:</div> <div class="line"><a class="reference external" href="https://sourceforge.net/mail/?group_id=274635">https://sourceforge.net/mail/?group_id=274635</a></div> </div> <p>For some reason they have been deleted, SF are looking into it and hopefully we will be back online soon.</p> 2011-11-08T14:22:00+01:002011-11-08T14:22:00+01:00ntfreaktag:openocd.org,2011-11-08:/new-helpers.html

<p>We have two new helpers to the OpenOCD team - <a class="reference external" href="http://code.google.com/p/gerrit/">Gerrit</a> and <a class="reference external" href="http://jenkins-ci.org/">Jenkins</a>.</p> <div class="line-block"> <div class="line">Gerrit is a web based review system that makes reviewing patches simpler for all - especially project devs.</div> <div class="line"><a class="reference external" href="http://openocd.zylin.com/">Here</a> is the link for our Gerrit server</div> </div> <div class="line-block"> <div class="line">Jenkins is a continuous integration server, and is being used to test any …</div></div>

<p>We have two new helpers to the OpenOCD team - <a class="reference external" href="http://code.google.com/p/gerrit/">Gerrit</a> and <a class="reference external" href="http://jenkins-ci.org/">Jenkins</a>.</p> <div class="line-block"> <div class="line">Gerrit is a web based review system that makes reviewing patches simpler for all - especially project devs.</div> <div class="line"><a class="reference external" href="http://openocd.zylin.com/">Here</a> is the link for our Gerrit server</div> </div> <div class="line-block"> <div class="line">Jenkins is a continuous integration server, and is being used to test any patches uploaded to Gerrit. This again makes our life simpler as some of the trivial tasks are now automated.</div> <div class="line"><a class="reference external" href="http://openocd.zylin.com/jenkins/">Here</a> is the link for our Jenkins server.</div> </div> <p>The server has been kindly donated by the kind folks at <a class="reference external" href="http://www.zylin.com/">Zylin</a>.</p> <p>In the long term this will hopefully mean a more stable OpenOCD.</p> 2011-11-08T14:06:00+01:002011-11-08T14:06:00+01:00ntfreaktag:openocd.org,2011-11-08:/mailing-lists-news.html

<p>All mailing lists have now moved over to <a class="reference external" href="https://sourceforge.net/projects/openocd/">sourceforge</a>, update any spam filters asap. Users that were subscribed to the Berlios lists have been migrated over, so you should have nothing todo.</p> <p><a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-devel">https://lists.sourceforge.net/lists/listinfo/openocd-devel</a></p> <p><a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-commit">https://lists.sourceforge.net/lists/listinfo/openocd-commit</a></p>

<p>All mailing lists have now moved over to <a class="reference external" href="https://sourceforge.net/projects/openocd/">sourceforge</a>, update any spam filters asap. Users that were subscribed to the Berlios lists have been migrated over, so you should have nothing todo.</p> <p><a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-devel">https://lists.sourceforge.net/lists/listinfo/openocd-devel</a></p> <p><a class="reference external" href="https://lists.sourceforge.net/lists/listinfo/openocd-commit">https://lists.sourceforge.net/lists/listinfo/openocd-commit</a></p> 2011-10-05T21:30:00+02:002011-10-05T21:30:00+02:00ntfreaktag:openocd.org,2011-10-05:/aurevoir.html

<p>Seems <a class="reference external" href="http://developer.berlios.de/projects/openocd/">Berlios</a> is closing on the 31/12/2011 :-(</p> <p>This means the website (this) and the mailing lists will be moving to <a class="reference external" href="https://sourceforge.net/projects/openocd/">sourceforge</a> - stay tuned for details.</p>

<p>Seems <a class="reference external" href="http://developer.berlios.de/projects/openocd/">Berlios</a> is closing on the 31/12/2011 :-(</p> <p>This means the website (this) and the mailing lists will be moving to <a class="reference external" href="https://sourceforge.net/projects/openocd/">sourceforge</a> - stay tuned for details.</p> 2011-08-09T11:00:00+02:002011-08-09T11:00:00+02:00ntfreaktag:openocd.org,2011-08-09:/openocd-v0-5-0-released.html

<p>It has been a while since an official OpenOCD release, but it is finally here !!</p> <p>Many thanks to all that helped get this release out the door - in the future we are planning to release on a more regular schedule.</p> <p>Here is the NEWS file relating to this release:</p> <p>This …</p>

<p>It has been a while since an official OpenOCD release, but it is finally here !!</p> <p>Many thanks to all that helped get this release out the door - in the future we are planning to release on a more regular schedule.</p> <p>Here is the NEWS file relating to this release:</p> <p>This file includes highlights of the changes made in the OpenOCD 0.5.0 source archive release.&nbsp; See the repository history for details about what changed, including bugfixes and other issues not mentioned here.</p> <p><strong>JTAG Layer:</strong></p> <ul class="simple"> <li>New driver for &quot;Bus Pirate&quot;</li> <li>Rename various commands so they're not JTAG-specific</li> </ul> <div class="line-block"> <div class="line">There are migration procedures for most of these, but you should convert your scripts to the new names, since those procedures will not be around forever.</div> <div class="line">- jtag jinterface ... is now adapter_name ...</div> <div class="line">- jtag_khz ... is now adapter_khz ...</div> <div class="line">- jtag_nsrst_delay ... is now adapter_nsrst_delay ...</div> <div class="line">- jtag_nsrst_assert_width ... is now adapter_nsrst_assert_width ...</div> </div> <ul class="simple"> <li>Support Voipac VPACLink JTAG Adapter.</li> </ul> <p><strong>Boundary Scan:</strong></p> <p>Transport framework core ... supporting future work for SWD, SPI, and other non-JTAG ways to debug targets or program flash.</p> <p><strong>Target Layer:</strong></p> <ul class="simple"> <li><strong>ARM:</strong> - basic semihosting support for ARMv7M. - renamed &quot;armv7m&quot; command prefix as &quot;arm&quot;</li> <li><strong>MIPS:</strong> - &quot;ejtag_srst&quot; variant removed. The same functionality is obtained by using &quot;reset_config none&quot;. - added PIC32MX software reset support, this means srst is not required to be connected anymore.</li> <li><strong>OTHER:</strong> - preliminary AVR32 AP7000 support.</li> </ul> <p><strong>Flash Layer:</strong></p> <ul class="simple"> <li>New &quot;stellaris recover&quot; command, implements the procedure to recover locked devices (restoring non-volatile state to the factory defaults, including erasing the flash and its protection bits, and possibly re-enabling hardware debugging).</li> <li>PIC32MX now uses algorithm for flash programming, this has increased the performance by approx 96%.</li> <li>New 'pic32mx unlock' cmd to remove readout protection.</li> <li>New STM32 Value Line Support.</li> <li>New 'virtual' flash driver, used to associate other addresses with a flash bank. See pic32mx.cfg for usage.</li> <li>New iMX27 NAND flash controller driver.</li> </ul> <p><strong>Board, Target, and Interface Configuration Scripts:</strong></p> <ul class="simple"> <li>Support IAR LPC1768 kickstart board (by Olimex)</li> <li>Support Voipac PXA270/PXA270M module.</li> <li>New $PARPORTADDR tcl variable used to change default parallel port address used.</li> <li>Remove lm3s811.cfg; use &quot;stellaris.cfg&quot; instead</li> </ul> <p><strong>Core Jim/TCL Scripting:</strong></p> <ul class="simple"> <li>New &quot;add_script_search_dir&quot; command, behaviour is the same as the &quot;-s&quot; cmd line option.</li> </ul> <p><strong>Documentation:</strong></p> <p>None.** **</p> <p><strong>Build and Release:</strong></p> <p>None.** **</p> <p>For more details about what has changed since the last release, see the git repository history.&nbsp; With gitweb, you can browse that in various levels of detail.</p> <p>For older NEWS, see the NEWS files associated with each release (i.e. NEWS-&lt;version&gt;).</p> <p>For more information about contributing test reports, bug fixes, or new features and device support, please read the new Developer Manual (or the BUGS and PATCHES.txt files in the source archive).</p> 2010-02-22T14:36:00+01:002010-02-22T14:36:00+01:00ntfreaktag:openocd.org,2010-02-22:/openocd-v040-released.html

<p>v0.4.0 highlights, taken from NEWS:</p> <p><strong>JTAG Layer:</strong></p> <ul class="simple"> <li>Support KT-Link JTAG adapter.</li> <li>Support USB-JTAG, Altera USB-Blaster and compatibles.</li> </ul> <p><strong>Target Layer:</strong></p> <ul class="simple"> <li>General<ul> <li>Removed commands which have been obsolete for at least a year (from both documentation and, sometimes, code).</li> <li>new &quot;reset-assert&quot; event, for systems without SRST</li> </ul> </li> <li><strong>ARM</strong><ul> <li>supports &quot;reset-assert&quot; event …</li></ul></li></ul>

<p>v0.4.0 highlights, taken from NEWS:</p> <p><strong>JTAG Layer:</strong></p> <ul class="simple"> <li>Support KT-Link JTAG adapter.</li> <li>Support USB-JTAG, Altera USB-Blaster and compatibles.</li> </ul> <p><strong>Target Layer:</strong></p> <ul class="simple"> <li>General<ul> <li>Removed commands which have been obsolete for at least a year (from both documentation and, sometimes, code).</li> <li>new &quot;reset-assert&quot; event, for systems without SRST</li> </ul> </li> <li><strong>ARM</strong><ul> <li>supports &quot;reset-assert&quot; event (except on Cortex-M3)</li> <li>renamed &quot;armv4_5&quot; command prefix as &quot;arm&quot;</li> <li>recognizes TrustZone &quot;Secure Monitor&quot; mode</li> <li>&quot;arm regs&quot; command output changed</li> <li>register names use &quot;sp&quot; not &quot;r13&quot;</li> <li>add top-level &quot;mcr&quot; and &quot;mrc&quot; commands, replacing various core-specific operations</li> <li>basic semihosting support (ARM7/ARM9 only, for now)</li> </ul> </li> <li>ARM11 should act much more like other ARM cores:<ul> <li>Preliminary ETM and ETB hookup</li> <li>accelerated &quot;flash erase_check&quot;</li> <li>accelerated GDB memory checksum</li> <li>support &quot;arm regs&quot; command</li> <li>can access all core modes and registers</li> <li>watchpoint support</li> <li>Shares some core debug code with Cortex-A8</li> </ul> </li> <li>Cortex-A8 should act much more like other ARM cores:<ul> <li>support &quot;arm regs&quot; command</li> <li>can access all core modes and registers</li> <li>watchpoint support</li> <li>Shares some core debug code with ARM11</li> </ul> </li> <li>Cortex-M3<ul> <li><ul class="first"> <li>Exposed DWT registers like cycle counter</li> </ul> </li> <li>vector_catch settings not clobbered by resets</li> <li>no longer interferes with firmware's fault handling</li> </ul> </li> <li>ETM, ETB<ul> <li>&quot;trigger_percent&quot; command moved from ETM to ETB</li> <li>&quot;etm trigger_debug&quot; command added</li> </ul> </li> <li>MIPS now uses fastdata writes Freescale</li> </ul> <p><strong>Flash Layer:</strong></p> <ul class="simple"> <li>'flash bank' and 'nand device' take &lt;bank_name&gt; as first argument. With this, flash/NAND commands allow referencing banks by name:<ul> <li>&lt;bank_name&gt;: reference the bank with its defined name</li> <li>&lt;driver_name&gt;[.N]: reference the driver's Nth bank</li> </ul> </li> <li>New 'nand verify' command to check bank against an image file.</li> <li>The &quot;flash erase_address&quot; command now rejects partial sectors; previously it would silently erase extra data.&nbsp; If you want to erase the rest of the first and/or last sectors instead of failing, you must pass an explicit &quot;pad&quot; flag.</li> <li>New at91sam9 NAND controller driver.</li> <li>New s3c64xx NAND controller driver.</li> </ul> <p><strong>Board, Target, and Interface Configuration Scripts</strong>:</p> <ul class="simple"> <li>ARM9 ... ETM and ETB hookup for iMX2* targets</li> <li>Add $HOME/.openocd to the search path.</li> <li>Handle Rev C of LM3S811 eval boards. ... <em>use &quot;luminary-lm3s811.cfg&quot; only for older boards</em>, use &quot;luminary.cfg&quot; for RevC and newer</li> </ul> <p><strong>Core Jim/TCL Scripting:</strong></p> <ul class="simple"> <li>New 'usage' command to provide terse command help.</li> <li>Improved command 'help' command output (sorted and indented).</li> <li>Improved command handling:<ul> <li>Most boolean settings now accept any of the following: on/off, enable/disable, true/false, yes/no, 1/0</li> <li>More error checking and reporting.</li> </ul> </li> </ul> <div class="line-block"> <div class="line"><strong>Documentation:</strong></div> <div class="line">New built-in command development documentation and primer.</div> </div> <div class="line-block"> <div class="line"><strong>Build and Release:</strong></div> <div class="line">Use --enable-doxygen-pdf to build PDF developer documentation.</div> <div class="line">Consider upgrading to libftdi 0.17 if you use that library; it</div> <div class="line">includes bugfixes which improve FT2232H support.</div> </div> 2009-12-16T00:10:00+01:002009-12-16T00:10:00+01:00oharboetag:openocd.org,2009-12-16:/openocd-git-server-only.html

<p>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.</p> <p>The <a class="reference external" href="http://openocd.sourceforge.net/">http://openocd.sourceforge.net …</a></p>

<p>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.</p> <p>The <a class="reference external" href="http://openocd.sourceforge.net/">http://openocd.sourceforge.net/</a> git server has been the official development git repository for a few months now.</p> <p>Øyvind Harboe</p> 2009-10-29T07:04:00+01:002009-10-29T07:04:00+01:00zwelchtag:openocd.org,2009-10-29:/openocd-030-rc.html

<div class="line-block"> <div class="line">OpenOCD has released its first -rc packages for testing: 0.3.0-rc0.</div> <div class="line">This version has been tagged in Git as 'v0.3.0-rc0'.</div> </div> <p>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 …</p>

<div class="line-block"> <div class="line">OpenOCD has released its first -rc packages for testing: 0.3.0-rc0.</div> <div class="line">This version has been tagged in Git as 'v0.3.0-rc0'.</div> </div> <p>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.</p> <p>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.</p> <p>Please take this opportunity to mention any outstanding issues, or send a work of thanks to the folks that contributed to release. Thanks!</p> 2009-10-09T03:11:00+02:002009-10-09T03:11:00+02:00zwelchtag:openocd.org,2009-10-09:/simplified-openocd-infrastructure.html

<p>The OpenOCD project has retired those BerliOS web site services that received insufficient attention from developers:</p> <ul class="simple"> <li>Bug Tracker and Bug Dependency List, Support, Forums, Patch Manager, and Feature Requests: post to the mailing list</li> <li>Screenshots: such content can be moved to our web pages</li> <li>Doc Manager: we provide access to …</li></ul>

<p>The OpenOCD project has retired those BerliOS web site services that received insufficient attention from developers:</p> <ul class="simple"> <li>Bug Tracker and Bug Dependency List, Support, Forums, Patch Manager, and Feature Requests: post to the mailing list</li> <li>Screenshots: such content can be moved to our web pages</li> <li>Doc Manager: we provide access to our Doxygen HTML</li> <li>Donations: this appears to be a &quot;WONT FIX&quot; with BerliOS</li> </ul> <p>These steps simplify the OpenOCD infrastructure considerably, leaving the following services hosted on their systems:</p> <ul class="simple"> <li>Mailing Lists</li> <li>File Releases</li> <li>WordPress (you are here)</li> <li>Subversion (legacy only)</li> </ul> <p>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.</p> 2009-10-08T05:02:00+02:002009-10-08T05:02:00+02:00zwelchtag:openocd.org,2009-10-08:/openocd-switches-from-berlios-svn-to-sfnet-git.html

<p>After a recent BerliOS service outage, the OpenOCD maintainers decided to switch the project version control system from Subversion to GIT.&nbsp; 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 …</p>

<p>After a recent BerliOS service outage, the OpenOCD maintainers decided to switch the project version control system from Subversion to GIT.&nbsp; 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 <a class="reference external" href="http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=summary">SF.net</a>, we have created an <a class="reference external" href="http://repo.or.cz/w/openocd.git">official mirror</a> on repo.or.cz for users behind firewalls.</p> <p>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.</p> 2009-07-15T10:35:00+02:002009-07-15T10:35:00+02:00zwelchtag:openocd.org,2009-07-15:/openocd-020-released.html

<p>The OpenOCD Project has produced its 0.2.0 source code release. The <a class="reference external" href="http://developer.berlios.de/project/shownotes.php?release_id=16455">summary of changes</a> since the last release may be found in the NEWS file. You may <a class="reference external" href="http://developer.berlios.de/project/showfiles.php?group_id=4148&amp;release_id=16455">download the source archives</a> from the BerliOS website.</p> <p>Beyond some new features and numerous bug fixes, this release reflects significant work …</p>

<p>The OpenOCD Project has produced its 0.2.0 source code release. The <a class="reference external" href="http://developer.berlios.de/project/shownotes.php?release_id=16455">summary of changes</a> since the last release may be found in the NEWS file. You may <a class="reference external" href="http://developer.berlios.de/project/showfiles.php?group_id=4148&amp;release_id=16455">download the source archives</a> from the BerliOS website.</p> <p>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.</p> <p>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.</p> <p>Finally, the OpenOCD project will no longer distribute binary packages or installers. The OpenOCD 0.1.0 installer was removed due to <a class="reference external" href="https://lists.berlios.de/pipermail/openocd-development/2009-June/007971.html">licensing violations</a> 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 <a class="reference external" href="https://lists.berlios.de/pipermail/openocd-development/2009-July/009518.html">provided guidance</a> and support for the OpenOCD community. Future GPL violations should be reported to the developer mailing list, the maintainers, or the SFLC.</p> 2009-02-13T12:37:00+01:002009-02-13T12:37:00+01:00ntfreaktag:openocd.org,2009-02-13:/openocd-010-released.html

<p>We have finally got around to making our first release.</p> <div class="line-block"> <div class="line">The src and binaries for this release can be found at the following url:</div> <div class="line"><a class="reference external" href="http://developer.berlios.de/project/showfiles.php?group_id=4148">http://developer.berlios.de/project/showfiles.php?group_id=4148</a></div> </div>

<p>We have finally got around to making our first release.</p> <div class="line-block"> <div class="line">The src and binaries for this release can be found at the following url:</div> <div class="line"><a class="reference external" href="http://developer.berlios.de/project/showfiles.php?group_id=4148">http://developer.berlios.de/project/showfiles.php?group_id=4148</a></div> </div> 2008-12-19T19:37:00+01:002008-12-19T19:37:00+01:00ntfreaktag:openocd.org,2008-12-19:/openocd-discussion.html

<p>A new section has been added to the website - <a class="reference external" href="http://openocd.berlios.de/web/?page_id=65">Discussion</a></p> <p>This should help users get info and help on using OpenOCD.</p>

<p>A new section has been added to the website - <a class="reference external" href="http://openocd.berlios.de/web/?page_id=65">Discussion</a></p> <p>This should help users get info and help on using OpenOCD.</p> 2008-11-21T00:54:00+01:002008-11-21T00:54:00+01:00ntfreaktag:openocd.org,2008-11-21:/openocd-documentation.html

<div class="line-block"> <div class="line">The OpenOCD manual is now available online in pdf and html formats - <a class="reference external" href="http://openocd.berlios.de/web/?page_id=54">online docs</a></div> <div class="line">The docs are generated from the svn repository and will always relate to the latest version available.</div> </div>

<div class="line-block"> <div class="line">The OpenOCD manual is now available online in pdf and html formats - <a class="reference external" href="http://openocd.berlios.de/web/?page_id=54">online docs</a></div> <div class="line">The docs are generated from the svn repository and will always relate to the latest version available.</div> </div> 2008-10-12T19:46:00+02:002008-10-12T19:46:00+02:00oharboetag:openocd.org,2008-10-12:/openocd-is-alive-and-well.html

<p>OpenOCD is alive and well.</p> <p>However, you won't find any news here about OpenOCD. For that you have to go to the openocd development mailing list.</p> <p>svn version 1000 was committed a while ago... In addition to new features such as improved scripting, new targets(MIPS particularly), there is a …</p>

<p>OpenOCD is alive and well.</p> <p>However, you won't find any news here about OpenOCD. For that you have to go to the openocd development mailing list.</p> <p>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.</p> <p>I'll be cleaning up old and misleading information on this web site now...</p> <p>Øyvind Harboe</p> 2008-02-11T21:05:00+01:002008-02-11T21:05:00+01:00ntfreaktag:openocd.org,2008-02-11:/loooooooooooooong-time-no-news.html

<p>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 …</p>

<p>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!</p> <p>With this posting I primarily want to thank those people that keep the OpenOCD alive while I'm busy with other things.</p> <p>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 <a class="reference external" href="http://www.yagarto.de">Yagarto</a> page, and testing all that new stuff on the boards and programmers he has access to. Thanks a lot Michael!</p> <p>Ø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!</p> <p>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 &quot;svn add&quot; new files that come with a patch. Thanks a lot Spen!</p> <p>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.</p> <div class="line-block"> <div class="line">The best of way of getting patches integrated is sending them to the OpenOCD mailinglist, see <a class="reference external" href="https://lists.berlios.de/mailman/listinfo/openocd-development">https://lists.berlios.de/mailman/listinfo/openocd-development</a> for instructions on how to subscribe.</div> <div class="line">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.</div> </div> <p>Best regards,</p> <p>Dominic Rath</p> 2007-01-27T17:20:00+01:002007-01-27T17:20:00+01:00ntfreaktag:openocd.org,2007-01-27:/new-openocd-binaries-available-at-wwwyagartode.html

<p>Michael Fischer just put up a new version of the OpenOCD at his <a class="reference external" href="http://www.yagarto.de">Yagarto</a> webpage. This release includes the new support for ARM926EJ-S based targets, as well as numerous other fixes and improvements. Release 128 from Michael Fischer's website is considered the current official version for the Windows platform, and …</p>

<p>Michael Fischer just put up a new version of the OpenOCD at his <a class="reference external" href="http://www.yagarto.de">Yagarto</a> webpage. This release includes the new support for ARM926EJ-S based targets, as well as numerous other fixes and improvements. Release 128 from Michael Fischer's website is considered the current official version for the Windows platform, and the recommended version for all users of OpenOCD.</p> <p>Best regards,</p> <p>Dominic</p> 2007-01-26T15:02:00+01:002007-01-26T15:02:00+01:00ntfreaktag:openocd.org,2007-01-26:/arm926ej-s-support.html

<p>I've checked in support for ARM926EJ-S based cores. This has only been tested with a LPC3180 yet, and the cache/MMU handling isn't tested at all, but basically it should work. Accessing CP15 registers works, and can be verified with the command &quot;arm926ejs cp15 0 0 0 0&quot; which does …</p>

<p>I've checked in support for ARM926EJ-S based cores. This has only been tested with a LPC3180 yet, and the cache/MMU handling isn't tested at all, but basically it should work. Accessing CP15 registers works, and can be verified with the command &quot;arm926ejs cp15 0 0 0 0&quot; which does a CP15 read with opcode_1, opcode_2, Rn and Rm all set to zero, reading the ID code from CP15 c0. Information about the cache can also be retrieved using the command &quot;arm926ejs cache_info&quot;.</p> <div class="line-block"> <div class="line">Lots of people have asked for ARM926EJ-S support, and several parties wanted to get me a board to work with, but unfortunately none of them were able to make that happen.</div> <div class="line">Finally, my university bought a board with a LPC3180, and I would like to thank the University Of Applied Sciences Augsburg (FHA) and Prof. Dr. Hubert Högl for their continued support for the OpenOCD.</div> </div> <p>Windows binaries of the new OpenOCD release (currently SVN revision 128) will be available shortly on Michael Fischer's <a class="reference external" href="http://www.yagarto.de">Yagarto</a> webpage.</p> <p>Best Regards,</p> <p>Dominic Rath</p> 2006-11-10T14:12:00+01:002006-11-10T14:12:00+01:00ntfreaktag:openocd.org,2006-11-10:/testers-wanted-cortex-m3-xscale.html

<p>It's been a while since the last post, but a lot has happened since then. OpenOCD is now at SVN revision 114 (115 once I commit my latest XScale changes).</p> <div class="line-block"> <div class="line">Changes include:</div> <div class="line">- support for Cortex-M3 cores, including flash writing for Luminary Stellaris (This was contributed by Magnus Lundin, thanks a …</div></div>

<p>It's been a while since the last post, but a lot has happened since then. OpenOCD is now at SVN revision 114 (115 once I commit my latest XScale changes).</p> <div class="line-block"> <div class="line">Changes include:</div> <div class="line">- support for Cortex-M3 cores, including flash writing for Luminary Stellaris (This was contributed by Magnus Lundin, thanks a lot)</div> <div class="line">- support for XScale cores (tested with PXA250 for now, others to come)</div> <div class="line">- various fixes throughout the code improving stability and functionality</div> <div class="line">- improved writing performance on STR7x devices</div> <div class="line">- allow FT2232 to be opened by serial number instead of device description (ft2232_serial)</div> <div class="line">- see the SVN changelog for details</div> </div> <p>For now, Cortex-M3 support is only available as a separate branch, and has to be compiled by yourself. Grab the source from the OpenOCD SVN repository at svn://svn.berlios.de/openocd/branches/cortex-m3/ (http://svn.berlios.de/svnroot/repos/openocd/branches/cortex-m3/ if you can't use the svn protocol).</p> <p>XScale support isn't in mainline yet, either. Grab the source from the OpenOCD SVN repository at svn://svn.berlios.de/openocd/branches/xscale/ (http://svn.berlios.de/svnroot/repos/openocd/branches/xscale/ if you can't use the svn protocol).</p> <p>Build instructions can be found <a class="reference external" href="http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD">here</a>.</p> <p>I've set up a mailinglist for OpenOCD development at <a class="reference external" href="http://developer.berlios.de/mail/?group_id=4148">http://developer.berlios.de/mail/?group_id=4148</a>. If you're interested in helping with development, or if you have questions/comments regarding the Cortex-M or XScale development branches, this list is the right place.</p> 2006-08-31T14:48:00+02:002006-08-31T14:48:00+02:00ntfreaktag:openocd.org,2006-08-31:/greetings-from-endianness-hell.html

<p>Revision 90 just got committed to the SVN.</p> <p>I've spent the last two weeks cleaning up the handling of different target/host endianness. So far, all the generic code should be endianness safe, but the flash writing code is definitely not. Please report back if the OpenOCD still doesn't work …</p>

<p>Revision 90 just got committed to the SVN.</p> <p>I've spent the last two weeks cleaning up the handling of different target/host endianness. So far, all the generic code should be endianness safe, but the flash writing code is definitely not. Please report back if the OpenOCD still doesn't work on your big-endian target and/or host. I only have little endian targets and hosts to test with. If your target is big-endian, make sure you've configured the OpenOCD accordingly (target line in the .cfg file).</p> <p>For those of you running OpenOCD on little-endian boxes with little-endian targets, the endianness fixes offer noticeable improvements to the memory reading code. The &quot;arm7_9 fast_writes [enable|disable]&quot; command was renamed to &quot;arm7_9 fast_memory_access [enable|disable]&quot; to reflect the changed behaviour, but the old name is still available (but deprecated, so change your init files).</p> <p>While working with a EP9301 based board, I stumbled accross a problem on ARM920T targets with the data cache enabled. The current workaround for this problem is to keep linefills to the cache enabled, to ensure correct operation. If you happen to know more about this problem (see <a class="reference external" href="http://groups.google.com/group/comp.sys.arm/browse_thread/thread/c99af4d31b7a0515/357f7ca6e21a8046#357f7ca6e21a8046">Google Groups</a> for a longer explanation).</p> <p>See the changelog for other fixes and enhancements.</p> 2006-08-11T20:14:00+02:002006-08-11T20:14:00+02:00ntfreaktag:openocd.org,2006-08-11:/svn-is-at-revision-83-and-michael-fischers-yagarto-page.html

<p>Michael Fischer, who's supporting OpenOCD with his Windows installer packages and how-to articles (among other things), has put a new site online for his &quot;Yet Another Gnu ARm TOolchain (<a class="reference external" href="http://www.yagarto.de">YAGARTO</a>)&quot;. It provides windows installer packages for OpenOCD, the GNU ARM toolchain and an integrated development environment using Eclipse and the …</p>

<p>Michael Fischer, who's supporting OpenOCD with his Windows installer packages and how-to articles (among other things), has put a new site online for his &quot;Yet Another Gnu ARm TOolchain (<a class="reference external" href="http://www.yagarto.de">YAGARTO</a>)&quot;. It provides windows installer packages for OpenOCD, the GNU ARM toolchain and an integrated development environment using Eclipse and the Zylin CDT plugin. What makes YAGARTO special is that it runs completely native on Windows, i.e. it's fully based on MinGW and doesn't require Cygwin.</p> <p>Among other things, the current code available from SVN (revision 83) unifies the 'ftd2xx' (with FTDI's FTD2XX library) and 'ftdi2232' (with the open-source libftdi) interfaces. The new interface is called 'ft2232', and the library used to access the hardware is selected with the ./configure options --enable-ft2232_ftd2xx and --enable-ft2232_libftdi.</p> <div class="line-block"> <div class="line">The configuration options are the same as the former ftd2xx options:</div> <div class="line">ft2232_device_desc &quot;USB dev description&quot;</div> <div class="line">ft2232_layout &quot;layout name&quot;</div> <div class="line">ft2232_vid_pid</div> </div> <p>The ft2232_device_desc is only honored if the FTD2XX library is being used. The ft2232_vid_pid setting is used with both libraries, but only on Linux.</p> <p>Revision 81 fixed several minor problems, and added support for ARM966E based devices like the new STR9 series from ST Microelectronics. This code was contributed by Spencer Oliver, thanks a lot.</p> <p>Revision 79/80 added two new commands, jtag_ntrst_delay and jtag_nsrst_delay , to accommodate for situations where external or internal reset circuitry might keep a reset signal asserted for some time after the reset signal from the JTAG interface was deasserted. Revision 82 fixed a bug that required the arguments to these commands to be in microseconds, while they were intended to be miliseconds.</p> 2006-07-17T21:05:00+02:002006-07-17T21:05:00+02:00ntfreaktag:openocd.org,2006-07-17:/status-update.html

<p>I've spent the last days integrating a patch from Spencer Oliver that allows native Windows builds of OpenOCD using MinGW, which is now available as SVN revision 78. There's one minor issue causing OpenOCD to quit when a GDB session is detached. This will be fixed in the next SVN …</p>

<p>I've spent the last days integrating a patch from Spencer Oliver that allows native Windows builds of OpenOCD using MinGW, which is now available as SVN revision 78. There's one minor issue causing OpenOCD to quit when a GDB session is detached. This will be fixed in the next SVN commit.</p> <p>Michael Fischer has added a new page to his website explaining how OpenOCD has to be installed. You can find his page at <a class="reference external" href="http://www.usbdip.de/en/openocd/index.html">http://www.usbdip.de/en/openocd/index.html</a>. Thanks a lot Michael.</p> <p>The xscale support is still going to take some time, as I'm still busy with some exams, but all the major parts are already working.</p> 2006-06-12T18:56:00+02:002006-06-12T18:56:00+02:00ntfreaktag:openocd.org,2006-06-12:/openocd-forum-moved-and-some-updates.html

<p>The forum system at Berlios is a bit unhandy to use - at least when you're used to the features offered by other systems. Tsvetan from <a class="reference external" href="http://www.olimex.com">Olimex</a> has been kind enough to ask <a class="reference external" href="http://www.sparkfun.com">Sparkfun</a> to host the OpenOCD forum, and they've just set up a new section at their forum. Thanks …</p>

<p>The forum system at Berlios is a bit unhandy to use - at least when you're used to the features offered by other systems. Tsvetan from <a class="reference external" href="http://www.olimex.com">Olimex</a> has been kind enough to ask <a class="reference external" href="http://www.sparkfun.com">Sparkfun</a> to host the OpenOCD forum, and they've just set up a new section at their forum. Thanks to both Tsvetan and Sparkfun. The new place to ask for help with OpenOCD, to discuss new features you'd like to have, or just to let everyone know what you think about OpenOCD is <a class="reference external" href="http://www.sparkfun.com/cgi-bin/phpbb/viewforum.php?f=18">http://www.sparkfun.com/cgi-bin/phpbb/viewforum.php?f=18</a>.</p> <p>The support for Intel XScale based devices is coming along nicely. So far uploading the debug handler, entry into debug, core register handling and memory access works. Working with the XScale requires the ability to identify some ARM instructions, to be able to calculate the next address that's going to be executed. I decided to add a complete disassembler to the OpenOCD, which is now (trunk, revision 68) available from the telnet interface:</p> <p>`` &gt; armv4_5 disassemble 0x0 11 0x00000000 0xe59ff018 LDR r15, [r15, #0x18] 0x00000004 0xe59ff018 LDR r15, [r15, #0x18] 0x00000008 0xe59ff018 LDR r15, [r15, #0x18] 0x0000000c 0xe59ff018 LDR r15, [r15, #0x18] 0x00000010 0xe59ff018 LDR r15, [r15, #0x18] 0x00000014 0xb9205f84 STMLTDB r0!, {r2, r7, r8, r9, r10, r11, r12, r14} 0x00000018 0xe51ffff0 LDR r15, [r15, #-0xff0] 0x0000001c 0xe59ff014 LDR r15, [r15, #0x14]``</p> 2006-06-03T12:57:00+02:002006-06-03T12:57:00+02:00ntfreaktag:openocd.org,2006-06-03:/branching-and-a-few-updates.html

<div class="line-block"> <div class="line"><strong>Branching</strong></div> <div class="line">Yesterday I've changed the OpenOCD SVN repository layout to allow additional branches to be kept. The reason for this is that I started working on support for Intel XScale based systems. To be able to work on this without breaking the stable ARM7/9 stuff, I've moved the current …</div></div>

<div class="line-block"> <div class="line"><strong>Branching</strong></div> <div class="line">Yesterday I've changed the OpenOCD SVN repository layout to allow additional branches to be kept. The reason for this is that I started working on support for Intel XScale based systems. To be able to work on this without breaking the stable ARM7/9 stuff, I've moved the current stable OpenOCD code to /trunk, and created a new subdirectory /branches which for now holds the /xscale branch. Once I'm confident that any changes to the common code don't negatively affect the stable stuff, I'm going to merge everything back into trunk.</div> </div> <div class="line-block"> <div class="line">To fetch the current <strong>stable</strong> OpenOCD, use the following svn command:</div> <div class="line"><tt class="docutils literal">svn checkout <span class="pre">http://svn.berlios.de/svnroot/repos/openocd/trunk</span></tt></div> </div> <div class="line-block"> <div class="line">To fetch the XScale development branch (which is currently simply a copy of the stable code), use this svn command instead:</div> <div class="line"><tt class="docutils literal">svn checkout <span class="pre">http://svn.berlios.de/svnroot/repos/openocd/branches/xscale</span></tt></div> </div> <div class="line-block"> <div class="line"><strong>Updates</strong></div> <div class="line">In the meantime, mostly bugs in the OpenOCD code have been fixed. These are, among others:</div> <div class="line">- &quot;flash erase_check&quot; would crash for CFI flashes when there was no working_area specified.</div> <div class="line">- register valid/dirty tracking was buggy. The result was an occasional &quot;register xxx dirty but no valid data&quot; error.</div> <div class="line">- The INTDIS signal wasn't high during debug execution (i.e. flash writing, DCC downloads, ...). This would corrupt memory or flash writing, if a system was already up and running with interrupts enabled.</div> <div class="line">- The working area reserved for LPC2000 flash operations was too small, and could corrupt flash writing.</div> </div> <div class="line-block"> <div class="line">Added/changed functionality includes, among others:</div> <div class="line">- Access to ETM registers. This is for a new project of mine, and isn't currently usable (another reason for branching)</div> <div class="line">- DCC downloads have been disabled by default. Use the &quot;arm7_9 dcc_downloads &quot; command to enable them. DCC drastically increases download performance (host-&gt;target), but requires a working area <strong>that must NOT be written to</strong>, and is potentially unsafe on targets running at a very low speed, like the 32kHz startup clock of some Atmel ARMs.</div> <div class="line">- Fast memory writes have been disabled by default. Use the &quot;arm7_9 fast_writes &quot; command to enable them. Fast writes drastically increase download performance, especially when using a USB JTAG interface (Amontec JTAGkey, Olimex ARM-USB-OCD, homebrew).</div> </div> <div class="line-block"> <div class="line">There might be an issue left with LPC2000 systems:</div> <div class="line">If the CCLK frequency specified in the config file lists the crystal frequency, but your startup code enabled the PLL already, flash writing might fail. This has been reported only once so far, and a possible solution might be to manually turn the PLL off before starting any flash operations:</div> <div class="line">`` mwb 0xe01fc080 0x0 mwb 0xe01fc08c 0xaa mwb 0xe01fc08c 0x55``</div> </div> <div class="line-block"> <div class="line"><strong>Comments</strong></div> <div class="line">Commenting in the blog has been disabled, because some spam bots sent me &gt;10 messages per day. If you have something to say, use the forums, bug tracker, feature requests, or send me an email.</div> </div> 2006-04-01T17:44:00+02:002006-04-01T17:44:00+02:00ntfreaktag:openocd.org,2006-04-01:/spring-tiredness.html

<p>Seems there is no (common) english word or phrase to express the german &quot;Fruehjahrsmuedigkeit&quot; - but that's just what I felt the last week or so. Luckily that doesn't mean that the OpenOCD remained unattended. I've fixed a few minor bugs (added others, but those got fixed, too), added the one …</p>

<p>Seems there is no (common) english word or phrase to express the german &quot;Fruehjahrsmuedigkeit&quot; - but that's just what I felt the last week or so. Luckily that doesn't mean that the OpenOCD remained unattended. I've fixed a few minor bugs (added others, but those got fixed, too), added the one thing or the other, and merged some patches people sent me.</p> <p>Improvements include:</p> <ul class="simple"> <li>Support for ST Microelectronics STR7xx on-chip flash programming (Thanks to Spen).</li> <li>Configurable driver type (push-pull or open-drain) for the reset signals. The Amontec devices and the USBJTAG-1 already support this, other designs should follow. Default is push-pull for TRST and open-drain for SRST (as implemented on most Wigglers).</li> <li>A configuration command (working_area) has been added to specify a working area that's used by the OpenOCD to speed up memory downloads and flash programming.</li> </ul> <p>I'd like to thank Jim Lynch for his excellent tutorial &quot;ARM Cross Development with Eclipse&quot;. There's an updated draft version available at <a class="reference external" href="http://www.megaupload.com/?d=CNY1Y6DX">megaupload</a> (ATTENTION: Some people reported advertisments that are not suitable for viewing at work) which shows how to use the OpenOCD. The package (190mb) includes all necessary software (Eclipse, Zylin tools, GNUarm, OpenOCD, ...).</p> <p>Michael Fischer (mifi) has put a very nice <a class="reference external" href="http://www.usbdip.de/en/armdev/index.html">site</a> online explaining how to get a GNU development system (using OpenOCD as the debugger) running on Windows without having to install Cygwin (which seems to cause trouble for some people). He also wrote an installer for the OpenOCD, allowing very easy evaluation of the OpenOCD. Thanks a lot to Michael.</p> 2006-03-10T14:50:00+01:002006-03-10T14:50:00+01:00ntfreaktag:openocd.org,2006-03-10:/back-from-fosdem-openocd-updates-at91sam7-support.html

<div class="line-block"> <div class="line">I've been a bit busy latey, and haven't had time to update this blog as often as I'd wanted to. Fosdem was really fun, and especially I'd like to thank Timo Hoenig <a class="reference external" href="http://blog.nouse.net/">(blog)</a>, Fred Blaise <a class="reference external" href="http://www.madpenguin.org/blogs/chapeaurouge/">(blog)</a>, Holger Macht <a class="reference external" href="http://www.homac.de/wordpress/">(blog)</a> and the rest of the <a class="reference external" href="http://www.opensuse.org/">OpenSUSE</a> team for the nice time …</div></div>

<div class="line-block"> <div class="line">I've been a bit busy latey, and haven't had time to update this blog as often as I'd wanted to. Fosdem was really fun, and especially I'd like to thank Timo Hoenig <a class="reference external" href="http://blog.nouse.net/">(blog)</a>, Fred Blaise <a class="reference external" href="http://www.madpenguin.org/blogs/chapeaurouge/">(blog)</a>, Holger Macht <a class="reference external" href="http://www.homac.de/wordpress/">(blog)</a> and the rest of the <a class="reference external" href="http://www.opensuse.org/">OpenSUSE</a> team for the nice time in brussels.</div> <div class="line">You can grab the slides of my <a class="reference external" href="http://openocd.berlios.de/OpenOCD_Fosdem2006_talk.odp">OpenOCD talk</a> or even the <a class="reference external" href="http://free-electrons.com/community/videos/conferences">video</a> (thanks to Michael Opdenacker from <a class="reference external" href="http://free-electrons.com/">Free Electrons</a>).</div> </div> <p>I've put a rather large update into the subversion repository, which should make OpenOCD more usable (you don't have to shut the daemon down so often anymore, initialization scripts, ...)and more stable (reinitialize Embedded-ICE after a testlogic-reset, better timeout handling, ...).</p> <p>This also includes a patch for writing the internal flash found on Atmel AT91SAM7 flashes by Magnus Lundin (thanks a lot). I don't have a SAM7 to test myself, so please report back if you encounter any problems.</p> <p>I've started moving the OpenOCD documentation to the <a class="reference external" href="http://openfacts.berlios.de/index-en.phtml?title=Open_On-Chip_Debugger">OpenOCD's entry in the Berlios OpenFacts Wiki</a>. Currently, there's documentation for the configuration file, and I'm planning to document every available feature as well as some general usage notes there. Please feel free to contribute, if you feel there's something missing.</p> 2006-02-21T23:15:00+01:002006-02-21T23:15:00+01:00ntfreaktag:openocd.org,2006-02-21:/back-from-embedded-world-and-preparing-for-fosdem-2006.html

<p>I'm back from the Embedded World in Nuremberg for several days now. Here's a short list of what I believe that I've learned from our visitor's feedback:</p> <ul class="simple"> <li>Integration with GUI debuggers. This seemed to be important to quite a lot of people, who had problems with the spartanic demonstration using …</li></ul>

<p>I'm back from the Embedded World in Nuremberg for several days now. Here's a short list of what I believe that I've learned from our visitor's feedback:</p> <ul class="simple"> <li>Integration with GUI debuggers. This seemed to be important to quite a lot of people, who had problems with the spartanic demonstration using only telnet and the gdb command line. I've tested OpenOCD today with Eclipse and the Zylin-patched CDT, and it worked quite well. I'm currently working on getting this to run a bit more smoothely.</li> <li>The website seems to be confusing, making it hard for people to find the stuff they're looking for. I'm thinking of moving to Joomla (a Mambo fork), but this requires a lot more administrative effort.</li> <li>Support for Intel XScale cores. I always wanted to add this, and I'm currently figuring out how much work this is going to be.</li> </ul> <p>Feel free to comment on this list, and tell me about things you'd like to see (or want to add yourself :)).</p> <p>I'm currently preparing for a trip to <a class="reference external" href="http://www.fosdem.org/2006">Fosdem</a>, where I'm supposed to give a short presentation on the Open On-Chip Debugger, so I might be a bit slow in replying to support requests during the next days.</p> 2006-02-16T00:11:00+01:002006-02-16T00:11:00+01:00ntfreaktag:openocd.org,2006-02-16:/greetings-from-the-embedded-world-2006.html

<p>The second day at the Embedded World in Nuremberg is over, and I've had the chance to meet a lot of interesting people from the embedded field. Today the demand for OpenOCD flyers exceeded all of our expectations and we ran out of copies, so here's a link to the …</p>

<p>The second day at the Embedded World in Nuremberg is over, and I've had the chance to meet a lot of interesting people from the embedded field. Today the demand for OpenOCD flyers exceeded all of our expectations and we ran out of copies, so here's a link to the poster/flyer's <a class="reference external" href="http://openocd.berlios.de/poster.pdf">http://openocd.berlios.de/poster.pdf</a></p> 2006-02-02T00:25:00+01:002006-02-02T00:25:00+01:00ntfreaktag:openocd.org,2006-02-02:/support-requests.html

<div class="line-block"> <div class="line">Please use the OpenOCD <a class="reference external" href="http://developer.berlios.de/forum/?group_id=4148">forums</a> and <a class="reference external" href="http://developer.berlios.de/support/?group_id=4148">support</a> ticketing system available at the <a class="reference external" href="http://developer.berlios.de/projects/openocd/">project site</a>, instead of posting comments to the blog posts/pages.</div> <div class="line">I'd prefer keeping the commenting system for feedback related to news or articles, while having general support issues in the project support features provided by Berlios.</div> </div>

<div class="line-block"> <div class="line">Please use the OpenOCD <a class="reference external" href="http://developer.berlios.de/forum/?group_id=4148">forums</a> and <a class="reference external" href="http://developer.berlios.de/support/?group_id=4148">support</a> ticketing system available at the <a class="reference external" href="http://developer.berlios.de/projects/openocd/">project site</a>, instead of posting comments to the blog posts/pages.</div> <div class="line">I'd prefer keeping the commenting system for feedback related to news or articles, while having general support issues in the project support features provided by Berlios.</div> </div> 2006-01-23T20:16:00+01:002006-01-23T20:16:00+01:00ntfreaktag:openocd.org,2006-01-23:/ftdi-ft2232c-support-for-cygwin.html

<p>The FTDI FT2232C is now supported on Cygwin, too. The configure script accepts --with-ftd2xx=PATH to specify which directory should be searched for the content of the FTD2XX driver package (available from <a class="reference external" href="http://www.ftdichip.com">ftdi</a>). This configure option is ignored for non-Cygwin builds.</p>

<p>The FTDI FT2232C is now supported on Cygwin, too. The configure script accepts --with-ftd2xx=PATH to specify which directory should be searched for the content of the FTD2XX driver package (available from <a class="reference external" href="http://www.ftdichip.com">ftdi</a>). This configure option is ignored for non-Cygwin builds.</p> 2006-01-23T01:13:00+01:002006-01-23T01:13:00+01:00ntfreaktag:openocd.org,2006-01-23:/cfi-flash-support.html

<p>Support for CFI compliant flashes has been added to OpenOCD. Currently, only flashes compatible with the Intel command sets (0x0001 and 0x0003) are supported. Flash writing is possible both using memory writes (slow) and using flash writing code running on the target (faster). Using the Amontec JTAG Accelerator, about 30 …</p>

<p>Support for CFI compliant flashes has been added to OpenOCD. Currently, only flashes compatible with the Intel command sets (0x0001 and 0x0003) are supported. Flash writing is possible both using memory writes (slow) and using flash writing code running on the target (faster). Using the Amontec JTAG Accelerator, about 30 kByte/s can be flashed. The CFI flash code has been tested with an Intel 28F640J3 and an Intel TE28F320C3, both in x16 configuration on a 16-bit bus, but support is included for any combination of up to 32-bit busses.</p> 2006-01-18T15:33:00+01:002006-01-18T15:33:00+01:00ntfreaktag:openocd.org,2006-01-18:/openocd-and-the-amontec-jtag-accelerator.html

<p><a class="reference external" href="http://www.amontec.com">Amontec</a> released their JTAG Accelerator configuration for the Amontec Chameleon. The JTAG Accelerator is a high-speed EPP mode parallel port interface offering up to 70kByte/s download speed to target RAM using memory writes, and about 120kByte/s using the Debug Communications Channel (DCC).</p>

<p><a class="reference external" href="http://www.amontec.com">Amontec</a> released their JTAG Accelerator configuration for the Amontec Chameleon. The JTAG Accelerator is a high-speed EPP mode parallel port interface offering up to 70kByte/s download speed to target RAM using memory writes, and about 120kByte/s using the Debug Communications Channel (DCC).</p> 2006-01-15T20:52:00+01:002006-01-15T20:52:00+01:00ntfreaktag:openocd.org,2006-01-15:/lpc2000-flash-writing-improved.html

<div class="line-block"> <div class="line">The LPC2000 flash driver is able to calculate the checksum that's used by the bootloader to identify a valid flash image.</div> <div class="line">`` #flash bank lpc2000 base size 0 0 lpc_variant target # cclk calc_checksum flash bank lpc2000 0x0 0x40000 0 0 lpc2000_v1 0 14765 calc_checksum``</div> <div class="line">When 'calc_checksum' is specified in the LPC2000 …</div></div>

<div class="line-block"> <div class="line">The LPC2000 flash driver is able to calculate the checksum that's used by the bootloader to identify a valid flash image.</div> <div class="line">`` #flash bank lpc2000 base size 0 0 lpc_variant target # cclk calc_checksum flash bank lpc2000 0x0 0x40000 0 0 lpc2000_v1 0 14765 calc_checksum``</div> <div class="line">When 'calc_checksum' is specified in the LPC2000 flash bank configuration, the flash writing code inserts the correct checksum whenever a write to offset 0x0 of at least 32 byte (size of the exception vectors) occurs.</div> </div> <div class="line-block"> <div class="line"><tt class="docutils literal">flash probe 0</tt></div> <div class="line">Uses the IAP routines to check the erase state of all flash sectors</div> <div class="line"><tt class="docutils literal">flash erase 0 x y</tt></div> <div class="line">Erases flash blocks x to y using IAP calls</div> <div class="line"><tt class="docutils literal">flash info 0</tt></div> <div class="line">Prints information about the flash bank (block sizes, block starting offsets, erase state)</div> <div class="line"><tt class="docutils literal">flash write 0 FILE OFFSET</tt></div> <div class="line">Writes the binary FILE to the LPC2000 internal flash starting at OFFSET.</div> </div> 2006-01-13T20:25:00+01:002006-01-13T20:25:00+01:00ntfreaktag:openocd.org,2006-01-13:/new-preview-release.html

<div class="line-block"> <div class="line">There's a new preview release (actually two) available in the <a class="reference external" href="http://developer.berlios.de/project/showfiles.php?group_id=4148">files</a> section.</div> <div class="line">preview-20060113 is a snapshot of the latest svn code, while preview-cygwin-20060113 is the snapshot precompiled for cygwin.</div> </div> <div class="line-block"> <div class="line">This release features:</div> <div class="line">- ARM7TDMI(-S) support</div> <div class="line">- ARM720t support</div> <div class="line">- ARM920t support</div> <div class="line">- LPC2xxx flash support</div> <div class="line">- a telnet interface (for low-level debugging tasks)</div> <div class="line">- a …</div></div>

<div class="line-block"> <div class="line">There's a new preview release (actually two) available in the <a class="reference external" href="http://developer.berlios.de/project/showfiles.php?group_id=4148">files</a> section.</div> <div class="line">preview-20060113 is a snapshot of the latest svn code, while preview-cygwin-20060113 is the snapshot precompiled for cygwin.</div> </div> <div class="line-block"> <div class="line">This release features:</div> <div class="line">- ARM7TDMI(-S) support</div> <div class="line">- ARM720t support</div> <div class="line">- ARM920t support</div> <div class="line">- LPC2xxx flash support</div> <div class="line">- a telnet interface (for low-level debugging tasks)</div> <div class="line">- a GDB interface</div> <div class="line">- support for Wiggler-style PC parallel port interfaces</div> <div class="line">- support for FTDI FT2232C based devices</div> <div class="line">- support for the Amontec Chameleon's JTAG Accelerator configuration</div> </div> 2006-01-13T01:17:00+01:002006-01-13T01:17:00+01:00ntfreaktag:openocd.org,2006-01-13:/embedded-world-2006.html

<p>OpenOCD will be presented at the <a class="reference external" href="http://www.embedded-world-2006.de/">Embedded World 2006</a> in Nuremberg, during Februrary 14th to 16th. The <a class="reference external" href="http://www.fh-augsburg.de">University of Applied Sciences Augsburg</a> is sharing the booth &quot;Forschung für die Zukunft&quot; (Research for the future) with the TU Dresden. You can find us in hall 11, booth 112.</p>

<p>OpenOCD will be presented at the <a class="reference external" href="http://www.embedded-world-2006.de/">Embedded World 2006</a> in Nuremberg, during Februrary 14th to 16th. The <a class="reference external" href="http://www.fh-augsburg.de">University of Applied Sciences Augsburg</a> is sharing the booth &quot;Forschung für die Zukunft&quot; (Research for the future) with the TU Dresden. You can find us in hall 11, booth 112.</p> 2006-01-04T22:53:00+01:002006-01-04T22:53:00+01:00ntfreaktag:openocd.org,2006-01-04:/stability-issue-fixed.html

<div class="line-block"> <div class="line">There was a stability issue where the target would fail to cleanly enter debug state. The reason for this is still unclear, but using a watchpoint unit to break on any instruction fetch instead of the DBGRQ bit solved the problem.</div> <div class="line">See the SVN history page for a list of …</div></div>

<div class="line-block"> <div class="line">There was a stability issue where the target would fail to cleanly enter debug state. The reason for this is still unclear, but using a watchpoint unit to break on any instruction fetch instead of the DBGRQ bit solved the problem.</div> <div class="line">See the SVN history page for a list of changes.</div> </div> 2006-01-02T20:44:00+01:002006-01-02T20:44:00+01:00ntfreaktag:openocd.org,2006-01-02:/improvements-and-a-preliminary-documentation.html

<p>OpenOCD is at SVN revision 16, containing several improvements on the GDB connection handling and several other fixes. The <a class="reference external" href="https://developer.berlios.de/docman/?group_id=4148">docs</a> section has a first version of the documentation that will be reworked to reflect the new codebase. Chapters 5 and 6 document the available command line switches and the available …</p>

<p>OpenOCD is at SVN revision 16, containing several improvements on the GDB connection handling and several other fixes. The <a class="reference external" href="https://developer.berlios.de/docman/?group_id=4148">docs</a> section has a first version of the documentation that will be reworked to reflect the new codebase. Chapters 5 and 6 document the available command line switches and the available configuration and user commands.</p> 2005-12-31T12:47:00+01:002005-12-31T12:47:00+01:00ntfreaktag:openocd.org,2005-12-31:/cygwin-support.html

<div class="line-block"> <div class="line">Since SVN revision 9, OpenOCD works with Cygwin. Currently, only the parport interface is supported, so you should disable building of FTDI FT2232C drivers with:</div> <div class="line">./configure --disable-ftd2xx --disable-ftdi2232</div> </div> <p>Make sure you have the Cygwin 'ioperm' package installed (can be selected from cygwin's setup.exe) and the driver loaded (ioperm -i …</p>

<div class="line-block"> <div class="line">Since SVN revision 9, OpenOCD works with Cygwin. Currently, only the parport interface is supported, so you should disable building of FTDI FT2232C drivers with:</div> <div class="line">./configure --disable-ftd2xx --disable-ftdi2232</div> </div> <p>Make sure you have the Cygwin 'ioperm' package installed (can be selected from cygwin's setup.exe) and the driver loaded (ioperm -i).</p> <p>Thanks to Spen for making me aware of some bugs in the code that stopped OpenOCD from working with Cygwin.</p> 2005-12-29T19:55:00+01:002005-12-29T19:55:00+01:00ntfreaktag:openocd.org,2005-12-29:/fixes-fixes-and-flash-support.html

<div class="line-block"> <div class="line">Development on OpenOCD has been busy during the holidays. Fixes include support for the Olimex JTAG interface, correct handling of Thumb state (at least for ARM7) and increased stability.</div> <div class="line">The on-chip flash found on LPC2000 devices is supported (tested with a LPC2294), and the parallel port bitbang driver (i.e …</div></div>

<div class="line-block"> <div class="line">Development on OpenOCD has been busy during the holidays. Fixes include support for the Olimex JTAG interface, correct handling of Thumb state (at least for ARM7) and increased stability.</div> <div class="line">The on-chip flash found on LPC2000 devices is supported (tested with a LPC2294), and the parallel port bitbang driver (i.e. Wigglers) can be used either using direct port I/O or additionally using ppdev (/dev/parport0). Ppdev has the advantage of not requiring root privileges, but the access is slowed down a bit. Direct I/O allowed transfers to target RAM at 10kb/s, while ppdev offers about 8kb/s (these numbers heavily depend on your system).</div> </div> 2005-12-18T13:09:00+01:002005-12-18T13:09:00+01:00ntfreaktag:openocd.org,2005-12-18:/development-tree-moved-to-subversion.html

<div class="line-block"> <div class="line">I've moved my development tree to the <a class="reference external" href="http://developer.berlios.de/svn/?group_id=4148">subversion</a> repository at berlios.</div> <div class="line">You can check out the most recent version with</div> <div class="line"><tt class="docutils literal">svn checkout <span class="pre">svn://svn.berlios.de/openocd/</span></tt></div> </div> <p>SVN History moved to &quot;Pages -&gt; SVN History&quot;</p>

<div class="line-block"> <div class="line">I've moved my development tree to the <a class="reference external" href="http://developer.berlios.de/svn/?group_id=4148">subversion</a> repository at berlios.</div> <div class="line">You can check out the most recent version with</div> <div class="line"><tt class="docutils literal">svn checkout <span class="pre">svn://svn.berlios.de/openocd/</span></tt></div> </div> <p>SVN History moved to &quot;Pages -&gt; SVN History&quot;</p> 2005-12-17T14:29:00+01:002005-12-17T14:29:00+01:00ntfreaktag:openocd.org,2005-12-17:/preview-release.html

<p>There's a preview release avaiable in the <a class="reference external" href="http://developer.berlios.de/project/showfiles.php?group_id=4148">files section</a>.</p> <p>There are still several small issues to be sorted out, and of course a lot of testing has to be done. Let me know of any problems you encounter.</p>

<p>There's a preview release avaiable in the <a class="reference external" href="http://developer.berlios.de/project/showfiles.php?group_id=4148">files section</a>.</p> <p>There are still several small issues to be sorted out, and of course a lot of testing has to be done. Let me know of any problems you encounter.</p> 2005-12-16T11:11:00+01:002005-12-16T11:11:00+01:00ntfreaktag:openocd.org,2005-12-16:/long-time-no-news.html

<p>Been a while since I last posted to this blog, but a lot has happened since then. The new codebase I've been working on is feature-complete, and most problems have been solved. What's really needed is improved usability - especially the telnet interface is tailored to debugging the debugger, and not …</p>

<p>Been a while since I last posted to this blog, but a lot has happened since then. The new codebase I've been working on is feature-complete, and most problems have been solved. What's really needed is improved usability - especially the telnet interface is tailored to debugging the debugger, and not so much its use.</p> <div class="line-block"> <div class="line">What this new version supports:</div> <div class="line">- ARM7TDMI (including -S)</div> <div class="line">- ARM9TDMI</div> <div class="line">- Wiggler, FTDI2232C and Amontec JTAG Accelerator (not yet released)</div> <div class="line">- Telnet interface</div> <div class="line">- GDB interface</div> <div class="line">- multiple targets (in theory)</div> <div class="line">- multiple devices in a JTAG scan chain (tested)</div> </div> <div class="line-block"> <div class="line">What's still missing</div> <div class="line">- MMU support. This is in the 'old' codebase, and has to be ported</div> <div class="line">- Flash support. For Intel Strataflash this is in the 'old' codebase, and has to be ported</div> </div> <p>Anyway, thought it's about time I give a short update. E-Mail me to get access to my private CVS development branch.</p> 2005-09-17T21:10:00+02:002005-09-17T21:10:00+02:00ntfreaktag:openocd.org,2005-09-17:/xsvf-player-working.html

<p>Openocd has been successfully used to program the Xilinx CPLD inside an Amontec Chameleon (Coolrunner XCR3128XL) using the bitbang interface on a PC parallel port. This is the first real use of the new codebase I've been working on. I'm looking to integrate SVF and STAPL support, too, but that'll …</p>

<p>Openocd has been successfully used to program the Xilinx CPLD inside an Amontec Chameleon (Coolrunner XCR3128XL) using the bitbang interface on a PC parallel port. This is the first real use of the new codebase I've been working on. I'm looking to integrate SVF and STAPL support, too, but that'll take some time, I guess.</p> <p>Documentation for the JTAG API (this should be final for now) will follow soon.</p> 2005-09-16T14:04:00+02:002005-09-16T14:04:00+02:00ntfreaktag:openocd.org,2005-09-16:/open-on-chip-debugger-website-launched.html

<p>Using <a class="reference external" href="http://www.wordpress.org">WordPress</a> as its Blog software / CMS, the new website for openocd has been launched today.</p>

<p>Using <a class="reference external" href="http://www.wordpress.org">WordPress</a> as its Blog software / CMS, the new website for openocd has been launched today.</p>