- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello
Q1)Is the CY7C65211A-24LTXI driver already scheduled for WHQL for the following OS version? Is automatic Windows update possible?
Windows10 IoT Enterprise LTSB (64bit)
Windows10 IoT Enterprise LTSC (64bit)
Q2) I think it needs to use Cypress's VID (0x04B4) as a condition for automatic Windows update. If a customer-specific VID( other than 0x04b4) is set in USB-Serial Configuration Utility,, automatic updating is not possible. Is it correct assuming?
Q3)
Is it possible to identify products using Device-ID other than VID? and, Is it possible to set a Device-ID with USB-Serial Configuration Utility,?
Best Regards
Arai
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A1)
CYUSB driver version 1.2.3.23 (driver of CY7C65211A) can support until version 1809 (LTSB/LTSC included).
USB driver will work if the IoT Enterprise OS has a Win 32 layer.
The driver we provided for Windows 10 has been used for IoT Enterprise as well.
A2)
In order to achieve automatic driver detection by Windows update, the corresponding device must be registered Microsoft Update Catalog by being certified Windows logo through WHQL test.
It is a customer responsibility. For more information,
Windows Hardware Certification Process for Customer Modified Cypress USB Driver Files
For Windows 10, Windows HLK needs to be used. Windows Hardware Lab Kit | Microsoft Docs
A3)
Are you talking about the continuation of Q2? If so, NO. See the above KBA.
If you talk about any other topic, kindly tell me the detail. (Better to create other Community thread.)
Best regards,
Hirotaka Takayama
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A1)
CYUSB driver version 1.2.3.23 (driver of CY7C65211A) can support until version 1809 (LTSB/LTSC included).
USB driver will work if the IoT Enterprise OS has a Win 32 layer.
The driver we provided for Windows 10 has been used for IoT Enterprise as well.
A2)
In order to achieve automatic driver detection by Windows update, the corresponding device must be registered Microsoft Update Catalog by being certified Windows logo through WHQL test.
It is a customer responsibility. For more information,
Windows Hardware Certification Process for Customer Modified Cypress USB Driver Files
For Windows 10, Windows HLK needs to be used. Windows Hardware Lab Kit | Microsoft Docs
A3)
Are you talking about the continuation of Q2? If so, NO. See the above KBA.
If you talk about any other topic, kindly tell me the detail. (Better to create other Community thread.)
Best regards,
Hirotaka Takayama
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>A1)
>CYUSB driver version 1.2.3.23 (driver of CY7C65211A) can support until version 1809 (LTSB/LTSC included).
>USB driver will work if the IoT Enterprise OS has a Win 32 layer.
>The driver we provided for Windows 10 has been used for IoT Enterprise as well.
>
>Windows10 IoT Enterprise LTSB (64bit)
>Windows10 IoT Enterprise LTSC (64bit)
>
Q1)I am understanding that above both driver are supported, but The above drivers already have WHQL tests passed and automatic Windows Update is possible.Also, both PID and VID are registered as Cypress number. is it correct?
>A2)
>In order to achieve automatic driver detection by Windows update, the corresponding device must be registered
>Microsoft Update Catalog by being certified Windows logo through WHQL test.
>It is a customer responsibility. For more information,
Windows Hardware Certification Process for Customer Modified Cypress USB Driver Files
>For Windows 10, Windows HLK needs to be used. Windows Hardware Lab Kit | Microsoft Docs
>
Q2-1)If the customer wants to use a dedicated driver for their product, thye can register their own VID/PID in the drive file. Also, if thye want to support automatic Windows Update, they need to aply by themselves and pass the WHQL test. is it correct?
Q2-2) I am understanding that Device ID can not be used as customer's driver identification information. but , is it possibe to use CHID information(Manufacture, Family) in their driver file?
Best Regards
Arai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A1. Correct.
A2-1. Correct.
A2-2. I will clarify the things that customers will do. They can set their own informaton on their driver.
PID and VID will be changed. Also, Manufacturer string and Product string can be changed for their product. Configuration Utility is helpful to do these changes.
For more information, kindly ask Microsoft.
Best regards,
Hirotaka
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Takayama san
Thank you for your reply.
Best Regards,
Arai