Orange Pi

General Chat, Feel Free To talk about anything here.
mssmison
Posts: 3
Joined: Tue Nov 08, 2016 6:55 pm

Orange Pi

Post by mssmison » Tue Nov 08, 2016 6:59 pm

Just wondering if anyone has used one of the Orange Pi's instead of a RP? The RP's are fairly costly where I am where as I can get an Orange for much much cheaper.

Thanks.

fishe972
Posts: 8
Joined: Wed Aug 10, 2016 2:30 pm

Re: Orange Pi

Post by fishe972 » Wed Nov 16, 2016 11:42 pm

I ordered one to try.
As soon as i received it , i will post my result .
I think i will try armbian as system os.it is debian based like raspbian . So maybe gimx compatibility will be ok .

fishe972
Posts: 8
Joined: Wed Aug 10, 2016 2:30 pm

Re: Orange Pi

Post by fishe972 » Sun Dec 11, 2016 5:20 pm

Salut a tous. I tried to run gimx on an orange pi pc , for now without success.the orange pi is running armbian jessie. I followed the same method as for rpi but gimx doesn't find the serial port ( gpio uart ) i did not tried the usb to setial maybe it should work.
Then i tried in command line with console version of armbian.gimx found the ttys3 serial port but it's not the good baudrates.i have to find out how to change uart speed with armbian.
It is hard to work on this for me as , like john snow , i know nothing in linux .but i'm learning.
I will keep you informed soon when i will find something. :)

User avatar
Cybereu
Posts: 110
Joined: Sun Jul 10, 2011 1:10 pm

Re: Orange Pi

Post by Cybereu » Tue Dec 13, 2016 12:55 am

I ordered an Orange Pi zero, it will take two months till i get it in my hand, If i get it working i Tell you.
Linux 4ev

chuchuchuchu
Posts: 12
Joined: Mon Dec 19, 2016 5:04 pm

Re: Orange Pi

Post by chuchuchuchu » Tue Dec 20, 2016 11:22 am

Hi all!

I have ordered Orange Pi Zero + USB hub and I will try also to get GIMX running on it.
I will share the results with you.
In the meanwhile, any update about that?

chuchuchuchu
Posts: 12
Joined: Mon Dec 19, 2016 5:04 pm

Re: Orange Pi

Post by chuchuchuchu » Fri Jan 06, 2017 5:38 pm

Hi all,

I already have my Orange Pi Zero with USB HUB. It is running armbian jessie:

Code: Select all

pi@orangepizero:~$ uname -a
Linux orangepizero 3.4.113-sun8i #50 SMP PREEMPT Mon Nov 14 08:41:55 CET 2016 armv7l GNU/Linux
First step was the pi user creation and I added it to same set of groups like in Raspbian:
* pi user groups in Raspbian

Code: Select all

pi@raspberrypi:~ $ groups
pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi
* pi user groups in armbian

Code: Select all

pi@orangepizero:~$ groups
pi adm dialout cdrom sudo audio video plugdev games users input netdev bluetooth
Then i installed GIMX 6.3 like we do for Raspbian:

Code: Select all

wget https://gimx.fr/download/gimx-raspbian -O gimx.deb
sudo dpkg -i gimx.deb
sudo apt-get -f install
Running GIMX from command line as follows (Using CP2102):

Code: Select all

pi@orangepizero:~$ /usr/bin/gimx -p /dev/ttyUSB0 -c LogitechMomoRacing_G29.xml --nograb
controller #1: option -p with value `/dev/ttyUSB0'
now reading arguments for controller #2
global option -c with value `LogitechMomoRacing_G29.xml'
grab flag is unset
USB adapter detected, controller type is: G29 PS4.
using default refresh period: 5.00ms
native mode is already enabled for HID device 08:01:00:00 (PID=ca03)
linux/uhidasync.c:223 wait_watch: select timed out

GIMX is able to authenticate against PS4 (DS4 forwards keys pressed correctly, I can navigate through menus) however the wheel/pedals are not responding on PS4.
Running GIMX in Test mode i have the output below:

Code: Select all

pi@orangepizero:~$ /usr/bin/gimx -c LogitechMomoRacing_G29.xml --status -t DS4
global option -c with value `LogitechMomoRacing_G29.xml'
controller #1: option -t with value `DS4'
status flag is set
using default refresh period: 10.00ms
native mode is already enabled for HID device 08:01:00:00 (PID=ca03)
linux/uhidasync.c:223 wait_watch: select timed out
joystick not found: Logitech  Logitech MOMO Racing  0

The Joystick "Logitech Logitech MOMO Racing 0" is not detected although it should be the correct name based on gimx-config autodetect function:
* Sample from default LogitechMomoRacing_G29.xml file:

Code: Select all

<button id="abs_axis_11" label="">
          <device type="joystick" id="0" name="Logitech  Logitech MOMO Racing "/>
          <event type="button" id="0"/>
        </button>
* Sample from LogitechMomoRacing_G29_custom.xml created from gimx-launcher:

Code: Select all

<button id="abs_axis_2" label="Aim">
          <device type="joystick" id="0" name="Logitech  Logitech MOMO Racing "/>
          <event type="button" id="9"/>
        </button>
Checking the uhidasync.c code, it seems like status variable ( select(ifd + 1, &readfds, NULL, NULL, &tv); ) is equals to 0 while we should expect an higher value.

I will try with Logitech DFGT as well in order to discard a particular problem only with Logitech Momo racing device.

User avatar
Matlo
Posts: 4969
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Orange Pi

Post by Matlo » Fri Jan 06, 2017 5:51 pm

Hi,

This line tells something went wrong:

Code: Select all

linux/uhidasync.c:223 wait_watch: select timed out
Could you post the output of the dmesg command after this issue happens?

The kernel version is quite old. There could be some issues with it.
GIMX creator Donate Shop

chuchuchuchu
Posts: 12
Joined: Mon Dec 19, 2016 5:04 pm

Re: Orange Pi

Post by chuchuchuchu » Fri Jan 06, 2017 6:12 pm

Hi Matlo, thanks for your quick response.
I tested with DFGT and the behaviour is exactly the same (I needed 3 attempts to get the native mode enable):
GIMX executions:

Code: Select all

pi@orangepizero:~$ /usr/bin/gimx -p /dev/ttyUSB0 -c LogitechDrivingForceGT_G29.xml --nograb
controller #1: option -p with value `/dev/ttyUSB0'
now reading arguments for controller #2
global option -c with value `LogitechDrivingForceGT_G29.xml'
grab flag is unset
USB adapter detected, controller type is: G29 PS4.
using default refresh period: 5.00ms
native mode command sent to HID device 08:01:00:00 (PID=c294)
failed to enable native mode for HID device 08:01:00:00
1483725537.631825 timer fired 2 times...
pi@orangepizero:~$
pi@orangepizero:~$ /usr/bin/gimx -p /dev/ttyUSB0 -c LogitechDrivingForceGT_G29.xml --nograb
controller #1: option -p with value `/dev/ttyUSB0'
now reading arguments for controller #2
global option -c with value `LogitechDrivingForceGT_G29.xml'
grab flag is unset
USB adapter detected, controller type is: G29 PS4.
using default refresh period: 5.00ms
libusb/gusbhid.c:304 gusbhid_write_timeout: libusb_interrupt_transfer failed with error: No such device (it may have been disconnected)
failed to send native mode command for HID device 08:01:00:00 (PID=c294)
1483725546.214866 timer fired 2 times...
pi@orangepizero:~$
pi@orangepizero:~$ /usr/bin/gimx -p /dev/ttyUSB0 -c LogitechDrivingForceGT_G29.xml --nograb
controller #1: option -p with value `/dev/ttyUSB0'
now reading arguments for controller #2
global option -c with value `LogitechDrivingForceGT_G29.xml'
grab flag is unset
USB adapter detected, controller type is: G29 PS4.
using default refresh period: 5.00ms
native mode is already enabled for HID device 08:01:00:00 (PID=c29a)
linux/uhidasync.c:223 wait_watch: select timed out
1483725556.344695 timer fired 2 times...
dmesg output:

Code: Select all

[  110.120083] usb 7-1: reset full-speed USB device number 2 using sunxi-ohci
[  110.647371] logitech 0003:046D:C294.0003: input,hidraw0: USB HID v1.00 Joystick [Driving Force GT] on usb-sunxi-ohci-1/input0
[  110.647467] logitech 0003:046D:C294.0003: Force feedback for Logitech Speed Force Wireless by Simon Wood <simon@mungewell.org>
[  115.837634] vmouse_input_dev_open
[  121.710147] vmouse_input_dev_close
[  122.066916] generic-usb 0003:054C:05C4.0004: input,hidraw1: USB HID v1.11 Gamepad [Sony Computer Entertainment Wireless Controller] on usb-sunxi-ohci-1/input0
[  123.840104] usb 7-1: reset full-speed USB device number 2 using sunxi-ohci
[  124.579553] ohci_irq: fullspeed or lowspeed device disconnect
[  124.579860] usb 8-1: USB disconnect, device number 2
[  124.583546] vmouse_input_dev_open
[  124.692983] ehci_irq: highspeed device connect
[  124.860517] ehci_irq: highspeed device disconnect
[  124.860600] ohci_irq: fullspeed or lowspeed device connect
[  125.200261] usb 8-1: new full-speed USB device number 3 using sunxi-ohci
[  125.463074] logitech 0003:046D:C29A.0005: input,hidraw0: USB HID v1.11 Joystick [Driving Force GT] on usb-sunxi-ohci-1/input0
[  125.463318] logitech 0003:046D:C29A.0005: Force feedback for Logitech Speed Force Wireless by Simon Wood <simon@mungewell.org>
[  127.110130] vmouse_input_dev_close
[  127.475926] generic-usb 0003:054C:05C4.0006: input,hidraw1: USB HID v1.11 Gamepad [Sony Computer Entertainment Wireless Controller] on usb-sunxi-ohci-1/input0
[  128.950082] usb 7-1: reset full-speed USB device number 2 using sunxi-ohci
[  134.712076] vmouse_input_dev_open
Regarding kernel version, I still not proceed with "apt-get upgrade" but I think that armbian for OPI Zero is only available on Legacy with kernel 3.4.113 https://www.armbian.com/orange-pi-zero/.
I am not sure if any armbian Nighty release could be better here, or even would be better using any of the releases provide by Orange Pi directly http://www.orangepi.org/downloadresources/. Any recommendation for next steps? ;)
I could provide remote access as well if needed.

User avatar
Matlo
Posts: 4969
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Orange Pi

Post by Matlo » Sat Jan 07, 2017 9:16 am

This is very likely to be a kernel issue. Sadly I don't have time to help on this matter.
GIMX creator Donate Shop

chuchuchuchu
Posts: 12
Joined: Mon Dec 19, 2016 5:04 pm

Re: Orange Pi

Post by chuchuchuchu » Sat Jan 07, 2017 8:18 pm

Hi,

No problem Matlo ;)

I tried upgrading to armbian 5.24.170108 dev version with kernel 4.9.0-sun8i, unfortunately with same result.

Code: Select all

pi@orangepizero:~$ uname -a
Linux orangepizero 4.9.0-sun8i #17 SMP Sat Jan 7 02:42:18 CET 2017 armv7l GNU/Linux
I performed following steps until reach same linux/uhidasync.c:223 wait_watch: select timed out message:
* Message:

Code: Select all

libusb/gusbhid.c:480 claim_device: libusb_open failed with error: Access denied (insufficient permissions)
* Solved by:

Code: Select all

Modified line below within /lib/udev/rules.d/50-udev-default.rules file:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
* Message:

Code: Select all

linux/uhidasync.c:249 guhid_create: open failed with error: Permission denied
* Solved by:

Code: Select all

pi@orangepizero:~$ sudo chmod 666 /dev/uhid
Current status is the same detected for kernel 3.4.113-sun8i before but message linux/uhidasync.c:223 wait_watch: select timed out is only appearing when Check button is clicked on gimx-launcher interface:
* Test execution

Code: Select all

pi@orangepizero:~$ /usr/bin/gimx -c LogitechMomoRacing_G29.xml --status -t DS4
global option -c with value `LogitechMomoRacing_G29.xml'
controller #1: option -t with value `DS4'
status flag is set
using default refresh period: 10.00ms
native mode is already enabled for HID device 08:01:00:00 (PID=ca03)
joystick not found: Logitech  Logitech MOMO Racing  0
* dmesg output

Code: Select all

[ 1754.409209] input: Logitech  Logitech MOMO Racing  as /devices/virtual/misc/uhid/0006:046D:CA03.0015/input/input21
[ 1754.421321] hid-generic 0006:046D:CA03.0015: input,hidraw0: <UNKNOWN> HID v1.00 Multi-Axis Controller [Logitech  Logitech MOMO Racing ] on

----- After Gimx Test execution stops ----- 

[ 1900.069901] logitech 0003:046D:CA03.0016: fixing up Logitech Momo Racing Force (Black) report descriptor
[ 1900.073162] input: Logitech  Logitech MOMO Racing  as /devices/platform/soc/1c1d400.usb/usb8/8-1/8-1:1.0/0003:046D:CA03.0016/input/input22
[ 1900.073823] logitech 0003:046D:CA03.0016: input,hidraw0: USB HID v1.00 Joystick [Logitech  Logitech MOMO Racing ] on usb-1c1d400.usb-1/input0
[ 1900.073934] logitech 0003:046D:CA03.0016: Force feedback support for Logitech Gaming Wheels
* Regular execution

Code: Select all

pi@orangepizero:~$ /usr/bin/gimx -p /dev/ttyUSB0 -c LogitechMomoRacing_G29.xml --nograb --status
controller #1: option -p with value `/dev/ttyUSB0'
now reading arguments for controller #2
global option -c with value `LogitechMomoRacing_G29.xml'
grab flag is unset
status flag is set
USB adapter detected, controller type is: G29 PS4.
found pass-through device 0x054c:0x05c4
using default refresh period: 5.00ms
native mode is already enabled for HID device 08:01:00:00 (PID=ca03)
joystick not found: Logitech  Logitech MOMO Racing  0
0 1483819660.534028
* dmesg output

Code: Select all

[ 2012.410590] usb 7-1: reset full-speed USB device number 4 using ohci-platform
[ 2012.759861] input: Logitech  Logitech MOMO Racing  as /devices/virtual/misc/uhid/0006:046D:CA03.0017/input/input23
[ 2012.771058] hid-generic 0006:046D:CA03.0017: input,hidraw0: <UNKNOWN> HID v1.00 Multi-Axis Controller [Logitech  Logitech MOMO Racing ] on

----- After Gimx Regular execution stops ----- 

[ 2050.286993] logitech 0003:046D:CA03.0018: fixing up Logitech Momo Racing Force (Black) report descriptor
[ 2050.290042] input: Logitech  Logitech MOMO Racing  as /devices/platform/soc/1c1d400.usb/usb8/8-1/8-1:1.0/0003:046D:CA03.0018/input/input24
[ 2050.293604] logitech 0003:046D:CA03.0018: input,hidraw0: USB HID v1.00 Joystick [Logitech  Logitech MOMO Racing ] on usb-1c1d400.usb-1/input0
[ 2050.293721] logitech 0003:046D:CA03.0018: Force feedback support for Logitech Gaming Wheels
[ 2050.297892] sony 0003:054C:05C4.0019: Using modified Dualshock 4 report descriptor with gyroscope axes
[ 2050.348247] input: Sony Computer Entertainment Wireless Controller as /devices/platform/soc/1c1c400.usb/usb7/7-1/7-1:1.0/0003:054C:05C4.0019/input/input25
[ 2050.348962] sony 0003:054C:05C4.0019: input,hidraw1: USB HID v1.11 Gamepad [Sony Computer Entertainment Wireless Controller] on usb-1c1c400.usb-1/input0
* gimx-launcher execution (Check button)

Code: Select all

pi@orangepizero:~$ gimx-launcher
09:09:32 PM: Debug: Failed to connect to session manager: SESSION_MANAGER environment variable not defined
native mode is already enabled for HID device 08:01:00:00 (PID=ca03)
linux/uhidasync.c:223 wait_watch: select timed out

Check execution result:
joystick not found: Logitech  Logitech MOMO Racing  (0)
joystick not found: Sony Computer Entertainment Wireless Controller (0)
* dmesg output:

Code: Select all

[ 2146.106064] input: Logitech  Logitech MOMO Racing  as /devices/virtual/misc/uhid/0006:046D:CA03.001A/input/input26
[ 2146.113937] hid-generic 0006:046D:CA03.001A: input,hidraw0: <UNKNOWN> HID v1.00 Multi-Axis Controller [Logitech  Logitech MOMO Racing ] on
[ 2151.201142] logitech 0003:046D:CA03.001B: fixing up Logitech Momo Racing Force (Black) report descriptor
[ 2151.213479] input: Logitech  Logitech MOMO Racing  as /devices/platform/soc/1c1d400.usb/usb8/8-1/8-1:1.0/0003:046D:CA03.001B/input/input27
[ 2151.219136] logitech 0003:046D:CA03.001B: input,hidraw0: USB HID v1.00 Joystick [Logitech  Logitech MOMO Racing ] on usb-1c1d400.usb-1/input0
[ 2151.219249] logitech 0003:046D:CA03.001B: Force feedback support for Logitech Gaming Wheels
I noted that /dev/input/js* are not created when DS4 and wheel are connected to the OPi as occurs with raspbian, however the wheel is detected under /dev/input/event0 and DS4 under /dev/input/event2 (event1 is assigned to gpio keys):

Code: Select all

pi@orangepizero:~$ evtest /dev/input/event0
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0xca03 version 0x100
Input device name: "Logitech  Logitech MOMO Racing "
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 288 (BTN_TRIGGER)
    Event code 289 (BTN_THUMB)
    Event code 290 (BTN_THUMB2)
    Event code 291 (BTN_TOP)
    Event code 292 (BTN_TOP2)
    Event code 293 (BTN_PINKIE)
    Event code 294 (BTN_BASE)
    Event code 295 (BTN_BASE2)
    Event code 296 (BTN_BASE3)
    Event code 297 (BTN_BASE4)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max     1023
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      255
    Event code 2 (ABS_Z)
      Value      0
      Min        0
      Max      255
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
  Event type 21 (EV_FF)
    Event code 82 (FF_CONSTANT)
    Event code 96 (FF_GAIN)
    Event code 97 (FF_AUTOCENTER)
Properties:
Testing ... (interrupt to exit)
Event: time 1483820437.632014, type 3 (EV_ABS), code 0 (ABS_X), value 510
Event: time 1483820437.632014, type 3 (EV_ABS), code 1 (ABS_Y), value 255
Event: time 1483820437.632014, type 3 (EV_ABS), code 2 (ABS_Z), value 255
Event: time 1483820437.632014, -------------- EV_SYN ------------
Event: time 1483820437.983997, type 3 (EV_ABS), code 0 (ABS_X), value 511
Event: time 1483820437.983997, -------------- EV_SYN ------------
Event: time 1483820437.991993, type 3 (EV_ABS), code 0 (ABS_X), value 512
Event: time 1483820437.991993, -------------- EV_SYN ------------
Event: time 1483820437.999991, type 3 (EV_ABS), code 0 (ABS_X), value 513
Event: time 1483820437.999991, -------------- EV_SYN ------------
Event: time 1483820438.007992, type 3 (EV_ABS), code 0 (ABS_X), value 514
Event: time 1483820438.007992, -------------- EV_SYN ------------
Event: time 1483820438.015989, type 3 (EV_ABS), code 0 (ABS_X), value 515
Event: time 1483820438.015989, -------------- EV_SYN ------------
Event: time 1483820438.023991, type 3 (EV_ABS), code 0 (ABS_X), value 516
Event: time 1483820438.023991, -------------- EV_SYN ------------
Event: time 1483820438.031990, type 3 (EV_ABS), code 0 (ABS_X), value 517

................................................................

Next step will be to test Debian server release (Upgrading kernel also) provided by Orange Pi instead of armbian.

Post Reply