target is to use orange pi board to read vems data for realtime data over ser2net or dataloging trigger frame stream.
current board: Orange pi lite
OS Armbian Ubuntu Desktop : https://www.armbian.com/download/
to connect it to vems we need to have serial port on the board, it has some UARTS but they are ttl level, so we need some max232 interface.
using one like that : http://www.dx.com/p/rs232-to-ttl-serial-communications-module-w-indicator-blue-black-221240#.WVLg6GiGNdg
using UART3 to connect it: 
to get it working we need to change orange configuration in /boot, link how to do that : https://forum.armbian.com/index.php?/topic/1524-orange-pi-one-how-to-enable-uart/
best way to test it is to download minicom and try to capture some aim data from vems serial port, in my case i had to swap rx and tx wires on serial cable which connects between vems and raspberry. both ends of the cable are female gender.
at the moment I'm using orange to have wireless connection for the ecu on test bench using ser2net
config file is located in /etc/ser2net.conf and has line 4400:raw:1000:/dev/ttyS3:19200 8DATABITS NONE 1STOPBIT banner
Test simple built binary, linking and serial port
- wget http://svn.x-dsl.hu/del/orangepi_fat/orangepi_main
- chmod +x orangepi_main
- ./orangepi_main /dev/ttyS0 /dev/ttyUSB1 | tee /dev/shm/dummy
- It opens both specified serial ports at 19200 baud, and reads data received and prints to outputfile orangepi_main
- only a test: indistinguishable which input the data is coming from (please also see CPU consumption, eg. top; if success is reported, the working stm32 sources that query v3 via triggerframe and saves VemsTune compatible .vemslog file will be linked in).
- Binary built on xenial armhf (32bit) orangepi H3 pc-plus
- similar to orangepi-PC or zero or lite: zero or lite have builtin wifi, and might be perfect to log and send data over mobile-net.
- orangepi_main: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=c2f3c15e6c7d2d228dc4a638bb205d1ae6dd15c0, not stripped in hex
- ldd orangepi_main
- libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6eaa000)
- /lib/ld-linux-armhf.so.3 (0xb6f96000)
- might also run on 32bit armhf Debian jessie, or even buildroot, or possibly 32bit raspberry (not a target currently, devels use and have all kinds of orangepi-s but only 64 bit raspberry)
- easy to build on aarch64 orangepi pc2 if necessary (although gigabit ethernet is hardly necessary in a vehicle logger/network proxy device), and no other advantage apparently.