FYI-
I've had problems with the libusb-0.1.12 that ships with most recent
Linux distros; I would try running with the new libusb
(libusb.sourceforge.net) 1.0, and the libusb-compat-0.1.12 that comes
with it. Hopefully distros start switching to this new libusb.
-Jeff
Rick Altherr wrote:
On Feb 3, 2009, at 1:29 PM, Georg Acher wrote:
On Tue, Feb 03, 2009 at 01:00:24PM -0800, Rick Altherr wrote:
It's possible that the USB signaling is valid for short bursts but
not
for sustained transfers. Sadly, I don't have one of these dongles to
try nor do I have a scope fast enough to
On Tue, Feb 03, 2009 at 01:00:24PM -0800, Rick Altherr wrote:
> It's possible that the USB signaling is valid for short bursts but not
> for sustained transfers. Sadly, I don't have one of these dongles to
> try nor do I have a scope fast enough to look at USB signals. If you
> can get yo
On Feb 3, 2009, at 12:43 PM, Georg Acher wrote:
On Tue, Feb 03, 2009 at 11:53:14AM -0800, Rick Altherr wrote:
Interesting. Do you have a different ft2232-based dongle to try?
Only one of the same type. It has the same issue.
I assume you built libftdi by hand then. Can you try libftdi 0
On Tue, Feb 03, 2009 at 11:53:14AM -0800, Rick Altherr wrote:
> Interesting. Do you have a different ft2232-based dongle to try?
Only one of the same type. It has the same issue.
> I assume you built libftdi by hand then. Can you try libftdi 0.14?
No difference.
> It _could_ be a design
On Feb 3, 2009, at 11:39 AM, Georg Acher wrote:
On Tue, Feb 03, 2009 at 10:54:37AM -0800, Rick Altherr wrote:
There was a large commit to the SVN trunk last night that touched the
ft2232 driver. Have you tried using the 0.1.0 release instead?
I've tried it with an older version from around
On Tue, Feb 03, 2009 at 10:54:37AM -0800, Rick Altherr wrote:
> There was a large commit to the SVN trunk last night that touched the
> ft2232 driver. Have you tried using the 0.1.0 release instead?
I've tried it with an older version from around November and had the same
problems.
> No on
On Feb 3, 2009, at 9:06 AM, Georg Acher wrote:
Hi,
I've bought the "OpenOCD USB" JTAG programmer:
http://www.embedded-projects.net/index.php?page_id=256
It has the usual FT2232, so I thought it should be supported, but
there are
some strange problems...
I've compiled the latest openocd fro
On Feb 2, 2009, at 11:32 PM, freddie_cho...@op.pl wrote:
quest 1: would that be possible to change "Type: Other " to sth like
"Type: Windows installer" on the project's file list? this would be
more informative for the users (;
There wasn't an option for that. The only windows-related b
Hi,
I've bought the "OpenOCD USB" JTAG programmer:
http://www.embedded-projects.net/index.php?page_id=256
It has the usual FT2232, so I thought it should be supported, but there are
some strange problems...
I've compiled the latest openocd from SVN and used libftdi-0.15 for
FTDI-support.
In prin
Hello,
I am using OpenOCD with an Olimex ARM-USB-OCD to debug an ARM7 platform.
The OpenOCD is from Rev 1362 with some personal patches but unrelated
to the code below ...
OpenOCD is crashing on me at :
bt
#0 buf_get_u32 (buffer=0x73677261 ,
first=0, num=32) at ../../src/helper/binarybuffer.h:5
11 matches
Mail list logo
