diff options
Diffstat (limited to 'meta-crownbay/README')
| -rw-r--r-- | meta-crownbay/README | 140 |
1 files changed, 0 insertions, 140 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README deleted file mode 100644 index 03dafb40..00000000 --- a/meta-crownbay/README +++ /dev/null | |||
| @@ -1,140 +0,0 @@ | |||
| 1 | This README file contains information on building the meta-crownbay | ||
| 2 | BSP layer, and booting the images contained in the /binary directory. | ||
| 3 | Please see the corresponding sections below for details. | ||
| 4 | |||
| 5 | The Crown Bay platform consists of the Intel Atom E6xx processor, | ||
| 6 | plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). | ||
| 7 | |||
| 8 | Further information on the platforms supported by this BSP can be | ||
| 9 | found here: | ||
| 10 | |||
| 11 | http://www.intel.com/p/en_US/embedded/hwsw/hardware/atom-e6xx/overview | ||
| 12 | |||
| 13 | And information on all IntelĀ® embedded platforms can be found here: | ||
| 14 | |||
| 15 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
| 16 | |||
| 17 | |||
| 18 | Yocto Project Compatible | ||
| 19 | ======================== | ||
| 20 | |||
| 21 | This BSP is compatible with the Yocto Project as per the requirements | ||
| 22 | listed here: | ||
| 23 | |||
| 24 | https://www.yoctoproject.org/webform/yocto-project-compatible-registration | ||
| 25 | |||
| 26 | |||
| 27 | Dependencies | ||
| 28 | ============ | ||
| 29 | |||
| 30 | This layer depends on: | ||
| 31 | |||
| 32 | URI: git://git.openembedded.org/bitbake | ||
| 33 | branch: master | ||
| 34 | |||
| 35 | URI: git://git.openembedded.org/openembedded-core | ||
| 36 | layers: meta | ||
| 37 | branch: master | ||
| 38 | |||
| 39 | URI: git://git.yoctoproject.org/meta-intel | ||
| 40 | layers: intel | ||
| 41 | branch: master | ||
| 42 | |||
| 43 | |||
| 44 | Patches | ||
| 45 | ======= | ||
| 46 | |||
| 47 | Please submit any patches against this BSP to the meta-intel mailing list | ||
| 48 | (meta-intel@yoctoproject.org) and cc: the maintainer: | ||
| 49 | |||
| 50 | Maintainer: Saul Wold <sgw@linux.intel.com> | ||
| 51 | |||
| 52 | Please see the meta-intel/MAINTAINERS file for more details. | ||
| 53 | |||
| 54 | |||
| 55 | Table of Contents | ||
| 56 | ================= | ||
| 57 | |||
| 58 | I. Building the meta-crownbay BSP layer | ||
| 59 | II. Booting the images in /binary | ||
| 60 | |||
| 61 | |||
| 62 | I. Building the meta-crownbay BSP layer | ||
| 63 | ======================================= | ||
| 64 | |||
| 65 | In order to build an image with BSP support for a given release, you | ||
| 66 | need to download the corresponding BSP tarball from the 'Board Support | ||
| 67 | Package (BSP) Downloads' page of the Yocto Project website. | ||
| 68 | |||
| 69 | Having done that, and assuming you extracted the BSP tarball contents | ||
| 70 | at the top-level of your yocto build tree, you can build a crownbay | ||
| 71 | image by adding the location of the meta-crownbay layer to | ||
| 72 | bblayers.conf, along with the meta-intel layer itself (to access | ||
| 73 | common metadata shared between BSPs) e.g.: | ||
| 74 | |||
| 75 | yocto/meta-intel \ | ||
| 76 | yocto/meta-intel/meta-crownbay \ | ||
| 77 | |||
| 78 | The meta-crownbay layer contains support for the crownbay-noemgd machine | ||
| 79 | configuration. The previously supported crownbay machine with the | ||
| 80 | proprietary EMGD graphics driver has been retired. The 'crownbay-noemgd' | ||
| 81 | machine configuration uses the open source 'vesa' kernel driver. | ||
| 82 | |||
| 83 | To enable the layer add the following to the local.conf file: | ||
| 84 | |||
| 85 | MACHINE ?= "crownbay-noemgd" | ||
| 86 | |||
| 87 | You should then be able to build a crownbay image as such: | ||
| 88 | |||
| 89 | $ source oe-init-build-env | ||
| 90 | $ bitbake core-image-sato | ||
| 91 | |||
| 92 | At the end of a successful build, you should have a live image that | ||
| 93 | you can boot from a USB flash drive (see instructions on how to do | ||
| 94 | that below, in the section 'Booting the images from /binary'). | ||
| 95 | |||
| 96 | As an alternative to downloading the BSP tarball, you can also work | ||
| 97 | directly from the meta-intel git repository. For each BSP in the | ||
| 98 | 'meta-intel' repository, there are multiple branches, one | ||
| 99 | corresponding to each major release starting with 'laverne' (0.90), in | ||
| 100 | addition to the latest code which tracks the current master (note that | ||
| 101 | not all BSPs are present in every release). Instead of extracting | ||
| 102 | a BSP tarball at the top level of your yocto build tree, you can | ||
| 103 | equivalently check out the appropriate branch from the meta-intel | ||
| 104 | repository at the same location. | ||
| 105 | |||
| 106 | |||
| 107 | II. Booting the images in /binary | ||
| 108 | ================================= | ||
| 109 | |||
| 110 | This BSP contains bootable live images, which can be used to directly | ||
| 111 | boot Yocto off of a USB flash drive. | ||
| 112 | |||
| 113 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
| 114 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
| 115 | example: | ||
| 116 | |||
| 117 | # dd if=core-image-sato-crownbay-noemgd.hddimg of=/dev/sdf | ||
| 118 | # sync | ||
| 119 | # eject /dev/sdf | ||
| 120 | |||
| 121 | This should give you a bootable USB flash device. Insert the device | ||
| 122 | into a bootable USB socket on the target, and power on. This should | ||
| 123 | result in a system booted to the Sato graphical desktop. | ||
| 124 | |||
| 125 | If you want a terminal, use the arrows at the top of the UI to move to | ||
| 126 | different pages of available applications, one of which is named | ||
| 127 | 'Terminal'. Clicking that should give you a root terminal. | ||
| 128 | |||
| 129 | If you want to ssh into the system, you can use the root terminal to | ||
| 130 | ifconfig the IP address and use that to ssh in. The root password is | ||
| 131 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
| 132 | the Password prompt: and you should be in. | ||
| 133 | |||
| 134 | ---- | ||
| 135 | |||
| 136 | If you find you're getting corrupt images on the USB (it doesn't show | ||
| 137 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
| 138 | characters), try doing this first: | ||
| 139 | |||
| 140 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||
