Tag Archives: allwinner

OctoPrint installation on Orange PI PC – Print Test File

2018-02-17 admin

After the OctoPrint server configuration

we set the connection parameters for the printer.

After connecting to the OctoPrint server with the octoprint user and password as password, we set up the printer connection

With these settings it is possible to print a gcode file already generated with Cura or Slic3r

Cura

Slic3r

or upload a stl file on which the slice will be executed using the loaded cura profile and the CuraEngine on the Orange Pi PC system.

In the case where a stl file is imported, the slicing of the file is proposed

At this point the file is ready for printing

Once the printing is started, the progress and temperature can be checked

as the layers that are being created

In this example, the basic settings were used to start the system for the first time.

For further information and configurations on OctoPrint refer to the software documentation

Octoprint Documentation

At the following link the supported printers are listed

Supported printers

Configuration, Software

OctoPrint installation on Orange PI PC – Printer Settings

2018-01-08 admin

After defining the local hostname resolution

Local Hostname Resolution

at this point it is necessary to configure the printer.

WARNING: Use of the settings shown is at your own risk. We assume no responsibility if these settings cause malfunctions or breakage of the printer.

At the first access to OctoPrint, the basic parameters for managing the printer are requested. In our case, we connect the Orange PI PC to an Anet A8 3d printer via the USB port. At the first access to the address

http://3dprinter.local

a configuration mask is shown

pressing next we access the next screen where to define the user who manages the printer with his password

We press Keep Access Control; the next step is the control of the Internet connection in which we disable the Connectivity Check

We have to import our cura profile for Anet A8 and set the path to the executable CuraEngine, compiled in the previous article

Octoprint Installation

The imported profile must be generated by Cura 15.04.x or older. Below is the link to the various versions of the Cura software

Cura

We can now define the parameters of the printer, in our case Anet A8

We set the bed size and print volume

The speed of movement using the control panel is defined in the next step; we set up conservative parameters

Finally, we set the extruder parameters

At the next screen we set the commands to be sent to Debian directly from OctoPrint; they are set as follows

Restart OctoPrint: echo password |  sudo -S systemctl restart octoprint

Restart system: echo password | sudo -S reboot

Shutdown system: echo password |  sudo -S poweroff

Restart OctoPrint: echo password | sudo -S systemctl restart octoprint

Restart system: echo password | sudo -S reboot

Shutdown system: echo password | sudo -S poweroff

where in the password you must enter the password to run the root commands on Debian.

The folder in which Octoprint has been installed is inserted for the software update

We do not insert anything for the webcam

Finally, the configuration is completed with the Finish button.

For more OctoPrint settings and addons refer to the site

OctoPrint

In the next article we’ll print a test model

Print test file

Configuration, Software

OctoPrint installation on Orange PI PC – Local Hostname Resolution

2018-01-03 admin

After configuring haproxy for the use of content in http on the standard port

HAProxy Installation

we configure the Linux machine to publish the hostname on the network with the avahi daemon.

On Linux and OSX machines this service is natively visible, while for Windows systems it is necessary to install the Bonjour service

Bonjour application for windows

On the Orange PI PC the avahi daemon must be installed with the command

sudo apt-get install avahi-daemon

1	sudo apt-get install avahi-daemon

We change the name to which our 3D print server must match in the two files /etc/hosts and /etc/hostname

sudo nano /etc/hosts
sudo nano /etc/hostname

1 2	sudo nano /etc/hosts sudo nano /etc/hostname

In our case the name orangepcpc has been changed to 3dprinter.

Restarting the linux box, the services are accessible using the name 3dprinter.local.

In the next article we’ll show a printer configuration

Printer Settings

Configuration, Software

OctoPrint installation on Orange PI PC – HAProxy Installation

2017-12-13 admin

After the automatic start of OctoPrint configuration

OctoPrint Autostart

at this point we can set up the system to answer to the standard port of an Http server.

For this purpose we install and configure the HAProxy reverse proxy

HAproxy

Proceed to the installation

sudo apt-get install haproxy

1	sudo apt-get install haproxy

Edit the /etc/haproxy/haproxy.cfg file and add to the default the directives including also the use of webcam

frontend public
        bind :::80 v4v6
        use_backend webcam if { path_beg /webcam/ }
        default_backend octoprint

backend octoprint
        reqrep ^([^\ :]*)\ /(.*)     \1\ /\2
        option forwardfor
        server octoprint1 127.0.0.1:5000

backend webcam
        reqrep ^([^\ :]*)\ /webcam/(.*)     \1\ /\2
        server webcam1  127.0.0.1:8080

frontend public

bind :::80 v4v6

use_backend webcam if { path_beg /webcam/ }

default_backend octoprint

backend octoprint

reqrep ^([^\ :]*)\ /(.*) \1\ /\2

option forwardfor

server octoprint1 127.0.0.1:5000

backend webcam

reqrep ^([^\ :]*)\ /webcam/(.*) \1\ /\2

server webcam1 127.0.0.1:8080

Restart the proxy with the command

sudo systemctl restart haproxy

1	sudo systemctl restart haproxy

Restart the Orange PI. If everything is configured correctly, the 3D print server answers on port 80 of the Orange Pi PC ip address

http://ORANGEPIPC_IP

It is possible to map the Octoprint service on port 5000 only to the loopback interface by editing the file ~/.octoprint/config.yaml

nano ~/.octoprint/config.yaml

1	nano ~/.octoprint/config.yaml

and adding the host reference under the server directive

server:
    host: 127.0.0.1

1 2	server: host: 127.0.0.1

Restart OctoPrint

sudo systemctl restart octoprint

1	sudo systemctl restart octoprint

Now the 5000 port is mapped only with the address 127.0.0.1.

In the next article, we’ll configure Linux to publish the hostname on the network so that it can be accessed through this reference without using the IP address

Local Hostname Resolution

Configuration, Software

OctoPrint installation on Orange PI PC – Autostart

2017-11-23 admin

After the installation of OctoPrint and CuraEngine in the previous article

OctoPrint Package Installation

we treat now the configuration of the 3d print server.

As first operation, we set up the automatic startup of OctoPrint.

Run the following commands

sudo cp /opt/octoprint/OctoPrint/scripts/octoprint.init /etc/init.d/octoprint
sudo chmod +x /etc/init.d/octoprint
sudo cp /opt/octoprint/OctoPrint/scripts/octoprint.default /etc/default/octoprint

sudo cp /opt/octoprint/OctoPrint/scripts/octoprint.init /etc/init.d/octoprint

sudo chmod +x /etc/init.d/octoprint

sudo cp /opt/octoprint/OctoPrint/scripts/octoprint.default /etc/default/octoprint

Edit the /etc/ defaults/octoprint file changing the pointing to the executable to start OctoPrint using vi

sudo vi /etc/default/octoprint

1	sudo vi /etc/default/octoprint

or nano

sudo nano /etc/default/octoprint

1	sudo nano /etc/default/octoprint

and edit the file from

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.
OCTOPRINT_USER=pi

# base directory to use
#BASEDIR=/home/pi/.octoprint

# configuration file to use
#CONFIGFILE=/home/pi/.octoprint/config.yaml

# On what port to run daemon, default is 5000
PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!
#DAEMON=/home/pi/OctoPrint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this
DAEMON_ARGS="--port=$PORT"

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user
UMASK=022

# Process priority, 0 here will result in a priority 20 process.
# -2 ensures Octoprint has a slight priority over user processes.
NICELEVEL=-2

# Should we run at startup?
START=yes

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.

OCTOPRINT_USER=pi

# base directory to use

#BASEDIR=/home/pi/.octoprint

# configuration file to use

#CONFIGFILE=/home/pi/.octoprint/config.yaml

# On what port to run daemon, default is 5000

PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!

#DAEMON=/home/pi/OctoPrint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this

DAEMON_ARGS="--port=$PORT"

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user

UMASK=022

# Process priority, 0 here will result in a priority 20 process.

# -2 ensures Octoprint has a slight priority over user processes.

NICELEVEL=-2

# Should we run at startup?

START=yes

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.
OCTOPRINT_USER=octoprint

# base directory to use
#BASEDIR=/home/octoprint/.octoprint

# configuration file to use
#CONFIGFILE=/home/octoprint/.octoprint/config.yaml

# On what port to run daemon, default is 5000
PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!
DAEMON=/opt/octoprint/OctoPrint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this
DAEMON_ARGS="--port=$PORT"

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user
UMASK=022

# Process priority, 0 here will result in a priority 20 process.
# -2 ensures Octoprint has a slight priority over user processes.
NICELEVEL=-2

# Should we run at startup?
START=yes

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.

OCTOPRINT_USER=octoprint

# base directory to use

#BASEDIR=/home/octoprint/.octoprint

# configuration file to use

#CONFIGFILE=/home/octoprint/.octoprint/config.yaml

# On what port to run daemon, default is 5000

PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!

DAEMON=/opt/octoprint/OctoPrint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this

DAEMON_ARGS="--port=$PORT"

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user

UMASK=022

# Process priority, 0 here will result in a priority 20 process.

# -2 ensures Octoprint has a slight priority over user processes.

NICELEVEL=-2

# Should we run at startup?

START=yes

taking into account also the different user being used.

Add the script to startup automatically OctoPrint

sudo update-rc.d octoprint defaults

1	sudo update-rc.d octoprint defaults

Start OctoPrint with the command

sudo systemctl start octoprint

1	sudo systemctl start octoprint

Check that OctoPrint is active on port 5000 of the Orange PI PC by accessing the address

http://IPORANGEPIPC:5000

1	http://IPORANGEPIPC:5000

Rebooting the Orange PI PC, the OctoPrint server now starts automatically.

In the next article, Linux will be configured to connect to OctoPrint on the Http standard port, i.e. on port 80

HAProxy Installation

Compilation, Installation, Software

OctoPrint installation on Orange PI PC – Python package installation

2017-11-21 admin

This article describes how to enable the Orange PI PC board to work as 3d printers network server.

A software that provides this functionality is OctoPrint

OctoPrint

From the OctoPrint site we can download an image for Raspberry PI with the system already ready; in the case of the Orange PI PC we have to install and configure OctoPrint on a Linux image.

You can also use a Linux image available for Orange PI PC and run the steps related to OctoPrint package installation, but you have to check the prerequisites for Octoprint python package installation.

We instead built for this article an image using the Armban scripts.

As a first step, prepare the micro sd card with an Armbian image. In the specific case, we’ll use a Debian Jessie image created using the Armbian script, as indicated on the link

Armbian building

and described also in a previous article

Building Armbian image for Orange PI PC

We followed these steps to build the Armbian image on Ubuntu Xenial 16.04; from a Linux command shell

git clone https://github.com/armbian/build
cd build
./compile.sh

git clone https://github.com/armbian/build

cd build

./compile.sh

In the building options choose

We selected the default kernel configuration

Choose an Orange PI PC board

We used the mainline kernel

and Debian Jessie as distribution

We built an image with desktop envinronment

After this option, the script proceeds to the compilation. The generated image is Armbian_5.34_Orangepipc_Debian_jessie_next_4.13.12_desktop.img. This image can be downloaded from the link

Armbian image for Orange Pi PC

Start Armbian and create the user for the Jessie image; in this case we choose octoprint/password as user.

If necessary, reconfigure the keyboard with the command

sudo dpg-reconfigure keyboard-configuration

1 2	sudo dpg-reconfigure keyboard-configuration

and proceed to upgrade the system

sudo apt-get update
sudo apt-get upgrade

1 2	sudo apt-get update sudo apt-get upgrade

If the system needs to be configured via a wireless connection, the connection must be active at startup. For this purpose in our case we used the Wicd daemon

Wicd Debian

Remove the network-manager package

sudo apt-get remove network-manager

1	sudo apt-get remove network-manager

This command uninstalls network-manager and network-manager-gnome.

Check that the wireless interface is not present in

/etc/network/interfaces

cat /etc/network/interfaces

1	cat /etc/network/interfaces

Proceed to Wicd installation

sudo apt-get install wicd

1	sudo apt-get install wicd

Check that the octoprint user is present in the netdev group

cat /etc/group | grep netdev

1	cat /etc/group \| grep netdev

In our case it is already present, giving as a result

If not present, add it with the command

sudo adduser octoprint netdev
sudo /etc/init.d/dbus reload

1 2	sudo adduser octoprint netdev sudo /etc/init.d/dbus reload

Start wicd

sudo systemctl start wicd

1	sudo systemctl start wicd

Logon to the armbian graphic desktop and start the wireless configuration with the command

wicd-client -n

1	wicd-client -n

Configure and save the network connection from the graphical interface.

If you want the remote desktop follow the steps listed in the article

Remote desktop setup for Armbian on Orange PI PC

We can now install Octoprint. Follow the steps available at the link

OctoPrint installation on Linux

Install the prerequisites

sudo apt-get update
sudo apt-get install python-pip python-dev python-setuptools virtualenv python-virtualenv git libyaml-dev build-essential

1 2	sudo apt-get update sudo apt-get install python-pip python-dev python-setuptools virtualenv python-virtualenv git libyaml-dev build-essential

Create under /opt the octoprint folder and assign the ownership to octoprint

sudo mkdir /opt/octoprint
sudo chown octoprint:octoprint -R /opt/octoprint

sudo mkdir /opt/octoprint

sudo chown octoprint:octoprint -R /opt/octoprint

In a Linux shell command go to /opt/octoprint folder and download the software

cd /opt/octoprint
git clone https://github.com/foosel/OctoPrint.git

1 2	cd /opt/octoprint git clone https://github.com/foosel/OctoPrint.git

Run

cd OctoPrint
virtualenv venv
./venv/bin/pip install pip --upgrade
./venv/bin/python setup.py install

cd OctoPrint

virtualenv venv

./venv/bin/pip install pip --upgrade

./venv/bin/python setup.py install

Create the .octoprint folder

mkdir ~/.octoprint

1	mkdir ~/.octoprint

Add octoprint to the following groups to manage the 3d printer using the USB port

sudo usermod -a -G tty octoprint
sudo usermod -a -G dialout octoprint

1 2	sudo usermod -a -G tty octoprint sudo usermod -a -G dialout octoprint

Check the correct installation by running the command

/opt/octoprint/OctoPrint/venv/bin/octoprint

1	/opt/octoprint/OctoPrint/venv/bin/octoprint

The OctoPrint server can be reached on port 5000 at the IP address of Orange PI PC

http://ipaddress:5000

Install the Cura Engine at this point; place yourself in the octoprint user’s home and download the source package

cd
wget https://github.com/Ultimaker/CuraEngine/archive/15.04.6.tar.gz

1 2	cd wget https://github.com/Ultimaker/CuraEngine/archive/15.04.6.tar.gz

Unpack the package

tar -zxvf 15.04.6.tar.gz

1	tar -zxvf 15.04.6.tar.gz

Go into the unpacked folder

cd CuraEngine-15.04.6/

1	cd CuraEngine-15.04.6/

Run the compilation with the command

make

make

The compiled software is located under the build folder

Create the /opt /octoprint/cura folder and copy the CuraEngine file to this folder

mkdir /opt/octoprint/cura
cd ~/CuraEngine-15.04.6/build
cp CuraEngine /opt/octoprint/cura/

mkdir /opt/octoprint/cura

cd ~/CuraEngine-15.04.6/build

cp CuraEngine /opt/octoprint/cura/

The executable is now in the /opt/octoprint/cura folder and will be used later by OctoPrint.

In the next article we’ll treat how to configure OctoPrint’s automatic startup

OctoPrint Autostart

Development, Software

Libreelec8 addon building for Orange PI PC

2017-04-30 admin

In the article about the Libreelec8 build for Orange PI PC

Libreelec8 in OrangePI PC

we created the environment and compiled the Libreelec8 image for our development board. We integrate what it has been said in the previous article showing how to build the Libreelec 8 addons for our Orange PI PC board.

Now we proceed to build some addons. The packages that you can build are available in the kodi-binary-addons folder as shown below

and in the packages/addons folder

We build the pvr.iptvsimple addon running the following command from the /home/sviluppo/orangepi/libreelec/libreelec-8.0 folder

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

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

We build the proftpd addon, among those avaliable in the packages/addons folder

PROJECT=H3 ARCH=arm scripts/create_addon proftpd

1	PROJECT=H3 ARCH=arm scripts/create_addon proftpd

The compiled addons are available in the following folder

/home/sviluppo/orangepi/libreelec/libreelec-8.0/target/addons/8.1/H3/arm/

1	/home/sviluppo/orangepi/libreelec/libreelec-8.0/target/addons/8.1/H3/arm/

Here are the links to download some compiled addons

PVR addons

Service Addons

Development, Software

Libreelec8 in OrangePI PC

2017-04-13 admin

This article describes the steps that I ran to prepare a first version of Libreelec 8 in Orange PI PC cards and other H3 socs.

Starting from the Debian development envinronment, with its installed packages, already used for the compilation of OpenELEC 7

Openelec compilation for Orange PI PC

we proceed to build an Libreelec 8 image.

We started as basis from the work done for Openelec 7 and Libreelec 7 available on the two github repositories

H3 Openelec 7 Github

H3 Libreelec 7 Github

sviluppo@debian8:~/orangepi$ mkdir libreelec
sviluppo@debian8:~/orangepi$ cd libreelec
sviluppo@debian8:~/orangepi/libreelec$

sviluppo@debian8:~/orangepi$ mkdir libreelec

sviluppo@debian8:~/orangepi$ cd libreelec

sviluppo@debian8:~/orangepi/libreelec$

Clone the Libreelec8 github

git clone -b libreelec-8.0 https://github.com/LibreELEC/LibreELEC.tv.git libreelec-8.0

1	git clone -b libreelec-8.0 https://github.com/LibreELEC/LibreELEC.tv.git libreelec-8.0

The patches have been created for a specific version of the commit, so we align our github clone to that version

cd libreelec-8.0
git checkout 745f6790ec0456aa8478fff5360107c148ea5204

1 2	cd libreelec-8.0 git checkout 745f6790ec0456aa8478fff5360107c148ea5204

Download from the following link the patches, the H3 project and other stuff

H3 Libreelec 8

Unzip this file in /home/sviluppo/orangepi/libreelec

Run the following steps

1)Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/projects the folder

2) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/multimedia the folders

cedarx
libmpeg2

3) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/tools the folder

sunxi-tools

4) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/sysutils the folder

sunxi-sys-utils

5) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/graphics the folder

sunxi-mali

6) Copy to /home/sviluppo/orangepi/libreelec/libreelec-8.0/packages/linux-drivers the folder

mt7601u

7) The following patches are available in /home/sviluppo/orangepi/libreelec/H3LE8/patches folder

linux.patch

image.patch

mkimage.patch

kodi.patch

libcec.patch

u-boot.patch

u-boot-release.patch

u-boot-update.patch

Patch the code from the /home/sviluppo/orangepi/libreelec folder running the following commands

patch  libreelec-8.0/packages/linux/package.mk < H3LE8/patches/linux.patch
patch  libreelec-8.0/scripts/image < H3LE8/patches/image.patch
patch  libreelec-8.0/scripts/mkimage < H3LE8/patches/mkimage.patch
patch libreelec-8.0/packages/mediacenter/kodi/package.mk < H3LE8/patches/kodi.patch 
patch  libreelec-8.0/packages/devel/libcec/package.mk < H3LE8/patches/libcec.patch
patch libreelec-8.0/packages/tools/u-boot/package.mk < H3LE8/patches/u-boot.patch
patch libreelec-8.0/packages/tools/u-boot/release < H3LE8/patches/u-boot-release.patch
patch libreelec-8.0/packages/tools/u-boot/scripts/update.sh < H3LE8/patches/u-boot-update.patch

patch libreelec-8.0/packages/linux/package.mk < H3LE8/patches/linux.patch

patch libreelec-8.0/scripts/image < H3LE8/patches/image.patch

patch libreelec-8.0/scripts/mkimage < H3LE8/patches/mkimage.patch

patch libreelec-8.0/packages/mediacenter/kodi/package.mk < H3LE8/patches/kodi.patch

patch libreelec-8.0/packages/devel/libcec/package.mk < H3LE8/patches/libcec.patch

patch libreelec-8.0/packages/tools/u-boot/package.mk < H3LE8/patches/u-boot.patch

patch libreelec-8.0/packages/tools/u-boot/release < H3LE8/patches/u-boot-release.patch

patch libreelec-8.0/packages/tools/u-boot/scripts/update.sh < H3LE8/patches/u-boot-update.patch

Proceed to the image build for Orange PI PC from the folder /home/sviluppo/orangepi/libreelec/libreelec-8.0 running

ARCH=arm PROJECT=H3 SYSTEM=opipc  make image

1	ARCH=arm PROJECT=H3 SYSTEM=opipc make image

At the end of the compilation in the /home/sviluppo/orangepi/libreelec/libreelec-8.0/target folder we find the files to install or update Libreelec 8

At the link

Openelec 7 H3 FAQ

we find the boards we can build changing the SYSTEM parameter in the building command

SYSTEM=opi2
SYSTEM=opione
SYSTEM=opipc
SYSTEM=opiplus
SYSTEM=opilite
SYSTEM=opipcplus
SYSTEM=opiplus2e
SYSTEM=bpim2p
SYSTEM=bx2

ARCH=arm PROJECT=H3 SYSTEM=BOARD  make image

1	ARCH=arm PROJECT=H3 SYSTEM=BOARD make image

This image is a first attempt to build Libreelec 8 for H3 socs. The image was installed on Orange PI PC and the system worked well, but still bugs and malfunctions may occur.

Here is the built Libreelec 8 image for Orange PI PC

Orange PI PC Libreelec 8 Image

We tested this image on an Orange PI PC board.

Here are other images we did’t test on the devices

Orange Pi2 Libreelec 8 Image

Orange Pi Lite Libreelec 8 Image

Orange Pi One Libreelec 8 Image

Orange Pi PC Plus Libreelec 8 Image

Orange Pi Plus Libreelec 8 Image

Orange Pi Plus 2e Libreelec 8 Image

WARNING: The image installation on the device is at your own risk. We accept no responsibility if the installation leads to malfunction or block of the device.

The following article shows how to build the addons

Libreelec 8 addon building for Orange PI PC

Development, Software

Openelec addon building for Orange PI PC

2016-12-18 admin

In the article about the OpenELEC build for Orange PI PC

Openelec building for Orange PI PC

we created the environment and compiled the OpenELEC image for our development board. We integrate what it has been said in the previous article showing how to build the Openelec addons for our Orange PI PC board.

As stated in the linked article we have to open a shell command window in the OPENELEC-OPIPC folder

cd OPENELEC-OPIPC

1	cd OPENELEC-OPIPC

Using the graphical interface in Debian we can verify the availabilty of the official addons structure. To add the unofficial ones we have to run from the OpenELEC-OPIPC folder

git clone https://github.com/jernejsk/unofficial-addons.git  packages/addons/unofficial

1	git clone https://github.com/jernejsk/unofficial-addons.git packages/addons/unofficial

Now we proceed to build an official addon and an unofficial one. The packages that you can build ara available in the official folder as shown below

and in the unofficial folder

We build the official pvr.iptvsimple addon with the command

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

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

For the unofficial we build the p7zip module

PROJECT=H3 ARCH=arm scripts/create_addon p7zip

1	PROJECT=H3 ARCH=arm scripts/create_addon p7zip

The compiled addons are availablein the following folder

/home/sviluppo/orangepi/openelec/OPENELEC-OPIPC/target/addons/7.0/H3/arm/

1	/home/sviluppo/orangepi/openelec/OPENELEC-OPIPC/target/addons/7.0/H3/arm/

In the case of errors in the compliation check the logs and proceed consequently. For example in the case of trasmission the system was not able to download the source package using the link in the package.mk file

/home/sviluppo/orangepi/openelec/OPENELEC-OPIPC/packages/addons/unofficial/addons/service/downloadmanager/transmission/package.mk

1	/home/sviluppo/orangepi/openelec/OPENELEC-OPIPC/packages/addons/unofficial/addons/service/downloadmanager/transmission/package.mk

To overcome this unexpected error we added another link to the package, i.e. we changed the package.mk file from

PKG_URL="http://download.transmissionbt.com/files/$PKG_NAME-$PKG_VERSION.tar.xz"
PKG_DEPENDS_TARGET="toolchain zlib libressl curl libevent"

1 2	PKG_URL="http://download.transmissionbt.com/files/$PKG_NAME-$PKG_VERSION.tar.xz" PKG_DEPENDS_TARGET="toolchain zlib libressl curl libevent"

PKG_URL="http://download.transmissionbt.com/files/$PKG_NAME-$PKG_VERSION.tar.xz"
PKG_URL="https://github.com/transmission/transmission-releases/raw/master/$PKG_NAME-$PKG_VERSION.tar.xz"
PKG_DEPENDS_TARGET="toolchain zlib libressl curl libevent"

PKG_URL="http://download.transmissionbt.com/files/$PKG_NAME-$PKG_VERSION.tar.xz"

PKG_URL="https://github.com/transmission/transmission-releases/raw/master/$PKG_NAME-$PKG_VERSION.tar.xz"

PKG_DEPENDS_TARGET="toolchain zlib libressl curl libevent"

In this way, the transmission addon has been compiled correctly, always with the command

PROJECT=H3 ARCH=arm scripts/create_addon transmission

1	PROJECT=H3 ARCH=arm scripts/create_addon transmission

Development, Software

Building Armbian image for Orange PI PC

2016-09-02 admin

We treat now the bulding of the image Armbian for Orange PI PC. From the developer’s github

Armbian Github

we find the steps to do the task.

From the Armbian site

Building Armbian

the supported building envinronment is Ubuntu. In our test we use Ubuntu 16.04.1 LTS x86-64

Ubuntu

and our Debian 8.5 envinroment used for the other tasks described on this site. With Ubuntu the compile.sh script installs all the required packages to build the image. On the Armbian web site we can find also various compilation options..

Using Debian 8.5 as host, we have to exectute some prerequisites tasks described below. In the case of issues execute the building on Ubuntu..

First we install the cross compilation envinronment in Debian

https://wiki.debian.org/CrossToolchains

We have to create the file crosstools.list in /etc/apt/sources.list.d

sudo vi /etc/apt/sources.list.d/crosstools.list

1	sudo vi /etc/apt/sources.list.d/crosstools.list

Edit this file and add the line

deb http://emdebian.org/tools/debian/ jessie main

1	deb http://emdebian.org/tools/debian/ jessie main

Save the file and add the repository key using curl. We install the curl package

sudo apt-get install curl

1	sudo apt-get install curl

and add the key

curl http://emdebian.org/tools/debian/emdebian-toolchain-archive.key | sudo apt-key add -

1	curl http://emdebian.org/tools/debian/emdebian-toolchain-archive.key \| sudo apt-key add -

Now we are ready to install the packages and architecture as listed below

sudo dpkg --add-architecture armhf
sudo apt-get update
sudo apt-get install autoconf
sudo apt-get install ccache
sudo apt-get install git
sudo apt-get install qemu
sudo apt-get install qemu-user-static
sudo apt-get install dchroot
sudo apt-get install debootstrap
sudo apt-get install apt-cacher-ng 
sudo apt-get install pigz
sudo apt-get install pv
sudo apt-get install mpv
sudo apt-get install  u-boot-tools
sudo apt-get install ntpdate
sudo apt-get install device-tree-compiler
sudo apt-get install pkg-config
sudo apt-get install libusb-1.0-0-dev
sudo apt-get install libusb-dev
sudo apt-get install gcc-4.9-multilib
sudo apt-get install crossbuild-essential-armhf

sudo dpkg --add-architecture armhf

sudo apt-get update

sudo apt-get install autoconf

sudo apt-get install ccache

sudo apt-get install git

sudo apt-get install qemu

sudo apt-get install qemu-user-static

sudo apt-get install dchroot

sudo apt-get install debootstrap

sudo apt-get install apt-cacher-ng

sudo apt-get install pigz

sudo apt-get install pv

sudo apt-get install mpv

sudo apt-get install u-boot-tools

sudo apt-get install ntpdate

sudo apt-get install device-tree-compiler

sudo apt-get install pkg-config

sudo apt-get install libusb-1.0-0-dev

sudo apt-get install libusb-dev

sudo apt-get install gcc-4.9-multilib

sudo apt-get install crossbuild-essential-armhf

At this point the procedure is the same on Ubuntu or Debian. We create a folder called armbian under orangepi folder in the home folder of the linux system; in our case the user is sviluppo

sviluppo@debian8:~/orangepi$ ls
openelec  sunxi
sviluppo@debian8:~/orangepi$ mkdir armbian

sviluppo@debian8:~/orangepi$ ls

openelec sunxi

sviluppo@debian8:~/orangepi$ mkdir armbian

We clone the repository with the following command in a shell command window in the armbian folder

git clone https://github.com/igorpecovnik/lib --depth 1
cp lib/compile.sh .

1 2	git clone https://github.com/igorpecovnik/lib --depth 1 cp lib/compile.sh .

To build the image execute

./compile.sh

1	./compile.sh

When requested enter the root password and for our image select the options described below.

Full OS image

Orangepipc board

default kernel

Debian stable image

Image with desktop envinronment

We find the image under the folder output/images ready to be transferred on a micro sd card as described in previous article

Micro Devices

Tag Archives: allwinner

OctoPrint installation on Orange PI PC – Print Test File

OctoPrint installation on Orange PI PC – Printer Settings

OctoPrint installation on Orange PI PC – Local Hostname Resolution

OctoPrint installation on Orange PI PC – HAProxy Installation

OctoPrint installation on Orange PI PC – Autostart

OctoPrint installation on Orange PI PC – Python package installation

Libreelec8 addon building for Orange PI PC

Libreelec8 in OrangePI PC

Openelec addon building for Orange PI PC

Building Armbian image for Orange PI PC

Blog about embedded devices