<?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: USBDCD module signals in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/USBDCD-module-signals/m-p/441304#M25868</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;Customer can connect VBUS signal to either USB module (USB0 or USB1).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The USB FS module wakeup from a a low power mode (except in LLS/VLLS mode where USB is not powered) occurs through an asynchronous interrupt triggered by activity on the USB bus. Setting the USBTRC0[USBRESMEN] bit enables this function. It needs a separate interrupt to wakeup USB FS module from low power mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The USB HS module is different. &lt;/P&gt;&lt;P&gt;In Stop/VLPS, the USB controller can generate an interrupt on VBUS detection or on Resume/Wakeup signaling on the USB1_DP and USB1_DM pins.&lt;/P&gt;&lt;P&gt;It needs a separate interrupt to wakeup USB HS module from low power mode.&lt;/P&gt;&lt;P&gt;In LLS/VLLS, the USB1_VBUS, USB1_DP and USB1_DM are input pins to the LLWU and a transition on those pins can generate a wakeup provided the USB is powered. In VLLS0 and VLLS1, a wakeup is only generated if the USB PHY was powered on entry into the low power mode. It does not need a separate wake up signal, which could be the same signal through LLWU module to wake up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There doesn't need a 5V tolerance GPIO pin, customer can use a normal I/O to wake up the core from low power mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With it helps.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Ma Hui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Jul 2015 05:19:28 GMT</pubDate>
    <dc:creator>Hui_Ma</dc:creator>
    <dc:date>2015-07-02T05:19:28Z</dc:date>
    <item>
      <title>USBDCD module signals</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/USBDCD-module-signals/m-p/441303#M25867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like to clarify the signals for the USBDCD module. I'll be using USB0 for normal FS communication. If I want to add the device charger detection module would I connect the VBUS signal (from the USB connector) to pin USB1_VBUS on the K65 processor for either USB0 or USB1? If I need to allow for the processor to be in a low power mode it sounds like I would need a separate interrupt with low power wakeup capability to power up the USB module? If so I believe I can use a status output from the charger chip to generate an interrupt with the correct voltage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Elizabeth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Jun 2015 20:39:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/USBDCD-module-signals/m-p/441303#M25867</guid>
      <dc:creator>ERussell</dc:creator>
      <dc:date>2015-06-29T20:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: USBDCD module signals</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/USBDCD-module-signals/m-p/441304#M25868</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;Customer can connect VBUS signal to either USB module (USB0 or USB1).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The USB FS module wakeup from a a low power mode (except in LLS/VLLS mode where USB is not powered) occurs through an asynchronous interrupt triggered by activity on the USB bus. Setting the USBTRC0[USBRESMEN] bit enables this function. It needs a separate interrupt to wakeup USB FS module from low power mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The USB HS module is different. &lt;/P&gt;&lt;P&gt;In Stop/VLPS, the USB controller can generate an interrupt on VBUS detection or on Resume/Wakeup signaling on the USB1_DP and USB1_DM pins.&lt;/P&gt;&lt;P&gt;It needs a separate interrupt to wakeup USB HS module from low power mode.&lt;/P&gt;&lt;P&gt;In LLS/VLLS, the USB1_VBUS, USB1_DP and USB1_DM are input pins to the LLWU and a transition on those pins can generate a wakeup provided the USB is powered. In VLLS0 and VLLS1, a wakeup is only generated if the USB PHY was powered on entry into the low power mode. It does not need a separate wake up signal, which could be the same signal through LLWU module to wake up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There doesn't need a 5V tolerance GPIO pin, customer can use a normal I/O to wake up the core from low power mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With it helps.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Ma Hui&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jul 2015 05:19:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/USBDCD-module-signals/m-p/441304#M25868</guid>
      <dc:creator>Hui_Ma</dc:creator>
      <dc:date>2015-07-02T05:19:28Z</dc:date>
    </item>
  </channel>
</rss>

