Hi,

Looks like 374b is mentioned in the stlink-v2-1.cfg configuration file in the OpenOCD directory. You can edit the %LOCALAPPDATA%VisualGDBEmbeddedDebugPackagescom.sysprogs.arm.openocdQuickSetupinterfaces.xml file to make VisualGDB recognize it automatically:

	

stlink-v2-1

ST-Link v2

interface/stlink-v2-1.cfg





0483

374B





true

NotSupported

com.sysprogs.libusb.mini

I finally got mine to work. This is basically what I had to do or why it did not work to start with.

First off download and install the STLink V2 Drivers and Utility.
This is the link for STSW-LINK003 which is the DRIVERS file from ST
http://www.st.com/st-web-ui/static/active/en/st_prod_software_internet/resource/technical/software/driver/st-link_v2_usbdriver.zip
This is the link for STSW-LINK004 which is the UTILITY file from ST
http://www.st.com/st-web-ui/static/active/en/st_prod_software_internet/resource/technical/software/utility/stsw-link004.zip

Now I uninstalled all my current drivers and then installed both of these files and drivers.

Then I plugged my board back in.

Once the drivers installed themselves I went back to Visual Studio and opened up a previous example so I could get to the settings.
Project > VisualGDB Project Properties > Debug settings. Debug Method: OpenOCD. View Mode: Quick Setup. The device type should be autodetected as STM32F4xxx. Programming Interface: ST-Link v2. Before Debugging: Load the program into FLASH/RAM. Then I clicked on the Test selected OpenOCD settings. Now when it asked me to install the WinUSB drivers I actually just hit cancel. I did not try to install them to see if that worked too but since it worked without them and I fought to get that far I just left it alone and OK’ed out. Have not had a problem since.

Hope this helps others and if you have questions ask and I will try my best to answer them. Not sure why no one answered this before and for a product that I am expected to purchase I was hoping for better tech support. Now I have 24 days to evaluate the program which should be fine but what else am I going to have issues with and not get any support 🙁

Hi,

Sorry, we tried reproducing it on our hardware (ST-Link v1 and v2) and could not get the problem. It looks like OpenOCD may not fully support st-link v2.1 at this point. Does the Texane/STLink tool work for your hardware?

@rraab wrote:

right Vendor ID but has a Device ID of 374B

Is this one of the ST Nucleo boards with mbed support etc? If so try ditching the ST drivers etc. completely and use Zadig to install a WinUSB driver for the board.

Good luck.