Building Intel Atom E3800 Processor Development Kit Yocto Project* Board Support Package (BSP)

Transcription

1 Building Intel Atom E3800 Processor Development Kit Yocto Project* Board Support Package (BSP) User Guide June 2014 Document Number: US

2 By using this document, in addition to any agreements you have with Intel, you accept the terms set forth below. 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. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined". Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information. The products described in this document 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. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling , or go to: Intel, Intel Atom, and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others. Copyright 2014, Intel Corporation. All rights reserved. User Guide June Document Number: US

3 Contents 1 Introduction Terminology Reference Documents Supported Platforms Building the Image for Valley Island Prerequisites Steps for Building the Image Step 1: Set Up the Build Environment for the Target BSP Step 2: Setup the Build Configuration Files bblayers.conf Step 3: Set Up the Build Configuration Files local.conf Step 4: Build an Image Step 5: Prepare the Bootable HDDIMG Image on a USB Mass Storage Device BIOS and Board Configuration Product features Known Issues for LPSS I/O Devices Figures Figure 1. Modifications to bblayers.conf... 9 Figure 2. Modification to Local Build Configuration File for Machine Type Tables Table 1. Table 2. Terminology... 5 Reference Documents... 6 Table 3. BIOS and Board Configuration June 2014 User Guide Document Number: US 3

4 Revision History Date Revision Description June Initial release User Guide June Document Number: US

5 Introduction 1 Introduction This document provides instructions for building the Yocto Project* Reference OS for the Intel Atom E3800 Processor Development Kit (formerly known as Valley Island) and contains the following information: Section 1: Introduction Section 2: Supported Platforms Section 3: Building the Image for Valley Island Yocto Project* Board Support Package (BSP) Section 4: BIOS and Board Configuration Section 5: Product features Section 6: Known Issues for LPSS I/O Devices For more information about Baytrail product info, refer to the EDC webpage at: Terminology Table 1. Terminology Term Description ACPI APIC BSP EDC FPGA KSC LPSS PCI PWM RTC SCC SUT Advanced Configuration and Power Interface Advanced Programmable Interrupt Controller Board Support Package Embedded Design Center Field Programmable Gate Array Keyboard System Controller Low Power Sub-System Peripheral Component Interconnect Pulse Width modulation Real Time Clock Storage Connecting Circuit System Under Test June 2014 User Guide Document Number: US 5

6 Introduction 1.2 Reference Documents Table 2. Reference Documents Document Document No./Location Yocto Project* Setup Getting Started Guide User Guide June Document Number: US

7 Supported Platforms 2 Supported Platforms The Yocto Project* Reference OS for Valley Island supports the following platforms: Bayley Bay Fab C (Green) Bakersport Fab A (Red) Valley Island Development Kit* Note: * Minimal test coverage (Boot test). June 2014 User Guide Document Number: US 7

8 Building the Image for Valley Island 3 Building the Image for Valley Island Yocto Project* Board Support Package (BSP) 3.1 Prerequisites Prior to building the image for Valley Island Yocto Project* Intel BSP, make sure that the environment setup is complete based on the steps in the Yocto Project* Setup Getting Started Guide (Document Number: ). 3.2 Steps for Building the Image Now that the Yocto Project* poky repo and meta-intel repo are ready in your build machine, follow the steps in this section closely. Intel recommends that you place your build folder at the same level as the poky directory. This shortens the grep and find command execution time when you explore the Yocto Project* recipe files Step 1: Set Up the Build Environment for the Target BSP Enter the following commands: $ cd ~/development/ $ mkdir build $ cd build $ source ~/development/poky/oe-init-build-env <bsp_name> The environment is set up and your shell prompt is moved to ~/development/build/<bsp-name>. Example: $ source ~/development/poky/oe-init-build-env valleyisland User Guide June Document Number: US

9 Building the Image for Valley Island Step 2: Setup the Build Configuration Files bblayers.conf Now you must link your build environment to the correct recipe folder. To do this, perform the following steps: 1. Modify the ~/development/build/<bsp-name>/conf/bblayers.conf file. $ vim ~/development/build/valleyisland/conf/bblayers.conf 2. Modify the bblayers.conf as shown Figure 1. Figure 1. Modifications to bblayers.conf Note: The path to meta-tlk ensures that the OS image you are building carries the timelimited-kernel feature. This means that the OS image will reboot itself every 10 days. The intention is to encourage customers to build their own production OS. If you do not want this feature, simply remove line-14 (see the following note). Note: /home/ilab/poky-daisy should be replaced with your build machine user s home directory, e.g. /home/<user>/development/poky. June 2014 User Guide Document Number: US 9

10 Building the Image for Valley Island Step 3: Set Up the Build Configuration Files local.conf Next, configure your local build configuration file (local.conf) so that it matches your target platform machine type. $ vim ~/development/build/valleyisland/conf/local.conf Specify the machine type to match your target platform. You can search for the offered machine type in the following meta-intel BSP directory structure: The machine type configuration file is at the following local within a BSP recipe: metaintel/meta-<bsp>/conf/machine/<machine-type>.conf. For example: meta-intel/meta-isg/meta-valleyisland/machine/ has the following machine type: valleyisland-32.conf valleyisland-64.conf Thus, to set the machine type for your local build configuration file, simply make the following change: Figure 2. Modification to Local Build Configuration File for Machine Type There are two types of MACHINE options for Valley Island BSP. For 32-bit system: valleyisland-32 For 64-bit system: valleyisland-64 User Guide June Document Number: US

11 Building the Image for Valley Island The meta-valleyisland contains support Intel High Definition Audio (Intel HD Audio). However, Intel HD Audio support is not turned on by default. The Intel HD Audio driver is dependent on gstreamer plugins and ffmpeg plugins to work properly. These gstreamer plugins require additional license flag settings to be included in the build. For Intel HD Audio support, add the following line in local.conf. LICENSE_FLAGS_WHITELIST = commercial Warning: By performing this step, you acknowledge that you are including a software package with a commercial license requirement. Yocto Project* does not grant any commercial licenses and it is the responsibility of the user to obtain the proper license Step 4: Build an Image There are a few images that you can build with an Intel BSP recipe and poky layers. These image types are located under the poky/meta/recipes-*/images/ folder. Additionally, some BSP recipes may have a specific image type defined under metaintel/meta-<bsp>/images/. The most frequently used image types are the following: core-image-sato = Image contains Sato mobile-style desktop core-image-sato-sdk = core-image-sato + SDK + development tool chain core-image-minimal = basic Linux* kernel with shell terminal only To build your choice of image, do the following: $ cd ~/development/build/valleyisland # Command: bitbake <image-type> $ bitbake core-image-sato OR OR $ bitbake core-image-sato-sdk $ bitbake core-image-minimal The above command initiates the image-build processes; where you see bitbake, the build system spawns multiple threads to fetch, configure, compile, install, and package each software ingredients. June 2014 User Guide Document Number: US 11

12 Building the Image for Valley Island At the end of the build, the bootable image with the file name <image-type>- <machine-type>.hddimg will be located at the following location for Yocto Project* version 1.5 and later: ~/development/build/<bsp-name>/tmp/deploy/images/<machinetype>/<image-type>-<machine-type>.hddimg Example: ~/development/build/crystalforest/tmp/deploy/images/valleyisla nd-32/core-image-sato-valleyisland-32.hddimg Step 5: Prepare the Bootable HDDIMG Image on a USB Mass Storage Device Note: The following steps are performed on the development machine used to build the Yocto Project* Intel BSP recipe as described in Section This BSP recipe contains (or builds) live images that must be converted to a partitioned image format to boot them on the supported platforms. To deploy the hddimg image on a USB or SATA device (boot-medium), you must know the device name on your host machine and the device name that is intended on the target platform. Warning: Be careful with this step as using the wrong host device path can result in overwriting data on your host machine. In Linux* distros, USB and SATA devices typically appear as /dev/sdb, /dev/sdc, etc. Watch your system messages as you connect the device to determine exactly which device name is assigned to the device. You can also use df to detect which is the device that is associated with the USB or SATA boot-medium. On the Valley Island platform, when the prepared boot-medium is attached, assuming only one storage device, typically your USB or SATA boot medium is /dev/sda. User Guide June Document Number: US

13 Building the Image for Valley Island There is a script under poky/scripts/contrib that can help install the HDDIMG into the USB stick. 1. Enter the following command lines: # Identify the device file for your USB thumb drive. $ df # To write the bootable image to USB thumb drive, we assume it is at /dev/sdc. # Unmount the the USB thumb drive first. $ umount /dev/sdc # Go to the scripts directory in poky. $ cd ~/development/poky/scripts/contrib/ # Command:./mkefidisk.sh <USB> <path/to/image> <target/rootfs> Example: $ sudo./mkefidisk.sh /dev/sdc core-image-sato-valleyisland- 32.hddimg /dev/sda 2. Finally, insert the USB thumb drive in your target platform USB slot and boot up the system. The BIOS or boot-loader should boot the image to the Sato desktop. Note: If your BIOS indicates that it cannot understand the bootable USB, it may mean that your USB thumb drive is corrupt. In this case, you must reformat the USB thumb drive as follow and redo the commands in this section: # This assumes the USB thumb drive is at /dev/sdc $ sudo dd if=/dev/zero of=/dev/sdc bs=1m count=512 June 2014 User Guide Document Number: US 13

14 BIOS and Board Configuration 4 BIOS and Board Configuration Table 3. BIOS and Board Configuration BIOS/FPGA/KSC Configuration Bayley Bay Fab C Bakersport Fab A PU Stepping BIOS version KSC Version General Settings LPSS and SCC configuration Intel HD Audio Configuration USB Configuration SATA Configuration Turn off Secure Boot B0 BYTICRB_IA32_R_SPI_0080_21_SeC_Enable.bin BYTICRB_X64_R_SPI_0080_21_SeC_Enable.bin ksc_v3_12.bin Device Manager > System Setup > Boot > Security Boot > Disable **IMPORTANT** The LPSS & SCC mode is PCI Mode by default in the BIOS setting. To enable PCI/ACPI mode: Device Manager > System Setup > South Cluster Configuration > LPSS & SCC Configuration > LPSS & SCC Devices Mode (select ACPI Mode or PCI Mode) The emmc controller v4.5 is enabled by default. To switch to emmc controller v4.41: Device Manager > System Setup > South Cluster Configuration > LPSS & SCC Configuration > SCC emmc Boot Controller > emmc4.41 Set Device Manager > System Setup > South Cluster Configuration > Audio Configuration > LPE Audio Support>Disable Set Device Manager > System Setup > South Cluster Configuration > Audio Configuration > Audio Controller >Enable To enable XHCI controller: Device Manager > System Setup > South Cluster Configuration > USB Configuration > EHCI Controller > Disable Device Manager > System Setup > South Cluster Configuration > USB Configuration > XHCI Controller > Enable Device Manager > System Setup > South Cluster Configuration > USB Configuration > XHCI Mode > Enable To enable USB Device (Bakersport ONLY): Device Manager > System Setup > South Cluster Configuration > USB Configuration >USB OTG Support > PCI Mode Device Manager > System Setup > South Cluster Configuration > USB Configuration >USB VBUS > OFF To enable AHCI mode: Device Manager > System Setup > South Cluster Configuration > SATA Drives > Chipset SATA Mode > AHCI User Guide June Document Number: US

15 BIOS and Board Configuration LPSS I/O Device Note: The I2C controller driver supports fast mode by default. To enable standard mode, append the arguments to the kernel command line. When the image is booted into a GRUB menu, press e to enable kernel command-line editing. Append the line at the end of linux/vmlinuz. "i2c-designware-pci.force_std_mode=1" (PCI mode) "i2c-designware-platform.force_std_mode=1" (ACPI mode) June 2014 User Guide Document Number: US 15

16 Product features 5 Product features This implementation supports the following features: Linux* Kernel version Intel s Open Source Integrated Graphics Driver for Linux* (i915) SATA (IDE, AHCI), USB Host Controller 2.0 and 3.0 USB device mode (Bakersport ONLY) emmc and SD Host Controller Intel HD Audio, GbE (Ethernet), APIC, RTC LPSS I/O devices - I2C Designware, SPI-PXA2XX, HSUART, SMBus i801, PWM (ACPI mode only) LPSS device enumeration in PCI mode and ACPI mode User Guide June Document Number: US

17 Known Issues for LPSS I/O Devices 6 Known Issues for LPSS I/O Devices Issue: HSUART When running PCI mode HSUART at baud rate 2M and above, you may receive a kernel message "serial8250: too much work for irq...". Generally, it will not disrupt the transfer and the data transfer will complete without data corruption. However, occasionally data transfer may halt when this kernel message appears. In this case: 1. Reopen the HSUART port. To do this, stop the current data transfer and close the terminal. 2. Then, open a new terminal and execute the data transfer again. Issue: SD Cards that supports DDR50 mode Due to the limitations in BIOS, not all SD cards that support DDR50 mode are supported by this BSP. June 2014 User Guide Document Number: US 17

18 Known Issues for LPSS I/O Devices User Guide June Document Number: US