HANtune is a PC program that reads signals (variables) and writes parameters (constants) fromto the board.By reading these signals, you can see if the software is working correctly and the parameters can be changed to tune the algorithm.When the Olimexino is connected the device manager will show it as STM32 Virtual COM port.
Stm32 Virtual Com Driver Has ToThis is not the right driver, unfortunately another driver has to be installed, hang on this is the last step. After the installation Windows should now recognize the Olimexino as STMicroelectronics Virtual COM Port, see below. After 2 seconds the program will be started and if the XCP over USB block is present in the model it will show up as STMicroelectronics Virtual COM Port. Stm32 Virtual Com Drivers Under WindowsWith an installation of these drivers under Windows 10 the problem is worse. Doesn anybody have a suggestion for a different driver or solution to this problem. Would like to attach files showing the device description under Windows 7 as generated by USBTreeView but option was missing. When reading the USB Device Description with USDTreeView the error case was due to a corrupted device description. 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. The device is shown as corrupt in the Windows DeviceManager and USBTreeView, usually with the message: ConfigDescriptor 1 Error: ERRORCRC. On the menu that appears, choose Update Driver to start the Hardware Update wizard. Stm32 Virtual Com Download The LatestIf 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. But 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. I am the first to use the board in conjunction with an FTDI-Controller and this is where the problems became 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 problem melts down to a corrupted USB Device Description for the STM-Driver with the windows error message ConfigDescriptor 1 Error: ERRORCRC. This error disappears in case of unplug and replug of the device 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 to access the device with my application will be aborted by error, it seems the system description still holds the error message.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |