USB and ethernet ports are not working - D14 led not powered

Sven_Bock · October 5, 2015, 3:50pm

Hello,

I do not manage to enable my USB or ethernet ports on my beagleboard xm rev C. The D14 Led is off. I use an external power supply of 5V 4A.

I installed Ubuntu 14.04 according to:
http://elinux.org/BeagleBoardUbuntu
This one boots into a command line.

I also tried it with the production image:
http://elinux.org/Beagleboard:BeagleBoard-xM
This one correctly boots the graphical interface

All usb ports, as well as the ethernet are dead.
I successfully managed connecting with a USB to serial adapter to the beagleboard. So I actually have a terminal and be able to type!
According to the linux configuration parameters below for USB, the ports are enabled.
/sys/bus/usb/devices/usb1/power/autosuspend_delay_m
/sys/bus/usb/devices/usb1/power/control

Is there a beagleboard specific configuration I have missed?
Do I need a uEnv.txt in the boot partition to power up the usb and ethernet during boot? If yes, what is the essential code for enabling the usb and ethernet?

Should they be working by default after flashing the image?
Could that be just a configuration problem or more a hardware issue?

Any hint, what is going on with my board is greatly appreciated.

Thanks!
Sven

Roger_Quadros · October 6, 2015, 7:24am

Hi Sven,

Hello,

I do not manage to enable my USB or ethernet ports on my beagleboard xm rev C. The D14 Led is off. I use an external power supply of 5V 4A.

I installed Ubuntu 14.04 according to:
BeagleBoardUbuntu - eLinux.org
This one boots into a command line.

I also tried it with the production image:
Beagleboard:BeagleBoard-xM - eLinux.org
This one correctly boots the graphical interface

All usb ports, as well as the ethernet are dead.
I successfully managed connecting with a USB to serial adapter to the beagleboard. So I actually have a terminal and be able to type!
According to the linux configuration parameters below for USB, the ports are enabled.
/sys/bus/usb/devices/usb1/power/autosuspend_delay_m
/sys/bus/usb/devices/usb1/power/control

Is there a beagleboard specific configuration I have missed?
Do I need a uEnv.txt in the boot partition to power up the usb and ethernet during boot? If yes, what is the essential code for enabling the usb and ethernet?

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

Should they be working by default after flashing the image?
Could that be just a configuration problem or more a hardware issue?

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.

Any hint, what is going on with my board is greatly appreciated.

Can you please paste your kernel boot log in pastebin and the output of
cat /sys/kernel/debug/gpio

cheers,
-roger

Sven_Bock · October 7, 2015, 1:13pm

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”?

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?

best,
sven

boot.log (3.58 KB)

dmesg (19.9 KB)

Roger_Quadros · October 7, 2015, 1:54pm

Sven,

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.

I'll investigate more and keep you updated.

cheers,
-roger

Roger_Quadros · October 7, 2015, 1:58pm

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

Sven_Bock · October 7, 2015, 2:15pm

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?

Roger_Quadros · October 7, 2015, 2:20pm

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?

I can't think of anything like that. The kernel should drive the D14 line
to the right state when the USB driver starts.

I just tested mainline kernel on my beagleboard-xm rev.B and it worked fine.

Which device tree blob are you loading with the kernel? For rev.C you need to
load omap3-beagle-xm.dtb and not omap3-beagle-xm-ab.dtb

cheers,
-roger

Sven_Bock · October 7, 2015, 2:35pm

> 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?

I can't think of anything like that. The kernel should drive the D14 line
to the right state when the USB driver starts.

I just tested mainline kernel on my beagleboard-xm rev.B and it worked
fine.

Which device tree blob are you loading with the kernel? For rev.C you need
to
load omap3-beagle-xm.dtb and not omap3-beagle-xm-ab.dtb

I used the command below for settting up the sd card as described on the
wiki
<BeagleBoardUbuntu - eLinux.org;
sudo ./setup_sdcard.sh --mmc /dev/sdb --dtb omap3-beagle-xm

RobertCNelson · October 7, 2015, 2:41pm

This install's a version of u-boot that correctly detects the xmab vs xmc..

I use to carry a patch to fix ehci on v4.2.x, but this wasn't needed
anymore on my xmc..

What board do you have? and can you add the serial log with the u-boot version?

Regards,

Sven_Bock · October 7, 2015, 2:53pm

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?

I can’t think of anything like that. The kernel should drive the D14 line
to the right state when the USB driver starts.

I just tested mainline kernel on my beagleboard-xm rev.B and it worked
fine.

Which device tree blob are you loading with the kernel? For rev.C you need
to
load omap3-beagle-xm.dtb and not omap3-beagle-xm-ab.dtb

I used the command below for settting up the sd card as described on the
wiki
sudo ./setup_sdcard.sh --mmc /dev/sdb --dtb omap3-beagle-xm

This install’s a version of u-boot that correctly detects the xmab vs xmc…

I use to carry a patch to fix ehci on v4.2.x, but this wasn’t needed
anymore on my xmc…

What board do you have?
I have the beagleboard xm rev C. I also attached you a picture of it.

and can you add the serial log with the u-boot version?
where do i find this log?

RobertCNelson · October 7, 2015, 3:01pm

and can you add the serial log with the u-boot version?
where do i find this log?

via the serial port.. But you have a C, same version i have here.. The
"early" xMA's had nand so some of the environmental variables can mess
with things..

Regards,

Sven_Bock · October 7, 2015, 3:13pm

Last hope: I use a 32 GB San disk ultra class 10 for the beagle. I don’t see why, but could that be a reason why the usb +ethernet ports are not working?

Roger_Quadros · October 8, 2015, 8:02am

Last hope: I use a 32 GB San disk ultra class 10 for the beagle. I don't see why, but could that be a reason why the usb +ethernet ports are not working?

No, SD card type shouldn't affect USB.
Can you provide the u-boot log that Robert requested. You can take a capture of the serial port
right from power up via the serial terminal application.

We just need to ensure that u-boot is loading the right DTB.

cheers,
-roger

John_Nichols · October 11, 2015, 1:21pm

I don want to hijack this string, just commenting that my BeagleBone Black is having what appears to be the exact same issue, or at least similar enough to be put in the same category.
I can access just fine using the mini USB port.
I cannot access via ethernet, it appears no IP address was set from DHCP server because the port seems active (lights all blinky and stuff).
I connected an FTDI serial cable and the connection is spotty but when i do (seem) to connect it doesnt recognize “root” use - all password attempts fail.

No LEDs lit except nearest power connection.

No SD card mounted (at the moment).

My MacBook Pro lives on my home wifi while the BBB is connected to a switch, connected directly to the router. I know the IPs are same subnet because my Drobo is also on that switch and I access that from my laptop continually.

I’m reading through your previous entries and will look for obvious similarities and address as suggested.

Thanks.

John

RobertCNelson · October 11, 2015, 8:57pm

Hi John,

I don want to hijack this string, just commenting that my BeagleBone Black
is having what appears to be the exact same issue, or at least similar
enough to be put in the same category.

Nope sorry, completely different hardware, and a completely different
usb "PHY" ip...

I can access just fine using the mini USB port.
I cannot access via ethernet, it appears no IP address was set from DHCP
server because the port seems active (lights all blinky and stuff).
I connected an FTDI serial cable and the connection is spotty but when i do
(seem) to connect it doesnt recognize "root" use - all password attempts
fail.

The default images printout the user/password combination.. If it
doesn't contact who you go the image from..

No LEDs lit except nearest power connection.

No SD card mounted (at the moment).

My MacBook Pro lives on my home wifi while the BBB is connected to a switch,
connected directly to the router. I know the IPs are same subnet because my
Drobo is also on that switch and I access that from my laptop continually.

I'm reading through your previous entries and will look for obvious
similarities and address as suggested.

Regards,

Roger_Quadros · October 12, 2015, 7:41am

Hi,

Hi John,

I don want to hijack this string, just commenting that my BeagleBone Black
is having what appears to be the exact same issue, or at least similar
enough to be put in the same category.

Nope sorry, completely different hardware, and a completely different
usb "PHY" ip...

Actually, on bone black, ethernet is not over USB. It is directly over MII.

I can access just fine using the mini USB port.
I cannot access via ethernet, it appears no IP address was set from DHCP
server because the port seems active (lights all blinky and stuff).
I connected an FTDI serial cable and the connection is spotty but when i do
(seem) to connect it doesnt recognize "root" use - all password attempts
fail.

The default images printout the user/password combination.. If it
doesn't contact who you go the image from..

No LEDs lit except nearest power connection.

No SD card mounted (at the moment).

My MacBook Pro lives on my home wifi while the BBB is connected to a switch,
connected directly to the router. I know the IPs are same subnet because my
Drobo is also on that switch and I access that from my laptop continually.

I'm reading through your previous entries and will look for obvious
similarities and address as suggested.

cheers,
-roger

MHE · November 18, 2017, 12:23am

Hi,
I experience exact same issue on the 3.14.20 linux kernel, u-boot detect ethernet port, load the omap3-beagle-xm.dtb after linux kernel loaded, the led is off, nothing never happens again nor usb, nor ethernet, seems the part is incompatible with the kernel.. what matters is the fb device not working too.. I suspect these things linked to same root cause.