> > Today I've tested urjtag for the first time on a system with libusb1. > For some reason, my arm-usb-ocd cable is not detecting the chain > anymore. The same setup works on the old host without problems. > > Old host > libusb 0.1.12 > libftdi 0.16 > > New host > libusb 1.0.8 > libusbcompat 0.1.13 > libftdi 0.18 > > The new host is a laptop that had the same software setup as "old host" > before. It's been re-installed from scratch with current OpenSUSE 11.3. > Urjtag worked on this laptop before without problems, so I'd rule out a > hardware issue. > > After upgrading, the detect command hangs forever without any output for > most of the times (maybe 95%). Once in a while, the chain length is > detected correctly and freezes then. > Debugging showed that the hang occurs in libusb read functions but with > no specific symptom. A Usb-Blaster cable works fine on both systems. My > first guess is a ftdi-mpsse specific issue. > > > With random trials I found a way to mitigate the freezes: Reducing > URJ_USBCONN_FTDX_MAXSEND_MPSSE to (16 * 1024) yields 100% successful > detect runs. I'm not yet sure what I'm looking at and, therefore, won't > commit to SVN for the time being. > Has anyone encountered similar behavior? As I wrote above, seems it's > related to the mpsse mode only (ft2232-based cable drivers).
ive personally been using a gnICE (FT2232) and gnICE+ (FT2232H) device with
latest urjtag trunk without problems. by "using", i mean doing real work with
JTAG, not just "cable;detect;quit". this setup is based on:
libusb 1.0.6
libftdi-1.0 branch which includes libusb-1.0 support
the big item i see here is that the latest libftdi release still doesnt
include the async support that comes with libusb-1.0, and you're using that
version. i do most of m urjtag development though against libusb-0.x.
when you configure trunk, what version of libusb does it say it's using ? do
you only have libusb-1.x + libusb-compat installed ? i dont think ive tested
that layer ... current trunk natively supports libusb-1.0 without the need for
the external compat layer. i wonder if we should tweak the configure script
to default to libusb-1.0 now and then only fall back to the libusb-0.x api if
it isnt available ...
-mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
