All posts by admin

DHT11 sensor reading on BeagleBone with node.js

2017-02-06 admin

In the previous article we read the temperature and humidity from DHT11 sensor in python

Temperature and humidity reading on Beaglebone in python

We perform now the same operation in javascript. We download the dht module for node.js. The module is available on the website

beaglebone dht

Log on BeagleBone in ssh as debian (temppwd as password) and run

sudo npm install -g mocha
sudo npm install -g chai
sudo npm install -g beaglebone-dht@0.0.3
sudo npm install -g beaglebone-dht --save

sudo npm install -g mocha

sudo npm install -g chai

sudo npm install -g beaglebone-dht@0.0.3

sudo npm install -g beaglebone-dht --save

to install the module globally.

For the sensor reading create a file test.js with the following code inside

var dht = require('/usr/local/lib/node_modules/beaglebone-dht'),
    sensor = dht.sensor('DHT11');
var i=0;

do {
        read=dht.read('P8_11');
        try {

                valore=read['humidity'];
                if(valore<=100.00&&valore>=0.0)  {

                        console.log(read);
                        break;
                        }
                }
        catch(err)  {
                        console.log("Error in sensor reading!");

                 }

        sleep(2000);

} while (i<15)

function sleep(milliseconds) {
  var start = new Date().getTime();
  for (var i = 0; i < 1e7; i++) {
    if ((new Date().getTime() - start) > milliseconds){
      break;
    }
  }
}

var dht = require('/usr/local/lib/node_modules/beaglebone-dht'),

sensor = dht.sensor('DHT11');

var i=0;

do {

read=dht.read('P8_11');

try {

valore=read['humidity'];

if(valore<=100.00&&valore>=0.0) {

console.log(read);

break;

}

catch(err) {

console.log("Error in sensor reading!");

}

sleep(2000);

} while (i<15)

function sleep(milliseconds) {

var start = new Date().getTime();

for (var i = 0; i < 1e7; i++) {

if ((new Date().getTime() - start) > milliseconds){

break;

}

Reading is performed running

sudo node test.js

1	sudo node test.js

The result in our case is the following

The same code can be run from Cloud9 IDE. Access the IDE on BeagleBone with the link http: //beaglebone.local:3000 and create a file named dht.js with the following code inside

var b = require('bonescript');
var dht = require('/usr/local/lib/node_modules/beaglebone-dht'),
    sensor = dht.sensor('DHT11');

var i=0;

do {
        read=dht.read('P8_11');
        try {

                valore=read['humidity'];
                if(valore<=100.00&&valore>=0.0)  {

                        console.log(read);
                        break;
                        }
                }
        catch(err)  {
                        console.log("Error in sensor reading!");

                 }

        sleep(2000);

} while (i<15)

function sleep(milliseconds) {
  var start = new Date().getTime();
  for (var i = 0; i < 1e7; i++) {
    if ((new Date().getTime() - start) > milliseconds){
      break;
    }
  }
}

var b = require('bonescript');

var dht = require('/usr/local/lib/node_modules/beaglebone-dht'),

sensor = dht.sensor('DHT11');

var i=0;

do {

read=dht.read('P8_11');

try {

valore=read['humidity'];

if(valore<=100.00&&valore>=0.0) {

console.log(read);

break;

}

catch(err) {

console.log("Error in sensor reading!");

}

sleep(2000);

} while (i<15)

function sleep(milliseconds) {

var start = new Date().getTime();

for (var i = 0; i < 1e7; i++) {

if ((new Date().getTime() - start) > milliseconds){

break;

}

The script execution gives the following result

Here is the link to download the two sample files

Node.js sample

Cloud9 sample

Development, Software

Temperature and humidity reading on Beaglebone in python

2017-02-02 admin

In the previous article we connected the DHT11 sensor to the Beaglebone

Sensors on Beaglebone

We install at this point the library in python and modules in c to read the sensor. The site with documentation about the library is

Adafruit Python DHT Sensor Library

mkdir temperature
cd temperature
git clone https://github.com/adafruit/Adafruit_Python_DHT.git

mkdir temperature

cd temperature

git clone https://github.com/adafruit/Adafruit_Python_DHT.git

Install the prerequisites

apt-get update
apt-get install build-essential python-dev

1 2	apt-get update apt-get install build-essential python-dev

Proceed to the installation of the library with the python command

cd Adafruit_Python
python setup.py install

1 2	cd Adafruit_Python python setup.py install

Enter the examples directory and do the following for reading the sensor values (dht 11 and pin P8_11)

cd examples
 ./AdafruitDHT.py 11 P8_11

1 2	cd examples ./AdafruitDHT.py 11 P8_11

The result in this case is the following

Development, Software

Sensors on Beaglebone

2017-02-02 admin

After describing the Beaglebone and its development tools

Startup of the Beaglebone development board

Development tools on Beaglebone

as an example we show how to interact with the Beaglebone and a temperature and humidity sensor.

Among the most popular we finde the DHT11 sensor. The sensor has 4 pin; we have to connnect it to the power supply through a resistance of 4.7 or 10 kΩ. In our case we have a three-pin DHT11 sensor with the resistance already included in the circuit. In the case of the only sensor follow as specified in the following article

DHT humidity sensor

The following image shows the connections with Beaglebone

In the article Development tools on Beaglebone we showed the Beaglebone headers; in this case we used 3.3V, ground and P8_11 headers.

In the next article we will install a library in python and modules in C to read temperature and humidity

Temperature and humidity reading on Beaglebone in python

Development, Software

Remote debug on Beaglebone

2017-01-25 admin

In the previous article we have prepared the environment with Eclipse for cross building for BeagleBone

Cross building for Beaglebone

Now we shall configure Eclipse and BeagleBone to debug the code directly on BeagleBone.

On BeagleBone install gdbserver

sudo apt-get install gdbserver

1	sudo apt-get install gdbserver

On the Debian system with Eclipse install gdb-multiarch

sudo apt-get install gdb-multiarch

1	sudo apt-get install gdb-multiarch

From Eclipse access to Run-> Debug Configurations

Double-click C++ Remote Application to set parameters

At the next window, create a new ssh connection with the New button

Enter the parameters for the connection

Set the remote destination folder for the file and execution management; with the browse button choose where to copy the files, and with the field “Commands to execute before application” will give execute permissions to the file

In our case we create a folder esempi under /root on the BeagleBone where to debug remotely

Set the multarch debugger in the Debugger Tab and other startup parameters and gdb command line settings

Set the port of the remote debug server installed on BeagleBone in the Gdbserver Settings Tab

Create .gdbinit files in the project folder with the command

To start debugging run the configuration we set

Eclipse connects with BeagleBone and performs remote debugging opening the Debug Perspective

Development, Software

Cross building for Beaglebone

2017-01-19 admin

In the article on the Debian environment we prepared the linux machine for the development of embedded systems

Debian development envinronment

In the article on building an image for the Orange PI PC we installed the cross build tools for armhf environment

Building Armbian for Orange PI PC

Starting from the clean image of the Debian envinronment we list the steps required to install the cross compiling environment. We log on Debian Desktop as sviluppo/ password.

As a preliminary step we install the cross toolchains in Debian

https://wiki.debian.org/CrossToolchains

Create the file crosstools.list in the /etc/apt/sources.list.d folder

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

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

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 key of the repository embedian.org

sudo apt-get install curl

1	sudo apt-get install curl

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 -

Install the following packages and add the armhf architecture

sudo dpkg --add-architecture armhf
sudo apt-get update
sudo apt-get install crossbuild-essential-armhf

sudo dpkg --add-architecture armhf

sudo apt-get update

sudo apt-get install crossbuild-essential-armhf

We install at this point the Eclipse IDE for Cpp downloading the IDE for Linux 64bit

Eclipse IDE

Unzip the eclipse package under / home /sviluppo.

Install the jre java

sudo vi /etc/apt/sources.list

1	sudo vi /etc/apt/sources.list

Add the line at the end of the file

# Backport Testing on stable
# JDK 8
deb http://ftp.de.debian.org/debian jessie-backports main

# Backport Testing on stable

# JDK 8

deb http://ftp.de.debian.org/debian jessie-backports main

Run the following commands

sudo apt-get update
sudo apt-get install openjdk-8-jre

1 2	sudo apt-get update sudo apt-get install openjdk-8-jre

Run Eclipse from the eclipse folder to start the IDE

As a first example we create a simple program in C for BeagleBone.

Create a new project in C, by inserting the following data

Select both configurations

Enter the cross compiler prefix and path

Press Finish.
Add to the project a source file in C

Insert the following simple code

#include <stdio.h>

int main()
   {
   printf("Hello, world.\n");
   return 0;
   }

#include <stdio.h>

int main()

{

printf("Hello, world.\n");

return 0;

}

Proceed with the build by selecting the project with the right mouse button and choosing Build Project

Transfer the generated files on BeagleBone. You can use scp or ftp.

Give execution permissions to the file and run it

chmod +x samplec
./samplec

1 2	chmod +x samplec ./samplec

The result is of course the text inserted in the code

Development, Software

Development tools on Beaglebone

2017-01-11 admin

In the previous article we have installed and updated to the latest Debian image our BeagleBone

Debian sd card setup for Beaglebone Black

We also enabled the network services to access the board using the hostname.

After these changes we can access the Beaglebone using the following address in the the browser

http: //beaglebone.local

The web interface presents several examples of code executed with bonescript, javascript library based on node.js framework

Node.js

You can perform these simple examples to begin to interact with the board. There are also links to the development tools such as Cloud9, Nodered and informations about these development tools

Clicking on Cloud9 we access at the section dedicated to this tool. It is shown how to create a simple example and to run at boot the code placing it into the autorun folder in the IDE interface. From this section we can access to the Cloud9 ide available on port 3000 of the Beaglebone site

For more information about the tool, refer to the site

Cloud9

Accessing to the Nodered section we find the link to the web page about the basic informations about Nodered

Getting stared with Nodered

and the link to the Nodered ide, running at 1880 port of the web server running on BeagleBone

Beaglebone Nodered

In the web page about the first steps for Nodered there are examples with which to start using the tool. From the web site https://nodered.org we can have more informations about the tool.

In addition to tools in javascript on BeagleBone there are C/C++ compilers, Python interpreter and the possibility to add additional development tools.

From the home page of the our BeagleBone board web interface, http: //beaglebone.local, we find the informations about all available headers and functions. The following image shows the expansion headers

In next articles we will show some code examples with the development board.

Installation, Software

Debian sd card setup for Beaglebone Black

2017-01-06 admin

In the previous article we started up the development board Beaglebone Black / Green.

Startup of the Beaglebone

Let’s look how to install an updated image of Debian for BeagleBone. As a first step we have to access the site which contains the Beaglebone images

Beaglebone images

We download, having a BeagleBone Black Rev. C, bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz. Unpack the 7zip image and load into a micro sd card with Win32DiskImager, as done for the Orange PI PC

SD card setup for Orange PI PC

If we wanted to load that image on the internal flash, we must edit the /boot/uEnv.txt files on a Linux system and uncomment the line

#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

1	#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

In that case, when we start the board the system will rewrite the operating system present on the internal flash with the version loaded on the micro sd card. We do not follow this road in order to do all the tests on the sd card leaving the internal partition unmodified. So let’s connect our Beaglebone to a network router. We insert the micro sd card and startup the development board. In some boards we need to press of the USER / BOOT button

because the operating system boots from micro sd card; with our board it is not necessary to perform this operation. We have to log on Beagleone now; the avahi-daemon service is already active on the Beaglebone and Linux systems resolve the address by hostname; Windows, instead, needs tha samba service activated to solve the Beaglebone hostname; installing samba we obtain the hostname recognition with the protocol netbios from Windows. If you are using a Windows machine to work with the Beagelbone you must first check the ip assigned by the network router to the BeagleBone. From a Linux system, for example, connect to the Beaglebone using ssh as debian / temppwd and the beaglebone hostname

ssh debian@beaglebone

1	ssh debian@beaglebone

In Windows we need to install the samba service first to have the same functionality. Proceed at this point with the updating and samba installation

sudo apt-get update
sudo apt-get install samba
sudo apt-get upgrade

sudo apt-get update

sudo apt-get install samba

sudo apt-get upgrade

After the updates and samba services activation, we are ready to show examples with our BeagleBone and we are able to connect to it using the beaglebone and beaglebone.local hostnames. In the next article we will see tools already available on the board and how to add more features.

We can install the ftp service too, as we could use it in next articles

sudo apt-get install vsftpd

1	sudo apt-get install vsftpd

To deactivate and activate it use the following commands

sudo systemctl disable vsftpd
sudo systemctl enable vsftpd

1 2	sudo systemctl disable vsftpd sudo systemctl enable vsftpd

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

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

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.

Micro Devices

All posts by admin

DHT11 sensor reading on BeagleBone with node.js

Temperature and humidity reading on Beaglebone in python

Sensors on Beaglebone

Remote debug on Beaglebone

Cross building for Beaglebone

Development tools on Beaglebone

Debian sd card setup for Beaglebone Black

Startup of the Beaglebone development board

Openelec addon building for Orange PI PC

Remote control configuration for Libreelec on Amlogic Socs

Blog about embedded devices