Re: [OpenOCD-user] Error: unable to open ftdi device

[<Pet...@t-...>]

Hello Paul,

I´ve deactivated it and see the composite parent on which I have replaced the driver with
WinUSB (v6.1.7600.16385)

I got the same error message with that. But when I´ve removed
#ftdi_device_desc "OOCDLink"
I see a different behavior:

C:\Program Files\GNU ARM Eclipse\OpenOCD\GNU MCU Eclipse\OpenOCD\0.10.0-10-20181
020-0522\bin>openocd -f C:\Users\oehler\workspace\Labor3\interface\thm_arduino.c
fg -f C:\Users\oehler\workspace\Labor3\mrt\board\thm_arduino.cfg
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
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: stm32f1x.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
in procedure 'init'
in procedure 'ocd_bouncer'
----


After this I´ve tried in the config file additional

ftdi_layout_init 0x0508 0x0f1b
ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400

which I have from  interface/ftdi/oocdlink.cfg
But then I see the same behavior.

I think I am now closer to the mikrocontroller board. Do you have any idea how to go on?

Best regards,
Peter

-----Original-Nachricht-----
Betreff: Re: [OpenOCD-user] Error: unable to open ftdi device
Datum: 2019-03-29T12:17:02+0100
Von: "Paul Fertser" <fer...@gm...>
An: "Pet...@t-..." <Pet...@t-...>

On Fri, Mar 29, 2019 at 11:55:08AM +0100, Pet...@t-... wrote:
> In the Options menu I´ve always used the
> Ignore Hubs or Composite Parents
> which is by default set. Perhaps here I should deactivate it?

Yes, it needs to be deactivated so that you could install driver for
the parent.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...