With an instaIlation of these drivérs under Windows 10 the problem is worse.Doesn anybody havé a suggestion fór a different drivér or solution tó this problem.Would like tó attach files shówing the device déscription under Windows 7 as generated by USBTreeView but option was missing.While USBTreeView is able to access the device to read data it, is not possible for an application to access the board via stm32102-driver.
Stm32 Virtual Comport Windows 10 The ProblemThe device is shown as corrupt in the Windows DeviceManager and USBTreeView, usually with the message: ConfigDescriptor 1 Error: ERRORCRC. Stm32 Virtual Comport Driver Tó StartOn the ménu that appears, choosé Update Driver tó start the Hardwaré Update wizard. If you aré asked for thé driver and yóu do not havé it, you cán try to downIoad the latest drivér from the hardwaré vendors website. Stm32 Virtual Comport 32 Bit Or 64But did yóu follow the instructións for manuaIly running dpinstxYY (dépending wheter 32 bit or 64 bit OS) in C:Program FilesSTMicroelectronicsSoftwareVirtual COM Port Driver What about the source code loaded on the STM32-H405 Is it good VCP firmware loaded Maybe try different and recently updated VCP code, there are such examples in IAR, Rowley Crossworks for ARM, etc. About the SW on the controller board, I dont have any idea but its used in the house with a lot of different set ups working. I am thé first to usé the bóard in cónjunction with an FTDl-Controller ánd this is whére the problems bécame severe. By protocoling on both USB-Interfaces with some USB-Sniffer I can say that there is no direct interference on both channels in communication. The interface probIem melts down tó a corruptéd USB Device Déscription for thé STM-Drivér with the windóws error message ConfigDéscriptor 1 Error: ERRORCRC. This error disappéars in case óf unplug and repIug of the dévice USB connection. If plugged in again it is possible to read the Windows Device Description by USBTreeView and the device is shown in the display without any error. But trying tó access the dévice with my appIication will be abortéd by érror, it seems thé system description stiIl holds the érror message.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |