1 meta-agl, the Yocto layer for Automotive Grade Linux Distribution
2 =================================================================
4 This layer's purpose is ... [TBD]
9 URI: git://git.yoctoproject.org/poky
11 > revision: 5f0d25152bac2d3798663a4ebfdd2df24060f153
13 URI: git://git.openembedded.org/meta-openembedded
16 > revision: 853dcfa0d618dc26bd27b3a1b49494b98d6eee97
18 ## The Renesas R-Car Gen2 (Porter) board depends in addition on: ##
20 URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-renesas
21 > branch: agl-1.0-bsp-1.8.0
22 > revision: 0a69b07cfca17d1435f2bc7bf779139c5fac09a3
27 There are 2 sub-layers in top-level `meta-agl`.
29 `meta-agl` is a layer which contains AGL common and middleware packages.
32 `meta-agl-bsp` is a layer which contains required packages to boot AGL distribution on an emulated machine(QEMU).
33 > meta-agl/meta-agl-bsp
38 AGL package group design:
40 These are the top-level packagegroups for AGL Distribution.
41 > packagegroup-agl-core (basic/common packages out of oe-core)
42 > packagegroup-agl-ivi (middlewares for AGL IVI)
44 Each package group can contain sub-package groups like these.
45 > packagegroup-agl-core-multimedia
46 > packagegroup-agl-core-connectivity
48 > packagegroup-agl-ivi-multimedia
49 > packagegroup-agl-ivi-connectivity
52 The recipe for `packagegroup-agl-core-*.bb` will contain common packages between meta-agl, meta-ivi and meta-tizen.
53 > directory: meta-agl/meta-agl/recipes-core/packagegroups
54 > recipes : packagegroup-agl-core-[subsystem].bb
56 The "packagegroups-agl-ivi-*" will contain AGL specific middleware packages.
57 > directory: meta-agl/meta-agl/recipes-ivi/packagegroups
58 > recipes : packagegroup-agl-ivi-[subsystem].bb
63 * QEMU (x86-64) - emulated machine: qemux86-64
64 * Renesas R-Car Gen2 (R-Car M2) - machine: porter
66 Supported Target of bitbake
67 ------------------------
69 * `agl-image-ivi` The baseline image of AGL Distributions
71 * `agl-image-minimal` For internal use to develop distribution (experimental)
72 * `agl-image-weston` For internal use to develop distribution (experimental)
74 Supposed Directory Trees of Layers to build
75 -------------------------------------------
95 You can build a QEMU image using the following steps:
97 1. Export TEMPLATECONF to pick up correct configuration for the build
98 > $ export TEMPLATECONF=/full/path/to/meta-agl/meta-agl/conf
100 2. Run the following command:
101 > $ source poky/oe-init-build-env
103 3. Build the minimal image of AGL Distribution
104 > $ bitbake agl-image-ivi
107 > $ PATH_TO_POKY/poky/scripts/runqemu agl-image-ivi qemux86-64
110 > $ PATH_TO_POKY/poky/scripts/runqemu agl-image-ivi qemux86-64 bootparams="uvesafb.mode_option=1280x720-32"
112 5. Some weston samples are available from weston terminal.
114 Build a R-Car M2 (porter) image
115 -------------------------------
119 NOTE: These instructions are based on GENIVI wiki, [here](http://wiki.projects.genivi.org/index.php/Hardware_Setup_and_Software_Installation/koelsch%26porter). If these didn't work correctly especially around Renesas Binary Packages, please check there and updated instructions.
121 #### Getting Source Code and Build image
123 1. Create a directory for working, then go to there.
124 $ mkdir -p $HOME/ANYWHERE_YOU_WANT_TO_WORK_THERE
125 $ cd $HOME/ANYWHERE_YOU_WANT_TO_WORK_THERE
126 $ export AGL_TOP=`pwd`
128 2. Get the meta data and checkout
129 $ git clone git://git.yoctoproject.org/poky
131 $ git checkout 5f0d25152bac2d3798663a4ebfdd2df24060f153
133 $ git clone git://git.openembedded.org/meta-openembedded
134 $ cd meta-openembedded
135 $ git checkout 853dcfa0d618dc26bd27b3a1b49494b98d6eee97
137 $ git clone https://gerrit.automotivelinux.org/gerrit/AGL/meta-renesas
139 $ git checkout 0a69b07cfca17d1435f2bc7bf779139c5fac09a3
141 $ git clone https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
143 #### Obtain and Install Renesas Graphics Drivers
145 1. Download packages from Renesas
147 The graphics and multimedia acceleration packages for the R-Car M2 Porter board
148 can be download directory from [here](http://www.renesas.com/secret/r_car_download/rcar_demoboard.jsp).
150 There are 2 ZIP files can be downloaded.
151 * Multimedia and Graphics library which require registeration and click through license
152 > r-car_series_evaluation_software_package_for_linux-*.zip
153 * Related Linux drivers
154 > r-car_series_evaluation_software_package_of_linux_drivers-*.zip
156 2. Unzip the two downloads into a temporary directory.
160 $ unzip PATH_TO_DOWNLOAD/r-car_series_evaluation_software_package_for_linux-*.zip
161 $ unzip PATH_TO_DOWNLOAD/r-car_series_evaluation_software_package_of_linux_drivers-*.zip
163 After this step there should be two files in binary-tmp:
164 * Multimedia and Graphics library
165 > R-Car_Series_Evaluation_Software_Package_for_Linux-*.tar.gz
166 * Related Linux drivers
167 > R-Car_Series_Evaluation_Software_Package_of_Linux_Drivers-*.tar.gz
169 3. Extract 2 tar archives
170 $ tar xf R-Car_Series_Evaluation_Software_Package_for_Linux-*.tar.gz
171 $ tar xf R-Car_Series_Evaluation_Software_Package_of_Linux_Drivers-*.tar.gz
173 4. Copy 2 files manually
174 1. Locate `EVA_r8a7791_linux_sgx_binaries_gles2.tar.bz2` in the Multimedia and Graphics library deliverable and copy it into the BSP layer.
176 $ cp <path_to_file>/EVA_r8a7791_linux_sgx_binaries_gles2.tar.bz2 \
177 meta-renesas/meta-rcar-gen2/recipes-graphics/gles-module/\
178 gles-user-module/r8a7791_linux_sgx_binaries_gles2.tar.bz2
180 2. Locate `SGX_KM_M2.tar.bz2` in the related linux drivers deliverable and copy it into the BSP layer.
181 $ cp <path_to_file>SGX_KM_M2.tar.bz2 \
182 $ meta-renesas/meta-rcar-gen2/recipes-kernel/gles-module/gles-kernel-module
184 #### Build from the Source code
186 You can build a R-Car2 M2 (porter) image using the following steps:
188 1. Export TEMPLATECONF to pick up correct configuration for the build
189 $ export TEMPLATECONF=$AGL_TOP/meta-renesas/meta-rcar-gen2/conf
191 2. Run the following command:
193 $ source poky/oe-init-build-env
195 3. Build the minimal image of AGL Distribution
196 $ bitbake agl-image-ivi
198 ### Deployment (SDCARD)
200 NOTE: These instructions are based on GENIVI wiki, [here](http://wiki.projects.genivi.org/index.php/Hardware_Setup_and_Software_Installation/koelsch%26porter#Deployment_.28SDCARD.29).
202 #### Instructions on the host
204 1. Format SD-Card and then, create single EXT3 partition on it.
206 2. Mount the SD-Card, for example `/media/$SDCARD_LABEL`.
208 3. Copy AGL root file system onto the SD-Card
209 1. Go to build directory
210 $ cd $AGL_TOP/build/tmp/deploy/images/porter
211 2. Extract the root file system into the SD-Card
212 $ sudo tar --extract --numeric-owner --preserve-permissions --preserve-order \
213 --totals --directory=/media/$SDCARD_LABEL --file=agl-image-ivi-porter.tar.bz2
214 3. Copy kernel and DTB into the `/boot` of the SD-Card
215 $ sudo cp uImage uImage-r8a7791-porter.dtb /media/$SDCARD_LABEL
217 4. After the copy finished, unmount SD-Card and insert it into the SD-Card slot of the porter board.
219 #### Instructions on the host
221 NOTE: There is details about porter board [here](http://elinux.org/R-Car/Boards/Porter).
223 NOTE: To boot weston on porter board, we need keyboard and mouse. (USB2.0 can be use for this)
225 ##### Change U-Boot parameters to boot from SD card
227 1. Power up the board and, using your preferred terminal emulator, stop the board's autoboot by hitting any key.
229 > Debug serial settings are 38400 8N1. Any standard terminal emulator program can be used.
231 2. Set the follow environment variables and save them
232 => setenv bootargs_console console=ttySC6,${baudrate}
233 => setenv bootargs_video vmalloc=384M video=HDMI-A-1:1024x768-32@60
234 => setenv bootcmd_sd 'ext4load mmc 0:1 0x40007fc0 boot/uImage;ext4load mmc 0:1 0x40f00000 boot/uImage-r8a7791-porter.dtb'
235 => setenv bootcmd 'setenv bootargs ${bootargs_console} ${bootargs_video} root=/dev/mmcblk0p1 rw rootfstype=ext3;run bootcmd_sd;bootm 0x40007fc0 - 0x40f00000'
238 ##### Boot from SD card
240 1. After board reset, U-Boot is started and after a countdown, ...
241 Linux boot message should be displayed. Please wait a moment.
242 2. Then weston is booted automatically, and weston-terminal appears.