BPI-R2 OpenHab development

BPI-R2 OpenHab development .

hennersHenry Smith10h

I got this working in the end.

Basically you need to enable the GPIO by amending the appropriate dts files in the kernel code ( https://github.com/BPI-SINOVOIP/BPI-R2-bsp ) and setting the uart entries to “status=okay”

detalled here:

http://fw-web.de/dokuwiki/doku.php?id=en:bpi-r2:gpio

Then compile the kernel (in a VM or whereever) and ship it over to the BPI-R2 SD card.

The good news is there is two other options:

frank-w has got pre compiled kernels here, I used 4.4.108. https://drive.google.com/drive/folders/15Y5Y3NAOwg_IMmN3k6hdb7pAQj9oTVTl . just copy over the BPI-BOOT and the BPI-ROOT over to the appropriate partition mounted on other machine as root!

If you prefer 4.14 with uart/gpio enabled in preconfgiured debian images, frank-w has done those too:

https://drive.google.com/open?id=15Y5Y3NAOwg_IMmN3k6hdb7pAQj9oTVTl

After than just follow the install. use /dev/ttyS2 . make sure setenv and openhab/default have the appropriate entries.

Make sure openhab is added to the tty group.

Sort java out etc…

Good to go - it works well.

Henry

more please see the discuss:

when using official 4.4.70 the missing nodes must be added first to mt7623.dtsi (like described in my wiki), only “status=okay” will fail. these uart-nodes must be added AFTER uart2 else the debug-console will not work after kernel is loaded because kernel uses ttyS0 for debug-Output (you can change that, but it’s safer to add device nodes as described for compatibility)

my kernels have enabled uart0-2, the razberry-board uses uart1. if only uart1 is activated the console-port is ttyS1

btw. actual kernel versions (4.4.112 and 4.14.14) are uploaded…

1 Like