Please select To the mobile version | Continue to access the desktop computer version

OrangePi

 Login            
 Register            
Search
Hot search: orangepi
View: 3342|Reply: 7

Orange Pi 2G-IoT - Ubuntu Server Image - Can not get USB port to work - Overlay?

[Copy link]

1

Threads

6

Posts

39

Credits

Novice

Rank: 1

Credits
39
Post time 2018-5-17 00:12:02 | Show all posts |Read mode

Hello,

I am working with a Orange Pi 2G-IoT with the latest Ubuntu Server Image from orangepi.com.   I have gotten pretty far with this device other then one issue, which is the USB port.   I have not been able to get it to work properly in this Ubuntu image.   I have tried multiple DIP configurations with no luck.   I want to use it as a standard USB Host for plugging in a printer (USB A to B cable standard).   I have read tutorials and I have seen issues posted about armbian and using overlays on other OPIs like the Zero, but nothing specific to the IOT-2g, and everything I have tried from the tutorials on other models have not worked to get the USB enabled so I wanted to ask the community here.   How can I use this USB port?   I do not need OTG and I only need to use the 1 port in normal host mode on Ubuntu.

Any suggestions on what I should try or what I need to do are appreciated.   Thank you!


Here is some info from the image and what I am seeing in case it helps:

  1. orangepi@opi-2g:~$ uname -a
  2. Linux opi-2g 3.10.62-rel5.0.2+ #92 PREEMPT Tue Jul 11 18:31:58 CST 2017 armv7l armv7l armv7l GNU/Linux

  3. orangepi@opi-2g:~$ lsb_release -a
  4. No LSB modules are available.
  5. Distributor ID: Ubuntu
  6. Description:    Ubuntu 16.04.4 LTS
  7. Release:        16.04
  8. Codename:       xenial

  9. orangepi@opi-2g:~$ lsusb
  10. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  11. orangepi@opi-2g:~$ ls /dev/ttyUSB*
  12. ls: cannot access '/dev/ttyUSB*': No such file or directory

  13. orangepi@opi-2g:~$ dmesg | grep usb
  14. [    0.375000] v_usb: 1800 <--> 2800 mV normal standby
  15. [    0.398193] usbcore: registered new interface driver usbfs
  16. [    0.398864] usbcore: registered new interface driver hub
  17. [    0.399536] usbcore: registered new device driver usb
  18. [    0.663085] usbcore: registered new interface driver usb-storage
  19. [    0.664978] platform disable musb
  20. [    0.665222] musb-hdrc: ConfigData=0x1a (UTMI-8, HB-ISO Rx, HB-ISO Tx, SoftConn)
  21. [    0.666137] musb-hdrc: HDRC RTL version 2.0
  22. [    0.666748] gpio-vbus gpio-vbus: registered host 'musb-hdrc'
  23. [    0.769409] usbcore: registered new interface driver usbmouse
  24. [    1.033081] musb_gadget_pullup android usb didn't ready
  25. [    1.034912] android_usb gadget: Mass Storage Function, version: 2009/09/11
  26. [    1.035583] android_usb gadget: Number of LUNs=1
  27. [    1.036987] android_usb gadget: android_usb ready
  28. [    1.037414] gpio-vbus gpio-vbus: registered gadget 'musb-hdrc'
  29. [    1.038208] musb-hdrc musb-hdrc: MUSB HDRC host driver
  30. [    1.038818] musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 1
  31. [    1.041076] platform enable musb
  32. [    5.028747] usb cable connect...
  33. [    6.669616] usb cable disconnect...
  34. [    7.743164] musb-hdrc musb-hdrc: configured as A device timeout

  35. orangepi@opi-2g:~$ dmesg | grep tty
  36. [    0.000000] Kernel command line: root=/dev/mmcblk0p2 rootwait rootfstype=ext4 console=ttyS0,921600 panic=10 consoleblank=0 loglevel=8
  37. [    0.000000] bootconsole [ttyS0] enabled
  38. [    0.636413] rda-uart.0: ttyS0 at MMIO 0x20a90000 (irq = 11) is a RDA UART
  39. [    0.637084] console [ttyS0] enabled, bootconsole disabled
  40. [    0.638366] rda-uart.1: ttyS1 at MMIO 0x20a00000 (irq = 9) is a RDA UART
  41. [    0.639831] rda-uart.2: ttyS2 at MMIO 0x20a10000 (irq = 10) is a RDA UART
  42. [    4.242858] systemd[1]: Created slice system-serial\x2dgetty.slice.
Copy the Code




1

Threads

6

Posts

39

Credits

Novice

Rank: 1

Credits
39
 Author| Post time 2018-5-17 08:19:24 | Show all posts
Has anyone been able to get the USB port to work on the Ubuntu image?   I can not see any way to make it function, and I would like to verify it is possible at this point.

Any suggestions are appreciated again.

Thank you

0

Threads

2

Posts

10

Credits

Novice

Rank: 1

Credits
10
Post time 2018-5-18 19:40:55 | Show all posts
Hi,
I have issue with USB port too. I want to use it for USB webcam but it does not detect the camera.
I even tested it with plugging a USB mouse but nothing happens in lsusb and it is always like this:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

0

Threads

2

Posts

10

Credits

Novice

Rank: 1

Credits
10
Post time 2018-5-18 19:59:28 | Show all posts
I changed toggle switches on the board and now it detects my cam
change it to 1,2,3,4 OFF 5,6,7,8 ON

1

Threads

6

Posts

39

Credits

Novice

Rank: 1

Credits
39
 Author| Post time 2018-5-19 04:02:42 | Show all posts
Farid replied at 2018-5-18 19:59
I changed toggle switches on the board and now it detects my cam
change it to 1,2,3,4 OFF 5,6,7,8 ON ...

Farid,

Thanks for the report!   I hope you can clairify something for me.

Can you tell me which OS image you are using and how you are powering?

Are you on Ubuntu, Armbian, or Andoird?

Are you using the USB Micro for power or a batter direct?

Thanks!

1

Threads

6

Posts

39

Credits

Novice

Rank: 1

Credits
39
 Author| Post time 2018-5-25 07:42:59 | Show all posts
Not getting much further....  has no one got the USB host mode to work with Ubuntu that can explain the setup?

I have now switch fully to battery power so the Micro USB is not used at all.

I did get a bit of additional output in my dmesg | grep USB at the end...


  1. ...
  2. [ 1.040649] platform enable musb
  3. [ 6.740295] musb-hdrc musb-hdrc: VBUS_ERROR in a_wait_bcon (80, <SessEnd), re try #1, port1 00000100
  4. [ 7.733276] musb-hdrc musb-hdrc: configured as A device timeout
  5. [ 7.820434] musb-hdrc musb-hdrc: VBUS_ERROR in a_wait_bcon (80, <SessEnd), re try #2, port1 00000100
  6. [ 8.788513] musb-hdrc musb-hdrc: configured as host timeout
  7. [ 9.870300] musb-hdrc musb-hdrc: VBUS_ERROR in a_wait_bcon (80, <SessEnd), re try #3, port1 00000100
  8. [ 10.953125] musb-hdrc musb-hdrc: VBUS_ERROR in a_wait_bcon (80, <SessEnd), re try #3, port1 00080108
  9. [ 11.907775] musb-hdrc musb-hdrc: configured as host timeout
Copy the Code


DIPs are 1-4 Down / 5-8 UP - with the opposite it does not boot from the card.

Anyone have any suggestions for me?

1

Threads

3

Posts

13

Credits

Novice

Rank: 1

Credits
13
Post time 2018-5-30 20:06:26 | Show all posts
Edited by tony1812 at 2018-5-30 20:07

The idiots in orange pi did not use OTG usb port for power, instead they, for some idiotic reason, use  coaxial plug for power, if you don't have the coaxial plug, you can use the GPIO pin 2 or 4 (positive) and pin 6
( negative). Be careful not to reverse them. I accidentally reversed them and the orange pi died in a puff of smoke!

5

Threads

13

Posts

67

Credits

Registered member

Rank: 2

Credits
67
Post time 2020-4-10 04:15:41 | Show all posts
tony1812 replied at 2018-5-30 20:06
The idiots in orange pi did not use OTG usb port for power, instead they, for some idiotic reason, u ...

Nope - I can't agree to your opimion:
I use microUSB (like used for Android phones) cable to power my OrPi 2G IoT and it worked fine. Important is to have enough power on the cable, so plug it directly into a laptop or power-suply with more than 2A. And don't use thin & long cable - use shorter and massive cable to get the power to the plug :-)
Another possibility is to solder 2 wires to the VBAT+ and VBAT- pins and feed it with 3,7V or a Lithium-Battery
You have to log in before you can reply Login | Register

Points Rules

Archiver|Mobile edition|Darkroom|OrangePi En ( 粤ICP备14086627号-2

2020-5-25 11:47 GMT+8 , Processed in 0.033934 second(s), 23 queries .

Powered by Discuz! X3.2

© 2014-2015 orangepibbs en.

Quick Reply To Top Return to the list