Orange PI disappointment

This small SOC seamed pretty neat to me, when I decided to order it for the affordable 10$ it costs, because it’s specs looked promising, compared to a Raspberry PI.

I decided it would make an expendable alternative to it, thinking I could do the same things on both boards, and in the same way.

I was dead wrong:
This board comes with little to no documentation, and the promising website, links to a forum page, where information are dumped here and there, and there are a few links to images provided.
As always users community does the greatest part, but sadly it’s not enough:
Informations and software provided is at least one year old, and you can immediately tell, the good intentions of the programmers, have gone away because of the overwhelming job that has to be done, and without any sensitive feedback from the community, and a neglettable number of boards being sold, this Orange Pi turned out not to be a great success.

I grabbed an Orange Pi One, attracted by it’s price, and as soon as I got it, I downloaded some IMG and tried them immediately

Couldn’t get any of it to work, except for the Armbian one, which also appears to be heavily flawed.
dmesg shows an awful streak of errors for bad cpu_freq, and after searching for a fix, on the aforementioned confused forum, I managed to get rid of them.

For the other images, there are instructions about replacing the files in the FAT partiton, once you burn your IMG to SD card, that should be matching your hardware/expected configuration.
Somewhere is specified that Orange Pi One is compatible with the Orange Pi 2
(didn’t see that coming) and the PI 2 config files should be used.
Well, it’s not working, and I got bored and demotivated 4-5 pages through the random questions/statements, that usually make a forum thread.

So basically, don’t waste 10$ with a neglected board, lacking software and support, unless you can be the real game changer on it’s community driven development.

The above considerations, are just my opinions, and regarding specifically the Orange Pi One board, the compatibility and operability of the other more expensive siblings, may vary.

Here’s the forum post with all the distributions listed:
http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=342

and here’s a source of informations to run Armbian on them (the only Image I was able to use, but couldn’t do pretty much nothing with it)

http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=55&extra=&page=1

 

 

Annunci

Ili9488 Raspberry Pi

sudo nano /boot/cmdline.txt

Add the following lines to the kernel command line parameters (the end of the line)

fbcon=map:10 fbcon=font:VGA8x8 FRAMEBUFFER=/dev/fb1

Install the required fbdev drivers, and make the framebuffer entry for the X11 server

sudo apt-get install xserver-xorg-video-fbdev
sudo nano /usr/share/X11/xorg.conf.d/99-fbdev.conf
Section "Device"
Identifier "myfb"
Driver "fbdev"
Option "fbdev" "/dev/fb1"
EndSection

Now, for the real modules loading, create the first config file

sudo nano /etc/modules-load.d/fbtft.conf

Add these lines to it

spi-bcm2835
flexfb
fbtft_device

And the one containing the display parameters

sudo nano /etc/modprobe.d/fbtft.conf

Add these lines to it

options fbtft_device name=flexpfb rotate=180 fps=60 gpios=dc:18,reset:7,wr:17,cs:4,db00:22,db01:23,db02:24,db03:10,db04:25,db05:9,db06:11,db07:8
options flexfb width=400 height=320 buswidth=8 init=-1,0xb0,0x0,-1,0x11,-2,120,-1,0x3A,0x55,-1,0xC2,0x33,-1,0xC5,0x00,0x1E,0x80,-1,0x36,0x28,-1,0xB1,0xB0,-1,0xE0,0x00,0x04,0x0E,0x08,0x17,0x0A,0x40,0x79,0x4D,0x07,0x0E,0x0A,0x1A,0x1D,0x0F,-1,0xE1,0x00,0x1B,0x1F,0x02,0x10,0x05,0x32,0x34,0x43,0x02,0x0A,0x09,0x33,0x37,0x0F,-1,0x11,-1,0x29,-3

Your display should start up at this time, if not, perform a reboot.
To have the boot console on the display, run

con2fbmap 1 1

You can install fbcp, an utility to mirror framebuffers

sudo apt-get install cmake
git clone https://github.com/tasanakorn/rpi-fbcp
cd rpi-fbcp/
mkdir build
cd build/
cmake ..
make
sudo install fbcp /usr/local/bin/fbcp

To disable the console blanking timeout, edit

sudo nano /etc/kbd/config
BLANK_TIME=0

You can set custom fonts, and resize the framebuffer resolution this way:

 

sudo apt-get install kbd
sudo dpkg-reconfigure console-setup

sources:
http://appdictive.dk/blog/projects/2015/10/30/cheap_tft_display_on_raspberry_pi/

ILI9341 on Raspberry PI

sudo apt-get install x11vnc Xvfb -y && sudo x11vnc -storepasswd
#Set password for server
x11vnc -bg -nevershared -forever -tightfilexfer -usepw -display :0

 

What’s better than a small computer ?
A small computer with a small neat display, of course 🙂
Let’s wire the ILI9341 to our pi:

Test the module:

sudo modprobe fbtft_device custom \
name=fb_ili9341 gpios=reset:25,dc:24,led:18 \
speed=16000000 rotate=90 bgr=1

Pictures pending

sudo nano /boot/cmdline.txt
#add to the end:
fbcon=map:10
For using the small display with an X session:
sudo nano /usr/share/X11/xorg.conf.d/99-fbdev.conf
#add the following to the file
Section "Device"
Identifier "myfb"
Driver "fbdev"
Option "fbdev" "/dev/fb1"
EndSection

To start the session:

sudo FRAMEBUFFER=/dev/fb1 startx

 

sudo apt-get update -y
sudo apt-get upgrade -y
sudo apt-get install kbd xserver-xorg-video-fbdev -y
sudo dpkg-reconfigure console-setup

Choose a small font like Terminus6x12

sudo sh -c "TERM=linux setterm -blank 1 >/dev/tty0"

sudo nano /etc/kbd/config
#Edit and search for BLANK_TIME=30 and set it to BLANK_TIME=0
#Test you actually changed something
cat /sys/module/kernel/parameters/consoleblank
sudo nano /etc/X11/Xwrapper.config
# allowd_users from "console" to "anybody"
sudo nano /boot/config.txt
#uncomment hdmi_force_hotplug=1
#hdmi_group=2
#hdmi_mode=82

Raspberry Pi Samba share

Instructions to access a raspberry pi filesystem via samba (from any machine)

install the required packages:

sudo apt-get install samba samba-common-bin

when done, tweak the configuration accordingly

sudo nano /etc/samba/smb.conf

search for the following lines, and uncomment and edit to make them like this

workgroup = your_workgroup_name
wins support = yes

Then, at the end of the file, add the following

[pihome]
comment= Pi Home
path=/home/pi
browseable=Yes
writeable=Yes
only guest=no
create mask=0777
directory mask=0777
public=no

Save and exit
Set the access credential for user “pi” with the following command

smbpasswd -a pi