W dniu 2014-04-21 22:45, Mark Byrnes pisze:
Jahn,
I got around this issue by using
http://zadig.akeo.ie to install LIBUSB drivers correctly for my Windows 7
machine.
This is noted in the README.Windows when you download the whole source, but
not if you download the pre-compiled package.
Jahn jana1972@... writes:
Paul
Thank you for the reply.
But it reports a different error now
C:\openocdbin1c:\openocdbin1\openocd -f interface/ftdi/jtagkey.cfg -f
target/mytest.cfg
Open On-Chip Debugger 0.8.0-dev-g03d7da0 (2014-02-03-18:49)
Licensed under GNU GPL v2
For bug reports,
Paul Fertser wrote:
You need to be using interface/ftdi/jtagkey2.cfg config, not the one
in interface/.
Maybe clean out the ft2232 ones?
//Peter
--
Managing the Performance of Cloud-Based Applications
Take advantage
On Tue, Feb 4, 2014 at 6:12 PM, Paul Fertser fercer...@gmail.com wrote:
On Tue, Feb 04, 2014 at 05:50:41PM +0100, Andreas Fritiofson wrote:
On Tue, Feb 04, 2014 at 05:05:51PM +0100, Yegor Yefremov wrote:
I had to install libusb-win32 with Zadig for my JTAGkey-2.
I strongly advice
On Thu, Feb 06, 2014 at 09:04:26AM +0100, Peter Stuge wrote:
Paul Fertser wrote:
You need to be using interface/ftdi/jtagkey2.cfg config, not the one
in interface/.
Maybe clean out the ft2232 ones?
I hope the runtime warning as proposed by Andreas will be enough;
those users that are
Paul Fertser wrote:
Maybe clean out the ft2232 ones?
I hope the runtime warning as proposed by Andreas will be enough;
I think it's a bad thing to teach any users to use ftdi/ if that
directory is intended to ever go away.
those users that are already using ft2232 are not having real
On Thu, Feb 06, 2014 at 01:36:33PM +0100, Peter Stuge wrote:
Paul Fertser wrote:
Maybe clean out the ft2232 ones?
I hope the runtime warning as proposed by Andreas will be enough;
I think it's a bad thing to teach any users to use ftdi/ if that
directory is intended to ever go away.
Paul Fertser wrote:
I think it's a bad thing to teach any users to use ftdi/ if that
directory is intended to ever go away.
I'm not anyone to decide, but my personal preference would be for it
to stay forever. ... I think it's easier to have them grouped
together for OpenOCD-related
Spencer Oliver wrote:
I'd prefer to avoid changing any project openocd.cfg configs again
..remember that you are an early adopter. What about the users who
have interface/$file.cfg in their configs? They'll get a warning..
Except they would have to change the driver used.
Not if they
On 6 February 2014 13:42, Peter Stuge pe...@stuge.se wrote:
Paul Fertser wrote:
I think it's a bad thing to teach any users to use ftdi/ if that
directory is intended to ever go away.
I'm not anyone to decide, but my personal preference would be for it
to stay forever. ... I think it's
On Thu, Feb 6, 2014 at 2:42 PM, Peter Stuge pe...@stuge.se wrote:
What about the users who
have interface/$file.cfg in their configs? They'll get a warning..
..when instead they could be using the new and improved driver
without having to change anything.
However, placing the ftdi configs
Andreas Fritiofson wrote:
And by now, the same logic can be applied to the ftdi-configs. We
wouldn't want to move them to interface/ at this point.
I think replacing the ones in interface/ with the ones in ftdi/ is
long overdue but oh well.
By the way, it's useful to place an 'interface.cfg'
I am using OpenOCD-7 with --enable-ft2232_libftdi with a FT2232D adapted
from Turtelizer2 on Linux
(Targer is STM32F101, a brand new project)
It's working fine...
Alain
Em 06-02-2014 10:24, Paul Fertser escreveu:
On Thu, Feb 06, 2014 at 09:04:26AM +0100, Peter Stuge wrote:
Paul Fertser
On Thu, Feb 6, 2014 at 2:32 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Wed, Feb 5, 2014 at 8:40 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Wed, Feb 5, 2014 at 12:50 AM, Andreas Fritiofson
andreas.fritiof...@gmail.com wrote:
Well, he only said he's using the libusb-win32 driver
On Thu, Feb 06, 2014 at 08:15:20AM +0100, Yegor Yefremov wrote:
How can I use WinUSB with precompiled OpenOCD 7.0 and Amontec JTAGkey2
device? I've installed WinUSB via Zadeg and OpenOCD couldn't find
device. With libusb-win32 I had no problems.
You need to be using interface/ftdi/jtagkey2.cfg
W dniu 2014-02-06 08:15, Yegor Yefremov pisze:
How can I use WinUSB with precompiled OpenOCD 7.0 and Amontec JTAGkey2
device? I've installed WinUSB via Zadeg and OpenOCD couldn't find
device. With libusb-win32 I had no problems.
Yegor
I was already answered - you use WRONG configuration
Paul,
Thank you for your help.
Now I can build the openOCD successfully but I am not able to run it
successfully. It says
C:\openocdbin1c:\openocdbin1\openocd -f interface/jtagkey.cfg -f
target/mytest.cfg
Open On-Chip Debugger 0.8.0-dev-g03d7da0 (2014-02-03-18:49)
Licensed under GNU GPL v2
For
On Tue, Feb 04, 2014 at 01:53:38PM +0100, Jahn wrote:
Paul,
Thank you for your help.
Now I can build the openOCD successfully but I am not able to run it
successfully. It says
C:\openocdbin1c:\openocdbin1\openocd -f interface/jtagkey.cfg -f
target/mytest.cfg
You should be using
Paul
Thank you for the reply.
But it reports a different error now
C:\openocdbin1c:\openocdbin1\openocd -f interface/ftdi/jtagkey.cfg -f
target/mytest.cfg
Open On-Chip Debugger 0.8.0-dev-g03d7da0 (2014-02-03-18:49)
Licensed under GNU GPL v2
For bug reports, read
On Tue, Feb 04, 2014 at 02:13:39PM +0100, Jahn wrote:
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 0403, pid cff8, description
'Amontec JTAGkey' and
serial '*'
If you're sure you have JTAGKey (and not JTAGKey 2 or
On Tue, Feb 4, 2014 at 3:29 PM, Paul Fertser fercer...@gmail.com wrote:
On Tue, Feb 04, 2014 at 02:13:39PM +0100, Jahn wrote:
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 0403, pid cff8, description
'Amontec
Hi Yegor,
On Tue, Feb 04, 2014 at 05:05:51PM +0100, Yegor Yefremov wrote:
I had to install libusb-win32 with Zadig for my JTAGkey-2. I used the
precompiled binary:
http://www.freddiechopin.info/en/download/category/4-openocd?download=99%3Aopenocd-0.7.0
I strongly advice you against using the
On Tue, Feb 4, 2014 at 5:26 PM, Paul Fertser fercer...@gmail.com wrote:
Hi Yegor,
On Tue, Feb 04, 2014 at 05:05:51PM +0100, Yegor Yefremov wrote:
I had to install libusb-win32 with Zadig for my JTAGkey-2. I used the
precompiled binary:
On Tue, Feb 04, 2014 at 05:50:41PM +0100, Andreas Fritiofson wrote:
On Tue, Feb 04, 2014 at 05:05:51PM +0100, Yegor Yefremov wrote:
I had to install libusb-win32 with Zadig for my JTAGkey-2. I used the
precompiled binary:
On Wed, Feb 5, 2014 at 12:50 AM, Andreas Fritiofson
andreas.fritiof...@gmail.com wrote:
Well, he only said he's using the libusb-win32 driver (libusb0.sys), which
can be used as a backend for libusb-1.0, just like WinUSB or libusbK...
Right now libusb (or libusbx) Windows backend does not work
25 matches
Mail list logo
