aboutsummaryrefslogtreecommitdiffstats
path: root/meta-rmobile/README
blob: 6ec55deed8af64056d4a9db26746b449f347b26a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
meta-rmobile
===========

This layer provides that evaluation board is mounted ARM SoCs of Renesas                                                                                                                      
Electronics, called the R-Mobile. Currently, this supports board and the
SoCs of the following:                                                                                                                                                          
  - Board: armadillo800eva / SoC: R8A7740 (R-Mobile A1)

This layer provides armadillo800eva board which is Renesas Electronics ARM SoCs
R8A7740 (R-Mobile A1) evaluation board.

Patches
=======

Please submit any patches for this layer to: takamitsu.honda.pv@renesas.com
Please see the MAINTAINERS file for more details.

Dependencies
============

This layer depends on:

	URI: git://git.yoctoproject.org/poky
	layers: meta, meta-yocto, meta-yocto-bsp
	branch: master

	URI: git://git.yoctoproject.org/meta-renesas
	layers: renesas
	branch: master

Build Instructions
==================

The following instructions require a Poky installation (or equivalent).

Initialize a build using the 'oe-init-build-env' script in Poky. Once
initialized configure bblayers.conf by adding the meta-renesas and
meta-rmobile layer. e.g.:

	BBLAYERS ?= " \
		<path to layer>/poky/meta \
		<path to layer>/poky/meta-yocto \
		<path to layer>/poky/meta-yocto-bsp \
		<path to layer>/meta-renesas \
		<path to layer>/meta-renesas/meta-rmobile \
	"

To build a specific target BSP configure the associated machine in local.conf:

	MACHINE ?= "<support board name>"

Build the target file system image using bitbake:

	$ bitbake core-image-minimal

Once complete the images for the target machine will be available in the output
directory 'tmp/deploy/images/<support board name>'.

Images generated:
	* uImage (Linux Kernel binary, in u-boot wrapped format)
	* uImage+dtb (Linux Kernel binary with DTB, in u-boot wrapped format)
	* zImage (Linux Kernel binary)
	* zImage+dtb (Linux Kernel binary with DTB)
	* uImage-<SoC namme>-<machine name>.dtb (DTB for target machine)
	* core-image-minimal-<machine name>.tar.bz2 (rootfs tar+bzip2)
	* core-image-minimal-<machine name>.jffs2 (rootfs in JFFS2 format)
	* u-boot.bin (U-Boot binary)