Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training


Is OpenOCD 0.1.0 stable?

Posted by Adam Turowski on May 19, 2009
I've managed to make only couple of steps during program debugging - and then OpenOCD almost always crashes with Segmentation fault exception. Is older OpenOCD version more stable?

RE: Is OpenOCD 0.1.0 stable?

Posted by Richard on May 20, 2009
I have not tried using the latest version, but have found the version that I include in the FreeRTOS download to be very stable.

I have however noted that the interface for hardware debugging in the latest Eclipse downloads has changed, which requires a bit of setup fiddling to get the projects to debug correctly. Also the newer versions of OpenOCD have changed the command syntax, so they will not work with the scripts that are in the FreeRTOS download.


RE: Is OpenOCD 0.1.0 stable?

Posted by Alain Mouette on May 20, 2009
Hi Richard,

as you said that a few things have changed, could you please sent an update for OpenOCD usage in new eclipse? And whatever else you can, if you find it may be usefull... :)

Versions and setup for OpenOCD are very confising because it is allways changing... Is there a wiki somewhere that we can add our experiences and feeedback?

RE: Is OpenOCD 0.1.0 stable?

Posted by Raphael Derosso Pereira on May 21, 2009
In OpenOCD source, there's a lot ready files. The new schema was done to permit the creation of multiple configuration files, each one to specify a class of device, like one for jtag, another for each target and so on.

RE: Is OpenOCD 0.1.0 stable?

Posted by Adam Turowski on May 21, 2009
I think there is some king of misunderstanding. Please find below the summary of what I've understood. Please correct me If I am wrong.

As I pointed in the first post in this topic, new (0.1.0) OpenOCD seems to be unstable. Then Richard concluded that the older OpenOCD version (I don't know which version it is?) seems to be stable. Also he said that to make it working with new Eclipse you have to make some fiddling with OpenOCD configuration files included in FreeRTOS distribution. And finally I believe that alainm3 is after information how to fiddle these files.

Richard, can you point me to the documentation for OpenOCD version, which is distributed with FreeRTOS?

Best regards,

RE: Is OpenOCD 0.1.0 stable?

Posted by Dave on May 21, 2009
I'm not sure of the command line option to get the version number, but openocd-pp (parallel port) is showing a build date of 2007-08-25 12:00 CEST, and open_ftdi is showing a build date of 2007-08-17 11:00 CEST. This might be the date that Richard built them though. They are in theDemo\Common\drivers\OpenOCD directory.

RE: Is OpenOCD 0.1.0 stable?

Posted by Adam Turowski on May 21, 2009
Mostly I am interested in ftdi version, which I want to run with Turtelizer2 board and AT91SAM7X256. I am looking for documentation corresponding to this version/build of OpenOCD to avoid struggling with OpenOCD command syntax changing so rapidly.


RE: Is OpenOCD 0.1.0 stable?

Posted by Stefano Oliveri on May 21, 2009
Dear all,

I'm currently working with OpenOD compiled from trunk 14xx and 16xx with support for Versaloon and FTDI based dongle (through FTD2XX). It is very stable and the MCU programming speed is increased. For sure this opinion is coming from my personal experience. I'm following some project based on STM32 MCU; the IDE is Eclipse Ganymede+CDT 5.0.2 and the one of the following dongle: Versaloon or JTAGKey-Tiny or Olimex.


RE: Is OpenOCD 0.1.0 stable?

Posted by Adam Turowski on May 21, 2009
Dear Stefano,

Can you send me resulting executable files and configuration files on my email address: adas _at_ ikp _dot_ pl please ? I would like to try them on Windows platform and AT91SAM7X256 micro to check, if the stability will improve.


RE: Is OpenOCD 0.1.0 stable?

Posted by Adam Turowski on May 21, 2009
Stefano has send me executable of OpenOCD SVN 1690 version. It needs little configuration files fiddling (i.e. at91sam7 flash driver name has to be changed to at91sam7_new) and seems to be really more stable than 0.1.0.

Once again thanks Stefano!

Now I've got another problem ;-). gdb "step" instruction always tries to set software breakpoint, but as expected it fails on FLASH running MCU. thbreak command works. How to enforce that gdb will always set hardware assisted breakpoint (especially during "step" command)?


RE: Is OpenOCD 0.1.0 stable?

Posted by Adam Turowski on May 22, 2009
I found the solution command "gdb_breakpoint_override hard" in OpenOCD configuration file does the job and converts all breakpoint set requests from gdb to be hardware assisted breakpoint.

This of course limits the amount of available breakpoints to 2. I think it can be automaticaly changed to use software breakpoints if the code where we want to set breakpoint is running from RAM. It could be possible if gdb knows the memory layout - OpenOCD command "gdb_memory_map enable" looks promising. I am still trying to force GDB to read memory map.

Any suggestions how to do that?

[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]

Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.

Free TCP/IP and file system demos for the RTOS

Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists