Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » OpenOCD compatibility(Differences between OpenOCD 0.7.0, 0.8.0 & 0.10.0)
OpenOCD compatibility [message #1772636] Wed, 13 September 2017 12:07
Alan Rouse is currently offline Alan RouseFriend
Messages: 8
Registered: July 2009
Junior Member
For several years I have been using a 'handmade' build of Eclipse, Zylin, OpenOCD 0.7.0 and an Olimex ARM-USB-OCD interface. I created an External Tools Configuration (which I named OpenOCD) and the following OpenOCD.cfg file:
# Configuration file to initialise openocd for a Mega_Link target
# via an Olimex ARM-USB-OCD
#debug_level 3
# source interface
source [find interface/olimex-arm-usb-ocd.cfg]
# source target
source [find target/stm32f1x.cfg]
init
reset

This works as expected. When I run it the Console shows the following
Open On-Chip Debugger 0.7.0 (2013-05-05-10:41)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
cortex_m3 reset_config sysresetreq
Info : clock speed 1000 kHz
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x06430041 (mfg: 0x020, part: 0x6430, ver: 0x0)
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x06430041 (mfg: 0x020, part: 0x6430, ver: 0x0)


I then tried to upgrade to OpenOCD 0.8.0, but it gives the following errors:
GNU ARM Eclipse 64-bits Open On-Chip Debugger 0.10.0-00113-g0f83948 (2017-01-24-18:48)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
openocd.cfg:8: Error: Can't find interface/olimex-arm-usb-ocd.cfg
in procedure 'script' 
at file "embedded:startup.tcl", line 60
at file "openocd.cfg", line 8
Error: Debug Adapter has to be specified, see "interface" command
openocd.cfg:8: Error: 
in procedure 'script' 
at file "embedded:startup.tcl", line 60
at file "openocd.cfg", line 8


It states that it couldn't find the Olimex driver. I looked at the openocd/scripts/interface folder and realised that the driver is in the /ftdi sub-folder, so I modifying the cfg file as follows:
# source interface
source [find interface/ftdi/olimex-arm-usb-ocd.cfg]


This makes a difference (why isn't it needed in OpenOCD 0.7.0?), but now gives the following error message:
GNU ARM Eclipse 64-bits Open On-Chip Debugger 0.10.0-00113-g0f83948 (2017-01-24-18:48)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
none separate
cortex_m reset_config sysresetreq
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 15ba, pid 0003, description 'Olimex OpenOCD JTAG', serial '*' at bus location '*'


I therefore reverted back to OpenOCD 0.7.0. I am now trying to create an integrated build using GNU MCU Eclipse Plug-ins - http://gnu-mcu-eclipse.netlify.com/v4-neon-updates from the marketplace. This installs OpenOCD 0.10.0 in the folder C:\Program Files\GNU ARM Eclipse and referenced this in the External Tools Configuration, and it generates the same error message as above.

Can anyone explain how I overcome this?
Previous Topic:Not your everyday can't resolve uint32_t
Next Topic:Eclipse CDT Debug attach usage
Goto Forum:
  


Current Time: Wed Dec 13 11:27:35 GMT 2017

Powered by FUDForum. Page generated in 0.01609 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software