Your message dated Wed, 7 Oct 2015 09:59:46 +0300 with message-id <[email protected]> and subject line Re: Bug#801145: openocd: interface script uses ft2232 (obsolete) not ftdi has caused the Debian Bug report #801145, regarding openocd: interface script uses ft2232 (obsolete) not ftdi to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 801145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801145 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: openocd Version: 0.8.0-4 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Attempted connection between Olimex ARM-USB-OCD / LPC-microcontroller and 'jessie' host for programming/debugging. * What exactly did you do (or not do) that was effective (or ineffective)? Attempted to edit interface script /usr/share/openocd/scripts/interface/olimex-arm-usb-ocd.cfg, which was ineffective. Tried using 'wheezy' system, which uses an older version of openocd. This worked, showing that the failure is a consequence of a change in openocd that no longer supports the ft2232 interface. (That system cannot be substituted for whole job, but demonstrates that the problem is with the newer software rather than the hardware). Also tried updating to stretch versions of openocd (and supporting libraries). This did not change the script, so (unsurprisingly) failed to fix the problem. * What was the outcome of this action? Various error messages, logs, etc., all indicating that the connection between the linux host and the target embedded system was not established. * What outcome did you expect instead? A proper connection as occurred with a wheezy system. PLEASE update the scripts so that they will work with the ftdi protocol. THANKS! *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.7-ckt11 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openocd depends on: ii libc6 2.19-18+deb8u1 ii libftdi1 0.20-3 ii libhidapi-hidraw0 0.8.0~rc1+git20140201.3a66d4e+dfsg-3 ii libusb-0.1-4 2:0.1.12-25 ii libusb-1.0-0 2:1.0.19-1 openocd recommends no packages. openocd suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Tue, Oct 06, 2015 at 01:00:41PM -0700, Frank Miles wrote: > I'd like to withdraw (or at least cut back) on my bug report. Minutes > after posting, I noticed the 'ftdi' subdirectory: > /usr/share/openocd/scripts/target > It has the proper (working) scripts. The only bug (of lesser importance) > would be getting rid of the old scripts which are, at best, an attractive > nuisance. Please open a separate bug in upstream OpenOCD bugtracker if you think there's a way to improve the situation (and no, just removing old configs is not appropriate, there're some people still using ft2232 for various reasons). I think when ft2232 driver is not available at all and one tries to source a deprecated adapter config, openocd will print a list of available interfaces, that will include ftdi and should be enough of a hint to check README, the official User's Guide or do a relevant Internet search. Thank you for using OpenOCD :) -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected]
--- End Message ---
