STM32F407G-DISC1 goes to unspecified

Install the driver:

https://www.st.com/en/development-tools/stsw-link009.html

After that also it is suggested to update ST-Link firmware:

https://www.st.com/en/development-tools/stsw-link007.html

What is the history of the USB cable? Was it supplied with the kit or sourced elsewhere?

Consider to source a quality USB cable that is as short as practical for your development but must be fully loaded. There are many USB cables that feature only Vbus & Ground (ie. missing the signal D+ / D-) that may raise the same fault.

Please post your update after testing.

Which end of the DISCO board are you trying to connect to PC?

JW

Very good call @Community member​, the MINI USB connector (larger one of the 2 on this kit) MUST be used to develop with the kit. Then you should see the enumeration of the ST-Link front end tool.

If you have a continuity meter handy, you can probe each pin of the cable. That is, insert the cable into the mini USB connector of the kit but do not mate with the PC. Then check the continuity of the free USB Type A connector to the kit. It is possible that you have only a "charging cable" - openly we wasted some time on this ourselves in the lab. Vendor must have saved pennies for this garbage cable.

Are you in the US or Canada?

If yes, we use Arrow all the time due to the FREE shipping on any purchase and next day delivery. Better than Amazon :)

Here are some that would work fine but do review the length of each:

https://www.arrow.com/en/products/88732-8510/molex

* USB 1.1 spec but is fully loaded with all 4 wires

* USB 2.0 is a better choice so you can use the same cable anywhere

• 0.8 mm

https://www.arrow.com/en/products/ak672m-1/assmann-wsw-components-inc

• 1 m length & USB 2.0 compliant

If in a pinch, you may be able to source one locally at the Dollar Store but could not guarantee the pinout. Walmart is another choice but will be more $$ than Arrow.

Before you proceed, do check the properties of the USB device inside of your Device Manager and share the details.

Control Panel -> Device Manager -> Select the Yellow Marked function -> Details -> Hardware IDs

What does that show? A proper USB widget must emit valid IDs and are listed here.

Hope this helps.

Hang on a sec - the screen looks good. If you remove the cable, does the ST Link icon get removed?

Is it possible that you may have some older device drivers on this box for this kit?

Consider to right mouse click on this function and select to remove AND delete the driver package. This procedure will then remove the driver from your box.

Unplug the cable and seat it back again to your USB port on your PC. Does the kit get installed with a driver? If yes, repeat the above procedure. You are basically removing any and all compatible drivers from your PC. We have had to do this on some of our older PC boxes. Once this was done, proceed to download the latest driver package noted above by @Community member​.

Hmm. Which OS are you on? Is that Windows 10? Somewhere around here believe to have the same kit but on Windows 7 (64 bit).

What does your toolchain report? It cannot locate the kit?

Toolchain = buzzword for the software tools that will make use of your kit.

What is your compiler? Does your compiler complain about this kit? Perhaps it will work regardless of where it is listed under Device Manager.

If you have not done so already, install Cube MX (latest version); also ST-Link utilities and the CubeF4 package:

https://www.st.com/en/development-tools/stsw-link004.html

• after installing and running this tool - is this program able to locate your kit?

https://www.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32-standard-peripheral-library-expansion/stsw-stm32068.html

https://www.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32cube-mcu-packages/stm32cubef4.html

Does the STLINK program detect the kit? There is a CONNECT option in one of the pull-down menus. Does that work to locate the kit?

Target -> Connect

What is the reported message?

Ok :) Then what is the issue?

If this connects, you are good to go and can use the kit.