Tina Linux V1.0 version have public


(bpi team) #1

**About Tina-IoT Linux **

Dear user for BPI-M2 Ultra R40 Tina Linux V1.0 have public,Come and try Tina Linux development by Allwinner TinaTEAM, it base on OpenWrt,To build an embedded Linux distributions,The purpose of this release is to provide a quick learning and development is simple and convenient mass production Linux TurnKey solutions. The release of R40 Tina Linux is base on BPI-M2 Ultra reference hardware, that is, the source code download directly support banana pi BPI-M2 Ultra. R40 Tina Linux V1.0 version Base on Linux-3.10 and Tina Linux V2.1, it support a lot of fun and practical support functions:

1.support smartlink,(ultrasonic wave,airkiss,cooee)

2.support DLNA、QPlay Audio transmission and control protocol

Too much, not to speak one by one, in support of all hardware modules on BPI-M2 Ultra How to use R40 Tina Linux

Play Tina need a 64 - bit Linux PC, we recommend using Ubuntu 12.04 or 14.04 64 - bit version, installed with the following command to install the build environment depends on:

sudo apt-get install build-essential subversion git-core libncurses5-dev zlib1g-dev gawk flex quilt libssl-dev xsltproc libxml-parser-perl mercurial bzr ecj cvs unzip

You can refer to detailed OpenWrt’s WIKI

download source code

use repo tool to download this code , tool download method is as follows:

$ curl https://raw.githubusercontent.com/tinalinux/repo/stable/repo > ~/bin/repo
$ chmod +x ~/bin/repo

Then add “repo” to the environment variables, it is better to put the following sentences. Bashrc inside

$ export PATH=~/binPATH

Download the repo, the next download Tina’s source code, as follows:

$ repo init -u https://github.com/tinalinux/manifest -b r40-v1.y -m r40/v1.y.xml
$ repo sync
$ repo start r40-v1.y --all

after downloading the source code, execute the following commands in Tina with directory compiled:

$ source build/envsetup.sh
$ lunch azalea_m2ultra-tina
$ make -j4
$ pack [-d]

Tina SDK need to perform "source "and “lunch” commond before every compile,Then perform other operations.

pack command has a “-d” parameter,The function of the parameter is: do not add - d use the default uart0 as a serial port output, added - d use TF bayonet IO mouth group as uart0

**Burn image **

Tina image Packaging has about 15 M, and support directly burned to eMMC flash on BPI-M2 Ultra.

Burning method is as follows:

if you use Linux system,Direct use LiveSuit for flash. Method of use is as follows: 1.LiveSuit we place it at tina SDK tools/aw_tools dir

2.unzip LiveSuit 64bit version,run./LiveSuit.sh

3.LiveSuit will install at ~/Bin dir,use dpkg -i install aw driver,driver also at ~/Bin dir.

4.run LiveSuit,choose tina image

5.Hold the BPI-M2 Ultra uboot key, insert the usb ,you can begin burn image

if use Windows system ,plsase use burn tool : phoenixsuit

we place it at tools/aw_tools dir

** How to configuration Tina **

Tina firmware configuration, there are two commonly used commands:“make menuconfig” and “make kernel_menuconfig”.

These two commands must be in execution after "source " and “lunch” commond run finished ,

make menuconfig : Which software is used to configure the system use

make kernel_menuconfig:Used to configure the kernel options.


(bpi team) #2

TinaLinux source code on github:


#3

This is all based on kernel 3.10.65 or 3.4.39. Are you kidding? These kernels contain so many security flaws for which exploits exist in the wild that no one wants to use such outdated stuff on IoT devices.


(Oleg) #4

Hi, I’ve tried to build it under ubuntu 12.04 and 14.04 running them within Vagrant and following the instructions above. In both cases I stuck at $ pack [-d] step. It’s falling with this error ERROR: update_mbr failed

There is an error message in the output which may be related:

/home/vagrant/scripts/pack_img.sh: line 541: /home/vagrant/out/host/bin/fsbuild: No such file or directory

vagrant@vagrant-ubuntu-trusty-64:~$ ls -la /home/vagrant/out/host/bin/fsbuild -rwxr-xr-x 1 vagrant vagrant 39643 Dec 19 17:07 /home/vagrant/out/host/bin/fsbuild

so apparently file exists.

Any ideas how to fix it?