• Before reporting problems with your board running Armbian, check the following:

    • 1. Check power supply, check SD card and check other people experiences   06/23/17

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information   06/24/17

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Usb Issue
1 1

13 posts in this topic

Recommended Posts

Hello to all,

I installed Armbian ( legacy kernel ) on my OPI plus 2 H3 but all usb ports not work, only micro usb Otg. I can t use mouse or keyboard someone help me please?

Share this post


Link to post
Share on other sites

Hi,

 

I wonder if this is related to the same issue I see on the NanoPi Neo.

 

I seem to be missing the USB connections that NanoPi Neo have on the extension pins with the Armbian 5.32.170704 nightly.

 

root@nanopiair:~# uname -a
Linux nanopiair 4.11.5-sun8i #3 SMP Mon Jul 3 02:24:22 CEST 2017 armv7l armv7l armv7l GNU/Linux
root@nanopiair:~# lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@nanopiair:~#

 

When I use the FriendlyArm Ubuntu build, then I get the USB port available;

 

root@NanoPi-NEO:~# uname -a
Linux NanoPi-NEO 4.11.2 #1 SMP Mon Jul 10 11:06:36 CST 2017 armv7l armv7l armv7l GNU/Linux
root@NanoPi-NEO:~# lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1199:9071 Sierra Wireless, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@NanoPi-NEO:~#

 

I also tried to install the armbianmonitor, but it seems to fail, but might be something related to this nightly build.

 

root@nanopineo:~# armbianmonitor -r
Installing RPi-Monitor. This can take up to 5 minutes. Be patient pleaseE: Unable to locate package rpimonitor
/usr/bin/armbianmonitor: line 562: /usr/share/rpimonitor/scripts/updatePackagesStatus.pl: No such file or directory

Now patching RPi-Monitor to deal correctly with H3

Now you're able to enjoy RPi-Monitor at http://147.214.54.14:8888
root@nanopineo:~#

 

I have tried to compare the device tree files between FriendlyArm build and Armbian, but can't find anything obvious that would indicate that the USB ports are missing, which makes me believe that it might be something in the kernel config instead.

 

Regards,

Sebastian

Share this post


Link to post
Share on other sites
1 hour ago, Igor said:

Nanopi Neo modern kernel was never released by Armbian. There was only some development builds ... Try recent 4.13.x kernel. https://dl.armbian.com/nanopineo/nightly/ we moved here few days ago and images need testing and minor fixing. If USB is not working it's probably just not enabled in DT.

 

Tested the 4.13.5, and see the same issue there.

 

I checked the DT between FriendlyArm and Mainline, and could only find the one below. (maybe other DT files need to be compared as well)

 

# diff friendlyarm/linux/arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts linux/arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts 
# diff friendlyarm/linux/arch/arm/boot/dts/sun8i-h3-nanopi.dtsi linux/arch/arm/boot/dts/sun8i-h3-nanopi.dtsi
50d49
< #include <dt-bindings/pinctrl/sun4i-a10.h>
#

 

Which include these,

 

#ifndef __DT_BINDINGS_PINCTRL_SUN4I_A10_H_
#define __DT_BINDINGS_PINCTRL_SUN4I_A10_H_

#define SUN4I_PINCTRL_10_MA    0
#define SUN4I_PINCTRL_20_MA    1
#define SUN4I_PINCTRL_30_MA    2
#define SUN4I_PINCTRL_40_MA    3

#define SUN4I_PINCTRL_NO_PULL    0
#define SUN4I_PINCTRL_PULL_UP    1
#define SUN4I_PINCTRL_PULL_DOWN    2

#endif /* __DT_BINDINGS_PINCTRL_SUN4I_A10_H_ */

 

But I don't know if this is related.

 

-Sebastian

Share this post


Link to post
Share on other sites

Thank You To All, for help,

i Temporarily solved changing distro but hope we find soon a solution if is a kernel related bug...

Share this post


Link to post
Share on other sites
21 minutes ago, pininux said:

i Temporarily solved changing distro but hope we find soon a solution if is a kernel related bug...


Opi Zero 2+ does not have USB connectors. If a connector is not there is (usually) disabled by default. It's a matter of user configuration. It's not a bug and it's not related to USB on Nanopi NEO with modern kernel ...

Share this post


Link to post
Share on other sites

Since there is the possibility of having NAS expansion board on top of OPiZeroPlus2, I think it is a good idea to have USB enabled by default.

Last time I've done an OPiZeroPlus2, if I recall, they were already enabled. If not, then, simple overlays could enable them.

 

Share this post


Link to post
Share on other sites
On 11.10.2017 at 1:58 PM, pininux said:

Armbian ( legacy kernel ) on my OPI plus 2

 

  • Legacy kernel (all USB ports enabled on every board)
  • OPi Plus 2 and not Opi Zero 2+

The next time you try it with Armbian please provide output from 'armbianmonitor -u' so we get an idea which OS image you tried.

 

Share this post


Link to post
Share on other sites
3 hours ago, tkaiser said:

OPi Plus 2 and not Opi Zero 2+

Ok ! I didn't pay attention to the OP, and the thread drifted by talking Opi Zero 2+ ... ;)

 

BTW, I've rebuilt an Opi Zero 2+ image today, and I've figured out that USB were not detect due to the USBPHY not enabled by the overlays... (I will fix that when I get some spare time)

 

Share this post


Link to post
Share on other sites
mzb    0
6 hours ago, martinayotte said:

Ok ! I didn't pay attention to the OP, and the thread drifted by talking Opi Zero 2+ ... ;)

 

BTW, I've rebuilt an Opi Zero 2+ image today, and I've figured out that USB were not detect due to the USBPHY not enabled by the overlays... (I will fix that when I get some spare time)

 

Sorry to be OT, but I'd love to see the USB fixed for zero 2+. I tried modifying a .dts file and making .dtb, but I'll need more practice before I have half a clue.

Share this post


Link to post
Share on other sites
mzb    0
20 hours ago, mzb said:

Sorry to be OT, but I'd love to see the USB fixed for zero 2+. I tried modifying a .dts file and making .dtb, but I'll need more practice before I have half a clue.

OK, put more effort in and built an image  (+1 vote for Debian instead of Ubuntu, btw!)  after realising that martinayotte had already made a commit!

 

So, after applying usbhost2+usbhost3 overlays I'm now met with:

root@orangepizeroplus2:~# lsusb 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0a5c:2121 Broadcom Corp. BCM2210 Bluetooth
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Thank you!

Note: untested functionality

 

[EDIT]

... a few hours later

 

Bluetooth dongle and a uBlox GPS both proven to work on the USB ports (simultaneously).

 

root@zp2:~# lsusb 
Bus 004 Device 002: ID 0a5c:2121 Broadcom Corp. BCM2210 Bluetooth
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 1546:01a8 U-Blox AG 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and able to cat/gpspipe data from gps to rfcomm serial on bluetooth, so all working.

Edited by mzb
Updated result

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

1 1

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.