diff options
| author | Kishore Bodke <kishore.k.bodke@intel.com> | 2012-09-06 10:47:46 -0700 |
|---|---|---|
| committer | Tom Zanussi <tom.zanussi@intel.com> | 2012-09-07 17:20:31 -0500 |
| commit | e3d9eb5df031ea32208d196061b5511849019da9 (patch) | |
| tree | fd2c0792fff88f61f1e3179038b48a1ce6559652 /meta-crystalforest/README | |
| parent | 66b516f3d3a287eecbf8804b2221bfc27e36db63 (diff) | |
| download | meta-intel-1.3_M4.tar.gz | |
meta-crystalforest: Crystal Forest BSP Created.1.3_M4.rc11.3_M4
Initial checkin for the new Crystal Forest BSP.
This BSP is based on Sandybridge CPU and Cave Creek Chipset.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Diffstat (limited to 'meta-crystalforest/README')
| -rw-r--r-- | meta-crystalforest/README | 139 |
1 files changed, 139 insertions, 0 deletions
diff --git a/meta-crystalforest/README b/meta-crystalforest/README new file mode 100644 index 00000000..7b88b224 --- /dev/null +++ b/meta-crystalforest/README | |||
| @@ -0,0 +1,139 @@ | |||
| 1 | This README file contains information on building the meta-crystalforest | ||
| 2 | BSP layer, and booting the images contained in the /binary directory. | ||
| 3 | Please see the corresponding sections below for details. | ||
| 4 | |||
| 5 | The 'Crystal Forest' platform consists of two versions. | ||
| 6 | 1. STARGO | ||
| 7 | 2. SHUMWAY | ||
| 8 | |||
| 9 | Stargo Platform is based on Intel Sandy Bridge Gladden Processor,plus the Cave Creek chipset. | ||
| 10 | Shumway Platform is based on two Intel Sandy Bridge (SNB-EP ES2 Grade and SNB-EN ES2 Grade) | ||
| 11 | Processors plus two Cave Creek Chipsets. | ||
| 12 | |||
| 13 | Both Platforms uses Matrox graphics Card. | ||
| 14 | |||
| 15 | |||
| 16 | Dependencies | ||
| 17 | ============ | ||
| 18 | |||
| 19 | This layer depends on: | ||
| 20 | |||
| 21 | URI: git://git.openembedded.org/bitbake | ||
| 22 | branch: master | ||
| 23 | |||
| 24 | URI: git://git.openembedded.org/openembedded-core | ||
| 25 | layers: meta | ||
| 26 | branch: master | ||
| 27 | |||
| 28 | URI: git://git.yoctoproject.org/meta-intel | ||
| 29 | layers: intel | ||
| 30 | branch: master | ||
| 31 | |||
| 32 | |||
| 33 | Patches | ||
| 34 | ======= | ||
| 35 | |||
| 36 | Please submit any patches against this BSP to the Yocto mailing list | ||
| 37 | (yocto@yoctoproject.org) and cc: the maintainer: | ||
| 38 | |||
| 39 | Maintainer: Kishore Bodke <kishore.k.bodke@intel.com> | ||
| 40 | |||
| 41 | Please see the meta-intel/MAINTAINERS file for more details. | ||
| 42 | |||
| 43 | |||
| 44 | Table of Contents | ||
| 45 | ================= | ||
| 46 | |||
| 47 | I. Building the meta-crystalforest BSP layer | ||
| 48 | II. Booting the images in /binary | ||
| 49 | |||
| 50 | |||
| 51 | I. Building the meta-crystalforest BSP layer | ||
| 52 | ======================================= | ||
| 53 | |||
| 54 | In order to build an image with BSP support for a given release, you | ||
| 55 | need to download the corresponding BSP tarball from the 'Board Support | ||
| 56 | Package (BSP) Downloads' page of the Yocto Project website. | ||
| 57 | |||
| 58 | Having done that, and assuming you extracted the BSP tarball contents | ||
| 59 | at the top-level of your yocto build tree, you can build a crystalforest | ||
| 60 | image by adding the location of the meta-crystalforest layer to | ||
| 61 | bblayers.conf, along with the meta-intel layer itself (to access | ||
| 62 | common metadata shared between BSPs) e.g.: | ||
| 63 | |||
| 64 | yocto/meta-intel \ | ||
| 65 | yocto/meta-intel/meta-crystalforest \ | ||
| 66 | |||
| 67 | To enable the Crystal Forest Stargo layer, add the crystalforest-stargo MACHINE to local.conf: | ||
| 68 | |||
| 69 | MACHINE ?= "crystalforest-stargo" | ||
| 70 | |||
| 71 | To enable the Crystal Forest Shumway layer, add the crystalforest-shumway MACHINE to local.conf: | ||
| 72 | |||
| 73 | MACHINE ?= "crystalforest-shumway" | ||
| 74 | |||
| 75 | |||
| 76 | You should then be able to build a crystalforest image as such: | ||
| 77 | |||
| 78 | $ source oe-init-build-env | ||
| 79 | $ bitbake core-image-sato | ||
| 80 | |||
| 81 | At the end of a successful build, you should have a live image that | ||
| 82 | you can boot from a USB flash drive (see instructions on how to do | ||
| 83 | that below, in the section 'Booting the images from /binary'). | ||
| 84 | |||
| 85 | As an alternative to downloading the BSP tarball, you can also work | ||
| 86 | directly from the meta-intel git repository. For each BSP in the | ||
| 87 | 'meta-intel' repository, there are multiple branches, one | ||
| 88 | corresponding to each major release starting with 'laverne' (0.90), in | ||
| 89 | addition to the latest code which tracks the current master (note that | ||
| 90 | not all BSPs are present in every release). Instead of extracting a | ||
| 91 | BSP tarball at the top level of your yocto build tree, you can | ||
| 92 | equivalently check out the appropriate branch from the meta-intel | ||
| 93 | repository at the same location. | ||
| 94 | |||
| 95 | |||
| 96 | II. Booting the images in /binary | ||
| 97 | ================================= | ||
| 98 | |||
| 99 | This BSP contains bootable live images, which can be used to directly | ||
| 100 | boot Yocto off of a USB flash drive. | ||
| 101 | |||
| 102 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
| 103 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
| 104 | example: | ||
| 105 | |||
| 106 | To boot the Stargo Platform: | ||
| 107 | |||
| 108 | # dd if=core-image-sato-crystalforest-stargo-20120829033154.hddimg of=/dev/sdf | ||
| 109 | # sync | ||
| 110 | # eject /dev/sdf | ||
| 111 | |||
| 112 | To boot the Shumway Platform: | ||
| 113 | |||
| 114 | # dd if=core-image-sato-crystalforest-shumway-20120829044852.hddimg of=/dev/sdf | ||
| 115 | # sync | ||
| 116 | # eject /dev/sdf | ||
| 117 | |||
| 118 | This should give you a bootable USB flash device. Insert the device | ||
| 119 | into a bootable USB socket on the target, and power on. This should | ||
| 120 | result in a system booted to the Sato graphical desktop. | ||
| 121 | |||
| 122 | If you want a terminal, use the arrows at the top of the UI to move to | ||
| 123 | different pages of available applications, one of which is named | ||
| 124 | 'Terminal'. Clicking that should give you a root terminal. | ||
| 125 | |||
| 126 | If you want to ssh into the system, you can use the root terminal to | ||
| 127 | ifconfig the IP address and use that to ssh in. The root password is | ||
| 128 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
| 129 | the Password prompt: and you should be in. | ||
| 130 | |||
| 131 | ---- | ||
| 132 | |||
| 133 | If you find you're getting corrupt images on the USB (it doesn't show | ||
| 134 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
| 135 | characters), try doing this first: | ||
| 136 | |||
| 137 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||
| 138 | |||
| 139 | |||
