Tag Archives: firmware

Openelec addon building for Orange PI PC

2016-12-18 admin

In the article about the OpenELEC build 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

Nodemcu Enduser_setup module lua sample(part2)

2016-11-28 admin

After the firmware build and its upload to the nodemcu dev kit, we connected a switch to pin D5, as shown in the previous article

Nodemcu Enduser_setup module lua sample(part1)

We finally can upload some sample code in which we use the enduser_setup module

Open ESPlorer and load the following sample code

webserver.lua

-- webserver.lua
--webserver sample from the nodemcu github
if srv~=nil then
 srv:close()
end

gpio.mode(1, gpio.OUTPUT)
srv=net.createServer(net.TCP)
srv:listen(80,function(conn)
    conn:on("receive", function(client,request)
        local buf = ""
        local _, _, method, path, vars = string.find(request, "([A-Z]+) (.+)?(.+) HTTP")
        if(method == nil)then
            _, _, method, path = string.find(request, "([A-Z]+) (.+) HTTP")
        end
        local _GET = {}
        if (vars ~= nil)then
            for k, v in string.gmatch(vars, "(%w+)=(%w+)&*") do
                _GET[k] = v
            end
        end
        buf = buf.."<h1> Hello, NodeMcu.</h1><form src=\"/\">Turn PIN1 <select name=\"pin\" onchange=\"form.submit()\">"
        local _on,_off = "",""
        if(_GET.pin == "ON")then
              _on = " selected=true"
              gpio.write(1, gpio.HIGH)
        elseif(_GET.pin == "OFF")then
              _off = " selected=\"true\""
              gpio.write(1, gpio.LOW)
        end
        buf = buf.."<option".._on..">ON</opton><option".._off..">OFF</option></select></form>"
        client:send(buf)
    end)
    conn:on("sent", function (c) c:close() end)
end)

-- webserver.lua

--webserver sample from the nodemcu github

if srv~=nil then

srv:close()

end

gpio.mode(1, gpio.OUTPUT)

srv=net.createServer(net.TCP)

srv:listen(80,function(conn)

conn:on("receive", function(client,request)

local buf = ""

local _, _, method, path, vars = string.find(request, "([A-Z]+) (.+)?(.+) HTTP")

if(method == nil)then

_, _, method, path = string.find(request, "([A-Z]+) (.+) HTTP")

end

local _GET = {}

if (vars ~= nil)then

for k, v in string.gmatch(vars, "(%w+)=(%w+)&*") do

_GET[k] = v

end

buf = buf.."<h1> Hello, NodeMcu.</h1><form src=\"/\">Turn PIN1 <select name=\"pin\" onchange=\"form.submit()\">"

local _on,_off = "",""

if(_GET.pin == "ON")then

_on = " selected=true"

gpio.write(1, gpio.HIGH)

elseif(_GET.pin == "OFF")then

_off = " selected=\"true\""

gpio.write(1, gpio.LOW)

end

buf = buf.."<option".._on..">ON</opton><option".._off..">OFF</option></select></form>"

client:send(buf)

end)

conn:on("sent", function (c) c:close() end)

end)

riasserawifi.lua

--riazzerawifi.lua
-- Starts the portal to choose the wi-fi router to which we have
-- to associate
wifi.sta.disconnect()
wifi.setmode(wifi.STATIONAP)
--ESP SSID generated wiht its chipid
wifi.ap.config({ssid="Mynode-"..node.chipid()
, auth=wifi.OPEN})
enduser_setup.manual(true)
enduser_setup.start(
  function()
    print("Connected to wifi as:" .. wifi.sta.getip())
  end,
  function(err, str)
    print("enduser_setup: Err #" .. err .. ": " .. str)
  end
);

--riazzerawifi.lua

-- Starts the portal to choose the wi-fi router to which we have

-- to associate

wifi.sta.disconnect()

wifi.setmode(wifi.STATIONAP)

--ESP SSID generated wiht its chipid

wifi.ap.config({ssid="Mynode-"..node.chipid()

, auth=wifi.OPEN})

enduser_setup.manual(true)

enduser_setup.start(

function()

print("Connected to wifi as:" .. wifi.sta.getip())

end,

function(err, str)

print("enduser_setup: Err #" .. err .. ": " .. str)

end

);

init.lua

-- init.lua
--Access Point management
pin = 5 --Input PIN
Resetta=0   --Variable used to manage AP reset
gpio.mode(pin,gpio.INPUT)   --Pin 5 in input mode

--If pin input is High let's start the nodemcu portal
if (gpio.read(pin)==gpio.HIGH ) then 

    Resetta=1
end

-- Check if reset the AP credential
if Resetta==1 then 

    -- Start the nodemcu portal
    tmr.alarm(0, 5000, 0, function() dofile("riazzerawifi.lua") end)

else
    -- Start the webserver wiht ip defined by Wi-Fi router
    tmr.alarm(0, 5000, 0, function() dofile("webserver.lua") end)

end

-- init.lua

--Access Point management

pin = 5 --Input PIN

Resetta=0 --Variable used to manage AP reset

gpio.mode(pin,gpio.INPUT) --Pin 5 in input mode

--If pin input is High let's start the nodemcu portal

if (gpio.read(pin)==gpio.HIGH ) then

Resetta=1

end

-- Check if reset the AP credential

if Resetta==1 then

-- Start the nodemcu portal

tmr.alarm(0, 5000, 0, function() dofile("riazzerawifi.lua") end)

else

-- Start the webserver wiht ip defined by Wi-Fi router

tmr.alarm(0, 5000, 0, function() dofile("webserver.lua") end)

end

It is possible to download the above samples at the following link

Sample code

Here is the documentation about the enduser_setup module

enduser_setup module documentation

The example consists of three files:

init.lua: It is executed at the startup of the esp8266.
riazzerawifi.lua: It starts the portal to connect and save the configuration to your Access Point.
webserver.lua: It starts the webserver sample on the nodemcu.

As you can see from the code in init.lua, when the pin D5 is in the state HIGH, we start the portal using enduser_setup module. In the case in which the pin D5 is in the state LOW the esp8266 acquires the IP from an Access Point defined previously after which the test webserver starts.

To save the access point confguration to which we want to connect we place the switch in order to have the HIGH input on pin D5 and reboot the card.

From a PC we can observe the presence of another access point, defined in the file riazzerawifi.lua

wifi.ap.config({ssid="Mynode-"..node.chipid()
, auth=wifi.OPEN})

1 2	wifi.ap.config({ssid="Mynode-"..node.chipid() , auth=wifi.OPEN})

composed by Mynode string + ChipID module

We can connect to this access point and via browser we access to the portal at the ip address 192.168.4.1

Select or enter the SSID of an access point providing the correct password. After the connection reposition the switch to have the LOW state for pin D5 and reboot the nodemcu dev kit.

Now the system will automatically connect to the SSID defined previously and starts the example of the web server.

Please refer to the Lua documentation nodemcu for further study and usable modules

LUA Nodemcu Documentation

Development, Software

Nodemcu Enduser_setup module lua sample(part1)

2016-11-21 admin

In the previous article we showed a sample LUA code for ESP8266

Lua sample code for esp8266

Let us now see an example in which we’ll use the enduser_setup Lua module.

As a first step we compile the nodemcu firmware by including the enduser_setup module. We have to apply the same steps discussed in the build process article

Nodemcu firmware build

editing the app/include/user_modules.h file and uncommenting the line

#define LUA_USE_MODULES_ENDUSER_SETUP

1	#define LUA_USE_MODULES_ENDUSER_SETUP

After the building and firmware upload to the device, we use a switch connected to nodemcu dev kit as shown in the picture

The pin D5 can be connected to a low or high input voltage. Based on the input voltage we can change the behavior of the system.

Note: The Pin D5 in this specific example has been used as Input Pin; in the case of use as Output Pin, you must insert a resistor to limit the output current, as specified in the link

GPIO Pin Allocations

In the next article we’lll upload a LUA sample code with enduser_setup module enabled and we’ll utilize it to manage the wifi connections

Nodemcu Enduser_setup module lua sample(part2)

Development, Software

Nodemcu compilation on Linux

2016-10-08 admin

We’ll cover the steps to follow to create your own Nodemcu image with cross compiling on Linux.

We always start from the Debian envinronment described in the previous article

Debian Envinronment

According the following link

Cross Compilation

as first step we prepare the cross compiling envinronment.

Log on Debian with our development user (sviluppo in our case) and create an esp8266 folder in a terminal window

mkdir esp8266
cd esp8266

1 2	mkdir esp8266 cd esp8266

We install the prerequisites

sudo apt-get install make
sudo apt-get install unrar
sudo apt-get install autoconf
sudo apt-get install automake
sudo apt-get install libtool
sudo apt-get install gcc
sudo apt-get install g++
sudo apt-get install gperf
sudo apt-get install flex
sudo apt-get install bison
sudo apt-get install texinfo
sudo apt-get install gawk
sudo apt-get install ncurses-dev
sudo apt-get install libncurses5-dev
sudo apt-get install libexpat-dev
sudo apt-get install python
sudo apt-get install python-dev
sudo apt-get install python-serial
sudo apt-get install sed
sudo apt-get install git
sudo apt-get install unzip
sudo apt-get install bash
sudo apt-get install help2man
sudo apt-get install wget
sudo apt-get install bzip2
sudo apt-get install libtool-bin
sudo apt-get install srecord
sudo apt-get install python2.7-dev

sudo apt-get install make

sudo apt-get install unrar

sudo apt-get install autoconf

sudo apt-get install automake

sudo apt-get install libtool

sudo apt-get install gcc

sudo apt-get install g++

sudo apt-get install gperf

sudo apt-get install flex

sudo apt-get install bison

sudo apt-get install texinfo

sudo apt-get install gawk

sudo apt-get install ncurses-dev

sudo apt-get install libncurses5-dev

sudo apt-get install libexpat-dev

sudo apt-get install python

sudo apt-get install python-dev

sudo apt-get install python-serial

sudo apt-get install sed

sudo apt-get install git

sudo apt-get install unzip

sudo apt-get install bash

sudo apt-get install help2man

sudo apt-get install wget

sudo apt-get install bzip2

sudo apt-get install libtool-bin

sudo apt-get install srecord

sudo apt-get install python2.7-dev

We download the open-esp-sdk repository

git clone --recursive https://github.com/pfalcon/esp-open-sdk

1	git clone --recursive https://github.com/pfalcon/esp-open-sdk

to proceed to its compilation

cd esp-open-sdk
make STANDALONE=y |& tee make0.log

1 2	cd esp-open-sdk make STANDALONE=y \|& tee make0.log

At the end of the compilation we have the following messages

Xtensa toolchain is built, to use it:

export PATH=/home/sviluppo/esp8266/esp-open-sdk/xtensa-lx106-elf/bin:$PATH

Espressif ESP8266 SDK is installed, its libraries and headers are merged with the toolchain

Xtensa toolchain is built, to use it:

export PATH=/home/sviluppo/esp8266/esp-open-sdk/xtensa-lx106-elf/bin:$PATH

Espressif ESP8266 SDK is installed, its libraries and headers are merged with the toolchain

So we have to include in the PATH variable the following

export PATH=/home/sviluppo/esp8266/esp-open-sdk/xtensa-lx106-elf/bin:$PATH
alias xgcc="xtensa-lx106-elf-gcc"

1 2	export PATH=/home/sviluppo/esp8266/esp-open-sdk/xtensa-lx106-elf/bin:$PATH alias xgcc="xtensa-lx106-elf-gcc"

We can clone at this point the Nodemcu firmware github. Always from the previous terminal window run

sviluppo@debian8:~/esp8266/esp-open-sdk$ cd ..
sviluppo@debian8:~/esp8266$ pwd
/home/sviluppo/esp8266
sviluppo@debian8:~/esp8266$e

sviluppo@debian8:~/esp8266/esp-open-sdk$ cd ..

sviluppo@debian8:~/esp8266$ pwd

/home/sviluppo/esp8266

sviluppo@debian8:~/esp8266$e

Once placed in the esp8266 folder execute

git clone https://github.com/nodemcu/nodemcu-firmware

1	git clone https://github.com/nodemcu/nodemcu-firmware

At the end go into the nodemcu-firmware folder

cd nodemcu-firmware

1	cd nodemcu-firmware

Before proceeding to the creation of our first firmware we have to make changes in the app / include / user_config.h file configuration:

We enable the directive for our devkit 0.9 (our devkit)

#define DEVKIT_VERSION_0_9 1 // define this only if you use NodeMCU devkit v0.9

We change the USB communication speed (speed for our devkit)

//#define BIT_RATE_DEFAULT BIT_RATE_115200
#define BIT_RATE_DEFAULT BIT_RATE_9600

We change the flash size to 4M (flash of our nodemcu devkit)

#define FLASH_4M
// #define FLASH_8M
// #define FLASH_16M
//#define FLASH_AUTOSIZE

We save the file and proceed to the creation of the firmware with the command

make

make

At the end under the bin folder

sviluppo@debian8:~/esp8266/nodemcu-firmware$ ls ./bin
0x00000.bin 0x10000.bin

1 2	sviluppo@debian8:~/esp8266/nodemcu-firmware$ ls ./bin 0x00000.bin 0x10000.bin

we’ll find two files: 0x00000.bin and 0x100000.bin. We generate a single file nodemcu_float.bin with the command

srec_cat -output ./bin/nodemcu_float.bin -binary ./bin/0x00000.bin -binary -fill 0xff 0x00000 0x10000 ./bin/0x10000.bin -binary -offset 0x10000

1	srec_cat -output ./bin/nodemcu_float.bin -binary ./bin/0x00000.bin -binary -fill 0xff 0x00000 0x10000 ./bin/0x10000.bin -binary -offset 0x10000

At this point we have to enable the sviluppo user to use the usb port with the command

sudo adduser $USER dialout

1	sudo adduser $USER dialout

Debian has no need for additional USB drivers. In the presence of virtual machine enable the USB device.

Access to the SDK downloaded and compiled previously; in the bin folder copy the files

blank.bin
esp_init_data_default.bin

into the folder we generated the 0x00000.bin and 0x100000.bin files

At this point we are able to flash the firmware on the device using the esptool. In the next article we’ll descrive how to load the firmware

Nodemcu firmware upload with esptool

Development, Software

Building OpenWrt firmware

2016-09-14 admin

After the brief description of OpenWrt system in the previous article

OpenWrt

we describe now how to build the firmware for our router.

We use as tartget device the TP-Link TL-MR3420 router version 1.

This model is in the list of the supported OpenWrt devices; here is the specific documentation for this device

TP-Link TL-MR3420

From the documentation we know that the SOC is an Atheros AR7241. This information will be used in the configruation phase of the buildin envinronment. As a preliminary operation also download the original firmware of this router from the link

Original Firmware

In the page TP-Link TL-MR3420 we find the links to two differents versions of the OpenWrt firmware:

Firmware used to install OpenWrt: openwrt-15.05.1-ar71xx-generic-tl-mr3420-v1-squashfs-factory.bin.
Firmware used to update OpenWrt: openwrt-15.05.1-ar71xx-generic-tl-mr3420-v1-squashfs-sysupgrade.bin

If we have the original firmware in our device we must utilize the first one, while in the case of updates we use the second one..

We now execute the operation described in the link

OpenWrt Building

in the Debian envinronment installed in previous article

Debian Envinronment

In a shell command window we install the prerequisites as non root user (sviluppo in our case)

sudo apt-get install git-core 
sudo apt-get install build-essential 
sudo apt-get install libssl-dev 
sudo apt-get install libncurses5-dev 
sudo apt-get install unzip 
sudo apt-get install gawk
sudo apt-get install subversion 
sudo apt-get install mercurial

sudo apt-get install git-core

sudo apt-get install build-essential

sudo apt-get install libssl-dev

sudo apt-get install libncurses5-dev

sudo apt-get install unzip

sudo apt-get install gawk

sudo apt-get install subversion

sudo apt-get install mercurial

We create a folder OpenWrt under the home user folder (sviluppo in our case) and clone the repository. In this build we choose the stable branch 15.05

mkdir OpenWrt
cd OpenWrt
git clone  https://git.openwrt.org/15.05/openwrt.git 15.05

mkdir OpenWrt

cd OpenWrt

git clone https://git.openwrt.org/15.05/openwrt.git 15.05

At the end of the git task, execute

cd 15.05
./scripts/feeds update -a
./scripts/feeds install -a

cd 15.05

./scripts/feeds update -a

./scripts/feeds install -a

We are now ready to build the firmware of the TP-Link TL-MR3420 V1.

Execute the command

make menuconfig

1	make menuconfig

and we choose as target Target System AR7xxx/AR9xxx as described in the following screenshotsWith the following choices we change the options

y: we buil it.
m: we build it as module.
n: we skip it.

At the following link

OpenWrt Building

we find all the documentation about the building.

In the Target System with enter we can choose our Target PlatformWe have to install the base packages to admin the system, so we access LuCI Optionthen Collectionsand at the end the luci package; with this option the system installs an http server tooWe choose as modules some cryptographics packages in the kernel modules sectionsthen Cryptographic Api modulesand at the end the following modules merged into the firmware fileYou should save the configuration in a file in order to use it again later. Finally save the configuration in the .config file.

We can now exit the menuconfig and execute the following command in the shell command window

make defconfig

1	make defconfig

This task checks for the prerequisites.

To build the firmware we execute

make V=s

make V=s

in verbose mode.

At the end of the task we can find the firmware in the atheros platform under the bin folder. In our case our images are highlighted in the following screenshotWe can now flash the firmware.

WARNING: Before installing the firmware verify the recovery process of your router in the event of a problem, i.e how to start in recovery mode, flash via tftp, use JTAG, etc. 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 OpenWrt web site describes all the vaious options to build the firmware and packages. In the next article

Building OpenWrt package

we’ll describe how to build and install from a shell window command the vsftpd package.

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

Development, Software

OpenATV Enigma2 image compilation

2016-08-17 admin

In this article we describe how to generate an OpenATV image, based on the Enigma 2 framework

Openatv

Atfer the compilation envinronment installation, described in this previous article

Debian envinroment setup

we can proceed as described below.

Execute the logon into Debian envinronment with the development user (sviluppo in our example). In the home directory create the enigma2 folder

mkdir enigma2
cd enigma2

1 2	mkdir enigma2 cd enigma2

Install the following packages

sudo apt-get install autoconf
sudo apt-get install automake
sudo apt-get install bison
sudo apt-get install bzip2
sudo apt-get install cvs
sudo apt-get install diffstat
sudo apt-get install flex
sudo apt-get install g++
sudo apt-get install gawk
sudo apt-get install gcc
sudo apt-get install gettext
sudo apt-get install git-core
sudo apt-get install gzip
sudo apt-get install help2man
sudo apt-get install ncurses-bin
sudo apt-get install ncurses-dev
sudo apt-get install libc6-dev
sudo apt-get install libtool
sudo apt-get install make
sudo apt-get install texinfo
sudo apt-get install patch
sudo apt-get install perl
sudo apt-get install pkg-config
sudo apt-get install subversion
sudo apt-get install tar
sudo apt-get install texi2html
sudo apt-get install wget
sudo apt-get install zlib1g-dev
sudo apt-get install chrpath
sudo apt-get install libxml2-utils
sudo apt-get install xsltproc
sudo apt-get install libglib2.0-dev
sudo apt-get install python-setuptools
sudo apt-get install libc6-i386
sudo apt-get install genromfs
sudo apt-get install guile-1.8-libs
sudo apt-get install gparted
sudo apt-get install quilt
sudo apt-get install git
sudo apt-get install  libproc-processtable-perl

sudo apt-get install autoconf

sudo apt-get install automake

sudo apt-get install bison

sudo apt-get install bzip2

sudo apt-get install cvs

sudo apt-get install diffstat

sudo apt-get install flex

sudo apt-get install g++

sudo apt-get install gawk

sudo apt-get install gcc

sudo apt-get install gettext

sudo apt-get install git-core

sudo apt-get install gzip

sudo apt-get install help2man

sudo apt-get install ncurses-bin

sudo apt-get install ncurses-dev

sudo apt-get install libc6-dev

sudo apt-get install libtool

sudo apt-get install make

sudo apt-get install texinfo

sudo apt-get install patch

sudo apt-get install perl

sudo apt-get install pkg-config

sudo apt-get install subversion

sudo apt-get install tar

sudo apt-get install texi2html

sudo apt-get install wget

sudo apt-get install zlib1g-dev

sudo apt-get install chrpath

sudo apt-get install libxml2-utils

sudo apt-get install xsltproc

sudo apt-get install libglib2.0-dev

sudo apt-get install python-setuptools

sudo apt-get install libc6-i386

sudo apt-get install genromfs

sudo apt-get install guile-1.8-libs

sudo apt-get install gparted

sudo apt-get install quilt

sudo apt-get install git

sudo apt-get install libproc-processtable-perl

Modify the shell as bash executing

sudo dpkg-reconfigure dash

1	sudo dpkg-reconfigure dash

and choosing the NO option.

Create under openatv an enigma2 folder

mkdir openatv
cd openatv

1 2	mkdir openatv cd openatv

At this step let’s create a folder sources; this folder will contain all the sources for the various set-top boxes we would like to compile

mkdir sources

1	mkdir sources

Using the git command we clone locally the oe-alliance repository

git clone https://github.com/oe-alliance/build-enviroment.git

1	git clone https://github.com/oe-alliance/build-enviroment.git

After this task enter into build-envinronment folder and execute

cd build-enviroment
make

1 2	cd build-enviroment make

Now we modifiy the source dowload folder editing the site.conf file and changing the parameter as described below from

DL_DIR = "/home/sviluppo/enigma2/openatv/build-enviroment/sources"

1	DL_DIR = "/home/sviluppo/enigma2/openatv/build-enviroment/sources"

DL_DIR = "/home/sviluppo/enigma2/openatv/sources"

1	DL_DIR = "/home/sviluppo/enigma2/openatv/sources"

We are ready now to proceed to the image compilation.

From the build-envinronment to generate, for example, the image for Airdigital Zgemma H2H set-top box execute

MACHINE=zgemmah2h DISTRO=openatv  make image

1	MACHINE=zgemmah2h DISTRO=openatv make image

For the Xtrend ET10000 set-top box

MACHINE=et10000 DISTRO=openatv  make image

1	MACHINE=et10000 DISTRO=openatv make image

At the end of the process we’ll find the image ready to be uploaded on the set-top box in the deploy folder for each machine type; in the case of the Zgemma H2H the folder is

/home/sviluppo/enigma2/openatv/build-enviroment/builds/openatv/release/h3/tmp/deploy/images/h3/

1	/home/sviluppo/enigma2/openatv/build-enviroment/builds/openatv/release/h3/tmp/deploy/images/h3/

The zip file contains for the Zgemma H2H the file to be unzipped on the usb pen and uploaded on the device.

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.

Development, Software

Openelec compilation for Orange PI PC

2016-08-02 admin

In this article we describe how to proceed to compile the Openelec image for the Orange PI PC card.

From the Orange PI PC forum, in the Openelec section the developers describe the steps to compile the image

Openelec Orange PI PC FAQ

In previous blogs we described how to install debian and how to modify the script.bin file to adapt the hdmi output to our television

Debian installation

Output resolution change

The compilation takes a long time; it is advisable to use multicore processors to speed up the compilation process.

Create a folder, openelec, under orangepi folder and move into it

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

sviluppo@debian8:~/orangepi$ mkdir openelec

sviluppo@debian8:~/orangepi$ cd openelec

sviluppo@debian8:~/orangepi/openelec$

Install the following packages

sudo apt-get install device-tree-compiler

1	sudo apt-get install device-tree-compiler

With git download the github sources in the local OPENELEC-OPIPC folder

git clone -b openelec-7.0 --depth 1 https://github.com/jernejsk/OpenELEC-OPi2  OPENELEC-OPIPC

1	git clone -b openelec-7.0 --depth 1 https://github.com/jernejsk/OpenELEC-OPi2 OPENELEC-OPIPC

After the above operation access to OPENELEC-OPIPC folder

cd OPENELEC-OPIPC

1	cd OPENELEC-OPIPC

Execute the following command

PROJECT=H3 SYSTEM=opipc ARCH=arm make image

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

The process check prerequisities and installs additional packages

**** Your system lacks the following tools needed to build OpenELEC ****
gperf xsltproc /usr/include/ncurses.h
**** You seem to use a debian system ****
would you like to install the needed tools ? (y/n) y

**** Your system lacks the following tools needed to build OpenELEC ****

gperf xsltproc /usr/include/ncurses.h

**** You seem to use a debian system ****

would you like to install the needed tools ? (y/n) y

Insert the root password when required; after the prerequisites installation the compilation begins.

At the end of the compilation in the target folder we find the files to install or update Openelec

The file having the .img.gz extension is to upack and tranfer to a micro sd card as described in previous posts.
The file with .tar extension is to be copied in the update folder on the Openelec system; this file updates the system when rebooting the Orange PI PC card

Micro Devices

Tag Archives: firmware

Openelec addon building for Orange PI PC

Nodemcu Enduser_setup module lua sample(part2)

Nodemcu Enduser_setup module lua sample(part1)

Nodemcu compilation on Linux

Building OpenWrt firmware

Building Armbian image for Orange PI PC

OpenATV Enigma2 image compilation

Openelec compilation for Orange PI PC

Blog about embedded devices