<?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>i.MX ProcessorsのトピックRe: USBH2 HSIC not working</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535043#M84949</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arindam&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on Sabre SD board these signals are also used by enet, so one can disable it,&lt;/P&gt;&lt;P&gt;it may be useful to check attached Linux Manual Chapter 45&lt;/P&gt;&lt;P&gt;Fast Ethernet Controller (FEC) Driver.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Aug 2016 23:47:10 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2016-08-17T23:47:10Z</dc:date>
    <item>
      <title>USBH2 HSIC not working</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535042#M84948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our board is based on Sabre SD board. In a revision of the board we added USB4604i Hub chip and hence we use USBH2 with HSIC interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using i.MX Dual.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The USB Hub chip is not configured by i.MX6 and it is an independent unit with no control from i.MX6.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using Linux 3.10.53 and our BSP is based on the reference BSP of Sabre SD board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following were ensured or added:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. NVCC_RGMII is connected to 1.2V&lt;/P&gt;&lt;P&gt;2. IOMUXC_SW_PAD_CTL_GRP_DDR_TYPE_RGMII is set with the following in u-boot (DDR_SEL is set to 10 for 1.2V) -&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DATA 4, 0x020e0790, 0x00080000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. A dts entry is added:&lt;/P&gt;&lt;P&gt;&amp;amp;usbh2 {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; pinctrl-names = "idle", "active";&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; pinctrl-0 = &amp;lt;&amp;amp;pinctrl_usbh2_1&amp;gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; pinctrl-1 = &amp;lt;&amp;amp;pinctrl_usbh2_2&amp;gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; osc-clkgate-delay = &amp;lt;0x3&amp;gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; status = "okay";&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It also includes imx6qdl.dtsi which contains entry for usbh2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, we are unable to enumerate the USB hub chip.&lt;/P&gt;&lt;P&gt;usb 2-1: new high-speed USB device number 66 using ci_hdrc&lt;/P&gt;&lt;P&gt;usb 2-1: device no response,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; device descriptor read/64, error -71&lt;/P&gt;&lt;P&gt;usb 2-1: device no response,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; device descriptor read/64, error -71&lt;/P&gt;&lt;P&gt;usb 2-1: new high-speed USB device number 67 using ci_hdrc&lt;/P&gt;&lt;P&gt;usb 2-1: device no response,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; device descriptor read/64, error -71&lt;/P&gt;&lt;P&gt;usb 2-1: device no response,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; device descriptor read/64, error -71&lt;/P&gt;&lt;P&gt;usb 2-1: new high-speed USB device number 68 using ci_hdrc&lt;/P&gt;&lt;P&gt;usb 2-1: device not accepting address 68, error -71&lt;/P&gt;&lt;P&gt;usb 2-1: new high-speed USB device number 69 using ci_hdrc&lt;/P&gt;&lt;P&gt;usb 2-1: device not accepting address 69, error -71&lt;/P&gt;&lt;P&gt;hub 2-0:1.0: unable to enumerate USB device on port 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;NOTE - &lt;/STRONG&gt;The same thing works when we use the SDK utility i.e. USB enumeration of the USB Hub chip happens when the SDK is used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are we missing something ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2016 11:08:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535042#M84948</guid>
      <dc:creator>arindamroy</dc:creator>
      <dc:date>2016-08-17T11:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: USBH2 HSIC not working</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535043#M84949</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arindam&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on Sabre SD board these signals are also used by enet, so one can disable it,&lt;/P&gt;&lt;P&gt;it may be useful to check attached Linux Manual Chapter 45&lt;/P&gt;&lt;P&gt;Fast Ethernet Controller (FEC) Driver.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2016 23:47:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535043#M84949</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-08-17T23:47:10Z</dc:date>
    </item>
    <item>
      <title>Re: USBH2 HSIC not working</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535044#M84950</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using different pads for Ethernet, so no conflict on that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apart from that, Is there any thing missing on the configuration as mentioned in the first post ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Arindam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Aug 2016 02:43:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535044#M84950</guid>
      <dc:creator>arindamroy</dc:creator>
      <dc:date>2016-08-18T02:43:23Z</dc:date>
    </item>
    <item>
      <title>Re: USBH2 HSIC not working</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535045#M84951</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arindam&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think no.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Aug 2016 03:22:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535045#M84951</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-08-18T03:22:57Z</dc:date>
    </item>
    <item>
      <title>Re: USBH2 HSIC not working</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535046#M84952</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not see any signals on the HSIC lines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any probable reason, even after the above mentioned configuration ( and no conflict with ENET lines ) ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Arindam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Aug 2016 08:16:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535046#M84952</guid>
      <dc:creator>arindamroy</dc:creator>
      <dc:date>2016-08-19T08:16:34Z</dc:date>
    </item>
    <item>
      <title>Re: USBH2 HSIC not working</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535047#M84953</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arindam&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one can check if USBH2 clock is enabled in CCM_CCGRn&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Aug 2016 09:36:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/USBH2-HSIC-not-working/m-p/535047#M84953</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-08-19T09:36:58Z</dc:date>
    </item>
  </channel>
</rss>

