From ea0075af9339839ec91a4075e4e016fd807c9868 Mon Sep 17 00:00:00 2001 From: Nitin A Kamble Date: Tue, 11 Dec 2012 10:29:48 -0800 Subject: meta-nuc: new BSP layer for Intel NUC systems MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This layer provides support for Intel NUC (Next Unit of Computing) systems. This BSP specifically targets the "Next Unit of Computing Kit DC3217IYE" containing the 3rd generation Intel® Core™ i3- 3217U (Ivy Bridge) processor and Intel Centrino Advanced-N 6235 Wireless mini PCI Express card. Signed-off-by: Nitin A Kamble Signed-off-by: Tom Zanussi --- meta-nuc/README | 149 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 meta-nuc/README (limited to 'meta-nuc/README') diff --git a/meta-nuc/README b/meta-nuc/README new file mode 100644 index 00000000..3b68609f --- /dev/null +++ b/meta-nuc/README @@ -0,0 +1,149 @@ +This README file contains information on building the meta-nuc +BSP layer, and booting the images contained in the /binary directory. +Please see the corresponding sections below for details. + +This BSP is made specifically for "Next Unit of Computing Kit DC3217IYE" +with Intel Centrino Advanced-N 6235 Wireless mini PCI Express card. + +Further information on this NUC platform can be found here: + + http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-boards-d33217gke-dc3217iye.html + +Information on all Intel® embedded platforms can be found here: + + http://www.intel.com/p/en_US/embedded/hwsw/hardware + + +Compliance +========== + +This BSP is compliant with the Yocto Project as per the requirements +listed here: + + http://www.yoctoproject.org/yocto-project-compatible-registration + + +Dependencies +============ + +This layer depends on: + + URI: git://git.openembedded.org/bitbake + branch: master + + URI: git://git.openembedded.org/openembedded-core + layers: meta + branch: master + + URI: git://git.yoctoproject.org/meta-intel + layers: intel + branch: master + + +Patches +======= + +Please submit any patches against this BSP to the Yocto mailing list +(yocto@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-nuc BSP layer + II. Booting the images in /binary + + +I. Building the meta-nuc 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 nuc +image by adding the location of the meta-nuc 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-nuc \ + +To enable the nuc layer, add the nuc MACHINE to local.conf: + + MACHINE ?= "nuc" + +You should then be able to build a nuc 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 'nuc' 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. + +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-nuc-20101207053738.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 -- cgit v1.2.3-54-g00ecf