This is an automated email from Gerrit.
Piotr Kasprzyk (c...@ciri.pl) just uploaded a new patch set to Gerrit, which
you can find at http://openocd.zylin.com/4798
-- gerrit
commit 0c129d7946b6d9ac2697bb42368fdbb965f9552e
Author: Piotr Kasprzyk
Date: Sat Dec 8 03:27:51 2018 +0100
Fix wro
This is an automated email from Gerrit.
Tomas Vanek (van...@fbl.cz) just uploaded a new patch set to Gerrit, which you
can find at http://openocd.zylin.com/4796
-- gerrit
commit 1514cdbd2ebb924516f80388742a977f88592d99
Author: Tomas Vanek
Date: Fri Dec 7 18:34:39 2018 +0100
target: move
This is an automated email from Gerrit.
Tomas Vanek (van...@fbl.cz) just uploaded a new patch set to Gerrit, which you
can find at http://openocd.zylin.com/4797
-- gerrit
commit 572932ced38e22741994cf048ba19612f26b11f1
Author: Tomas Vanek
Date: Fri Dec 7 18:45:06 2018 +0100
target: allo
Well it is covered here as mentioned previously...
http://openocd.org/doc-release/README.Windows
---
** [tickets:#214] Error: The specified debug interface was not found (ft2232)**
**Status:** closed
**Milestone:** 0.9.0
**Created:** Thu Dec 06, 2018 10:26 AM UTC by Dr. Peter Oehler
**Last
This is an automated email from Gerrit.
Tomas Vanek (van...@fbl.cz) just uploaded a new patch set to Gerrit, which you
can find at http://openocd.zylin.com/4794
-- gerrit
commit 0205f3e588bbfe50ad7d74268a2bc15ff1d54b27
Author: Tomas Vanek
Date: Fri Dec 7 17:00:12 2018 +0100
target/corte
This is an automated email from Gerrit.
Tomas Vanek (van...@fbl.cz) just uploaded a new patch set to Gerrit, which you
can find at http://openocd.zylin.com/4795
-- gerrit
commit 1d7dee6c468ae7a3abcc9efc122678f6638e2cdc
Author: Tomas Vanek
Date: Fri Dec 7 17:51:49 2018 +0100
target/corte
> I'd imagine that this is covered already somewhere.
and if it is not, it probably should be; even if we do not love Windows (or
exactly because of this) the OpenOCD documentation should also document how to
use it on Windows, to avoid such questions..
---
** [tickets:#214] Error: The speci
Apologies Paul bit just to wrap it up...
You don't have the correct driver installed.
You need to replace the windows default one with a suitable libusb/WinUsb one.
Zadig is a common way of doing that but if it doesn't work on vista (which is
obviously very old and arguably defunct) then you'll n
- **status**: new --> closed
- **Comment**:
The ticket system is meant to track problems with OpenOCD, it's not a support
forum.
---
** [tickets:#214] Error: The specified debug interface was not found (ft2232)**
**Status:** closed
**Milestone:** 0.9.0
**Created:** Thu Dec 06, 2018 10:26 AM
Hello Tommy,
when I connect my board to an USB, I can see the device in the Windows
hardware-manager:
Bits per second: 9600
Data bits: 8
Parity: no
Stopbits: 1
Flowcontrol: none
FTDI
Driver date: 12.7.2013
Driver version: 2.8.30.0
Driver details:
Driver files:
C:\windows\system32\drivers\fser2
If you're still getting this error then there's almost certainly something
still wrong with the driver setup since OpenOCD is obviously not finding any
ftdi/oocdlink device. Have you checked Windows Device Manager to see how your
device is seen and configured etc?
Error: no device found
Error:
Hello Paul, Tommy,
I've checked now that the content of oocdlink.cfg is identical with that one
which was installed with OpenOCD.
I've tried to install Zadig USB drivers, but the actualversion is no longer
valid for Windows Vista, and with older versions the installation failed. So I
have ins
12 matches
Mail list logo
