Bug#793214: openocd: OpenRD Ultimate unsupported since removal of ft2232 (so >=0.8.0)
Patched and re-ran. I can see the difference in the debug output, but the behavior does not appear to be affected. I've attached both a debug and dmesg log. This time, I've included the dmesg messages printed as a result of running OpenOCD. Cheers! Benjamin Rodgers On Wed, Aug 10, 2016 at 5:17 PM, Andreas Fritiofson < andreas.fritiof...@gmail.com> wrote: > Looking into it. The failure is on a really low level because the scan > chain discovery just finds garbage. I suspect a problem with the reset > signals because the I/O initialization seems to otherwise match the legacy > driver. Looking at the old driver it seems the adapter has fully > tristate-buffered reset signals even though they are not used as such. Not > sure why that should be a problem but can you anyway try the following > config file patch? > > diff --git a/tcl/interface/ftdi/sheevaplug.cfg b/tcl/interface/ftdi/ > sheevaplug.cfg > index f299f27..5e3f369 100644 > --- a/tcl/interface/ftdi/sheevaplug.cfg > +++ b/tcl/interface/ftdi/sheevaplug.cfg > @@ -10,5 +10,5 @@ ftdi_vid_pid 0x9e88 0x9e8f > ftdi_channel 1 > > ftdi_layout_init 0x0608 0x0f1b > -ftdi_layout_signal nTRST -data 0x0200 > -ftdi_layout_signal nSRST -noe 0x0400 > +ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100 > +ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400 > > > Nothing in dmesg when openocd starts and ttyUSB0 goes missing? I just want > to confirm that openocd actually opens the correct interface, otherwise > that could be the problem (talking JTAG with the serial port circuitry). > The "ftdi_channel 1" option is not used a lot and I've never tested it > myself. A disappearing serial port might indicate that the interface is > actually wrong, but it could also be some quirk of > libusb/ftdi_sio/virtualbox. > > Regards, > Andreas Fritiofson > vagrant@jessie:~$ git -C openocd-code rev-parse HEAD cd9b9a636411671808e8669ad8d6ee8f8815ad1b vagrant@jessie:~$ git -C openocd-code diff diff --git a/tcl/interface/ftdi/sheevaplug.cfg b/tcl/interface/ftdi/sheevaplug.cfg index f299f27..5e3f369 100644 --- a/tcl/interface/ftdi/sheevaplug.cfg +++ b/tcl/interface/ftdi/sheevaplug.cfg @@ -10,5 +10,5 @@ ftdi_vid_pid 0x9e88 0x9e8f ftdi_channel 1 ftdi_layout_init 0x0608 0x0f1b -ftdi_layout_signal nTRST -data 0x0200 -ftdi_layout_signal nSRST -noe 0x0400 +ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100 +ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400 vagrant@jessie:~$ sudo openocd -d 3 -f /usr/local/share/openocd/scripts/board/sheevaplug.cfg Open On-Chip Debugger 0.10.0-dev-00335-gcd9b9a6 (2016-08-10-20:54) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html User : 13 2 command.c:544 command_print(): debug_level: 3 Debug: 14 2 options.c:96 add_default_dirs(): bindir=/usr/local/bin Debug: 15 3 options.c:97 add_default_dirs(): pkgdatadir=/usr/local/share/openocd Debug: 16 3 options.c:98 add_default_dirs(): run_prefix= Debug: 17 3 configuration.c:42 add_script_search_dir(): adding /root/.openocd Debug: 18 4 configuration.c:42 add_script_search_dir(): adding /usr/local/share/openocd/site Debug: 19 4 configuration.c:42 add_script_search_dir(): adding /usr/local/share/openocd/scripts Debug: 20 4 configuration.c:82 find_file(): found /usr/local/share/openocd/scripts/board/sheevaplug.cfg Debug: 21 4 configuration.c:82 find_file(): found /usr/local/share/openocd/scripts/interface/ftdi/sheevaplug.cfg Debug: 22 5 command.c:143 script_debug(): command - ocd_command ocd_command type ocd_interface ftdi Debug: 23 5 command.c:143 script_debug(): command - interface ocd_interface ftdi Debug: 25 5 command.c:364 register_command_handler(): registering 'ocd_ftdi_device_desc'... Debug: 26 5 command.c:364 register_command_handler(): registering 'ocd_ftdi_serial'... Debug: 27 5 command.c:364 register_command_handler(): registering 'ocd_ftdi_location'... Debug: 28 5 command.c:364 register_command_handler(): registering 'ocd_ftdi_channel'... Debug: 29 5 command.c:364 register_command_handler(): registering 'ocd_ftdi_layout_init'... Debug: 30 5 command.c:364 register_command_handler(): registering 'ocd_ftdi_layout_signal'... Debug: 31 6 command.c:364 register_command_handler(): registering 'ocd_ftdi_set_signal'... Debug: 32 6 command.c:364 register_command_handler(): registering 'ocd_ftdi_vid_pid'... Debug: 33 6 command.c:364 register_command_handler(): registering 'ocd_ftdi_tdo_sample_edge'... Debug: 34 6 command.c:143 script_debug(): command - ocd_command ocd_command type ocd_ftdi_device_desc SheevaPlug JTAGKey FT2232D B Debug: 35 6 command.c:143 script_debug(): command - ftdi_device_desc ocd_ftdi_device_desc SheevaPlug JTAGKey FT2232D B Debug: 37 6 command.c:143 script_debug(): command - ocd_command ocd_command type ocd_ftdi_vid_pid 0x9e88 0x9e8f Debug: 38 6 command.c:143 script_debug(): command - ftdi_vid
Bug#793214: openocd: OpenRD Ultimate unsupported since removal of ft2232 (so >=0.8.0)
On Wed, Aug 10, 2016 at 3:24 AM, Andreas Fritiofson < andreas.fritiof...@gmail.com> wrote: > > On Wed, Aug 10, 2016 at 4:55 AM, Benjamin Rodgers <benjamin.rodgers@ > verizondigitalmedia.com> wrote: > >> I compiled OpenOCD 0.9.0 from source first without >> "--enable-legacy-ft2232_libftdi" to confirm no change in behavior, and >> then with "--enable-legacy-ft2232_libftdi". With a couple caveats, it's >> actually working now. >> > >> > >> >> Caveat 2: When I don't have a serial connection open (screen >> /dev/ttyUSB0 115200), everything works great. When I do, OpenOCD >> periodically chokes. This may be related to my hardware configuration >> (Debian Jessie as set up by Vagrant debian/jessie64 running on VirtualBox >> on a Mac), but I'm mentioning it just in case others experience similar >> behavior. >> >> Error: ftdi_write_data: usb bulk write failed >>> Error: couldn't write MPSSE commands to FT2232 >>> Polling target feroceon.cpu failed, trying to reexamine >>> Info : Embedded ICE version 0 >>> Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit >>> For reference, the telltale >> >> > This symptom was common with the ft2232 adapter driver (for several > reasons) and was part of the motivation for the full rewrite. We will not > fix issues with the deprecated ft2232 driver upstream, in fact we have a > patch pending to purge it completely. Now that we know that the same setup > works with ft2232 but not with ftdi, let's focus on getting the latter > working. > Makes sense to me. Glad I mentioned it. On Wed, Aug 10, 2016 at 3:24 AM, Andreas Fritiofson < andreas.fritiof...@gmail.com> wrote: > > On Wed, Aug 10, 2016 at 4:55 AM, Benjamin Rodgers <benjamin.rodgers@ > verizondigitalmedia.com> wrote: >> >> On Thu, 23 Jul 2015 00:57:21 +0200 Andreas Fritiofson < >> andr...@fritiofson.net> wrote: >> >>> On Wed, 22 Jul 2015 14:17:31 +0100 Philip Hands <p...@hands.com> wrote: >>> >>>> I notice that running openocd causes the /dev/ttyUSB0 device to >>>> disapear, >>>> so it's certainly doing something, even if it's not very useful. >>> >>> >>> OpenOCD detaches the kernel driver on the selected interface (FTDI >>> channel) >>> which might serve a serial port if so configured. Do you really have a >>> tty >>> on the same interface/channel as the JTAG circuitry? Channel A *should* >>> be >>> unaffected by OpenOCD if "ftdi_channel 1" is selected. >> >> >> With the legacy driver "/dev/ttyUSB0" is no longer disappearing upon >> running OpenOCD. It was disappearing with the FTDI driver. >> > > Can you send the output of "lsusb -v -d 0x9e88:0x9e8f" and whatever adds > to "dmesg" after plugging in the adapter and starting openocd (beginning > with the line "new full-speed USB device number...")? > I've attached the output of both (lsusb.txt, dmesg.txt). On Wed, Aug 10, 2016 at 3:24 AM, Andreas Fritiofson < andreas.fritiof...@gmail.com> wrote: > > On Wed, Aug 10, 2016 at 4:55 AM, Benjamin Rodgers <benjamin.rodgers@ > verizondigitalmedia.com> wrote: > For reference, here is the output of OpenOCD with the FTDI driver. >> > >> vagrant@jessie:~/a/openocd-0.9.0$ src/openocd -f >>> tcl/board/sheevaplug.cfg -s tcl >> >> > Please add "-d" to get a verbose log. Also, if you compile from source > anyway, use the git master if possible (for easier matching the log to the > code). > Rebuilt from git master and ran with "-d". I've attached the Vagrantfile for reference and logged output (debug.txt). Cheers! Benjamin Rodgers ... [6.811545] PM: Hibernation image not present or could not be loaded. [6.844175] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [6.863399] usb 1-1: new full-speed USB device number 2 using ohci-pci [6.943184] tsc: Refined TSC clocksource calibration: 2495.109 MHz [6.950286] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. ... [7.146478] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [7.147695] alg: No test for crc32 (crc32-pclmul) [7.148380] usb 1-1: New USB device found, idVendor=9e88, idProduct=9e8f [7.148382] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [7.148383] usb 1-1: Product: SheevaPlug JTAGKey FT2232D B [7.148384] usb 1-1: Manufacturer: FTDI [7.148385] usb 1-1: SerialNumbe
Bug#793214: openocd: OpenRD Ultimate unsupported since removal of ft2232 (so >=0.8.0)
This issue appears to be affecting me as well while trying to connect to a
DreamPlug.
Most of my troubleshooting has been performed using with Vagrant
debian/jessie64. I've tried the backports package for 'openocd' as well,
and dist-upgrading to Stretch. The only difference I've noticed is that
the OpenOCD shipped with Jessie (0.8.0-4) refuses to match the adapter with
this line in place in
"/usr/share/openocd/scripts/interface/ftdi/sheevaplug.cfg".
> ftdi_device_desc "SheevaPlug JTAGKey FT2232D B"
On Thu, 23 Jul 2015 00:57:21 +0200 Andreas Fritiofson <
andr...@fritiofson.net> wrote:
> A lot has happened since 0.5.0 apart from the adapter driver change so the
> problem might lie somewhere else than ftdi vs ft2232. Can you try the
> latest release that included the ft2232 driver (0.8?), or even better,
> build from source and explicitly pass --enable-legacy-ft2232_libftdi to
> configure (make sure you have libusb-1.0 and libftdi dev packages
> installed). The feroceon target has AFAIK not been tested in a long time
so
> there might be issues with that. Does the hardware allow you to connect
> other targets to the same debug adapter or vice versa (i.e. an external
> debug connector or such)? Just trying to reduce the number of unknowns.
I compiled OpenOCD 0.9.0 from source first without
"--enable-legacy-ft2232_libftdi" to confirm no change in behavior, and then
with "--enable-legacy-ft2232_libftdi". With a couple caveats, it's
actually working now.
Caveat 1: Switching back to the non-FTDI interface is necessary (obvious
reasons).
> vagrant@jessie:~$ diff -u {a,b}/openocd-0.9.0/tcl/board/sheevaplug.cfg
> --- a/openocd-0.9.0/tcl/board/sheevaplug.cfg 2015-05-17
21:14:10.0 +
> +++ b/openocd-0.9.0/tcl/board/sheevaplug.cfg 2016-08-10
02:07:55.674787653 +
> @@ -1,6 +1,6 @@
> # Marvell SheevaPlug
>
> -source [find interface/ftdi/sheevaplug.cfg]
> +source [find interface/sheevaplug.cfg]
> source [find target/feroceon.cfg]
>
> adapter_khz 2000
Caveat 2: When I don't have a serial connection open (screen /dev/ttyUSB0
115200), everything works great. When I do, OpenOCD periodically chokes.
This may be related to my hardware configuration (Debian Jessie as set up
by Vagrant debian/jessie64 running on VirtualBox on a Mac), but I'm
mentioning it just in case others experience similar behavior.
> Error: ftdi_write_data: usb bulk write failed
> Error: couldn't write MPSSE commands to FT2232
> Polling target feroceon.cpu failed, trying to reexamine
> Info : Embedded ICE version 0
> Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
> For reference, the telltale
On Thu, 23 Jul 2015 00:57:21 +0200 Andreas Fritiofson <
andr...@fritiofson.net> wrote:
> On Wed, 22 Jul 2015 14:17:31 +0100 Philip Hands <p...@hands.com> wrote:
> > I notice that running openocd causes the /dev/ttyUSB0 device to
disapear,
> > so it's certainly doing something, even if it's not very useful.
>
> OpenOCD detaches the kernel driver on the selected interface (FTDI
channel)
> which might serve a serial port if so configured. Do you really have a tty
> on the same interface/channel as the JTAG circuitry? Channel A *should* be
> unaffected by OpenOCD if "ftdi_channel 1" is selected.
With the legacy driver "/dev/ttyUSB0" is no longer disappearing upon
running OpenOCD. It was disappearing with the FTDI driver.
For reference, here is the output of OpenOCD with the FTDI driver.
> vagrant@jessie:~/a/openocd-0.9.0$ src/openocd -f tcl/board/sheevaplug.cfg
-s tcl
> Open On-Chip Debugger 0.9.0 (2016-08-10-02:21)
> 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 '.
> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
connect_deassert_srst
> adapter_nsrst_delay: 200
> jtag_ntrst_delay: 200
> adapter speed: 2000 kHz
> dcc downloads are enabled
> Warn : use 'feroceon.cpu' as target identifier, not '0'
> sheevaplug_load_uboot
> Info : clock speed 2000 kHz
> Info : TAP feroceon.cpu does not have IDCODE
> Info : TAP auto0.tap does not have IDCODE
> Info : TAP auto1.tap does not have IDCODE
> Info : TAP auto2.tap does not have IDCODE
> Info : TAP auto3.tap does not have IDCODE
Cheers!
Benjamin Rodgers
Bug#574111: E: main.c: Failed to create '/tmp/pulse-$USER': Permission denied
Confirmed that downgrading from 'libpulsecore5_0.9.10-3+lenny2_amd64' to 'libpulsecore5_0.9.10-3+lenny1_amd64' resolves the issue. Also confirmed that adding a distclean + bootstrap to debian/patches resolves the issue. However, am I wrong to assume that the output of bootstrap (or any of the autotools chain) is arch-dependant? Guess I'll spend some time reading up on CDBS. signature.asc Description: OpenPGP digital signature
Bug#324397: abiword: Was getting an undefined symbol fribidi_get_type with older libfribidi
Package: abiword Version: 2.2.9-1 Severity: important Tags: experimental I am currently using abiword 2.2.9-1 and I was using libfribidi0 0.10.4-6. When using this combination, typing anything into AbiWord would crash and produce the following error: abiword: symbol lookup error: abiword: undefined symbol: fribidi_get_type After upgrading to libfribidi0 0.10.5-3 this error has gone away. I am assuming at this point that AbiWord now requires a newer libfribidi0 version. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages abiword depends on: ii abiword-common2.2.9-1WYSIWYG word processor based on GT ii libatk1.0-0 1.10.1-2 The ATK accessibility toolkit ii libc6 2.3.5-3GNU C Library: Shared libraries an ii libenchant1c2 1.1.6-1a wrapper library for various spel ii libfontconfig12.3.1-2generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libfribidi0 0.10.5-3 Free Implementation of the Unicode ii libgcc1 1:4.0.1-3 GCC support library ii libglade2-0 1:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.6.1-3The GLib library of C routines ii libgtk2.0-0 2.6.2-4The GTK+ graphical user interface ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library ii libpango1.0-0 1.8.2-1Layout and rendering of internatio ii libperl5.85.8.7-4Shared Perl library ii libpng12-01.2.8rel-1 PNG library - runtime ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm64.3.0.dfsg.1-8 X Window System Session Management ii libstdc++64.0.1-3The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li ii libxft2 2.1.2-6FreeType-based font drawing librar ii libxml2 2.6.20-1 GNOME XML library ii libxrender1 1:0.9.0-2 X Rendering Extension client libra ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m ii zlib1g1:1.2.2-4 compression library - runtime abiword recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#304576: pciutils: lspci -mn shows the wrong identifier for subvendor
Package: pciutils Version: 1:2.1.11-15 Severity: normal The subvendor ID provided by lspci -mn is erroneous. Apparently lspci is duplicating the device ID instead of printing the subvendor ID. Example follows: __ BEGIN EXAMPLE __ lspci -mn 00:00.0 0600 10de 01e0 c1 00 01e0 80ac [...] 02:01.0 0200 10b7 9201 40 00 9201 80ab lspci -mnx :00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) 00: de 10 e0 01 06 00 b0 00 c1 00 00 06 00 00 80 00 10: 08 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ac 80 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 [...] 02:01.0 0200 10b7 9201 40 00 9201 80ab 00: b7 10 01 92 07 00 10 02 40 00 00 02 08 20 00 00 10: 01 c0 00 00 00 00 00 e8 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ab 80 30: 00 00 00 00 dc 00 00 00 00 00 00 00 05 01 0a 0a The relevant lines for the last device are 02:01.0 0200 10b7 9201 40 00 9201 80ab and 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 ab 80 The device ID, 9201, is duplicated for the subvendor ID, while the hex dump shows the subvendor ID to be 1043. Perhaps the more readable version (including labels) would be produced by lspci -mnv. Output as follows for the same device: Device: 02:01.0 Class: 0200 Vendor: 10b7 Device: 9201 SVendor:9201 SDevice:80ab Rev:40 The matching pci.ids entry for the device is 10b7 3Com Corporation 9201 3C920B-EMB Integrated Fast Ethernet Controller [Tornado] 1043 80ab A7N8X Deluxe onboard 3C920B-EMB Integrated Fast Ether Which re-confirms the 1043 subvendor ID. __ END EXAMPLE __ This error applies to every subvendor ID provided by lspci -mn. Thank you for reviewing this bug report. -Tyln -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages pciutils depends on: ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
