![]() ![]() This error disappears in case of unplug and replug of the device USB connection. The interface problem melts down to a corrupted USB Device Description for the STM-Driver with the windows error message ConfigDescriptor 1 Error: ERRORCRC. I am the first to use the board in conjunction with an FTDI-Controller and this is where the problems became severe.īy protocoling on both USB-Interfaces with some USB-Sniffer I can say that there is no direct interference on both channels in communication. If you are asked for the driver and you do not have it, you can try to download the latest driver from the hardware vendors website.īut did you follow the instructions for manually running dpinstxYY (depending 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.Ībout 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. On the menu that appears, choose Update Driver to start the Hardware Update wizard. The device is shown as corrupt in the Windows DeviceManager and USBTreeView, usually with the message: ConfigDescriptor 1 Error: ERRORCRC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |