💬 Building a Raspberry Pi Gateway

[marceloaqno]

@musthafa Yes, set the IP Address to 127.0.0.1 in your openhab for the ethernet gateway.

[hausinger]

@aand said:

@hausinger -- are you running armbian on your orange pi one?

Yes, I'm running on armbian on my orange pi one

[jirm]

@aand

Hi again!

I spend some time seeing and reading some of the files from the mysensors github build and I see some things that can help to understand why the error raised to @aand trying to compile on OPI.

First say that I´m not a coding expert, so please be nice with my if I´m wrong and say something stupid ;-)

I see in the .configure file that the machine detection have H3 Soc and this are fine detected , but then I see that selecting type and CPU flags seems not properly selected to match OPI specs , because on OPI soc H3 have a cpu armv7 (not armv8) and is a A20 and not A53.
So maybe that cpu "selection" is not correct for H3 soc , and is so easy try if anyone that have OPI and have time can change only that values in the config file and try to compile.
All the values on the A20 line seems correct for the OPI H3 soc, so only needed copy them from the A20 line to the H3 line, and give a try.

File Configure

.......

function gcc_cpu_flags {
local soc=$1
case $soc in
BCM2835)
flags="-march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard"
;;
BCM2836)
flags="-march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard"
;;
AM33XX)
flags="-march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=hard"
;;
A10)
flags="-march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=hard"
;;
A13)
flags="-march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=hard"
;;
A20)
flags="-march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard"
;;
H3)
flags="-march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard"
;;
*)

[musthafa]

@marceloaqno Thank you!

[eyesoft]

also on banana pi pro when i trie to compile i'm getting this :

[SECTION] Detecting target machine.
[OK] machine detected: SoC=A20, Type=unknown, CPU=armv7l.
[OK] init system detected: sysvinit
[SECTION] Saving configuration.
[SECTION] Cleaning previous builds.
[OK] Finished.

type i think must be BananaPro

on make :

-o build/examples_linux/mysgw.o
In file included from examples_linux/mysgw.cpp:74:0:
./MySensors.h:258:2: error: #error No support for nRF24 radio on this platform
#error No support for nRF24 radio on this platform
^
In file included from ./drivers/RF24/RF24.cpp:23:0,
from ./MySensors.h:294,
from examples_linux/mysgw.cpp:74:
./drivers/RF24/RF24.h:52:17: fatal error: SPI.h: No such file or directory
#include <SPI.h>
^
compilation terminated.
Makefile:98: recipe for target 'build/examples_linux/mysgw.o' failed
make: *** [build/examples_linux/mysgw.o] Error 1

so Banana Pi Pro soc A20 it's also on wait list or never worked ?

[jirm]

@eyesoft

Yes...I see. That error is that said @marceloaqno about own mysensors NRF24 drivers and SPI bus adapt for Raspberry, because for now mysensors is only supported at Raspi and arduinos.
On Banana CPU detection seems work better (I agree type seems not good...maybe you can change this on configure file and give a try to compile to see what happends) and I figure can work too on OPI too only changing that I said before, but then is raised NRF24 driver and SPI error.

I see that mysensors RF24 driver are derivated from that https://github.com/mz-fuzzy/RF24 build that at same time last this is forked directly from http://tmrh20.github.io/RF24Installer/RPi/install.sh that we know are working fine on OPI and armbian, so I figure that maybe it´s not so much hard to modify mysensors RF24 to adapt to work on OPI.

Hope any mysensors "coder" ear our call and cand give us some hand to make the changes on the mysensors build and we can compile the mysgw to OPI soon.

Cheers

[jirm]

@jirm

As a side coment, the configure file is on the root Mysensors directory that is buid when you complete the first step "git clone https://github.com/mysensors/MySensors.git" on the mysgw install process.

Anyone can edit the file with a plain text editor and change the values for see what happens when try compile.

Regards

[marceloaqno]

@jirm The configure script from MySensor repo is based on the https://github.com/TMRh20/RF24/blob/master/configure. Could you try with theTMRh20 master branch and post the result?

git clone https://github.com/TMRh20/RF24.git
cd RF24
./configure
make

[eyesoft]

@marceloaqno

git clone https://github.com/TMRh20/RF24.git
cd RF24
./configure
[SECTION] Detecting arm compilation environment.
[OK] arm-linux-gnueabihf-gcc detected.
[OK] arm-linux-gnueabihf-g++ detected.
[SECTION] Detecting target machine.
[OK] machine detected: SoC=A20, Type=unknown, CPU=armv7l.
[SECTION] Detecting DRIVER
[OK] DRIVER detected:SPIDEV.
[SECTION] Detecting OS.
[INFO] OS detected:LINUX.
[SECTION] Preparing configuration.
[SECTION] Saving configuration.
[SECTION] Cleaning previous builds.
[OK] Finished.

make
arm-linux-gnueabihf-g++ -fPIC -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -Ofast -Wall -pthread -c RF24.cpp
arm-linux-gnueabihf-g++ -fPIC -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -Ofast -Wall -pthread -c utility/SPIDEV/spi.cpp
arm-linux-gnueabihf-g++ -fPIC -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -Ofast -Wall -pthread -c utility/SPIDEV/gpio.cpp
arm-linux-gnueabihf-gcc -fPIC -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -Ofast -Wall -pthread -c utility/SPIDEV/compatibility.c
arm-linux-gnueabihf-g++ -fPIC -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -Ofast -Wall -pthread -c utility/SPIDEV/interrupt.c
[Linking]
arm-linux-gnueabihf-gcc -pthread -shared -Wl,-soname,librf24.so.1 -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -Ofast -Wall -pthread -o librf24.so.1.2.0 RF24.o spi.o gpio.o compatibility.o interrupt.o

[marceloaqno]

@Oli After these steps:

git clone https://github.com/mysensors/MySensors.git
cd MySensors

to switch to the master branch, run:

git checkout master

and reinstall the gateway following the same steps from the instructions.

[eyesoft]

@marceloaqno
i've tried on banana pi pro :

cat /etc/debian_version
8.6
cat /etc/bananian_platform
BananaPro

[marceloaqno]

@eyesoft thanks for the feedback, we need to add support for SPIDEV driver in order to use the BananaPi.

[jirm]

@marceloaqno Sadly I´m so much bussy and traveling for few days and cannot acces to my OPI´s :-( , but I´m sure someone here (@aand , @hausinger, etc.. ) can give a try on her OPI the things we said before. At least I hope this ...

[jirm]

@marceloaqno I see some huge steps up on BananaPi...seems only need add SPIDEV support for make it working... :-)

[Oli]

@marceloaqno I am rather copy/paste not a programming kind a guy, so sorry for my lame questions.

pi@raspberrypi ~ $ git clone https://github.com/mysensors/MySensors.git
fatal: destination path 'MySensors' already exists and is not an empty directory

pi@raspberrypi ~/MySensors $ git checkout master
Branch master set up to track remote branch master from origin.
Switched to a new branch 'master'

but after that:

pi@raspberrypi ~/MySensors $ make
make: *** No targets specified and no makefile found. Stop.
pi@raspberrypi ~/MySensors $ sudo make install
make: *** No rule to make target 'install'. Stop.

[eyesoft]

@Oli ... try :
./configure
make
sudo make install

[Oli]

@eyesoft same errors

[eyesoft]

@Oli see commands above how to Install and Build, with git checkout master you are on master if you :
cat README.md
MySensors Library v2.1.0

default on git clone you are on development :
cat README.md
MySensors Library v2.2.0-beta

[jirm]

@Oli First you need delete all Mysensors directory on your machine.
Then use step by step the guide on Mysensors Gateway installation process:
https://www.mysensors.org/build/raspberry
Dont forget put command sudo on sentences if needed.

Regards

[Oli]

I wanna update not to re install of MySensors. I thought about something like ./updaterelease or ./updatebeta... I spend hours of make it work before, so I leave it as it is. No time or nerves for fighting next couple of days.