diff options
Diffstat (limited to 'meta-crystalforest')
-rw-r--r-- | meta-crystalforest/README | 100 |
1 files changed, 62 insertions, 38 deletions
diff --git a/meta-crystalforest/README b/meta-crystalforest/README index 210df563..2053a3c2 100644 --- a/meta-crystalforest/README +++ b/meta-crystalforest/README | |||
@@ -2,34 +2,38 @@ This README file contains information on building the meta-crystalforest | |||
2 | BSP layer, and booting the images contained in the /binary directory. | 2 | BSP layer, and booting the images contained in the /binary directory. |
3 | Please see the corresponding sections below for details. | 3 | Please see the corresponding sections below for details. |
4 | 4 | ||
5 | The 'Crystal Forest' platform consists of two versions. | 5 | Overview of Intel Communication Product Offering |
6 | 1. GLADDEN | 6 | ------------------------------------------------ |
7 | 2. SERVER | ||
8 | 7 | ||
9 | The Gladden Platform consists of Intel Xeon E3-1125C/E3-1105C Processor, | 8 | The following platforms are supported on meta-intel dizzy branch ONLY: |
10 | plus the Intel Communication Chipset 89xx for Smaller Form Factor | ||
11 | Communication Infrastructure. | ||
12 | (Gladden + Cave Creek) also known as CrystalForest-Gladden | ||
13 | 9 | ||
14 | The Server Platform consists of Intel Xeon E5-2600 and E5-2400 Processors, | 10 | Crystal Forest/Server - Shumway reference platform configurations: |
15 | plus the Intel Communication Chipset 89xx for Large-Scale Communications | 11 | processor: Intel Xeon E5-2600/E5-2400 (Sandy Bridge-based) or |
16 | Infrastructure. | 12 | Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based) |
17 | (Ivy Bridge-EP/EN + Coleto Creek) also known as HighlandForest | 13 | chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek) |
18 | (Sandy Bridge-EP/EN + Cave Creek) also known as CrystalForest-Server | 14 | url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview |
19 | 15 | ||
20 | Both Platforms use Matrox graphics Card. | 16 | Crystal Forest/Gladden - Stargo reference platform configurations: |
17 | processor: Intel Xeon E3-1125C/E3-1105C (Sandy Bridge-based) or | ||
18 | Intel Xeon E3-1125v2/E3-1105v2 (Ivy Bridge-based) | ||
19 | chipset: Intel Communication Chipset 8900-8920 Series (Cave Creek) | ||
20 | url: http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview | ||
21 | 21 | ||
22 | Further information about the Crystal Forest Gladden platform supported | 22 | Highland Forest (Crystal Forest/Server Refresh) - Shumway reference platform configurations: |
23 | by this BSP can be found here: | 23 | processor: Intel Xeon E5-2600v2/E5-2400v2 (Ivy Bridge-based) |
24 | chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek) | ||
25 | url: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/crystal-forest-server/xeon-e5-v2-89xx-chipset-ibd.html | ||
24 | 26 | ||
25 | http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-core-pentium-celeron-89xx/overview | 27 | The following platform is supported on meta-intel fido branch and beyond. |
26 | 28 | ||
27 | Further information about the Crystal Forest server platform supported | 29 | River Forest - Long Brook reference platform configurations: |
28 | by this BSP can be found here: | 30 | processor: Intel Xeon E5-2600v3/E5-2400v3 (Haswell EP-based) |
31 | chipset: Intel Communication Chipset 8925-8955 Series (Coleto Creek) | ||
32 | url: https://www-ssl.intel.com/content/www/my/en/embedded/products/river-forest/overview.html?wapkw=coleto | ||
29 | 33 | ||
30 | http://www.intel.com/p/en_US/embedded/hwsw/hardware/xeon-e5-89xx/overview | 34 | All above four platforms use PCIe-based Matrox graphics card for display. |
31 | 35 | ||
32 | Information on all IntelĀ® embedded platforms can be found here: | 36 | More Information on all IntelĀ® embedded platforms can be found here: |
33 | 37 | ||
34 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | 38 | http://www.intel.com/p/en_US/embedded/hwsw/hardware |
35 | 39 | ||
@@ -65,7 +69,7 @@ Patches | |||
65 | Please submit any patches against this BSP to the meta-intel mailing | 69 | Please submit any patches against this BSP to the meta-intel mailing |
66 | list (meta-intel@yoctoproject.org) and cc: the maintainer: | 70 | list (meta-intel@yoctoproject.org) and cc: the maintainer: |
67 | 71 | ||
68 | Maintainer: Chan Wei Sern <wei.sern.chan@intel.com> | 72 | Maintainer: Wu Chia Chuan <chia.chuan.wu@intel.com> |
69 | 73 | ||
70 | Please see the meta-intel/MAINTAINERS file for more details. | 74 | Please see the meta-intel/MAINTAINERS file for more details. |
71 | 75 | ||
@@ -114,6 +118,8 @@ At the end of a successful build, you should have a live image that | |||
114 | you can boot from a USB flash drive (see instructions on how to do | 118 | you can boot from a USB flash drive (see instructions on how to do |
115 | that below, in the section 'Booting the images from /binary'). | 119 | that below, in the section 'Booting the images from /binary'). |
116 | 120 | ||
121 | The live image is located within build/tmp/deploy/images/<machine> folder. | ||
122 | |||
117 | As an alternative to downloading the BSP tarball, you can also work | 123 | As an alternative to downloading the BSP tarball, you can also work |
118 | directly from the meta-intel git repository. For each BSP in the | 124 | directly from the meta-intel git repository. For each BSP in the |
119 | 'meta-intel' repository, there are multiple branches, one | 125 | 'meta-intel' repository, there are multiple branches, one |
@@ -131,15 +137,26 @@ II. Booting the images in /binary | |||
131 | This BSP contains bootable live images, which can be used to directly | 137 | This BSP contains bootable live images, which can be used to directly |
132 | boot Yocto off of a USB flash drive. | 138 | boot Yocto off of a USB flash drive. |
133 | 139 | ||
134 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | 140 | You can deploy the hddimg image to a USB or SATA device. You will |
135 | takes device /dev/sdf, use dd to copy the live image to it. For | 141 | need to know the device name on your host as well as the device name on |
136 | example: | 142 | the target. Be careful with this step as using the wrong host device can |
143 | result in overwriting data on your host machine. | ||
144 | |||
145 | Under Linux, USB and SATA devices typically appears as /dev/sdb, | ||
146 | /dev/sdc, etc. Watching your system messages as you connect the device | ||
147 | will tell you exactly which device name is assigned to the device. | ||
148 | On the Valley Island platform, assuming only one storage device is | ||
149 | attached at boot, a USB or SATA device will be /dev/sda. | ||
150 | |||
151 | After inserting the boot media into your host machine and determining | ||
152 | your host and target device, create the image using the mkefidisk.sh | ||
153 | script, provided by poky under scripts/contrib/. Note that root | ||
154 | privileges are required. For example, using an USB device which appears | ||
155 | as /dev/sdc on the host: | ||
137 | 156 | ||
138 | To boot on both Gladden and Server Platforms: | 157 | $ sudo ./mkefidisk.sh /dev/sdc core-image-sato-<machine>.hddimg /dev/sda |
139 | 158 | ||
140 | # dd if=core-image-sato-crystalforest.hddimg of=/dev/sdf | 159 | Follow the prompts on the screen to confirm the action. |
141 | # sync | ||
142 | # eject /dev/sdf | ||
143 | 160 | ||
144 | This should give you a bootable USB flash device. Insert the device | 161 | This should give you a bootable USB flash device. Insert the device |
145 | into a bootable USB socket on the target, and power on. This should | 162 | into a bootable USB socket on the target, and power on. This should |
@@ -165,6 +182,9 @@ a. Boot Loader | |||
165 | - Support BIOS version at Stargo board ( CrystalForest-Gladden ): | 182 | - Support BIOS version at Stargo board ( CrystalForest-Gladden ): |
166 | CIVGCCK1.86C.0003.P00 | 183 | CIVGCCK1.86C.0003.P00 |
167 | 184 | ||
185 | - Support BIOS version at Long Brook board (RiverForest) | ||
186 | GRNDCRB1.86B.0022.R01.i02.1405151000 | ||
187 | |||
168 | b. I/O drivers | 188 | b. I/O drivers |
169 | -------------- | 189 | -------------- |
170 | -Support Matrox graphic card. | 190 | -Support Matrox graphic card. |
@@ -176,16 +196,20 @@ b. I/O drivers | |||
176 | IV. Enabling Intel DPDK and QuickAssist Technology | 196 | IV. Enabling Intel DPDK and QuickAssist Technology |
177 | =================================================== | 197 | =================================================== |
178 | 198 | ||
179 | There are recipes available for the 'Intel Data Plane Development Kit and | 199 | DPDK recipe: meta-intel/meta-isg/common/recipes-extended/dpdk |
180 | Intel QuickAssist Technology components for use with this BSP. Please | 200 | QAT recipe: meta-crystalforest/recipes-extended/qat |
181 | contact your Intel Field Sales Representative or visit Intel Embedded Design | 201 | QAT-enable zlib recipe: meta-crystalforest/recipes-extended/zlib-qat |
182 | Center (www.intel.com/p/en_US/embedded/designcenter) for instructions on how | 202 | |
183 | to locate and use these recipes. | 203 | Note: |
204 | qat16 recipe is meant for platform with Coleto Creek chipset. | ||
205 | qat15 recipe is meant for platform with Cave Creek chipset. | ||
184 | 206 | ||
185 | ---- | 207 | By default, the machine configuration does not assume that the above |
208 | ingredients are pre-installed onto the BSP. Developers are required | ||
209 | to either use smart tool to install those software packages or | ||
210 | configure IMAGE_INSTALL under build/conf/local.conf, for example. | ||
186 | 211 | ||
187 | If you find you're getting corrupt images on the USB (it doesn't show | 212 | IMAGE_INSTALL += "dpdk qat16 zlib-qat" |
188 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
189 | characters), try doing this first: | ||
190 | 213 | ||
191 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | 214 | The list of packages can be searched under tmp/deploy/<package-type> |
215 | folder. | ||