<?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>topic Re: Kinetis K40 USB OTG in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182374#M1802</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After digging thru the docs,&amp;nbsp; you just route the ID pin to a GPIO pin on the K40. there are examples in the KQRUG document and application notes.&lt;/P&gt;&lt;P&gt;See:&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=K40_100&amp;amp;fpsp=1&amp;amp;tab=Documentation_Tab" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=K40_100&amp;amp;fpsp=1&amp;amp;tab=Documentation_Tab"&gt;K40_100 Product Summary Page&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Sep 2012 16:31:55 GMT</pubDate>
    <dc:creator>Jack_at_Oxigraf</dc:creator>
    <dc:date>2012-09-27T16:31:55Z</dc:date>
    <item>
      <title>Kinetis K40 USB OTG</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182370#M1798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kinetis is a new part and I am trying to use it for a new design.&amp;nbsp; The peripheral that I have question on is the USB OTG.&amp;nbsp; According to the standard, USB OTG receptacle should have an ID pin to identify if connected device is an A or B device.&amp;nbsp; However, such a pin is missing from K40.&amp;nbsp; So, how does K40 knows when to be a host or when to be a device?&amp;nbsp; Does it default as to a host operation all the time?&amp;nbsp; If that is true, what happen when another default host OTG&amp;nbsp; gets connected to it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any response is appreciated.&amp;nbsp; If responses are not relevant, please at least make them funny.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jay Wong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 23:12:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182370#M1798</guid>
      <dc:creator>jay123456789</dc:creator>
      <dc:date>2011-02-09T23:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K40 USB OTG</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182371#M1799</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same question here.... hello Freescale..are you there?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 May 2011 07:05:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182371#M1799</guid>
      <dc:creator>Jack_at_Oxigraf</dc:creator>
      <dc:date>2011-05-21T07:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K40 USB OTG</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182372#M1800</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kinetis uses the USB&amp;nbsp;module from Coldfire. Take a look at Page 6 of AN3324 for OTG implementation.&amp;nbsp; Pull/Pull down resistors on D+ and D- as well as the ID pin is taken care by the MAX3353 which communicates with the core via I2C.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Jun 2011 09:26:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182372#M1800</guid>
      <dc:creator>lim2669</dc:creator>
      <dc:date>2011-06-09T09:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K40 USB OTG</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182373#M1801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Wow... so for actual OTG support, I have to add an additional IC, munch an IRQ pin, and munch an I2C interface?&amp;nbsp; That's pretty short-sighted on Freescale's part.&amp;nbsp; I'm doing a schematic pinout selection on the K60, and I noticed there wasn't a dedicated ID pin, thought maybe it was only present on the big pin count devices... nope.&amp;nbsp; There's a pin for it on the Tower Elevator, but the K60 Tower board doesn't connect to it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To be fair, I suppose Freescale would contend that if you're not doing high speed (for which you would need an external ULPI PHY anyway), then you probably don't care about true OTG.&amp;nbsp; And in my case that's true, we're probably just going to be a full-speed device, for this project anyway.&amp;nbsp; Still, rather strange that Freescale wouldn't put an ID pin on the part.&amp;nbsp; Oh well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Dec 2011 01:08:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182373#M1801</guid>
      <dc:creator>dmarks_ls</dc:creator>
      <dc:date>2011-12-01T01:08:49Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K40 USB OTG</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182374#M1802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After digging thru the docs,&amp;nbsp; you just route the ID pin to a GPIO pin on the K40. there are examples in the KQRUG document and application notes.&lt;/P&gt;&lt;P&gt;See:&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=K40_100&amp;amp;fpsp=1&amp;amp;tab=Documentation_Tab" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=K40_100&amp;amp;fpsp=1&amp;amp;tab=Documentation_Tab"&gt;K40_100 Product Summary Page&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2012 16:31:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182374#M1802</guid>
      <dc:creator>Jack_at_Oxigraf</dc:creator>
      <dc:date>2012-09-27T16:31:55Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis K40 USB OTG</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182375#M1803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;no you do not have to have an additional chip or use an I2C.. but do have to munch the pin state.&amp;nbsp; see the doc link and search for OTG in the KQRUG and app notes.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=K40_100&amp;amp;fpsp=1&amp;amp;tab=Documentation_Tab" title="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=K40_100&amp;amp;fpsp=1&amp;amp;tab=Documentation_Tab"&gt;K40_100 Product Summary Page&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2012 16:35:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-K40-USB-OTG/m-p/182375#M1803</guid>
      <dc:creator>Jack_at_Oxigraf</dc:creator>
      <dc:date>2012-09-27T16:35:20Z</dc:date>
    </item>
  </channel>
</rss>

