<?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中的主题 LPC1768FBD100 USB Host communicates with keyboard issues.</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521541#M4242</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CH Wu on Wed Dec 17 20:45:59 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;There's an issue of LPC1768FBD100 that use the USB Host function to communicate with keyboards. The USB Host has a re-try function if the keyboard doesn't feedback to Host that the Host will send request continuously.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The issue only caused while re-try to kenboard for 1 byte. If the communication date is above 2 bytes that the re-try function works fine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 17:50:29 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T17:50:29Z</dc:date>
    <item>
      <title>LPC1768FBD100 USB Host communicates with keyboard issues.</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521541#M4242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CH Wu on Wed Dec 17 20:45:59 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;There's an issue of LPC1768FBD100 that use the USB Host function to communicate with keyboards. The USB Host has a re-try function if the keyboard doesn't feedback to Host that the Host will send request continuously.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The issue only caused while re-try to kenboard for 1 byte. If the communication date is above 2 bytes that the re-try function works fine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:50:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521541#M4242</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:50:29Z</dc:date>
    </item>
    <item>
      <title>Re: LPC1768FBD100 USB Host communicates with keyboard issues.</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521542#M4243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CH Wu on Wed Dec 17 21:00:24 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Add more information.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The re-try function sometimes lose data while sending 1 byte data to the keyboard. It will cause keyboard failed on description.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It looks like chip issue of LPC1768FBD100 of different date codes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The same USB Host sample code to program to different date code chips.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The date code of 1335A, 1304A, 1403A, 1424A, 1437A are all failed to communicate with keyboard.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The date code of 1328A is always OK.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The viewer to open the USB log file. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.ellisys.com%2Fproducts%2Fdownload%2Fvisualusb.msi" rel="nofollow" target="_blank"&gt;http://www.ellisys.com/products/download/visualusb.msi&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:50:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521542#M4243</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: LPC1768FBD100 USB Host communicates with keyboard issues.</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521543#M4244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CH Wu on Wed Dec 17 21:03:51 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Enclosed the sample code of USB Host.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:50:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521543#M4244</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:50:31Z</dc:date>
    </item>
    <item>
      <title>Re: LPC1768FBD100 USB Host communicates with keyboard issues.</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521544#M4245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CH Wu on Wed Dec 17 21:12:51 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Enclosed the log files of USB.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 17:50:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC1768FBD100-USB-Host-communicates-with-keyboard-issues/m-p/521544#M4245</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T17:50:32Z</dc:date>
    </item>
  </channel>
</rss>

