In Windows I can't see USBD Descriptors

[Durukan]

 Hello there, I use USB CDC interface and I am sure that all my configurations are okey. There is no problem about connecting and data transfer between windows and my system, but there is a problem about descriptors such as "Manufacturer" or name of comport. There are no problems about vendor id or product id. In Linux I don't have any problem about it, so I tried to find a solution about this problem in windows and installed ST's comport driver (STM32 Virtual COM Port Driver). 

 After I updated the driver I saw comport name as "STMicroelectronics Virtual Comport" and manufacturer as "STMicroelectronics" but these are not the configuration macros that I set. As I said there is no problem in Linux, so I tried to solve the problem is on another way.

  Finally I tried to write an "inf" file as an driver to solve the problem. I wrote the driver for specific purpose but can't use the driver because it wasn't signatured. I know I can use unsigned drivers after hew changes in settings but it's not practical.

 

 I know that Linux systems directly reads the CDC interface packets but windows don't. All the solutions I thought are those but I still couldn't solve the problem, Is there any solution that I missed?

[FBL]

Hi @Durukan & welcome to ST Community

Which STM32 product are you using? You may need to try different PID. Also make sure to use latest version of cube firmware available on GitHub.

Driver signing can be complex and it is not recommended to modify INF file for windows. Windows should automatically load the appropriate driver, otherwise you may point to different driver if available by Microsoft for example. We would also suggest using USB sniffer to identify any discrepancies.

[Durukan]

 Hi, and thank you for your response,

 

I am using a STM32L072 mcu based project, But we also have different STM32 mcu based projects. We are using latest version of Cube firmwares. I changed vendor id's and product id's for testing in several times. I know driver signing is complex process, but we are planning to use USB in our devices but we don't know how to control this process.

 

 I searched for it and find some posts about it sublicence and provide generic PID are good starting but I still can't understand how to get sublicence. How can I define our projects are small or not, what kind of process that I should follow. If I get this product id will manufacturer or comport name change like I desire, even if we get sublicence how much time will take and is it necessary?

 

 As I said, I tried some solutions but I couldn't done it. I only want to change comport name and manufacturer name in windows. There is no any problem in Linux, I tested and it worked but in windows it didn't.

 

In summary, is there any simple way to change USB Device Descriptor for USB CDC or should I follow that complex process, if I should how can I get more detailed information about it.

 

Kind Regards,

Durukan

[Pavel A.]

Hi,

Unfortunately (or maybe fortunately) Windows USB device framework works in a certain way. Tweaking it is possible but the effort is significant, so it's up to you to decide if it's worth it. For specific details please visit Microsoft forums or Stack Overflow.  Linux, of course, has its advantages, as long as you can cope with its problems.

Obtaining a custom USB device id for your device is a good measure for a commercial product. For this, please send a request here.

You don't need a custom driver because Windows 10+ will recognize your CDC device by USB class, not by vendor/device IDs. Therefore you can completely skip all the headaches of signing and distributing a custom driver.

 

[FBL]

Hi @Durukan 

Sorry for my late response ! if still having issues, it seems you want to update the string descriptor in USBD defines.