Intel® 2nd Generation Core™ Platforms: Core i3, i5, i7 (Sandy Bridge)

Board Info

Sugar Bay
Processor Family: Intel x86-64
Organization: Intel Corporation

Download

Built with: Yocto Project 1.7 – Dizzy
Compatible with: Dizzy 1.7.x
Release Date: 12/01/2014
MD5 sum: 83de2e9c492a25777a13e187e394e9ed

Clone with Git (preferred)

git://git.yoctoproject.org/meta-intel -b dizzy

Release Notes

The ‘Sugar Bay’ platform consists of the Intel Sandy Bridge processor,
plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This
BSP assumes that the Sandy Bridge integrated graphics are being used.

Further information on the platforms supported by this BSP can be
found here:

http://www.intel.com/p/en_US/embedded/hwsw/hardware/core-q67-b65/overview

And information on all Intel® embedded platforms can be found here:

http://www.intel.com/p/en_US/embedded/hwsw/hardware

Yocto Project Compatible
========================

This BSP is compatible with the Yocto Project as per the requirements
listed here:

https://caffelli-staging.yoctoproject.org/webform/yocto-project-compatible-registration

Dependencies
============

This layer depends on:

URI: git://git.openembedded.org/bitbake
branch: 1.24

URI: git://git.openembedded.org/openembedded-core
layers: meta
branch: dizzy

URI: git://git.yoctoproject.org/meta-intel
layers: intel
branch: dizzy

Patches
=======

Please submit any patches against this BSP to the meta-intel mailing list
(meta-intel@yoctoproject.org) and cc: the maintainer:

Maintainer: Nitin A Kamble

Please see the meta-intel/MAINTAINERS file for more details.

Table of Contents
=================

I. Building the meta-sugarbay BSP layer
II. Booting the images in /binary

I. Building the meta-sugarbay BSP layer
=======================================

In order to build an image with BSP support for a given release, you
need to download the corresponding BSP tarball from the ‘Board Support
Package (BSP) Downloads’ page of the Yocto Project website.

Having done that, and assuming you extracted the BSP tarball contents
at the top-level of your yocto build tree, you can build a sugarbay
image by adding the location of the meta-sugarbay layer to
bblayers.conf, along with the meta-intel layer itself (to access
common metadata shared between BSPs) e.g.:

yocto/meta-intel \
yocto/meta-intel/meta-sugarbay \

To enable the sugarbay layer, add the sugarbay MACHINE to local.conf:

MACHINE ?= “sugarbay”

You should then be able to build a sugarbay image as such:

$ source oe-init-build-env
$ bitbake core-image-sato

At the end of a successful 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 images from /binary’).

NOTE: The ‘sugarbay’ machine will include support for hardware video
acceleration via gstreamer if and only if the “commercial” string is
added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.

For example:

LICENSE_FLAGS_WHITELIST = “commercial”

The reason this is needed is to prevent the image from including
anything that might violate the license terms of the packages used to
implement the the video acceleration feature, such as gst-ffmpeg and
ffmpeg. As always, please consult the licenses included in the
specific packages for details if you use packages that require
particular LICENSE_FLAGS.

The xf86-video-intel recipe depends on Xorg’s dri and glx modules,
which are built only when ‘opengl’ is listed in DISTRO_FEATURES. So
if the distro doesn’t list ‘opengl’ in the DISTRO_FEATURES, then you
would need this additional line in your local.conf:

DISTRO_FEATURES_append = ” opengl”

As an alternative to downloading the BSP tarball, you can also work
directly from the meta-intel git repository. For each BSP in the
‘meta-intel’ repository, there are multiple branches, one
corresponding to each major release starting with ‘laverne’ (0.90), in
addition to the latest code which tracks the current master (note that
not all BSPs are present in every release). Instead of extracting a
BSP tarball at the top level of your yocto build tree, you can
equivalently check out the appropriate branch from the meta-intel
repository at the same location.

II. Booting the images in /binary
=================================

This BSP contains bootable live images, which can be used to directly
boot Yocto off of a USB flash drive.

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-sugarbay.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. 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