Please remember to vote and to mark the replies as answers if they help. It shall give 168 MHz HLCK and 48 MHz in the 48 MHz (USB). Assuming you use an up-to-date STM32CubeMX and library: Enable peripheral UBSOTGFS device only (leave over stuff uncheck) In the clock tab check the clock source is HSE HCLK. Create STM32 USB CDC device using CubeMX. A STM32CubeMX project for Discovery F4 with CDC as USB device should work out of the box. Also with Microsoft OS String Descriptor, no need to install WINUSB driver for Windows 10. 'CDC' name will be retained in order to show the differenece. This library initialize and manage completely the USB. The communication with the serial port can be handled with YAT, PuTTY, Arduino Serial Monitor and other serial terminals. This will change the source code of CDC USB HAL library. This library allows to connect an STM32F103XX to a PC, through USB, be recognised as an USB Virtual Serial Port and communicate as if it were a standard serial COM port. Msinfo32 > save as NFO (do not save as txt) post share links into this thread using one drive, drop box, or google driveĭxdiag > save as txt > post share links into this thread using one drive drop box, or google drive This project show the steps to convert STM32 USB CDC to WINUSB Device with HAL library. If possible change the default language to English: andi done it i ll remove now the r10 resistor and solder the 1.5-8k between pa12 and 3.3v. However, my Windows 10 computer doesn't even recognize that there is a USB device plugged in, only showing the FTDI adapter's COM port and my STLink v2: As of now, I've tried the following potential fixes from the other SO Q/A: In usbdcdcif. It provides always Virtual port named STMicroelectronics STLink Virtual COM Port (COMx) under Windows. NOTE: There are two Virtual COM ports: CN1 - USB PWR - this is ST-Link connector. this is a 'ArduinoSTM32-masterdriverswin' >installdrivers and installSTMCOMdrivers. It finally connects to Host and provides Virtual COM port (for User USB connector on Nucleo board). On the single computer that has the update and the other computer: if you are using STM32 official core, you need to select USB-CDC in your config to have USB-CDC. On the single computer and one of the other computers > open device manager > click view > click show hidden devices > manually expand all rowsĪ) any row displaying a yellow triangle with black exclamation mark or unknown > post images into this threadī) STMicroelectronics > right click properties > click details tab > from the property drop down menu choose hardware Ids > the vendor ID and device ID are typically displayed > right click on the value results > post images into this thread
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |