Re: [OpenOCD-user] FTDI and ST-Link V2 problems with OpenOCD 0.11.0 on Windows

[Xiaofan C. <xia...@gm...>]

On Wed, Jul 21, 2021 at 4:50 PM Xiaofan Chen <xia...@gm...> wrote:
>
> On Tue, Jul 20, 2021 at 9:30 PM R. Diez via OpenOCD-user
> <ope...@li...> wrote:
> > Unfortunately, I am still at a loss regarding the ST-Link V2. That is no
> >  composite device, so your suggestion wouldn't help in that case.
> >
>
> Take note ST-Link V2 is a USB Composite Device.
>
> You have an option for the following two.
> 1) Debug (WinUSB.sys) + Virtual Com Ports (usbser.sys)
> 2) Debug (WinUSB.sys) + Virtual Com Ports (usbser.sys) + USB Mass Storage
>
> In my test, I choose to go with Option 1. I do not see the difference
> if using Option 2.
>
> And I do not need to use WinUSB driver to replace the USB
> Composite Parent. It just works with ST's default driver.
>

Even if I switch to Option 2, I still have no issues.

C:\work\libusb\openocd_test\release\bin> .\openocd.exe -f board\st_nucleo_f3.cfg
Open On-Chip Debugger 0.11.0 (2021-03-07-12:52)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The
results might differ compared to plain JTAG/SWD
srst_only separate srst_nogate srst_open_drain connect_deassert_srst

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 1000 kHz
Info : STLINK V2J37M27 (API v2) VID:PID 0483:374B
Info : Target voltage: 3.253891
Info : stm32f3x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for stm32f3x.cpu on 3333
Info : Listening on port 3333 for gdb connections



-- 
Xiaofan