summaryrefslogtreecommitdiffstats
path: root/meta-rcar-gen3/README
diff options
context:
space:
mode:
authorTakamitsu Honda <takamitsu.honda.pv@renesas.com>2017-01-27 11:47:06 +0900
committerTakamitsu Honda <takamitsu.honda.pv@renesas.com>2017-01-27 11:47:06 +0900
commit3613b2780a6b5d5d70ea6802be5060a8214cbdb5 (patch)
treefab60ccb7b38da7e8558a2879885f06e5b0662d2 /meta-rcar-gen3/README
Renesas BSP v3.5.1 (kernel v4.9 stable) [Environment] poky: yocto-2.1.2 (cca8dd15c8096626052f6d8d25ff1e9a606104a3) meta-openembedded: 55c8a76da5dc099a7bc3838495c672140cedb78e meta-linaro: 2f51d38048599d9878f149d6d15539fb97603f8f [Information] - U-boot: Changed load address from H'49000000 to H'50000000 - XDG_RUNTIME_DIR has been changed from "/run/user/root" to "/run/user/0" - Change location of include directory, which stores common user header files, to $(INCSHARED) - In BSP Only, core-image-weston is not supported even though local-wayland.conf is provided. - Please set Salvator-x SW7 Pin-1. In after Yocto BSP v2.12.0, it is  necessary to enable BKUP_TRG signal for Suspend to RAM. - The dtb filename was changed in R-Car H3. Only "Image-r8a7795-es1-salvator-x.dtb" is supported in this version. Please use "Image-r8a7795-es1-salvator-x.dtb" It supports R-Car H3 WS1.0 and WS1.1. - Please update your local.conf and bblayers.conf corresponding to Yocto v2.16.0 package. You can refer to meta-rcargen3/docs/sample/conf/ for updated contents. - You have to re-compile out-of-recipe software like user application by v2.16.0 SDK toolchains. - In some boards, the resuming from System Suspend to RAM may cause unstable operation or failed to resume. Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
Diffstat (limited to 'meta-rcar-gen3/README')
-rw-r--r--meta-rcar-gen3/README124
1 files changed, 124 insertions, 0 deletions
diff --git a/meta-rcar-gen3/README b/meta-rcar-gen3/README
new file mode 100644
index 0000000..dd87e65
--- /dev/null
+++ b/meta-rcar-gen3/README
@@ -0,0 +1,124 @@
+meta-rcar-gen3
+==============
+
+This layer provides that evaluation board is mounted ARM SoCs of Renesas
+Electronics, called the R-Car Generation 3. Currently, this supports
+board and the SoCs of the following:
+ - Board: Salvator-X / SoC: R8A7795 (R-Car H3), R8A7796 (R-Car M3)
+ - Board: R-Car Starter Kit premier(H3ULCB) / SoC: R8A7795 (R-Car H3)
+ - Board: R-Car Starter Kit pro(M3ULCB) / SoC: R8A7796 (R-Car M3)
+
+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: krogoth
+
+ URI: git://github.com/renesas-rcar/meta-renesas
+ layers: meta-rcar-gen3
+ branch: krogoth
+
+ URI: git://git.linaro.org/openembedded/meta-linaro.git
+ layers: meta-optee
+ branch: krogoth
+
+ URI: git://git.openembedded.org/meta-openembedded
+ layers: meta-oe
+ branch: krogoth
+
+Build Instructions
+==================
+
+The following instructions require a Poky installation (or equivalent).
+
+Initialize a build using the 'oe-init-build-env' script in Poky. e.g.:
+
+ $ source poky/oe-init-build-env
+
+After that, initialized configure bblayers.conf by adding meta-rcar-gen3 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/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:
+
+ MACHINE ??= "<supported board name>"
+
+Select the SOC
+
+ For H3: r8a7795
+ SOC_FAMILY = "r8a7795"
+
+ For M3: r8a7796
+ SOC_FAMILY = "r8a7796"
+
+Must change the package class to ipk files in local.conf:
+
+ PACKAGE_CLASSES ?= "package_ipk"
+
+Configure for systemd init in local.conf:
+
+ DISTRO_FEATURES_append = " systemd"
+ VIRTUAL-RUNTIME_init_manager = "systemd"
+
+Build the target file system image using bitbake:
+
+ $ 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)
+ * core-image-minimal-<machine name>.cpio.gz (rootfs cpio+gz format)
+
+Build Instructions for SDK
+==========================
+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.
+
+ SDKIMAGE_FEATURES_append = " staticdev-pkgs"
+
+Use bitbake -c populate_sdk for generating the toolchain SDK:
+For 64-bit target SDK (aarch64):
+
+ $ 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:
+
+ $ sh poky-glibc-x86_64-core-image-minimal-aarch64-toolchain-x.x.sh
+
+For 64-bit application use environment script in /opt/poky/x.x
+
+ $ source /opt/poky/x.x/environment-setup-aarch64-poky-linux
+
+ULCB Information
+================
+Refer to the following for more information of ULCB:
+
+ http://elinux.org/R-Car