Can't find STM32-F411E Discovery Board VCP

[gammmmmm]

Moved from: https://community.st.com/t5/mems-sensors/gyroscope-l3gd20-on-stm32-f411e-discovery-board/m-p/742133#M24523 as this starts a new question:

 

Thanks for replying! @waclawek.jan @Andrew Neil 
I have found the necessary libraries in the cubeF4 packages, But i'm facing another problem.
I can't find the com port of the device on the device manager, I installed the stlink driver and It still doesnt appear.
I also tried to configure the usb peipheral as virtual COM but it still doesnt work.

[Andrew Neil]

Don't forget to mark the solution in your other thread.

 

---

@gammmmmm wrote:

I can't find the com port of the device on the device manager

---

Which "device" are you referring to?

There are two on this board:

1. The ST-Link;
2. The STM32-F411E target.

 

[Pavel A.]

Older ST-LINKs do not have VCP. You cannot find the VCP in device manager probably because there isn't any.

 

[Andrew Neil]

Indeed the User Manual makes no reference to a VCP

https://www.st.com/en/evaluation-tools/32f411ediscovery.html#documentation

Although the schematic does show UART connections to the ST-Link:

https://www.st.com/en/evaluation-tools/32f411ediscovery.html#cad-resources 

 

@gammmmmm does the ST-Link show as a debugger in your Device Manager?

See: https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/tac-p/698105/highlight/true#M956 for troubleshooting tips

 

 

[Andrew Neil]

---

@Andrew Neil wrote:

Indeed the User Manual makes no reference to a VCP

---

The Product Page overview also says nothing about VCP:

https://www.st.com/en/evaluation-tools/32f411ediscovery.html#overview

 

Perhaps @mƎALLEm can confirm whether or not there is one?

[mƎALLEm]

Hello,

Are you sure you are using a data cable and not a charging cable?

If you try to connect with STM32CubeProgrammer, are you able to connect to the MCU?

[Karl Yamashita]

That STM32F411 board looks to be similar to the STM32F4DISCOVERY. 

The STM32F4DISCOVERY's on board ST-Link doesn't incorporate a VCP. I would take a guess to say the STM32F411 doesn't either.

I used a Mikroe board which added a UART port, CAN and Mikro Bus. https://www.mikroe.com/stm32f4-discovery-click-shield

 

[Tesla DeLorean]

The Original STM32F4-DISCO lacked mbed and the VCP/MSC, smaller STM32F103

Later mbed was adopted, and a newer/larger STM32F103 was employed

The STM32F4-DISC1 iteration escaped the ST-LINK/V2-1 VCP to pins, but did not change the circuit to get them to the STM32F407

The NUCLEO-F4 boards DON'T have this issue because they came out to support mbed.

But the NUCLEO-64 boards typically shared the VCP UART and ARDUINO D0/D1 pins