<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Kinetis Microcontrollers中的主题 USB Standard CDC Driver</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/USB-Standard-CDC-Driver/m-p/475039#M28892</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have developed a simple USB virtual com port (CDC) for a K20 microcontroller. I am currently using my own inf driver file with my own PId/VId.&lt;/P&gt;&lt;P&gt;It works great and I am able to transmit and receive data with ease.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, is there a Pid/Vid combination that will cause any computer to automatically recognize the device as a standard CDC device when it's first plugged in and thus install the appropriate device driver? (I don't want end users to have to manually acquire and install my driver file)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Jan 2016 21:56:32 GMT</pubDate>
    <dc:creator>danielg14</dc:creator>
    <dc:date>2016-01-29T21:56:32Z</dc:date>
    <item>
      <title>USB Standard CDC Driver</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/USB-Standard-CDC-Driver/m-p/475039#M28892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have developed a simple USB virtual com port (CDC) for a K20 microcontroller. I am currently using my own inf driver file with my own PId/VId.&lt;/P&gt;&lt;P&gt;It works great and I am able to transmit and receive data with ease.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, is there a Pid/Vid combination that will cause any computer to automatically recognize the device as a standard CDC device when it's first plugged in and thus install the appropriate device driver? (I don't want end users to have to manually acquire and install my driver file)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jan 2016 21:56:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/USB-Standard-CDC-Driver/m-p/475039#M28892</guid>
      <dc:creator>danielg14</dc:creator>
      <dc:date>2016-01-29T21:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: USB Standard CDC Driver</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/USB-Standard-CDC-Driver/m-p/475040#M28893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use an interface association desriptor for CDC with the device class set for communication and control to values&lt;BR /&gt;0x02, 0x02, 0x00&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Windows 10 will automaticall install usbser.sys (generic CDC on Windows) - See &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://msdn.microsoft.com/en-gb/library/windows/hardware/dn707976%28v=vs.85%29.aspx" rel="nofollow"&gt;https://msdn.microsoft.com/en-gb/library/windows/hardware/dn707976%28v=vs.85%29.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are a few other tricks for Windows:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://msdn.microsoft.com/en-us/library/windows/hardware/ff537430%28v=vs.85%29.aspx" rel="nofollow"&gt;https://msdn.microsoft.com/en-us/library/windows/hardware/ff537430%28v=vs.85%29.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://msdn.microsoft.com/en-us/windows/hardware/gg463179.aspx" rel="nofollow"&gt;https://msdn.microsoft.com/en-us/windows/hardware/gg463179.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know of no VID/PD combinations that are designed to control such things and generally you will need to have a valid VID for your company (or use a PID under Freescale's - which you can request through your sale's representative as log as your production is &amp;lt; 10k).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In some cases you can also instruct the user to chose a standard driver from a set that Windows keeps, but this is also messy since Windows will issue a warning that it can't confirm that it matches with the device and will recommend to not use it - but it works with RNDIS from experience (which is based on CDC) so you you may find one that does operate with some trial and error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Most CDC users will supply their driver with the product or on their web site and get it signed (costs about $100 year I believe) so that there are no warnings that it coud be from an untrusted source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jan 2016 22:57:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/USB-Standard-CDC-Driver/m-p/475040#M28893</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2016-01-29T22:57:32Z</dc:date>
    </item>
  </channel>
</rss>

