2017-10-27 12:30 PM
I am using the STM USB CDC VCP middle-ware stack on STM32F777II MCU. I just wanted to know if there is a way to create the application in such a way that when this USB CDC VCP device connects to my windows PC, it comes up with a custom VID, PID, MANUFACTURER_STRING, PRODUCT_STRING. I see that on the mcu side this can be done by changing the following macros in 'usbd_desc.c' file:
&sharpdefine USBD_VID 1155
&sharpdefine USBD_MANUFACTURER_STRING (uint8_t*)'STMicroelectronics'&sharpdefine USBD_PID_FS 22336&sharpdefine USBD_PRODUCT_STRING_FS (uint8_t*)'STM32 Virtual ComPort'However, when I change any of these, I am unable to use the USB VCP windows driver provided by STM. Do I need to customize the windows drivers as well. If yes, then is there a quick way of doing so?
#usb-cdc #usb-hs-vcp #usb-vcp #stm32f72017-10-28 02:01 PM
Hello !
First of all VID's are managed from usb.org
The driver is usbser.sys and belongs to windows OS.
You need to customize the stmcdc.inf by change the PID and VID inside the file and reinstall it again.
But, the new stmcdc.inf will not pair with stmcdc.cat, which is the 'catalog file' that contains the driver's digital signature.
So the new produced .inf file (driver) will not be digitaly signed.
Regards
vf