Intel® Xeon® Processor D-1500

Board Info

Camelback Mountain
Processor: Intel x86-64
Organization: Intel Corporation


You can either clone with Git or download the tarball.

Clone with Git (preferred)

git:// -b 8.1-rocko-2.4.2


Built with: Yocto Project 2.4 – Rocko
Compatible with: Rocko 2.4.2
Release Date: April 2018
MD5 sum: 68cf8adbfb5e02f8605a39ee2184443c


You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein.
You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein.
No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.
All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmaps.
The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current
characterized errata are available on request.
Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548-4725 or by
Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Learn more
at or from the OEM or retailer.
No computer system can be absolutely secure.
Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.
*Other names and brands may be claimed as the property of others.
Copyright ©2018, Intel Corporation. All rights reserved.

Camelback Mountain is supported by Intel Common Core BSP.

Building Common Core BSP layer for Camelback Mountain Intel® Xeon® Processor D-1500:
Download the Poky build system to your development machine.
$ git clone -b rocko git://

Get the BSP layer either by cloning with Git or downloading the BSP tarball.

Option 1: git clone git:// -b 8.1-rocko-2.4.2

Option 2: Download the corresponding BSP tarball from this ‘Board Support Package (BSP) Downloads’ page of the Yocto Project website.

Extract the downloaded BSP tarball into meta-intel folder
$ tar -xvjf meta-intel-8.1-rocko-2.4.2.tar.bz2

Rename the folder of the extracted BSP tarball to meta-intel.
Note: Ignore this step if there is already a folder with the same name.
$ mv meta-intel-8.1-rocko-2.4.2 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 “source” command.
$ source ../poky/oe-init-build-env .

Build an image for Camelback Mountain by adding the location of meta-intel layer to conf/bblayers.conf, e.g.:
/path/poky/meta \
/path/poky/meta-poky \
/path/poky/meta-yocto-bsp \
/path/meta-intel \

To build 64-bit image, add “intel-corei7-64” MACHINE to local.conf:
MACHINE = “intel-corei7-64”

To build image with specified kernel version of linux-intel (Eg. linux-intel 4.14), add these parameters to local.conf:
PREFERRED_PROVIDER_virtual/kernel = “linux-intel”
PREFERRED_VERSION_linux-intel = “4.14%”

The kernel config for ixgbe module is bydefault disabled and need to enable manually to support 10GbE SFP+ Network Interface.
To compile ixgbe driver as module :
• Create file meta-intel/common/recipes-kernel/linux/linux-intel/ixgbe.cfg and add below kernel configs to file ixgbe.cfg:

• To include file “ixgbe.cfg”, add below line to kernel recipe file meta-intel/common/recipes-kernel/linux/
SRC_URI_append = ” file://ixgbe.cfg”

Once the configurations are added, kick start the image building process by using bitbake command.
To build an image with sato graphical interface :
$ 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:

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:
$ sudo dd if=core-image-sato-intel-corei7-64.hddimg of=/dev/sdc bs=4M
$ sync
$ 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
5. Commit Changes and Exit
6. Continue
7. Once reset it should display shell terminal, reboot using UEFI Shell Commands:
• fs0:\EFI\BOOT\bootx64.efi


Best Known Configuration:
Platform: Camelback Mountain
CPU: Intel® Xeon® Processor D-1500
PCH: PCH Revision: Lynxpoint SuperSku – C2 stepping
BIOS/Firmware Version: GNVDCRB1.86B.0089.R18.1706121603

Features Supported in this Release:
• CPU PCIe Gen3
• PCH PCIe Gen2
• DDR4@2133 MHz
• SATA Gen 2 and Gen 3
• USB Gen 2 and Gen 3
• 2x 1GbE Network Interface
• 2x 10GbE SFP+ Network Interface

Known Issues:
• 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.

• Ethernet NVM
The Ethernet ports may not function if the NVM is not yet programmed.
V1 stepping:
V2/Y0 stepping:
Both MAC NVM image and PHY NVM image must be programmed for a functional Ethernet, refer to the flash update guide in the package for details.