Thank you so much for your support Roger. I assume with the stock rom the D14 should turn on by default. Could there be something set on the board, independent of the sd card?
On Wed, Oct 7, 2015 at 3:58 PM, Roger Quadros <[email protected]> wrote: > On 07/10/15 16:54, Roger Quadros wrote: > > Sven, > > > > On 07/10/15 16:13, Sven Bock wrote: > >> Hello Roger, > >> > >> thanks for your reply. > >> > >> > >> You don't need any uEnv. All you need in the kernel is the USB EHCI > drivers. > >> > >> CONFIG_USB_EHCI_HCD=y > >> CONFIG_USB_EHCI_HCD_OMAP=y > >> > >> You will also need the TWL PMIC GPIO driver > >> CONFIG_GPIO_TWL4030=y > >> > >> > >> Where should I find this config? Also in "/sys/kernel"? > >> > > > > This is when you build the kernel. But never mind. From your cat gpio it > looks like > > it is enabled as it shows twl4030-gpio. > > > >> > >> led D14 must turn ON when USB hub is powered. Looks like the > software > >> isn't turning on power for the USB hub so I wouldn't suspect > hardware yet. > >> > >> It is not turning on. > >> > >> > >> Can you please paste your kernel boot log in pastebin and the > output of > >> cat /sys/kernel/debug/gpio > >> > >> > >> I attached the boot.log and the dmesg > >> Here is the output of gpio: > >> > >> root@arm:/sys/kernel/debug# cat gpio > >> GPIOs 0-31, platform/49050000.gpio, gpio: > >> > >> GPIOs 32-63, platform/49052000.gpio, gpio: > >> > >> GPIOs 64-95, platform/49054000.gpio, gpio: > >> > >> GPIOs 96-127, platform/49056000.gpio, gpio: > >> gpio-115 (reset ) out hi > >> gpio-117 (? ) out lo > >> gpio-118 (? ) out lo > >> > >> GPIOs 128-159, platform/49058000.gpio, gpio: > >> > >> GPIOs 160-191, platform/48310000.gpio, gpio: > >> gpio-164 (user ) in lo IRQ > >> > >> GPIOs 1004-1023, platform/twl4030-gpio, twl4030, can sleep: > >> gpio-1006 (tfp410 PD ) out lo > >> gpio-1022 (hsusb2_vbus ) out hi > >> > >> Do you see anything wrong in this configuration? > > > > This is fine. From your kernel log I see this > > > > [ 3.789886] ehci-omap: OMAP-EHCI Host Controller driver > > [ 3.790405] ehci-omap 48064800.ehci: Can't get PHY device for port 1: > -517 > > > > This means that the EHCI USB controller couldn't get the PHY device > > and has bailed out. It seems to occur in mainline as well. > > Well I'm wrong. A bit later it seems to have been registered fine. > > So hsusb2_vbus line should have gone low to enable the USB HUB power > and hence D14. That doesn't seem to be happening. > > cheers, > -roger > -- *Cordialement / Best Regards / Mit freundlichen Grüßen / Sven Bock M.Sc.Research Engineer* *Tel: +33 556 393 705* *Génération Robots <http://www.generationrobots.com/> | HumaRobotics <http://www.humarobotics.com/>* -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
