blob: cad7736fe428d5f9835a719e7e1e710a533b68be (
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
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
|
# meta-rcar-gen3
This layer provides the support for the evaluation board mounted ARM SoCs of
Renesas Electronics, called the R-Car Generation 3.
Currently, this supports boards and the SoCs of the following:
```bash
- Board: Salvator-X / SoC: R8A7795 (R-Car H3), R8A7796 (R-Car M3), R8A77965 (R-Car M3N)
- Board: R-Car Starter Kit premier(H3ULCB) / SoC: R8A7795 (R-Car H3)
- Board: R-Car Starter Kit pro(M3ULCB) / SoC: R8A7796 (R-Car M3)
- Board: Ebisu / SoC: R8A77990 (R-Car E3)
```
## Branch Policy
* This is Community Yocto BSP to follow Yocto/Poky releases.
* It is not supported to the level of the Customer Yocto BSP.
## Tag Policy
* Releases are created from the respective working branch.
* After a Customer Yocto BSP version releases, the Community Yocto BSP will be
rebased and released accordingly.
* thud-X:
* The versions used on thud (Yocto Project 2.6) will start on
thud-Yocto-v3.15.0 to keep the major version numbers in sync.
## Contribution
* Please submit any patches for this layer to: takamitsu.honda.pv@renesas.com
* Please see the MAINTAINERS file for more details.
## Layer Dependencies
This layer depends on:
* poky
```bash
URI: git://git.yoctoproject.org/poky
layers: meta, meta-yocto, meta-yocto-bsp
branch: thud
revision: 84eecb017ef92ef36b4df730908828e54aeff85c
```
* meta-linaro
```bash
URI: git://git.linaro.org/openembedded/meta-linaro.git
layers: meta-optee
branch: thud
revision: edb7ffc2a121df7596385595abe75180296103e0
```
* meta-openembedded
```bash
URI: git://git.openembedded.org/meta-openembedded
layers: meta-oe
branch: thud
revision: cca27b5ea7569d2730ee5da7ee7f47b39d775d89
```
## Build Instructions
The following instructions require a Poky installation (or equivalent).
* This also needs git user name and email defined:
```bash
$ git config --global user.email "you@example.com"
$ git config --global user.name "Your Name"
```
* Initialize a build using the 'oe-init-build-env' script in Poky. e.g.:
```bash
$ source poky/oe-init-build-env
```
* After that, initialized configure bblayers.conf by adding meta-rcar-gen3 layer.
e.g.:
```bash
BBLAYERS ?= " \
<path to layer>/poky/meta \
<path to layer>/poky/meta-yocto \
<path to layer>/poky/meta-yocto-bsp \
<path to layer>/meta-renesas/meta-rcar-gen3 \
<path to layer>/meta-linaro/meta-optee \
<path to layer>/meta-openembedded/meta-oe \
"
```
* To build a specific target BSP, configure the associated machine in local.conf:
```bash
MACHINE ??= "<supported board name>"
```
* Select the SOC
* For H3: r8a7795
```bash
SOC_FAMILY = "r8a7795"
```
* For M3: r8a7796
```bash
SOC_FAMILY = "r8a7796"
```
* For M3N: r8a77965
```bash
SOC_FAMILY = "r8a77965"
```
* For E3: r8a77990
```bash
# Already added in machine config: ebisu.conf
SOC_FAMILY = "r8a77990"
```
* Configure for systemd init in local.conf:
```bash
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
```
* Configure for ivi-shell and ivi-extension
```bash
DISTRO_FEATURES_append = " ivi-shell"
```
* Configure for USB 3.0
```bash
MACHINE_FEATURES_append = " usb3"
```
* Enable tuning support for Capacity Aware migration Strategy (CAS)
```bash
MACHINE_FEATURES_append = " cas"
```
* Build the target file system image using bitbake:
```bash
$ bitbake core-image-minimal
```
After completing the images for the target machine will be available in the
output directory 'tmp/deploy/images/<supported board name>'.
Images generated:
* Image (generic Linux Kernel binary image file)
* Image-<machine name>.dtb (DTB for target machine)
* core-image-minimal-<machine name>.tar.bz2 (rootfs tar+bzip2)
* core-image-minimal-<machine name>.ext4 (rootfs ext4 format)
## Build Instructions for SDK
NOTE:
**This may be changed in the near feature. These instructions are tentative.**
Should define the staticdev in SDK image feature for installing the static libs
to SDK in local.conf.
```bash
SDKIMAGE_FEATURES_append = " staticdev-pkgs"
```
### For 64-bit target SDK (aarch64)
Use `bitbake -c populate_sdk` for generating the toolchain SDK
```bash
$ bitbake core-image-minimal -c populate_sdk
```
The SDK can be found in the output directory `tmp/deploy/sdk`
* `poky-glibc-x86_64-core-image-minimal-aarch64-toolchain-x.x.sh`
### Usage of toolchain SDK
Install the SDK to the default: `/opt/poky/x.x`
* For 64-bit target SDK
```bash
$ sh poky-glibc-x86_64-core-image-minimal-aarch64-toolchain-x.x.sh
```
* For 64-bit application, using environment script in `/opt/poky/x.x`
```bash
$ source /opt/poky/x.x/environment-setup-aarch64-poky-linux
```
## R-Car Generation 3 Information
Refer to the following for more information from eLinux website
https://elinux.org/R-Car
|
