On Wed, Apr 15, 2009 at 9:34 PM, twebb <taliaferro62@xxxxxxxxx> wrote: > I'm having issues getting USB up and going on HSUSB2/EHCI on > OMAP35xx-based hardware (very similar to beagle board). We're using > an SMSC3317 connected to HSUSB2, and in turn, the 3317 is connected to > an onboard hub - a SMSC USB2513. When the hub is removed from reset, > it appears that handshaking/chirping starts to happen between xcvr and > hub, but ends with the code announcing that it is "unable to enumerate > USB device on port 2". I'm guessing it's failing because we never see > PED set in the PORTSC_1 reg (and we are seeing PO=1 which doesn't make > any sense). Is the driver chirping properly? Is it identifying the speed properly? I had a similar problem. Please check the D+ and D- line for loading. I used SMSC3320 which also had similar problems because of ESD protection thermistors placed in the board. > I'm running a l-o git-based 2.6.28-omap1 kernel with > omap3_beagle_defconfig. Beagle board works fine (with patch to > ehci-omap.c and with CONFIG_USB_EHCI_HCD turned on), but my hardware > (with virtually same xcvr and and onboard hub) does not. > > Kind of new to this low level USB functionality, so a few questions... > 1. Any ideas why we'd see PORTSC_1[PO] = 1? > 2. Any suggestions on debugging basic connectivity between 35xx EHCI > controller and transceiver + hub? > > Thanks, > twebb > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
