Recertifying a Customized Driver Package (WLK)

Transcription

1 Recertifying a Customized Driver Package (WLK) UPDATED: May 7, 2012 The driver certification process is always changing; if you want to ensure proper certification please read the documentation at Silicon Labs is not responsible for failing submissions due to changes in Microsoft s submission process. OVERVIEW This document explains in detail the process to recertify a customized Silicon Labs CP210x or USBXpress device driver through the Windows Dev Center. Below is a brief description of the entire process. First, you will need to buy a code signing certificate from Verisign and create a Windows Live account (you can also link an existing live account to the Windows Dev Center). Then you will need to accept the reseller submission of the original device driver granted by Silicon Labs (there is a single flat fee for accepting this). Next, you will download the Winqual Tools needed to create and submit your updated driver package. Once these tools are installed you should download the WST file from the reseller submission. This WST file is an XML file that contains description of the driver set. Using the Winqual Submission Tool you will modify this file to point to your updated submission package, which then can be submitted to the Windows Dev Center as a Driver Update Acceptable. Driver Update Acceptable is a term used by Microsoft to describe a driver update in which binaries do not change. In this case, your customized submission only includes an INF change and changes to the Driver Installer INI file (the Driver Installer is optional and does not affect the submission). After your submission is complete and reviewed you can then download your signed catalog files to be included in your custom driver installation (there is a fee for each OS you will support for the update submission). *For the latest fees see and or whqlbill@microsoft.com. Silicon Labs itself does not charge or collect any fee for this process. Note: The submission process is always changing. If what you see in this document does not match up with the options in the tools or on the Winqual website please visit and open a support request to notify that an update is needed to this document. Note: During the submission process Microsoft might require you to accept multiple agreements before allowing you to continue with the submission. You must sign all required agreements to fully certify your driver. These agreements are specific to Microsoft, so questions on them should be directed to sysdev@microsoft.com. Note: This process may require that you have as a trusted website in your browser in order to upload your submission package. Note: This document assumes that you have already created and tested your customized driver package using the Driver Customization Wizard available in the software package for AN220. AN220 Links are provided below: AN220 Documentation: AN220 Software:

2 1. OBTAIN VERISIGN AND WINDOWS LIVE LOGIN The first step requires buying a code signing certificate from Verisign. This can be purchased at The certificate that should be obtained is the Code Signing Certificate for Microsoft Authenticode. To be a reseller you must also have an account with Windows Live, visit and apply for an account (you can also link an existing Windows Live account if you have one). Then contact Silicon Labs customer support and ask to become a reseller for the driver you want to recertify. This can be done on the Silicon Labs website, Provide Silicon Labs with: the name of your company that you registered your Windows Live and Windows Dev Center account the type of driver (VCP or USBXpress) the driver version and they will specify you as a reseller for your driver. Next you will need to accept the granted reseller submission. After you obtain your Verisign certificate you will need to notify Dev Center of your certificate. This is done by signing a simple EXE file from the Dev Center using your new digital certificate. To do this go to Administration->Upload a New Digital Certificate and follow the instructions there.

3 2. ACCEPT RESELLER SUBMISSION Login to your Windows Live Account at the Windows Dev Center and go to Hardware Logo->Manage Logo to view and accept the reseller submission. The current pricing for the reseller submission can be found on the Dev Center ( or the Windows Hardware Developer Central ( sites. If you get an Alert! No submissions were found message change the Submitted By section to Entire Company and the Period Section to More Than 1 Year, then click the Apply button.

4 3. DOWNLOAD WINQUAL TOOLS AND WINDOWS UPDATES You will need to download and install the following tool: Winqual Submission Tool To download this, log in to Windows Dev Center and go to Hardware Logo- >Create Logo and the download link will appear. Once you have installed the above tool, go to Windows Update to ensure that you have all of the latest updates for your computer. It is recommended to obtain all critical and security updates and service packs. The following are specifically recommended for Windows XP users: Windows XP Update for Microsoft Core XML Services (MSXML) 6.0 Service Pack 1 (KB934268) Windows XP Microsoft.NET Framework 3.0: x86 (KB928416) Windows XP Update for Windows XP (KB920342) Windows XP Update for Windows XP (KB904942)

5 4. DOWNLOAD THE WST FILE Login to Windows Dev Center, and go to your newly accepted reseller submission (See step 2 for instructions on how to get back to the reseller submission. On the Summary & Tasks tab, find the WST File link under the Download section. Click this link to download the WST file (which is in an XML format) and save it. This will be used with the Winqual Submission Tool in the next steps to create your updated driver submission package.

6 5. CREATE YOUR UPDATED DRIVER SUBMISSION PACKAGE Follow these steps to create your updated driver submission package: Launch the Winqual Submission Tool, and in the Submission Type drop down at the top choose "Driver Update Submission".

7 Go to Submission->Open... and open the WST file that you downloaded above. Look at the list of supported operating systems (currently Windows XP, Server 2003 and Vista x86/x64 and Windows 7 x86/x64 are now supported during the submission process see the note below for more information). If you do not want support for one of the currently supported operating systems, then click corresponding line and select "Remove". NOTE: There is a charge for each individual OS that you will support. The current pricing for the each OS can be found on the Dev Center ( or the Windows Hardware Developer Central ( sites. NOTE: Windows XP is now allowed a complimentary signature by Dev Center and therefore might not show up in this list of Operating Systems, depending on when the submission was placed. To include a signature for XP Check the box during the submission process online as instructed in the steps for Section 6.

8 Once you have a list of all OS's you would like to support, you will need to update the driver package that each of them points to: o Click on an OS line and select "Edit" and a dialog box will come up. o In the Edit Drivers section browse to your customized driver package directory created from AN220 and click OK. o Repeat the above steps for each OS line.

9 When you have targeted the customized driver for all of the OS's, click "Create Package". This will produce a CAB file along side your WST file that you downloaded before.

10 6. SIGNING YOUR CAB FILE WITH VERISIGN For submission to Windows Dev Center, Microsoft requires that the CAB file be signed. The Verisign certificate obtained in step one will provide you with the PFX file needed to sign the CAB file: At the command prompt, navigate to the directory that contains signtool.exe. If you do not already have signtool.exe it is available in the Microsoft Platform SDK or the Windows Driver Kit. Run the following command: signtool sign /f <PFX file path> /p <PFX file password> <CAB file path> where o PFX file path is the location of your PFX file from Verisign o PFX file password is the password for your PFX file o CAB file path is the location of your CAB file created with the Winqual Submission Tool in step 5

11 7. SUBMIT THE CREATED PACKAGE Login to Windows Dev Center and go to Hardware Logo->Manage Logo. Click on the previously accepted reseller submission. Click Upload Driver Update.

12 Click the Choose File button to the location of the downloaded your WST XML file, called WQReady.xml by Dev Center (WQReady.xml is just the numbered submission file downloaded in step 4). Then click Next. This page requires the following entries: o Select your billing group and provide the Purchase Order number (optional). o Check Signature only for OS s that you want to sign, but doesn t necessarily require testing. Any OS that was tested and specified in the Winqual Submission Tool will already be checked by default. o Supply your specific Product Name. o Firmware version can be set to whatever you desire, or N/A. The next page will allow signing of several WHQL exhibits and policies if they are required. If you agree with them, sign and click Next (Microsoft requires that they be signed in order to continue with the submission). Finally, review your submission and click Submit. It s possible you will need to install SilverLight to upload your submission. NOTE: If there are problems uploading the file ensure that you have as a trusted site in your browser.

13 8. DOWNLOADING THE SIGNED CATALOG FILES You will be notified upon approval of the submission. When your submission is approved, login to Dev Center to download the signed CAT (catalog) files to include with your driver package. This can be done as follows: Login to Dev Center and go to Hardware Logo->Manage Logo. Click on your customized submission (not your original reseller submission). Click Signed Catalog File on the right to download the CAB file that contains signed CAT files. Extract the CAT files from this CAB file to your customized driver package and it is ready for distribution. NOTE: The CAT files are needed by the driver installation to remove "Windows Hardware Warnings". The CAT files are required by 64 bit operating systems, or the drivers will not install even with a warning.