This README file contains information on building the meta-up-board BSP layer. Please see the corresponding sections below for details.
For more information on the UP board see: http://up-board.org
- Prerequisites
- Downloading the meta-up-board BSP layer
- Building your Yocto image for each UP machine
- Booting the live USB image
- Connecitvity firmware
- Additional Resources
- UP Board
- UP Squared
- UP Core
- UP Core Plus
- UP Xtreme
DEVELOPMENT: Supported hardware versions for Yocto 2.7 (warrior-dev) currenlty under development/testing
- UP Board
- UP Squared
- UP Core
- UP Core Plus
- UP Xtreme
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 meta-virtualization and openembedded-core for Docker containers:
git clone -b sumo git://git.yoctoproject.org/meta-virtualization
git clone -b sumo git://git.openembedded.org/openembedded-core
Download this UP Board BSP layer for Sumo:
git clone -b sumo https://github.com/emutex/meta-up-board
From the poky directory:
TEMPLATECONF=meta-up-board/conf source oe-init-build-env
MACHINE=up-board bitbake upboard-image-sato
From the poky directory:
TEMPLATECONF=meta-up-board/conf source oe-init-build-env
MACHINE=up-squared bitbake upboard-image-sato
From the poky directory:
TEMPLATECONF=meta-up-board/conf source oe-init-build-env
MACHINE=up-core bitbake upboard-image-sato
From the poky directory:
TEMPLATECONF=meta-up-board/conf source oe-init-build-env
MACHINE=up-core-plus 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').
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=core-image-sato-up-board.hddimg of=/dev/sdf
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/sdf bs=1M count=512
Ampak connectivity firmware is included to enable WiFi and Bluetooth for UPCorePlus boards.
Firmware will be included by defaults for building your image. If you don't want to include it, just edit conf/machine/up-board.conf file and disable "Ampak-firmware, SystemD and network tools" parameters.
Scan your available WiFi networks:
iwlist wlan0 scan
You will see all the WiFi interfaces in your area.
Check your Bluetooth devices in your area:
systemctl restart firmware-ampak-ap6355.service
rfkill unblock bluetooth
hciconfig hci0
hcitool scan
In addition to this README, please see the following URLs for details and additional documentation:
Please submit any patches against this BSP to the maintainer: Maintainer: Ubilinux Team ubilinux@emutex.com