Hello Paul,
I've tried
#interface/ftdi/oocdlink.cfg:
#
# Joern Kaipf's OOCDLink
#
# http://www.joernonline.de/contrexx2/cms/index.php?page=126
#
echo "WARNING!"
echo "This file was not tested with real interface, but is assumed to work as
this"
echo "interface uses the same layout as configs that were verified. Please
report your"
echo "experience with this file to openocd-devel mailing list, so it could be
marked"
echo "as working or fixed."
interface ftdi
ftdi_device_desc "OOCDLink"
ftdi_vid_pid 0x0403 0xbaf8
ftdi_layout_init 0x0508 0x0f1b
ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400
which I've found at
https://github.com/arduino/OpenOCD/blob/master/tcl/interface/ftdi/oocdlink.cfg
Now I got the following message:
GNU MCU Eclipse 32-bit Open On-Chip Debugger 0.10.0+dev-00352-gaa6c7e9b
(2018-10-20-02:36)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
WARNING!
This file was not tested with real interface, but is assumed to work as this
interface uses the same layout as configs that were verified. Please report your
experience with this file to openocd-devel mailing list, so it could be marked
as working or fixed.
Info : auto-selecting first available session transport "jtag". To override use
'transport select <transport>'.
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
none separate
cortex_m reset_config sysresetreq
Started by GNU ARM Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: no device found
Error: unable to open ftdi device with vid 0403, pid baf8, description
'OOCDLink', serial '*' at bus location '*'
I think I'm now closer to run OpenOCD fine. But I am not familiar with that USB
stuff at Windows. I've just connected my board with an ft2232 chip to USB at my
computer (running still Windows Vista) and after some time Windows has found
and installed the correct driver (as it has noted). But perhaps that is not
sufficient?
Best regards, Peter
---
** [tickets:#214] Error: The specified debug interface was not found (ft2232)**
**Status:** new
**Milestone:** 0.9.0
**Created:** Thu Dec 06, 2018 10:26 AM UTC by Dr. Peter Oehler
**Last Updated:** Thu Dec 06, 2018 12:49 PM UTC
**Owner:** nobody
Hello all.
I have a problem, running OpenOCD within Eclipse, similar to that reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751372
Is this bug not solved with the newer versions of OpenOCD?
That's the message at the console:
GNU MCU Eclipse 32-bit Open On-Chip Debugger 0.10.0+dev-00352-gaa6c7e9b
(2018-10-20-02:36)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Error: The specified debug interface was not found (ft2232)
The following debug interfaces are available:
1: parport
2: dummy
3: ftdi
4: usb_blaster
5: jtag_vpi
6: ft232r
7: amt_jtagaccel
8: gw16012
9: presto
10: usbprog
11: openjtag
12: jlink
13: vsllink
14: rlink
15: ulink
16: arm-jtag-ew
17: remote_bitbang
18: hla
19: osbdm
20: opendous
21: aice
22: cmsis-dap
23: kitprog
24: xds110
Thanks & best regards,
Peter
---
Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/openocd/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list._______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
