Category Archives: Configuration

MQTT with BeagleBone and ESP8266 – Mosquitto installation on Beaglebone

2017-03-12 admin

After summarizing the architecture that we are implementing in the previous article

Mqtt with Beaglebone and ESP8266-Architecture

We proceed now with the installation of the MQTT broker on Beaglebone Black with the following version of Debian

root@beaglebone:~#  cat /etc/dogtag
BeagleBoard.org Debian Image 2016-11-06
root@beaglebone:~# uname -a
Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Lux

root@beaglebone:~# cat /etc/dogtag

BeagleBoard.org Debian Image 2016-11-06

root@beaglebone:~# uname -a

Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Lux

The image used is the following

Beaglebone Black Image

We proceed to the configuration as described in the article

Debian sd card setup for Beaglebone Black

Proceed to extend the space on the SD card with the application gparted in a linux host or using the grow_partition.sh tool on BeagleBone in the /opt/scripts/tools folder

root@beaglebone:/opt/scripts/tools# ./grow_partition.sh

1	root@beaglebone:/opt/scripts/tools# ./grow_partition.sh

Performing the upgrade with this image we have had space issue with 4Gb partition.

The message broker we’ll use is mosquitto

Mosquitto

The version of Mosquitto with Debian Jessie doesn’t not have the Wesockets services, which we’ll use for the Dashboard. For this reason, we have to install a more recent version of Mosquitto (or recompile it from source).

Log on as root in a command shell on BeagleBone and add the Debian testing repository

cd /etc/apt
vi sources.list

1 2	cd /etc/apt vi sources.list

deb http://httpredir.debian.org/debian stretch main contrib non-free

1	deb http://httpredir.debian.org/debian stretch main contrib non-free

Run the following

apt-get update
apt-get install mosquitto
apt-get install mosquitto-clients

apt-get update

apt-get install mosquitto

apt-get install mosquitto-clients

After the installation comment the reference of the debian testing repository in /etc/apt/sources.list

#deb http://httpredir.debian.org/debian stretch main contrib non-free

1	#deb http://httpredir.debian.org/debian stretch main contrib non-free

and run

apt-get update

1	apt-get update

We test at this point if the server is installed correctly by running in a shell the subscription to a topic

mosquitto_sub -h localhost -t "topic/test"

1	mosquitto_sub -h localhost -t "topic/test"

In another command shell run the publishing on topic “topic / test”

mosquitto_pub -h localhost -t "topic/test" -m "Prova"

1	mosquitto_pub -h localhost -t "topic/test" -m "Prova"

The first shell has to show the message “Prova”

With MQTT protocol we can define different QOS, as described in the Mosquitto FAQ

QOS Mosquitto

With QoS = 0 the message is sent only once and is not required confirmation of receipt by the subscribers; the MQTT implementation in these articles is without protection with name/password or ssl channel encryption and with QOS=0.

In the next article we’ll proceed to the preparation of ESP9266 module with the Mqtt lua library inside the nodemcu firmware

MQTT with BeagleBone and ESP8266-MQTT ESP8266

Configuration, Software

Mqtt with Beaglebone and Esp8266-Architecture

2017-03-12 admin

In this series of articles we treat a MQTT message broker installed on BeagleBone Black; this componet allows to manage various esp8266 devices, to which we connect various probes such as temperaure sensors, relays.

All this is handled with the help of apps on Android and a Dashboard installed on Apache on BeagleBone.

We start from the message MQTT broker (Message Queue Telemetry Transport); here there is the description of the protocol

MQTT

In particular in the FAQ section there are the first indications on the protocol and its use

MQTT Faq

The system is formed by three components:

MQTT Broker: relays the messages published to all subscribers.
Publisher: Publish messages in the registered topics on MQTT Broker.
Subscriber: Receives messages for its registered topics from MQTT Broker.

The following shows the topology for two topics used in our example

The system is composed of a MQTT broker on BeagleBone. In this MQTT broker server you can define topics; different devices can be registered to these topics. For each topic the action can be subscription and publishing. By subscribing you receive all messages of topics, while with the publishing we can perform actions on the topic (for example, turn on a relay, restart a device, send sensor measurement,etc.). In the example we treat there will be, for example, a queue for the temperature monitor, hooked to esp8266 temperature reading device, another for the management of a relay, always run with esp8266. The MQTT broker relays the received messages among all subscribers/ publishers for each topic.

We can subcribe/publish to the topics on the MQTT broker using Android apps; the apps can receive messages and send commands to the esp8266 end device (Turn onRelay, Restart sensor, etc.).

With the javascript framework Freeboard

Freeboard

installed on the Beablebone Apache web server we can monitor in real time the end devices.

For more informations on MQTT system, consult the web site listed above.

In the next article we’ll start by installing the MQTT broker on BeagleBone Black

MQTT with BeagleBone and ESP8266 – Mosquitto installation on Beaglebone

Configuration, Software

Generating Images for BeagleBone with Omap Image Builder

2017-02-26 admin

This article describes how to proceed to the autonomous creation of an image for the BeagleBone Black /Green using the Omap Image Builder. In this specific example we create the image for the BeagleBone Black Rev. C.

The informations on the procedure to be followed are available on the site

Omap image builder

As a prerequisite to the creation of the image there is the need to perform the operations on arm hardware; with other systems it is possible to have issues. To this end, we will proceed to perform tasks on a Orange PI PC with Armbian operating system. After preparing the Armbian system for Orange PI PC, as described in

Armbian Boot on Orange PI PC

It is possible also to connect by enabling Remote Desktop

Remote desktop setup for Armbian on Orange PI PC

Create a folder named beaglebone

mkdir beaglebone
cd beaglebone

1 2	mkdir beaglebone cd beaglebone

Clone the code to create the image

git clone git://github.com/beagleboard/image-builder.git

1	git clone git://github.com/beagleboard/image-builder.git

The folder tree is the following

image-builder
├── configs
├── docs
├── emacs
├── machinekit
├── publish
├── scripts
├── target
│   ├── boot
│   ├── chroot
│   ├── init_scripts
│   ├── keyring
│   └── other
└── tools
    └── hwpack

image-builder

├── configs

├── docs

├── emacs

├── machinekit

├── publish

├── scripts

├── target

│ ├── boot

│ ├── chroot

│ ├── init_scripts

│ ├── keyring

│ └── other

└── tools

└── hwpack

We proceed first to the creation of a standard Debian 8 image for Beaglebone Black

cd image-builder
sudo ./beagleboard.org_jessie_image.sh

1 2	cd image-builder sudo ./beagleboard.org_jessie_image.sh

The task takes a long time and creates other folders including the deploy folder within which we will find the images. At the end go into deploy /image folder and run

sudo ./setup_sdcard.sh --img-4gb BBB-debian-8.6-lxqt-aaaa-mm-dd --dtb beaglebone --enable-systemd --boot_label BEAGLEBONE --bbb-old-bootloader-in-emmc --hostname beaglebone

1	sudo ./setup_sdcard.sh --img-4gb BBB-debian-8.6-lxqt-aaaa-mm-dd --dtb beaglebone --enable-systemd --boot_label BEAGLEBONE --bbb-old-bootloader-in-emmc --hostname beaglebone

Compress the created image with the command

sudo xz -z -8 -v BBB-debian-8.6-lxqt-aaaa-mm-dd-4gb.img

1	sudo xz -z -8 -v BBB-debian-8.6-lxqt-aaaa-mm-dd-4gb.img

To create a customized image proceed as follows:

Go into the image-builder/configs folder and copy a configuration as base named custom-debian.conf. We have used as a base configuration bb.org-debian-jessie-lxqt-4gb-v4.1.conf. In custom-debian.conf add the following changes in the deb_include section; as example we add the vsftpd server; change the chroot_script value too

deb_include=="   \         alsa-utils      \ ....... xserver-xorg-video-modesetting \         vsftpd \ "

1
2
3
4
5
6
7

deb_include=="   \
        alsa-utils      \
.......

xserver-xorg-video-modesetting \
        vsftpd \
"

chroot_script="custom-debian.sh"

1

chroot_script="custom-debian.sh"

To exclude packages to be installed use the deb_exclude section. In the script are commented the various sections, among which we find those about the definition of the hostname, passwords, user name creation, etc.
Navigate to the image-builder/target/chroot folder and copy beagleboard.org-jessie.sh as custom-debian.sh.
If you want to add python packages edit the custom-debian.sh file and add the other packages in install_pip_pkgs function

install_pip_pkgs () {
        if [ -f /usr/bin/python ] ; then
                wget https://bootstrap.pypa.io/get-pip.py || true
                if [ -f get-pip.py ] ; then
                        python get-pip.py
                        rm -f get-pip.py || true

                        if [ -f /usr/local/bin/pip ] ; then
                                echo "Installing pip packages"
                                #Fixed in git, however not pushed to pip yet...(use git and install)
                                #libpython2.7-dev
                                #pip install Adafruit_BBIO

                                git_repo="https://github.com/adafruit/adafruit-beaglebone-io-python.git"
                                git_target_dir="/opt/source/adafruit-beaglebone-io-python"
                                git_clone
                                if [ -f ${git_target_dir}/.git/config ] ; then
                                        cd ${git_target_dir}/
                                        python setup.py install
                                fi
                                pip install --upgrade PyBBIO
                                pip install iw_parse
#Add other python packages here
                        fi
                fi
        fi
}

install_pip_pkgs () {

if [ -f /usr/bin/python ] ; then

wget https://bootstrap.pypa.io/get-pip.py || true

if [ -f get-pip.py ] ; then

python get-pip.py

rm -f get-pip.py || true

if [ -f /usr/local/bin/pip ] ; then

echo "Installing pip packages"

#Fixed in git, however not pushed to pip yet...(use git and install)

#libpython2.7-dev

#pip install Adafruit_BBIO

git_repo="https://github.com/adafruit/adafruit-beaglebone-io-python.git"

git_target_dir="/opt/source/adafruit-beaglebone-io-python"

git_clone

if [ -f ${git_target_dir}/.git/config ] ; then

cd ${git_target_dir}/

python setup.py install

pip install --upgrade PyBBIO

pip install iw_parse

#Add other python packages here

}

In this example we added only the ftp server. Go into the image-builder folder and run the command

sudo ./RootStock-NG.sh -c custom-debian

1	sudo ./RootStock-NG.sh -c custom-debian

The task takes a long time. At the end access to the deploy/imagename folder and run

sudo ./setup_sdcard.sh --img-4gb BBB-custom-debian-8.6-aaa-mm-dd --dtb beaglebone --enable-systemd --boot_label BEAGLEBONE --bbb-old-bootloader-in-emmc --hostname beagleboneblack

1	sudo ./setup_sdcard.sh --img-4gb BBB-custom-debian-8.6-aaa-mm-dd --dtb beaglebone --enable-systemd --boot_label BEAGLEBONE --bbb-old-bootloader-in-emmc --hostname beagleboneblack

Compress the created image with the command

sudo xz -z -8 -v BBB-custom-debian-8.6-aaa-mm-dd-4gb.img

1	sudo xz -z -8 -v BBB-custom-debian-8.6-aaa-mm-dd-4gb.img

You can create now the micro sd card with the FTP server available in the image and the hostname changed in beagleboneblack.

The microSD burning is already described in the article

Debian sdcard setup for Beaglebone Black

On Omap image builder site you’ll find other images types among which we highlight those for BeagleBone Black, Green, Iot, Machine Kit (image to manage Machinekit CNC machines), etc.

Configuration, Software

Startup of the Beaglebone development board

2016-12-28 admin

In a previous article we have given a brief description of Beaglebone Black board and its variants.

Beaglebone development board

The BeagleBone in this review comes with 4GB of space on board, and with the operating system already installed.

We can access the BeagleBone, in our case the Black, without using the Ethernet network, but connecting it to a PC through the mini service USB connection as specified on the BeagleBone site

Getting started with Beaglebone

After connecting the BeagleBone Black to the PC via the USB cable we find another removable device to the existing disks

Running start.htm we start an interface similar to the one available on the getting-started web site

We proceed to the installation of network-over-USB drivers for the operating system, Windows 64-bit in our case

Proceed to download the file and run it, providing the permissions required by Windows

At the end the window with the performed operations is shown

Using Firefox or Chrome we access to the following address http://192.168.7.2; we access in this way to the web server, running on Beaglebone board, through network over USB

The page shows how to update the system, login to the IDECloud9, perform various Bonescript examples.

The access to the Cloud9 IDE

Cloud9 IDE Informations

takes place on port 3000 to the IP address specified above, ie http://192.168.7.2:3000

In our examples, we will not change the operating system present on the internal eMMC card but we will download an updated version of Debian for BeagleBone and will install it on a micro sd card.

The system can be closed using the Power button on board

or by connecting via ssh at 192.168.7.2 address with the debian user ,using temppwd as password, and executing the command “sudo poweroff”

In the next article we will proceed to download and install on a micro sd card the last Debian image for BeagleBone

Debian sd card setup for Beaglebone Black

Configuration, Software

Remote control configuration for Libreelec on Amlogic Socs

2016-12-12 admin

In the previous article we installed on a microsd card Libreelec and started the device with this image

Libreelec Image for Amlogic socs

The remote control of the Beelink Minimx III is basic, so to have more keys we decided to associate another remote control to the box.

We chose the following remote control that has more buttons included

According to this document on Amlogic site, although prepared in Chinese, through the use of online translators

How to change IR codes

It shows that the soc Amlogic natively manages the NEC protocol for remote controls and through remote.conf file we can associate the remote control code to the Linux system events. The map of the codes for the Linux system events is available in the header files of the Linux kernel

Input Event Codes

As a first step we log on Libreelec in ssh with root/libreelec. Copy the /etc/amremote/libreelec.conf file as remote.conf in /storage/.config folder

cp /etc/amremote/libreelec.conf /storage/.config/remote.conf

1	cp /etc/amremote/libreelec.conf /storage/.config/remote.conf

and edit it as follows

#*********************************************************************************************************
#this file is configuration for each factory remote device
#     work_mode      0 :software mode  1 :hardware mode 
#    repeat_enable      0 :disable repeat 1 :enable repeat    
#
#    factory_code      each device has it's unique factory code. 
#              pattern:custom_code(16bit)+index_code(16bit)
#              examble: 0xff000001 = 0xff00(custom cod)  0001 (index)
#
#    release_delay      unit:ms.release will report from kernel to user layer after this period of time
#              from press or repeat triggered. 
#
#    debug_enable      0 :debug disable  1 :debug disable
#
# SW MODE:
#    bit_count      how many bits in each frame      
#    tw_leader_act      time window for leader active 
#    tw_bit0          time window for bit0 time.
#    tw_bit1          time window for bit1 time
#    tw_repeat_leader  time window for repeat leader
# REG
#    reg_base_gen      set value for PREG_IR_DEC_BASE_GEN    
#    reg_control      set value for PREG_IR_DEC_CONTROL
#    reg_leader_act      set value for PREG_IR_DEC_LEADER_ACTIVE
#    reg_leader_idle      set value for PREG_IR_DEC_LEADER_IDLE
#    reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE
#    reg_bit0_time      set value for PREG_IR_DEC_BIT0_TIME
#************************************************************************************************************* 
#amlogic NEC remote

#factory_code    = 0x00680001
work_mode       = 0
repeat_enable   = 1
release_delay   = 150
debug_enable    = 1
#reg_control     = 0xfbe40

#*********************************************************************************************************

#this file is configuration for each factory remote device

# work_mode 0 :software mode 1 :hardware mode

# repeat_enable 0 :disable repeat 1 :enable repeat

# factory_code each device has it's unique factory code.

# pattern:custom_code(16bit)+index_code(16bit)

# examble: 0xff000001 = 0xff00(custom cod) 0001 (index)

# release_delay unit:ms.release will report from kernel to user layer after this period of time

# from press or repeat triggered.

# debug_enable 0 :debug disable 1 :debug disable

# SW MODE:

# bit_count how many bits in each frame

# tw_leader_act time window for leader active

# tw_bit0 time window for bit0 time.

# tw_bit1 time window for bit1 time

# tw_repeat_leader time window for repeat leader

# REG

# reg_base_gen set value for PREG_IR_DEC_BASE_GEN

# reg_control set value for PREG_IR_DEC_CONTROL

# reg_leader_act set value for PREG_IR_DEC_LEADER_ACTIVE

# reg_leader_idle set value for PREG_IR_DEC_LEADER_IDLE

# reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE

# reg_bit0_time set value for PREG_IR_DEC_BIT0_TIME

#*************************************************************************************************************

#amlogic NEC remote

#factory_code = 0x00680001

work_mode = 0

repeat_enable = 1

release_delay = 150

debug_enable = 1

#reg_control = 0xfbe40

Load the new codes of the remote file with the command

remotecfg /storage/.config/remote.conf

1	remotecfg /storage/.config/remote.conf

Press some button of the new remote control and run

dmesg -c

dmesg -c

In the case of compatible remote control we should see messages as shown below

remote: Wrong custom code is 0xae517f80

1	remote: Wrong custom code is 0xae517f80

The format is as follows: 0xAABBCCCC. Following Amlogic document linked above, the remote control code for a specific key is 0xBB; while defining the remote control code we have to use 0xCCCC0001. AA corresponds to the inverse logic of the command. In the case of the above example

BB = 0x51 = 01010001 in binary. The logical inverse = 10101110 in binary, which is just 0xAE.

AA = 0xAE. Binary = 10101110

The AA code is not used for our remote control configuration.

Press all the buttons on remote control and run the dmesg -c command. In our case we have the following codes

[  563.475708@0] remote: Wrong custom code is 0xae517f80
[  564.273258@0] remote: Wrong custom code is 0xb24d7f80
[  565.096453@0] remote: Wrong custom code is 0xf6097f80
[  565.805424@0] remote: Wrong custom code is 0xee117f80
[  566.450804@0] remote: Wrong custom code is 0xab547f80
[  567.118602@0] remote: Wrong custom code is 0xb04f7f80
[  567.963741@0] remote: Wrong custom code is 0xa9567f80
[  568.631341@0] remote: Wrong custom code is 0x42bd7f80
[  569.321289@0] remote: Wrong custom code is 0x44bb7f80
[  570.077504@0] remote: Wrong custom code is 0xb14e7f80
[  570.953170@0] remote: Wrong custom code is 0xac537f80
[  571.665000@0] remote: Wrong custom code is 0xe41b7f80
[  572.354812@0] remote: Wrong custom code is 0xd9267f80
[  573.163774@0] remote: Wrong custom code is 0xda257f80
[  573.853329@0] remote: Wrong custom code is 0xf20d7f80
[  574.520600@0] remote: Wrong custom code is 0xd8277f80
[  575.210029@0] remote: Wrong custom code is 0xd7287f80
[  575.988176@0] remote: Wrong custom code is 0xb6497f80
[  576.633419@0] remote: Wrong custom code is 0xad527f80
[  577.189905@0] remote: Wrong custom code is 0xce317f80
[  577.834915@0] remote: Wrong custom code is 0xcd327f80
[  578.391382@0] remote: Wrong custom code is 0xcc337f80
[  578.881274@0] remote: Wrong custom code is 0xcb347f80
[  579.482089@0] remote: Wrong custom code is 0xca357f80
[  580.060612@0] remote: Wrong custom code is 0xc9367f80
[  580.550538@0] remote: Wrong custom code is 0xc8377f80
[  581.195652@0] remote: Wrong custom code is 0xc7387f80
[  581.730036@0] remote: Wrong custom code is 0xc6397f80
[  582.242330@0] remote: Wrong custom code is 0xa7587f80
[  582.865319@0] remote: Wrong custom code is 0xcf307f80
[  583.554914@0] remote: Wrong custom code is 0xbb447f80

[ 563.475708@0] remote: Wrong custom code is 0xae517f80

[ 564.273258@0] remote: Wrong custom code is 0xb24d7f80

[ 565.096453@0] remote: Wrong custom code is 0xf6097f80

[ 565.805424@0] remote: Wrong custom code is 0xee117f80

[ 566.450804@0] remote: Wrong custom code is 0xab547f80

[ 567.118602@0] remote: Wrong custom code is 0xb04f7f80

[ 567.963741@0] remote: Wrong custom code is 0xa9567f80

[ 568.631341@0] remote: Wrong custom code is 0x42bd7f80

[ 569.321289@0] remote: Wrong custom code is 0x44bb7f80

[ 570.077504@0] remote: Wrong custom code is 0xb14e7f80

[ 570.953170@0] remote: Wrong custom code is 0xac537f80

[ 571.665000@0] remote: Wrong custom code is 0xe41b7f80

[ 572.354812@0] remote: Wrong custom code is 0xd9267f80

[ 573.163774@0] remote: Wrong custom code is 0xda257f80

[ 573.853329@0] remote: Wrong custom code is 0xf20d7f80

[ 574.520600@0] remote: Wrong custom code is 0xd8277f80

[ 575.210029@0] remote: Wrong custom code is 0xd7287f80

[ 575.988176@0] remote: Wrong custom code is 0xb6497f80

[ 576.633419@0] remote: Wrong custom code is 0xad527f80

[ 577.189905@0] remote: Wrong custom code is 0xce317f80

[ 577.834915@0] remote: Wrong custom code is 0xcd327f80

[ 578.391382@0] remote: Wrong custom code is 0xcc337f80

[ 578.881274@0] remote: Wrong custom code is 0xcb347f80

[ 579.482089@0] remote: Wrong custom code is 0xca357f80

[ 580.060612@0] remote: Wrong custom code is 0xc9367f80

[ 580.550538@0] remote: Wrong custom code is 0xc8377f80

[ 581.195652@0] remote: Wrong custom code is 0xc7387f80

[ 581.730036@0] remote: Wrong custom code is 0xc6397f80

[ 582.242330@0] remote: Wrong custom code is 0xa7587f80

[ 582.865319@0] remote: Wrong custom code is 0xcf307f80

[ 583.554914@0] remote: Wrong custom code is 0xbb447f80

The mapping of the remote control in kodi is in the /usr/share/kodi/system/keymaps/remote.xml file.

We mapped the remote control codes to the Linux input events. As an example let’s consider the Power button. The remote control code is

0x51

0x51

The KEY_POWER event in the input-event-codes.h file is

116

116

We created a link between the remote control code and the event in Linux in the key_begin, key_end section of the remote.conf file

key_begin
    0x51 116        #Poweroff KEY_POWER
key_end

key_begin

0x51 116 #Poweroff KEY_POWER

key_end

Between the two data

0x51 116

0x51 116

insert a space, as indicated in Amlogic document linked above . The file used in this case is available at the following link

remote.conf

At the restart of the box Libreleelc reads the new configuration in /storage/.config/remote.conf allowing so the use of the new remote control.

Configuration, Software

Remote desktop setup for Armbian on Orange PI PC

2016-08-11 admin

To enable the remote desktop for Armbian on Orange PI PC execute the logon to the system, for example using an ssh client

Delete, if installed, the packages

sudo apt-get purge vnc4server
sudo apt-get purge  tightvnc
sudo apt-get purge xrdp

sudo apt-get purge vnc4server

sudo apt-get purge tightvnc

sudo apt-get purge xrdp

Install the following packages

sudo apt-get install tightvncserver
sudo apt-get install xrdp

1 2	sudo apt-get install tightvncserver sudo apt-get install xrdp

Now we are able to login on Armbian using the remote desktop. Start the remote desktop client entering the Orange PI PC IP address

Execute the login with the user created at the first boot of Armbian, for example user1

We now have the access to the XFCE desktop remotely

Configuration, Software

Armbian Boot on Orange PI PC

2016-08-11 admin

After the creation of the micro sd card with the Armbian image for Orange PI PC

Armbian image on micro sd

we can boot the Orange PI PC with the card inserted in the card slot. At the boot the first operation is the partition increase on the card, then the system requires the root password change from the default, 1234, to a new password. The next operation is the creation of a normal Debian user, for example user1; we provide the main required informations like username, password and letting the default for the other fields. After these steps the system opens the XFCE graphical interface with the default resolution. To change the resolution execute the following command

sudo dh3disp

1	sudo dh3disp

It shows a list with all the available options; to enable a 1080p60 resolution execute

sudo h3disp -m 10

1	sudo h3disp -m 10

To change the locales configuration execute the following command choosing the language to use

sudo dpkg-reconfigure locales

1	sudo dpkg-reconfigure locales

while to modify the keyboard layout use the following command

sudo dpkg-reconfigure keyboard-configuration

1	sudo dpkg-reconfigure keyboard-configuration

Configuration, Software

Resolution change of the video output in Openelec on Orange PI PC (Part2)

2016-07-29 admin

After the installation and compilation of the sunxi tools we are able to manage the script.bin file

http://www.microdev.it/wp/en/2016/07/29/resolution-change-of-the-video-output-in-openelec-on-orange-pi-pc-part1/

Copy into scriptfile folder our script.bin file.

From th sunxi link it is possible to view the guide about the parameters of the fex file

Fex Guide

Using the tool, compiled in part1 article, let’s convert the file from binary into a text one, executing the following command

sviluppo@debian8:~/orangepi/sunxi/scriptfile$ bin2fex ./script.bin ./script.fex
fexc-bin: ./script.bin: version: 0.1.2
fexc-bin: ./script.bin: size: 34080 (73 sections)
sviluppo@debian8:~/orangepi/sunxi/scriptfile$ ls
script.bin  script.fex

sviluppo@debian8:~/orangepi/sunxi/scriptfile$ bin2fex ./script.bin ./script.fex

fexc-bin: ./script.bin: version: 0.1.2

fexc-bin: ./script.bin: size: 34080 (73 sections)

sviluppo@debian8:~/orangepi/sunxi/scriptfile$ ls

script.bin script.fex

Now we can work on the script.fex file. Edit it with a text tool software, for example pluma in Debian

In this file we have to find the parameters to modify the video output; here are the parameters to modify

screen0_output_type
screen1_output_type
screen0_output_mode
screen1_output_mode

screen0_output_type

screen1_output_type

screen0_output_mode

screen1_output_mode

In our test file we found the following settings

screen0_output_type = 3
screen0_output_mode = 10
screen1_output_type = 0
screen1_output_mode = 0

screen0_output_type = 3

screen0_output_mode = 10

screen1_output_type = 0

screen1_output_mode = 0

According to the fex guide, for the HDMI output (screen_output_type=3) and a setting of 720p60 we have to change the 10 value into 5 in the screen0_output_mode parameter

screen0_output_type = 3
screen0_output_mode = 5
screen1_output_type = 0
screen1_output_mode = 0

screen0_output_type = 3

screen0_output_mode = 5

screen1_output_type = 0

screen1_output_mode = 0

WARNING: This file contains all the main parameters for the correct operation of the card. Don’t change anything if you are not sure waht the change of parameters entails.

After the parameters change convert the text file into a binary format with the following command, generating a .bin file

sviluppo@debian8:~/orangepi/sunxi/scriptfile$ fex2bin ./script.fex ./script720p60.bin

1	sviluppo@debian8:~/orangepi/sunxi/scriptfile$ fex2bin ./script.fex ./script720p60.bin

Move this file into the micro sd card; rename the original script.bin file into script.bin.back and move the script720p60.bin into script.bin.

In the Fex Guide we find all the parameters settings according to the various output resolutions.

Inserting the sd card into the Orange PI PC we can test the new output resolution connecting the hdmi to our television and powering on the card.

Configuration, Software

Resolution change of the video output in Openelec on Orange PI PC (Part1)

2016-07-29 admin

In the Orange PI Openelec image the default video output resolution is 1080p60. If our tv works with a different resolution we’ll have no image on the television.

To overcome this problem it is possible to change the resolution and fps for the video output.

The micro sd has two partitions. We have to work in the vfat partition

We have to modify the script.bin file.

In the home partition of the debian user (sviluppo in our case) create a folder orangepi; inside this folder create another folder called sunxi. Go into sunxi folder

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

sviluppo@debian8:~$ mkdir orangepi

sviluppo@debian8:~$ cd orangepi/

sviluppo@debian8:~/orangepi$ mkdir sunxi

sviluppo@debian8:~$ cd sunxi/

Follow the instructions available from linux-sunxi site in order to modify the script.bin file. As first step install the required tools

Sunxi Tools

We have to install the libusb package, as described below

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

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

Install git and pkg-config

sudo apt-get install git
sudo apt.get install pkg-config

1 2	sudo apt-get install git sudo apt.get install pkg-config

Now using git download the tool sources

git clone https://github.com/linux-sunxi/sunxi-tools

1	git clone https://github.com/linux-sunxi/sunxi-tools

Go into sunxi.tools folder

sviluppo@debian8:~/orangepi/sunxi$ cd sunxi-tools/

1	sviluppo@debian8:~/orangepi/sunxi$ cd sunxi-tools/

Execute the tools compilation

make

make

We are now able to modify the Orange PI PC parameters available in the script.bin file.

Create a folder under sunxi, for example scriptfile

sviluppo@debian8:~/orangepi/sunxi$ mkdir scriptfile

1	sviluppo@debian8:~/orangepi/sunxi$ mkdir scriptfile

Add to th ePATH variable the sunxi tools folders executables

sviluppo@debian8:~/orangepi/sunxi$ cd scriptfile

1	sviluppo@debian8:~/orangepi/sunxi$ cd scriptfile

export PATH=$PATH:~/orangepi/sunxi/sunxi-tools

1	export PATH=$PATH:~/orangepi/sunxi/sunxi-tools

Now in next article we can modify the parameters of video output in the script.bin file

http://www.microdev.it/wp/en/2016/07/29/resolution-change-of-the-video-output-in-openelec-on-orange-pi-pc-part2/

Configuration, Development, Installation, Software

Debian envinronment for embedded systems development

2016-07-13 admin

In this article we describe Debian 8.5 installation we’ll use to compile Openelec for Orange Pi PC, Enigma2 images and other operations for embedded devices.

Download AMD64 Debian 8.5 iso

Debian X86_64

Proceed with the operating system installation on your system. It is recommended to use a virtual machine like VirtualBox. Use at least 4 GB of ram and 50 GB of hard disk.

VirtualBox

Using VirtualBox it is possible the virtual disk creation with dynamic space allocation. After the operating system installation log on into the system with the user created during the installation; we used the “sviluppo” user id. It is possible to log on to the linux system using the graphical interface or through ssh to the IP address of the Debian system.

Add to sudo group the user created in the Debian installation; open a shell command window and execute

id

In our case we have the following output

sviluppo@debian8:~$ id
uid=1000(sviluppo) gid=1000(sviluppo) groups=1000(sviluppo),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),108(netdev),115(bluetooth),118(lpadmin),119(scanner)

1 2	sviluppo@debian8:~$ id uid=1000(sviluppo) gid=1000(sviluppo) groups=1000(sviluppo),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),108(netdev),115(bluetooth),118(lpadmin),119(scanner)

sviluppo user doesn’t belong to sudo group. Execute the command

su -

su -

Enter the root password when required and execute

root@debian8:~# adduser user sudo

1	root@debian8:~# adduser user sudo

In our example

root@debian8:~# adduser sviluppo sudo

1	root@debian8:~# adduser sviluppo sudo

Reboot the system

root@debian8:~# reboot

1	root@debian8:~# reboot

At the reboot log on into Debian and proceed to add the packages repositories, if not already present. Go to the /etc/apt folder

cd /etc/apt

1	cd /etc/apt

Backup the original file

sudo cp sources.list sources.list.back

1	sudo cp sources.list sources.list.back

Edit the file using for example the vi editor

sudo vi sources.list

1	sudo vi sources.list

It is possible to comment out the lines positioning at the beginning of the line, press i to go in editing mode and add the # character. Pressing the ESC key we go into reading mode and it is possible to move in the file using the arrow keys. In case of errors in editing mode it is possible to avoid the last change using the key ESC+u.

Comment out the lines

#deb http://security.debian.org/ jessie/updates main contrib
#deb-src http://security.debian.org/ jessie/updates main contrib

1 2	#deb http://security.debian.org/ jessie/updates main contrib #deb-src http://security.debian.org/ jessie/updates main contrib

Add the following lines

deb http://httpredir.debian.org/debian jessie main contrib non-free
deb-src http://httpredir.debian.org/debian jessie main contrib non-free

deb http://httpredir.debian.org/debian jessie-updates main contrib non-free
deb-src http://httpredir.debian.org/debian jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free

deb http://httpredir.debian.org/debian jessie main contrib non-free

deb-src http://httpredir.debian.org/debian jessie main contrib non-free

deb http://httpredir.debian.org/debian jessie-updates main contrib non-free

deb-src http://httpredir.debian.org/debian jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free

deb-src http://security.debian.org/ jessie/updates main contrib non-free

To add the lines press o keys to go into writing mode with an empty new line; with copy and paste we can add all the lines or proceed manually for each of them.

To save the file and quit press ESC+:wq.

It is possible to use one of the text editors available in Desktop Envinroment on which we logged into to edit and save the file. For example to use pluma editor open a shell command windows and execute

xhost +
sudo pluma

1 2	xhost + sudo pluma

From pluma open the file /etc/apt/sources.list, make the changes described above and save the file.

Update the repository lists and the packages

sudo apt-get update
sudo apt-get upgrade

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

Install the development packages

sudo apt-get install dpkg-dev

1	sudo apt-get install dpkg-dev

Install an ftp server to use for files transfer

sudo apt-get install vsftpd

1	sudo apt-get install vsftpd

After the installation open the file /etc/vsftpd.conf and uncomment the following parameter

#write_enable=YES

1	#write_enable=YES

Open the file with vi or pluma as superuser

sudo vi /etc/vsftpd.conf

1	sudo vi /etc/vsftpd.conf

With vi editor search the string with the command

/write_enable

1	/write_enable

Delete the # character positioning the cursor on it and pressing the x key.

write_enable=YES

1	write_enable=YES

Save and quit with ESC+:wq.

Restart the ftp server using the command

sudo service vsftpd restart

1	sudo service vsftpd restart

We have now the envinronment to compile, modify, develop our embedded systems.

Micro Devices

Category Archives: Configuration

MQTT with BeagleBone and ESP8266 – Mosquitto installation on Beaglebone

Mqtt with Beaglebone and Esp8266-Architecture

Generating Images for BeagleBone with Omap Image Builder

Startup of the Beaglebone development board

Remote control configuration for Libreelec on Amlogic Socs

Remote desktop setup for Armbian on Orange PI PC

Armbian Boot on Orange PI PC

Resolution change of the video output in Openelec on Orange PI PC (Part2)

Resolution change of the video output in Openelec on Orange PI PC (Part1)

Debian envinronment for embedded systems development

Blog about embedded devices