1 1
zanzibar

[ODROID C2] USB ports are (still?) not working properly

Recommended Posts

(edited)

Hello,

I have installed Armbian Debian Stretch Next (mainline kernel) on my Odroid C2 and updated to newest version(apt update & apt upgrade).

Everything works fine except USB ports.

 

I have USB LTE modem which is not recognized. I have tried "lsusb -v" but with this modem not works.

But when I connect USB keyboard first then "lsusb -v" and next I connect LTE modem and type "lsusb -v" then it's works.

 

I also tried connecting USB LTE modem before Odroid C2 boot but this workaround not working.

 

Is there any workaround which not involving connecting more than one USB device?

 

Maybe usb kernel modules (usbcore, ehci_hcd, ...) compiled as external modules will help find workaround?

Edited by zanzibar

Share this post


Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

I'm getting the old bug where the hub powers down if nothing is attached.  I thought I killed that one, but maybe in the switch it came back.  Doesn't completely fit your issue but we'll see.

Share this post


Link to post
Share on other sites

I found easy workaround.

Add usbcore.autosuspend=-1 as kernel parameter by /boot/armbianEnv.txt file. Eg.:

extraargs=usbcore.autosuspend=-1

 

Of course this workaround have cons: odroid c2 will take more power.

 

@TonyMac32

Could you please give me more details where I should look for this issue in source files? Is it dwc2 usb driver?

 

Share this post


Link to post
Share on other sites

Hi,

 

I've had similar problems with my C2. USB would not power up any device except the internal hub. The above workaroud seems to work for me.

Questions :

Considering this :

dmesg
[...]
[    2.804560] phy phy-c0000020.phy.1: Linked as a consumer to regulator.3
[    2.804955] dwc2 c9000000.usb: c9000000.usb supply vusb_d not found, using dummy regulator
[    2.805002] dwc2 c9000000.usb: Linked as a consumer to regulator.0
[    2.805009] dwc2 c9000000.usb: c9000000.usb supply vusb_a not found, using dummy regulator
[    2.806314] phy phy-c0000000.phy.0: USB ID detect failed!
[    2.806322] phy phy-c0000000.phy.0: phy poweron failed --> -22
[    2.806395] dwc2: probe of c9000000.usb failed with error -22
[    2.806604] dwc2 c9100000.usb: c9100000.usb supply vusb_d not found, using dummy regulator
[    2.806627] dwc2 c9100000.usb: Linked as a consumer to regulator.0
[    2.806633] dwc2 c9100000.usb: c9100000.usb supply vusb_a not found, using dummy regulator
[    2.867643] dwc2 c9100000.usb: dwc2_check_params: Invalid parameter lpm=1
[    2.867648] dwc2 c9100000.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1
[    2.867651] dwc2 c9100000.usb: dwc2_check_params: Invalid parameter besl=1
[    2.867655] dwc2 c9100000.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1
[...]

I wonder if this patch is actually applied in the latest armbian version (I expect not seeing the latest github commit, but I can really tell)

https://patchwork.kernel.org/patch/10785943/

 

On a side note I also have another dmesg error but inconsistent (not on every boot sequence)

[   19.535969] meson-i2s-dai meson-i2s-dai.0.auto: Unable set to set i2s description
[   19.535980] meson-i2s-dai meson-i2s-dai.0.auto: ASoC: can't set meson-i2s-dai.0.auto hw params: -22

This is repeated 20 times

 

 

 

 

Best,

Share this post


Link to post
Share on other sites

Just downloaded yesterday latest version:

Armbian Buster
mainline kernel 4.19.y

 

Linux odroidc2 4.19.57-meson64 #5.90 SMP PREEMPT Sat Jul 6 15:54:33 CEST 2019 aarch64 GNU/Linux

 

And still hiting this bug. Workaround works.

Share this post


Link to post
Share on other sites

I can confirm this with a 5.3.1 mainline kernel, and success with the given workaround.

 

(I'm not using Armbian, but in this case it does not matter.)

Share this post


Link to post
Share on other sites

Hi, I'm new to odroid.... i bought a odroid C2, and installed odroid's ubuntu mate. Straight away, the keyboard would disappear .... 5 or 6 minutes, it would flash and then no response. the only way to get it back was to reboot. Following a recomendation, I rebuilt with armbian last night. I'm still having the same problems. I've tried the k/b on the usb ports as well as the otg...both the same. Following a suggestion, I tried using an old usb1.1 hub...still the same. If anyone has any suggestions.... Thanks in advance Terry

Share this post


Link to post
Share on other sites

Hi Igor, just tried you suggestion.....and still the same. Partway through installing armbian-config the keyboard lights flash, then nothing. 

Share this post


Link to post
Share on other sites
(edited)
59 minutes ago, nik-ii said:

Still not working: Armbian_20.02.0-rc1_Odroidc2_buster_current_5.4.14


What is not working?

Edit: USB port are working on image made from trunk http://ix.io/2aQn

Edited by Igor
Add test resoults

Share this post


Link to post
Share on other sites

If I boot up the C2 and plug in a USB-RS232 Converter the device does not power up. If I than add an USB-Stick to the C2 the the USB-RS232 Converter gets power and is accessible by the OS.

(Armbian_20.02.0-rc1_Odroidc2_buster_current_5.4.14)

Share this post


Link to post
Share on other sites
On 2/7/2020 at 10:33 AM, nik-ii said:

If I boot up the C2 and plug in a USB-RS232 Converter the device does not power up. If I than add an USB-Stick to the C2 the the USB-RS232 Converter gets power and is accessible by the OS.

 

USB on C2 is known to make troubles. This is present for years and it seems we don't have a proper fix.

 

... or we do?

 

Share this post


Link to post
Share on other sites

After applying the following my USB attached disks are no longer visible
 

commandline: apt upgrade
Upgrade: linux-image-current-meson64:arm64 (20.02.3, 20.02.5), linux-dtb-current-meson64:arm64 (20.02.3, 20.02.5), armbian-config:arm64 (20.02.2, 20.02.6)
End-Date: 2020-03-23  19:40:19

 

I plugged the USB enclosure into my Pi and I can see the LVM and the LV's.

Share this post


Link to post
Share on other sites

I will test again, my last round of testing had working USB. Not to say something didn't change, there was another time that an unexplainable loss of USB happened that fixed itself after some time and upstream patches that seemed unrelated.

Sent from my Pixel using Tapatalk

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
1 1