Jump to content

Kodi on Allwinner H3 based boards

hannibal1986

By hannibal1986
in Allwinner sunxi

 Share

Recommended Posts

fedyhd

fedyhd

Posted
Posted

1- Hi, I realized that Kodi on Armbian does not use the internal player but mpv and does not support Hdmi-CEC. It's right?

 

2- I use armbian successfully on one of my two Opi-pc from March 2016. Now, I tried Jernej Openelec port on my other orange pi and works fine with CEC although a little hot. However I would use at least this program (which works perfect on Armbian): "https://github.com/r10r/rcswitch-pi.git"on Openelec, but I do not know how to compile it as an addon for installing on Openelec. Orangepi-forum is almost always out of reach, and I can not write there a question. From https://github.com/jernejsk/OpenELEC-OPi2 I compiled the OpenELEC image but what steps should I follow for the addons? I do not understand this example:

"You can build wanted addon with:

 

PROJECT=H3 ARCH=arm scripts/create_addon pvr.iptvsimple

 

where pvr.iptvsimple is the addon you want to build." pvr.iptvsimple is the folder source?

Link to comment
Share on other sites
jernej

jernej

Posted
Posted

I'm not sure if hijacking Armbian forum is ok for my OpenELEC fork, but due to reachability issues I will answer anyway. You can open an issue on github with question label.

 

1- Hi, I realized that Kodi on Armbian does not use the internal player but mpv and does not support Hdmi-CEC. It's right?

 

Not sure on mpv but certainly doesn't support CEC.

 

 

2- I use armbian successfully on one of my two Opi-pc from March 2016. Now, I tried Jernej Openelec port on my other orange pi and works fine with CEC although a little hot. However I would use at least this program (which works perfect on Armbian): "https://github.com/r10r/rcswitch-pi.git"on Openelec, but I do not know how to compile it as an addon for installing on Openelec. Orangepi-forum is almost always out of reach, and I can not write there a question. From https://github.com/jernejsk/OpenELEC-OPi2 I compiled the OpenELEC image but what steps should I follow for the addons? I do not understand this example:
"You can build wanted addon with:

PROJECT=H3 ARCH=arm scripts/create_addon pvr.iptvsimple

where pvr.iptvsimple is the addon you want to build." pvr.iptvsimple is the folder source?

 

One thing which helps with lowering temperature is disabling RSS feeds. It will lower it for at least few degrees. I guess OE is hotter due to more intensive GPU usage. I think usual temperature settings are basically the same.

 

Yes, pvr.iptvsimple is a folder inside build system. Please take a look at content inside this folder to get an idea what is needed to create custom plugin. AFAIK a big issue here in my opinion is that all plugins must be compiled statically or at least without external dependencies (other than already included in base image). RCSwitch has dependency on wiringPi. I already compiled it as a plugin (gpio program) and you can test it here (link will be valid for 14 days): https://transfer.sh/ILHOt/tools.wiringop-7.0.1.zipI will take a look if there is some way to compile plugins with external dependencies or else I may include wiringPi in base image.

 

Does anyone know which wiringPi port for H3 is best? I used this: https://github.com/WereCatf/WiringOP/commits/h3

Link to comment
Share on other sites
fedyhd

fedyhd

Posted
Posted

I'm not sure if hijacking Armbian forum is ok for my OpenELEC fork, but due to reachability issues I will answer anyway. You can open an issue on github with question label.

 

 

Not sure on mpv but certainly doesn't support CEC.

 

 

 

One thing which helps with lowering temperature is disabling RSS feeds. It will lower it for at least few degrees. I guess OE is hotter due to more intensive GPU usage. I think usual temperature settings are basically the same.

 

Yes, pvr.iptvsimple is a folder inside build system. Please take a look at content inside this folder to get an idea what is needed to create custom plugin. AFAIK a big issue here in my opinion is that all plugins must be compiled statically or at least without external dependencies (other than already included in base image). RCSwitch has dependency on wiringPi. I already compiled it as a plugin (gpio program) and you can test it here (link will be valid for 14 days): https://transfer.sh/ILHOt/tools.wiringop-7.0.1.zipI will take a look if there is some way to compile plugins with external dependencies or else I may include wiringPi in base image.

 

Does anyone know which wiringPi port for H3 is best? I used this: https://github.com/WereCatf/WiringOP/commits/h3

 

Many thanks for your reply, jernej.

 

Regarding the temperature, I see that after a few minutes in the home the temperature is about 70 degrees centigrade (on Armbian in idle is about 50 degrees). I disabled the RSS feeds but for now I have not tested well if the situation improves.

 

About wiringOP, on armbian (OPI-PC) I had used https://github.com/zhaolei/WiringOP and It worked well in the few tests done. Nevertheless, with  https://transfer.sh/ILHOt/tools.wiringop-7.0.1.zip in your openelec fork I get the following output of the command "gpio readall":

 

OpenELEC:~ # gpio readall
 +-----+-----+----------+------+---+-Orange Pi+---+---+------+---------+-----+--+
 | BCM | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | BCM |
 +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
 |     |     |     3.3v |      |   |  1 || 2  |   |      | 5v       |     |     |
 |     |     |    SDA.0 |      |   |  3 || 4  |   |      | 5V       |     |     |
 |     |     |    SCL.0 |      |   |  5 || 6  |   |      | 0v       |     |     |
 |   6 |   6 | IO6 PA06 | ALT3 | 0 |  7 || 8  |   |      | TxD3     |     |     |
 |     |     |       0v |      |   |  9 || 10 |   |      | RxD3     |     |     |
 |     |     |     RxD2 |      |   | 11 || 12 | 0 | ALT3 | IO1 PD14 | 1   | 110 |
 |     |     |     TxD2 |      |   | 13 || 14 |   |      | 0v       |     |     |
 |     |     |     CTS2 |      |   | 15 || 16 | 0 | ALT3 | IO4 PC04 | 4   | 68  |
 |     |     |     3.3v |      |   | 17 || 18 | 0 | ALT3 | IO5 PC07 | 5   | 71  |
 |     |     |     MOSI |      |   | 19 || 20 |   |      | 0v       |     |     |
 |     |     |     MISO |      |   | 21 || 22 |   |      | RTS2     |     |     |
 |     |     |     SCLK |      |   | 23 || 24 |   |      | SPI-CE0  |     |     |
 |     |     |       0v |      |   | 25 || 26 |   |      | CE1      |     |     |
 |     |     |    SDA.1 |      |   | 27 || 28 |   |      | SCL.1    |     |     |
 |   7 |   7 |  IO7 PA7 | ALT3 | 0 | 29 || 30 |   |      | 0v       |     |     |
 |   8 |   8 |  IO8 PA8 | ALT3 | 0 | 31 || 32 | 0 | ALT3 | IO9 PG08 | 9   | 200 |
 |   9 |  10 | IO10 PA9 | ALT3 | 0 | 33 || 34 |   |      | 0v       |     |     |
 |  10 |  12 | IO12PA10 | ALT3 | 0 | 35 || 36 | 0 | ALT3 | IO13PG09 | 13  | 201 |
 |  20 |  14 | IO14PA20 | ALT3 | 0 | 37 || 38 | 0 | ALT3 | IO15PG06 | 15  | 198 |
 |     |     |       0v |      |   | 39 || 40 | 0 | ALT3 | IO16PG07 | 16  | 199 |
 +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
 | BCM | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | BCM |
 +-----+-----+----------+------+---+-Orange Pi+---+------+----------+-----+-----+

 

Note the written "Orange Pi" instead of "OrangePIPC" and also the gpio numbering is different from that on armbian with https://github.com/zhaolei/WiringOP. Indeed I copied the folder compiled on armbian inside /storage in OpenELEC and I get:

 

OpenELEC:~/WiringOP # LD_LIBRARY_PATH=/storage/WiringOP /storage/WiringOP/gpio/gpio readall
 +-----+-----+----------+------+---+--OrangePiPC--+---+------+---------+-----+--+
 | BCM | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | BCM |
 +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
 |     |     |     3.3v |      |   |  1 || 2  |   |      | 5v       |     |     |
 |   2 |   8 |    SDA.0 | ALT5 | 0 |  3 || 4  |   |      | 5V       |     |     |
 |   3 |   9 |    SCL.0 | ALT5 | 0 |  5 || 6  |   |      | 0v       |     |     |
 |   4 |   7 |   GPIO.7 | ALT3 | 0 |  7 || 8  | 0 | ALT3 | TxD3     | 15  | 14  |
 |     |     |       0v |      |   |  9 || 10 | 0 | ALT3 | RxD3     | 16  | 15  |
 |  17 |   0 |     RxD2 | ALT3 | 0 | 11 || 12 | 0 | ALT3 | GPIO.1   | 1   | 18  |
 |  27 |   2 |     TxD2 | ALT3 | 0 | 13 || 14 |   |      | 0v       |     |     |
 |  22 |   3 |     CTS2 | ALT3 | 0 | 15 || 16 | 0 | ALT3 | GPIO.4   | 4   | 23  |
 |     |     |     3.3v |      |   | 17 || 18 | 0 | ALT3 | GPIO.5   | 5   | 24  |
 |  10 |  12 |     MOSI | ALT4 | 0 | 19 || 20 |   |      | 0v       |     |     |
 |   9 |  13 |     MISO | ALT4 | 0 | 21 || 22 | 0 | ALT3 | RTS2     | 6   | 25  |
 |  11 |  14 |     SCLK | ALT4 | 0 | 23 || 24 | 0 | ALT4 | CE0      | 10  | 8   |
 |     |     |       0v |      |   | 25 || 26 | 0 | ALT3 | GPIO.11  | 11  | 7   |
 |   0 |  30 |    SDA.1 | ALT4 | 0 | 27 || 28 | 0 | ALT4 | SCL.1    | 31  | 1   |
 |   5 |  21 |  GPIO.21 | ALT3 | 0 | 29 || 30 |   |      | 0v       |     |     |
 |   6 |  22 |  GPIO.22 | ALT3 | 0 | 31 || 32 | 0 | ALT3 | RTS1     | 26  | 12  |
 |  13 |  23 |  GPIO.23 | ALT3 | 0 | 33 || 34 |   |      | 0v       |     |     |
 |  19 |  24 |  GPIO.24 | ALT3 | 0 | 35 || 36 | 0 | ALT3 | CTS1     | 27  | 16  |
 |  26 |  25 |  GPIO.25 | ALT3 | 0 | 37 || 38 | 0 | ALT3 | TxD1     | 28  | 20  |
 |     |     |       0v |      |   | 39 || 40 | 0 | ALT3 | RxD1     | 29  | 21  |
 +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+
 | BCM | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | BCM |
 +-----+-----+----------+------+---+--OrangePIPC--+------+----------+-----+-----+
 
where I added "LD_LIBRARY_PATH=/storage/WiringOP" because I have copied there "WiringOP/wiringPi/libwiringPi.so.2.0" renamed in "WiringOP/libwiringPi.so" and "WiringOP/devLib/libwiringPiDev.so.2.0" renamed in "WiringOP/libwiringPiDev.so". Otherwise I get the error "libwiringPi.so" and "libwiringPiDev.so" not found.
 
In the moment I could not directly test the gpio command installed via openelec addons with, for example, a LED or a relay, but I tested the above libraries ("libwiringPi.so" and "libwiringPiDev.so") copied in ~/WiringOP from armbian that work perfect.
In fact, I copied the folder "rcswitch-pi" compiled on armbian ("https://github.com/r10r/rcswitch-pi") inside /storage of openelec like before, and then the following command works perfectly:
LD_LIBRARY_PATH=/storage/WiringOP /storage/rcswitch-pi/send XXXXX X 1
 etc. (My electrical outlet turns on)
 
The same thing works with the "codesend" command from "https://github.com/timleland/rfoutlet.git" compiled again on Armbian 5.20.
Link to comment
Share on other sites
jernej

jernej

Posted
Posted

Heh, it seems that zhaolei merged WereCatf improvements 9 hours ago, so I guess zhaolei's version is now better.

 

Are you ok with current state, e.g. copied libraries and executables, or do you want to have everything packed as a plugin?

Link to comment
Share on other sites
fedyhd

fedyhd

Posted
Posted

Heh, it seems that zhaolei merged WereCatf improvements 9 hours ago, so I guess zhaolei's version is now better.

 

Are you ok with current state, e.g. copied libraries and executables, or do you want to have everything packed as a plugin?

 

I'm ok now thanks, but it would be even better to have plugins in the unofficial repository (for wiringOP sure, then about 433mhz transmitters the above projects "rcswitch-pi" and "rfoutlet" only depend from that two library of WiringOP).

 

Finally I wanted to thank you for your wonderful work with OpenELEC.

Link to comment
Share on other sites
mirek

mirek

Posted
Posted

Hi,

is there any solution to get Kodi working on Armbian 5.20?

I have a black screen and message from console:

/usr/lib/arm-linux-gnueabihf/kodi/kodi-xrandr: Failed to get size of gamma for output default

 

Please help!

Link to comment
Share on other sites
Johann Pascher

Johann Pascher

Posted
Posted

I have kodi on ARMBIAN 5.25 stable Ubuntu 16.04.1 LTS 3.4.113-sun8i 

orangepipc+ board running tested the latest version kodi alfa as well but kodi 17 and 18 don only work on a headless server with codi alone installed.

 

Version 15 of Kodi can bi installed easy, had only some problem with ma remote control.

See may thread about it:

 

Link to comment
Share on other sites
coliscip

coliscip

Posted
Posted

Can you explain how to install KODI 16 on Armbian 5.25 Desktop based on Ubuntu16.04? I've tried to install it but I received errors on libcec4 and libshairplay.

Board is Orange Pi pC.

 

Thank you in advance!

 

Ciprian

Link to comment
Share on other sites
talraash

talraash

Posted
Posted
Quote

how to install KODI 16 on Armbian 5.25 Desktop based on Ubuntu16.04

It's great install from yakkety repos. I don't test cec and shareplay, but default mediaplayer functionalityi work fine.

Link to comment
Share on other sites
ekonik3

ekonik3

Posted
Posted
how to install KODI 16 on Armbian 5.25 Desktop based on Ubuntu16.04
It's great install from yakkety repos. I don't test cec and shareplay, but default mediaplayer functionalityi work fine.
Could you please tell me how to do it? I'm willing to install Kodi on my armbian too

Sent from my Mi A1 using Tapatalk

Link to comment
Share on other sites
talraash

talraash

Posted
Posted
4 hours ago, ekonik3 said:

It's great install from yakkety repos. I don't test cec and shareplay, but default mediaplayer functionalityi work fine.
Could you please tell me how to do it? I'm willing to install Kodi on my armbian too

Sent from my Mi A1 using Tapatalk
 

That post from 2017, now 2018... Use mainline kernel +cedrus+kodi now.

Link to comment
Share on other sites
Valery Rezvyakov

Valery Rezvyakov

Posted
Posted
On 10/8/2018 at 12:41 PM, Kianabrey said:

Hi guys, I also want to install Kodi on Armbian, how do I install? I would like to experience the Armbian if it is a beautiful or a suit.

kodi-wayland

FEATURES:
- mainline kernel & U-Boot
- completely open source except GPU (Mali) driver
- latest Kodi
- MPEG2 should work well

Link to comment
Share on other sites
  • Werner unpinned this topic
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept