I hated that, so I installed the Open Source STM32 development platform, which allows you to program to the bare metal. To enable the USB you have to use the HAL. This generates a project with a lot of source files with in total about 20 lines of C code to initialize the clock sources. And I am talking about the LL interface, the HAL one is a maze. h files, with either a HAL (the default) or a Low Level interface. At the start you have to run the STM32CubeMX tool, which generates the startup and initialization code. I installed the (brand new) official STM32 development platform. But Arduino isn't a real development platform, it's for light hobby usage only. I installed Arduino and the STM32 support, the devices I had were available and the simple program (flash the led) worked right away. I checked the device and cpu configuration files, and they look pretty good, but they're only available for the common STM32F controllers. => Please how can i handle to fix this issue! if there is a wrong value generated by CubeMX! or a change that should i do in my environement (PID, VID.I think I can build a bootable image with the embedded version as installed through fpcupdeluxe. #define USBD_INTERFACE_STRING_FS "CDC Interface" #define USBD_CONFIGURATION_STRING_FS "CDC Config" #define USBD_PRODUCT_STRING_FS "STM32 Virtual ComPort" #define USBD_MANUFACTURER_STRING "STMicroelectronics" I thought that the probem is related to my USB converterĪctivate USB_Device middelware in CDC modeĬheck the CubeMX file attached for more detailsīut the problem still exist!=> VCP error ''This device cannot start(code 10)''.Īnd here is the define in "usbd_desc.c" file In the first case, i tried to configure UART but when i connect my USB TTL converter to my PC: it informs me that VCP error ''This device cannot start(code 10)''. I want to handle STM32F407 Disco via VCP. I use CubeMX to generate the code, in which the only thing I have changed is the device descriptor, although Windows still usesĭoes anybody have an idea of where to start tracking down the problem? Thank you! This makes me think it is something on the MCU USB stack where it retains information between soft resets, but I don't know how the stack works at all. It will stop working if I do a hard reset and cut power. The interesting thing I discovered is that if I plug the usb cable into the Mac or Win10 machine first and then plug it into the Win7 or 8.1 machine, I can connect to it! And it will still works after I do a soft reset. Both machines have the latest v1.5 VCP drivers from STM installed. Unable to configure serial port.'įor Windows 7 & 8.1, the device manager has the MCU listed as STMicroelectronics Virtual COM Port. For instance Putty says 'Unable to open connection to COM6. When I attempt to do the same with a Windows 7 or 8.1 machine, the COM port does not open. When I connect it to a Windows 10 or MacOS machine, I can open a terminal program and communicate with the MCU just fine. The MCU is self powered with VBus sensing. I have an embedded STM32F732 using USB FS CDC for communication. I have strange problem on my hand which I can't figure out if it is a Windows driver or USB stack issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |