<?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>LPC MicrocontrollersのトピックRe: LPC4357 USB serial host</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4357-USB-serial-host/m-p/625161#M24555</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Quyen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FTDI devices use vendor specific comands which requires an specific protocol/driver. LPC USB Host CDC example is design to communicate with standard CDC devices, that is why you cannot communicate with it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am attaching an USB capture where an FTDI device was connected. As you can see, it is shown as vendor-specific protocol:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/6261iF60823051775FF1E/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When connecting a FTDI device, its descriptors contain just one interface that uses vendor-specific class so Host cannot find an endpoint to configure this device (this should be done through device’s driver, but Host could not look for a vendor-specific driver)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this can help you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Isaac&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Nov 2016 21:18:49 GMT</pubDate>
    <dc:creator>isaacavila</dc:creator>
    <dc:date>2016-11-04T21:18:49Z</dc:date>
    <item>
      <title>LPC4357 USB serial host</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4357-USB-serial-host/m-p/625160#M24554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I want to use USB port on LPC4357 as USB serial host and communicate with FTDI chip via FT232R USB UART.&lt;/P&gt;&lt;P&gt;I use nxpUSBlib, CDC class for communicate. At the enumerate process, the usb lib return that it’s is not valid CDC device when it read the device descriptor.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is CDC Class host is the right way for communicate with FTDI USB UART chip and if it’s not, which is the correct way for using NXPUSBlib&lt;/P&gt;&lt;P&gt;to communicate with FTDI USB UART chip?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Nov 2016 09:45:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4357-USB-serial-host/m-p/625160#M24554</guid>
      <dc:creator>quyenngo</dc:creator>
      <dc:date>2016-11-02T09:45:08Z</dc:date>
    </item>
    <item>
      <title>Re: LPC4357 USB serial host</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4357-USB-serial-host/m-p/625161#M24555</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Quyen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FTDI devices use vendor specific comands which requires an specific protocol/driver. LPC USB Host CDC example is design to communicate with standard CDC devices, that is why you cannot communicate with it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am attaching an USB capture where an FTDI device was connected. As you can see, it is shown as vendor-specific protocol:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/6261iF60823051775FF1E/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.png" alt="pastedImage_3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When connecting a FTDI device, its descriptors contain just one interface that uses vendor-specific class so Host cannot find an endpoint to configure this device (this should be done through device’s driver, but Host could not look for a vendor-specific driver)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this can help you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Isaac&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2016 21:18:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC4357-USB-serial-host/m-p/625161#M24555</guid>
      <dc:creator>isaacavila</dc:creator>
      <dc:date>2016-11-04T21:18:49Z</dc:date>
    </item>
  </channel>
</rss>

