2024-11-12 11:21 AM - last edited on 2024-11-12 12:47 PM by Andrew Neil
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.
2024-11-12 12:57 PM - edited 2024-11-12 12:58 PM
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:
2024-11-12 01:00 PM
Older ST-LINKs do not have VCP. You cannot find the VCP in device manager probably because there isn't any.
2024-11-12 01:12 PM
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
2024-11-12 01:13 PM
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?
2024-11-12 01:29 PM
@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 @SofLit can confirm whether or not there is one?
2024-11-12 01:36 PM
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
2024-11-12 02:49 PM
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
2024-11-13 12:46 AM
@Andrew Neil wrote:
The Product Page overview also says nothing about VCP:
https://www.st.com/en/evaluation-tools/32f411ediscovery.html#overview
Perhaps @SofLit can confirm whether or not there is one?
Yes I think VCP is not supported in that board as it was not stated in the user manual UM1842.
2024-11-14 02:35 AM
Hey, it appears as STM32 STlink