Difference between revisions of "Yocto-based"

From UpWiki
Jump to: navigation, search
(Undo revision 591 by Carlos.calderon (talk))
Line 143: Line 143:
  
 
After some seconds, the board should reboot as expected.
 
After some seconds, the board should reboot as expected.
 +
 +
== Yocto based image for UP based systems and boards ==
 +
 +
=== UP Squared ===
 +
 +
Linux OS Image based on Yocto 2.5 sumo and meta-layer support for UP Squared from:
 +
 +
Highlights:
 +
 +
Linux Kernel 4.14 for UP Squared
 +
Sato image, includes basic GUI
 +
Container support, includes docker, docker-compose
 +
 +
[https://downloads.up-community.org/download/yocto-2-5-sumo-evaluation-image-for-up-squared/ Yocto 2.5 Sumo evaluation image for UP Squared]

Revision as of 08:11, 14 June 2019

Install Yocto 2.5 for UP family boards

Supported Yocto versions

  • Yocto 2.3 (Pyro)
  • Yocto 2.5 (Sumo)

Supported hardware versions

  • UP Board
  • UP Squared
  • UP Core
  • UP Core Plus

Prerequisites

  • an UP, UP2 or UP Core board
  • an USB stick with at least 1Gb of space
  • keyboard, mouse, a screen and an Internet connection

Installation

Download the latest Sumo release and enter the poky directory:

git clone -b sumo git://git.yoctoproject.org/poky.git
cd poky

Download the latest Intel BSP layer version for Sumo:

git clone -b sumo git://git.yoctoproject.org/meta-intel.git

Download the latest collection of layers for OE-core universe for Sumo:

git clone -b sumo git://git.openembedded.org/meta-openembedded 

Download this UP Board BSP layer for Sumo:

NOTE:

Due to an issue with Linux-Intel kernel for Cherry Trail SoCs, the layer must be separated for each kernel version:

For UP board and UP Core (Cherry Trail SoCs):

git clone -b meta-up-board-yocto-2.5-linux-yocto https://github.com/emutex/meta-up-board

For UP Squared and UP Core Plus (Apollo Lake SoCs):

git clone -b meta-up-board-yocto-2.5-linux-intel https://github.com/emutex/meta-up-board

Building your Yocto image for each UP machine

UP Board:

From the poky directory:

TEMPLATECONF=meta-up-board/conf source oe-init-build-env
bitbake upboard-image-sato

UP Squared Board:

From the poky directory:

TEMPLATECONF=meta-up-board/conf source oe-init-build-env
bitbake upboard-image-sato

UP Core Board:

From the meta-up-board directory:

sudo nano conf/machine/up-board.conf

Uncomment required file for up-core boards to enable all features:

require conf/machine/include/up-core.inc

Then, from the poky directory:

TEMPLATECONF=meta-up-board/conf source oe-init-build-env
bitbake upboard-image-sato


UP Core Plus Board:

From the meta-up-board directory:

sudo nano conf/machine/up-board.conf

Uncomment required file for up-core-plus boards to enable all features:

require conf/machine/include/up-core-plus.inc

Then, from the poky directory:

TEMPLATECONF=meta-up-board/conf source oe-init-build-env
bitbake upboard-image-sato

At the end of a successfull build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section 'Booting the live USB image').

Booting the live USB image

This BSP creates bootable live images, which can be used to directly boot Yocto off of a USB flash drive. Upon completion of a successful build, described in the previous section, the images are created in a sub-folder named ./tmp/deploy/images/up-board/

Under Linux, insert a USB flash drive. Assuming the USB flash drive takes device /dev/sdf, use dd to copy the live image to it. For example:

dd if=upboard-image-sato-up-board.hddimg of=/dev/sdb
sync
eject /dev/sdf

This should give you a bootable USB flash device. Insert the device into a bootable USB socket on the target, and power on. At the initial BIOS splash screen, press F7 to display a menu of boot options and select the USB device. This should result in a system booted to the Sato graphical desktop.

If you want a terminal, use the arrows at the top of the UI to move to different pages of available applications, one of which is named 'Terminal'. Clicking that should give you a root terminal.

If you want to ssh into the system, you can use the root terminal to ifconfig the IP address and use that to ssh in. The root password is empty, so to log in type 'root' for the user name and hit 'Enter' at the Password prompt: and you should be in.

If you find you're getting corrupt images on the USB (it doesn't show the syslinux boot: prompt, or the boot: prompt contains strange characters), try doing this first:

dd if=/dev/zero of=/dev/sdb bs=1M count=512

Connectivity firmware

Ampak connectivity firmware is included to enable WiFi and Bluetooth for UP Core and UP Core Plus boards.

  • WiFi

Scan your available WiFi networks:

iwlist wlan0 scan

You will see all the WiFi interfaces in your area.

  • Bluetooth

Check your Bluetooth devices in your area:

For UP Core active the Ampak AP6214 service:

systemctl restart firmware-ampak-ap6355.service

For UP Core Plus active the Ampak AP6355 service:

systemctl restart firmware-ampak-ap6355.service

Unblock your Bluetooth device and check your available devices:

rfkill unblock bluetooth
hciconfig hci0
hcitool scan

Active iTCO Watchdog

You only need to write to the watchdog device and it will be active.

cat >> /dev/watchdog

After some seconds, the board should reboot as expected.

Yocto based image for UP based systems and boards

UP Squared

Linux OS Image based on Yocto 2.5 sumo and meta-layer support for UP Squared from:

Highlights:

Linux Kernel 4.14 for UP Squared Sato image, includes basic GUI Container support, includes docker, docker-compose

Yocto 2.5 Sumo evaluation image for UP Squared