Can we use ST VID and PID in commercial product?

[JKSah]

We are trying to build a usb temperature logger. As we know that while using usb cdc we have to define VID and PID to the usb middleware.

I have some question:

1.Can I use ST's VID and PID in our final product version?

2.If so, can I redistribute ST's Virtual COM Port driver to our customers?

3.How much does it cost to use ST's VID (0x0483) and unique PID?

4.We have a USB VID, but how much does it cost to change the VCP driver if we use our VID?

5.Do we need to define new PID per piece of the product or does it remains same for all pieces in one type of product?

[Uwe Bonnes]

Better ask your FAE.

[Pavel A.]

If your USB device exposes plain CDC interface, you don't need other PID; you already have ST PID and VID from their CDC examples.

>  can I redistribute ST's Virtual COM Port driver to our customers?

You don't need ST's Virtual COM Port driver for Win10 and other modern OS (Linux etc) which recognize CDC devices by their class, not by VID/PID.

-- pa

[JKSah]

Yes I am just using usb with CDC & MSC class simultaneously to expose flash as file system and change setting of device using CDC. So i guess i can use the same VID and PID (provided in middleware by st) without any cost or licensing?

But these drivers are needed for win7,8 and some other operation systems. Is is possible to redestribute those drivers to such customers?