Camelback Mountain BSP is supported by Intel Common Core BSP.
Building Common Core BSP layer for Camelback Mountain Intel® Xeon® Processor D-1500:
Please download the Poky build system to your development machine.
First create a directory:
$ mkdir ~/dev/yocto-git/
$ cd ~/dev/yocto-git/
$ git clone -b jethro git://git.yoctoproject.org/poky.git
Download the corresponding BSP tarball from the 'Board Support
Package (BSP) Downloads' page of the Yocto Project website.
Extract the downloaded BSP tarball
$ tar xvjf intel-corei7-64-4.0-jethro-2.0.tar.bz2
Rename the folder of the extracted BSP tarball to meta-intel. Ignore this step if there is already a folder with the same name.
$ mv intel-corei7-64-4.0-jethro-2.0 meta-intel
Create a build folder at the same level of "poky" directory.
$ mkdir yocto_build
$ cd yocto_build
Assuming that you have downloaded the BSP tarball and extracted the content at top level of your
development build tree, you need to prepare the build environment using the "source" command.
$ source ../poky/oe-init-build-env .
You can build an image for Camelback Mountain by adding the location of meta-intel layer to bblayers.conf, e.g.:
BBLAYERS ?= " \
To build a 64-bit image, add "intel-corei7-64" MACHINE to local.conf:
MACHINE = "intel-corei7-64"
And comment the existing variable:
#MACHINE ??= "qemux86"
Once the configurations are added, build an image as such:
$ bitbake core-image-sato
For building an image with the development tools, type the following command:
$ bitbake core-image-sato-sdk
A bootable image will be generated in yocto_build/tmp/deploy/images/intel-corei7-64/ once the compilation successful.
File name that will be generated:
Note: All prebuilt binaries utilize a time-limited kernel. Yocto Project users should build their own kernel image in their end product.
At the end of a successful build, you should have a live image that you can boot from a USB flash drive.
You can deploy the hddimg image to a USB or SATA device. You will need to know the device name on your host as well as the device name on the target. Be careful with this step as using the wrong host device can result in overwriting data on your own host machine.
Under Linux, USB and SATA devices typically appear as /dev/sdb, /dev/sdc, etc.
Watching your system messages as you connect the device will tell you exactly which device name
is assigned to the device. Let's assuming the USB flash drive takes device /dev/sdc, use dd to copy the live image to it. For example:
$ cd ~/dev/yocto-git/yocto_build/tmp/deploy/images/intel-corei7-64/
$ sudo dd if=core-image-sato-intel-corei7-64.hddimg of= /dev/sdc
$ eject /dev/sdc
Insert the device into the Camelback Mountain platform and power on, it should display a menu.
Before booting the platform, need to change the boot configuration, go to:
1. Boot Maintenance Manager
2. Boot Options
3. Change Boot Order
4. Change the order to:
• UEFI Internal Shell
• UEFI USB
5. Commit Changes and Exit
7. Once reset it should display shell terminal, reboot using UEFI Shell Commands:
Supported Boot Loader (BIOS version)
Features Supported in this Release:
• CPU PCIe Gen3
• PCH PCIe Gen2
• DDR4@2133 MHz
• SATA Gen3
• USB Gen 2 and Gen 3
• 2x 1GbE Network Interface
• The 10Gbe interface is not yet enabled but will be made available through the next Yocto Project release, trending end of Q2 2016.
• The Mini-USB/UART may not transmit properly for the following Processor Stepping:
CPUID: 00050662, Stepping: 2
Workaround: Use a PCIe/UART converter (Syba SY-PEX15034 is known to be working)
Note: This issue was fixed in new CPU stepping.
Please contact your Intel representative for more information.