R Car H3/M3 Series User Manual: Linux Interface Specification Yocto Recipe Start Up Guide RENESAS RCH3M3 Startup UME V2.23.0

User Manual:

Open the PDF directly: View PDF .
Page Count: 48

Download
Open PDF In Browser	View PDF

User’s Manual

CONFIDENTIAL

Linux Interface
Specification
Yocto recipe Start-Up Guide
User’s Manual: Software
R-Car H3/M3 Series

All information contained in these materials, including products and product specifications,
represents information on the product at the time of publication and is subject to change by
Renesas Electronics Corp. without notice. Please review the latest information published by
Renesas Electronics Corp. through various means, including the Renesas Electronics Corp.
website (http://www.renesas.com).

www.renesas.com

Rev.2.23.0 Aug. 2017

CONFIDENTIAL
Notice
1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of
semiconductor products and application examples. You are fully responsible for the incorporation or any other use of the circuits,
software, and information in the design of your product or system. Renesas Electronics disclaims any and all liability for any losses and
damages incurred by you or third parties arising from the use of these circuits, software, or information.
2. Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other disputes involving
patents, copyrights, or other intellectual property rights of third parties, by or arising from the use of Renesas Electronics products or
technical information described in this document, including but not limited to, the product data, drawing, chart, program, algorithm,
application examples.
3. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas
Electronics or others.
4. You shall not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. Renesas
Electronics disclaims any and all liability for any losses or damages incurred by you or third parties arising from such alteration,
modification, copy or otherwise misappropriation of Renesas Electronics products.
5. Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The intended
applications for each Renesas Electronics product depends on the product’s quality grade, as indicated below.
"Standard":
Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment;
home electronic appliances; machine tools; personal electronic equipment; and industrial robots etc.
"High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control (traffic lights); large-scale communication
equipment; key financial terminal systems; safety control equipment; etc.
Renesas Electronics products are neither intended nor authorized for use in products or systems that may pose a direct threat to human life
or bodily injury (artificial life support devices or systems, surgical implantations etc.), or may cause serious property damages (space and
undersea repeaters; nuclear power control systems; aircraft control systems; key plant systems; military equipment; etc.). Renesas
Electronics disclaims any and all liability for any damages or losses incurred by you or third parties arising from the use of any Renesas
Electronics product for which the product is not intended by Renesas Electronics.
6. When using the Renesas Electronics products, refer to the latest product information (data sheets, user’s manuals, application notes,
"General Notes for Handling and Using Semiconductor Devices" in the reliability handbook, etc.), and ensure that usage conditions are
within the ranges specified by Renesas Electronics with respect to maximum ratings, operating power supply voltage range, heat radiation
characteristics, installation, etc. Renesas Electronics disclaims any and all liability for any malfunctions or failure or accident arising out
of the use of Renesas Electronics products beyond such specified ranges.
7. Although Renesas Electronics endeavors to improve the quality and reliability of Renesas Electronics products, semiconductor products
have specific characteristics such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Further,
Renesas Electronics products are not subject to radiation resistance design. Please ensure to implement safety measures to guard them
against the possibility of bodily injury, injury or damage caused by fire, and social damage in the event of failure or malfunction of
Renesas Electronics products, such as safety design for hardware and software including but not limited to redundancy, fire control and
malfunction prevention, appropriate treatment for aging degradation or any other appropriate measures by your own responsibility as
warranty for your products/system. Because the evaluation of microcomputer software alone is very difficult and not practical, please
evaluate the safety of the final products or systems manufactured by you.
8. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each
Renesas Electronics product. Please investigate applicable laws and regulations that regulate the inclusion or use of controlled
substances, including without limitation, the EU RoHS Directive carefully and sufficiently and use Renesas Electronics products in
compliance with all these applicable laws and regulations. Renesas Electronics disclaims any and all liability for damages or losses
occurring as a result of your noncompliance with applicable laws and regulations.
9. Renesas Electronics products and technologies shall not be used for or incorporated into any products or systems whose manufacture, use,
or sale is prohibited under any applicable domestic or foreign laws or regulations. You shall not use Renesas Electronics products or
technologies for (1) any purpose relating to the development, design, manufacture, use, stockpiling, etc., of weapons of mass destruction,
such as nuclear weapons, chemical weapons, or biological weapons, or missiles (including unmanned aerial vehicles (UAVs)) for
delivering such weapons, (2) any purpose relating to the development, design, manufacture, or use of conventional weapons, or (3) any
other purpose of disturbing international peace and security, and you shall not sell, export, lease, transfer, or release Renesas Electronics
products or technologies to any third party whether directly or indirectly with knowledge or reason to know that the third party or any
other party will engage in the activities described above. When exporting, selling, transferring, etc., Renesas Electronics products or
technologies, you shall comply with any applicable export control laws and regulations promulgated and administered by the governments
of the countries asserting jurisdiction over the parties or transactions.
10. Please acknowledge and agree that you shall bear all the losses and damages which are incurred from the misuse or violation of the terms
and conditions described in this document, including this notice, and hold Renesas Electronics harmless, if such misuse or violation results
from your resale or making Renesas Electronics products available any third party.
11. This document shall not be reprinted, reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas
Electronics.
12. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or
Renesas Electronics products.
(Note 1) "Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its majority-owned
subsidiaries.
(Note 2) "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics.
(Rev.3.0-1 November 2016)

CONFIDENTIAL
Trademark
・
・
・
・
・

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
ARM is a registered trademark of ARM Limited (or its subsidiaries) in the EU and/or elsewhere. All rights reserved.
Windows and Windows Media are registered trademarks of Microsoft Corporation in the United States and other countries.
Other company names and product names mentioned herein are registered trademarks or trademarks of their respective owners.
Registered trademark and trademark symbols (® and ™) are omitted in this document

CONFIDENTIAL

How to Use This Manual


[Readers]
This manual is intended for engineers who develop products which use the R-Car H3/M3 processor.



[Purpose]
This manual is intended to give users an understanding of the functions of the R-Car H3/M3 processor device driver
and to serve as a reference for developing hardware and software for systems that use this driver.



[How to Read This Manual]
It is assumed that the readers of this manual have general knowledge in the fields of electrical
 engineering, logic circuits, microcontrollers, and Linux.
→ Read this manual in the order of the CONTENTS.
 To understand the functions of a multimedia processor for R-Car H3/M3
→ See the R-Car H3/M3 User’s Manual.
 To know the electrical specifications of the multimedia processor for R-Car H3/M3
→ See the R-Car H3/M3 Data Sheet.



[Conventions]
The following symbols are used in this manual.
Data significance: Higher digits on the left and lower digits on the right
Note: Footnote for item marked with Note in the text
Caution: Information requiring particular attention
Remark: Supplementary information
Numeric representation: Binary ... ××××, 0b××××, or ××××B
Decimal ... ××××
Hexadecimal ... 0x×××× or ××××H
Data type: Double word ... 64 bits
Word … 32 bits
Half word ... 16 bits
Byte ... 8 bits

CONFIDENTIAL

Table of Contents

Introduction ............................................................................................................................................ 1
1. R-Car H3/M3 Linux BSP package files............................................................................................. 2
1.1

Reference (R-Car H3/M3) ........................................................................................................................................ 2

2. Environmental Requirement .............................................................................................................. 3
2.1
2.2

Setting of parts .......................................................................................................................................................... 3
Setting of dip switch ................................................................................................................................................. 5

3. Building Instructions .......................................................................................................................... 7
3.1
3.2
3.3

In case of BSP + 3D Graphics + Multimedia package .............................................................................................. 9
In case of BSP + 3D Graphics (without Multimedia package) ............................................................................... 16
In case of BSP Only ................................................................................................................................................ 18

4. Writing of IPL/Secure ...................................................................................................................... 20
4.1
4.2
4.3
4.4

Writing data ............................................................................................................................................................ 20
Dip-Switch .............................................................................................................................................................. 20
How to write ........................................................................................................................................................... 20
IPL/Secure write ..................................................................................................................................................... 22

5. Confirm starting of U-Boot and Linux ............................................................................................ 23
6. Exporting Toolchains ....................................................................................................................... 26
7. Memory map .................................................................................................................................... 28
8. U-Boot command ............................................................................................................................. 35

CONFIDENTIAL

Introduction
This start-up guide explains R-Car H3/M3 Yocto recipe package files, the system environments, the make method of
kernel, the operating of U-Boot and so on.
This product R-Car H3/M3 Yocto recipe is a basic package to operate built-in Linux and basic middleware on the R-Car
H3/M3 System Evaluation Board. Please contact Renesas Electronics person who provided this product to you in case of
questions.

Rev.2.23.0
Aug. 29, 2017

Page 1 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
H3/M3 Linux BSP package files

R-Car

R-Car H3/M3 Linux BSP package files

This Yocto recipe will be taken
The U-Boot source code from:
git://github.com/renesas-rcar/u-boot.git

R-Car H3/M3 Linux source code from:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git

1.1

Reference (R-Car H3/M3)
Document name

Version

R-Car Series, 3rd Generation User’s Manual: Hardware

Rev.0.54

R-CarH3-SiP System Evaluation Board Salvator-X Hardware Manual

Rev.1.03

R-CarM3-SiP System Evaluation Board Salvator-X Hardware Manual

Rev.1.03

R-CarH3-SiP/M3-SiP System Evaluation Board Salvator-XS Hardware Manual

Rev.2.00

Rev.2.23.0
Aug. 29, 2017

Page 2 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Environmental Requirement

Environmental Requirement

2.1

Setting of parts

Host PC and terminal software are necessary for the operation of this product. Furthermore, Ethernet cable is required to
use NFS mount function. Please refer to Table 1.

Table 1 R-Car H3/M3 Linux BSP Environmental Requirement
Equipment
Linux Host PC

Explanation
Ubuntu 14.04 LTS (64bit) is recommended as OS. 32bit version is not supported.
It is used as building and debugging environment.
It is used as TFTP server and NFS server.

Windows Host PC

Windows 7 is recommended as OS.
It is used as debugging environment.
Terminal software and VCP driver are executed.

Terminal software

Please use following software.
1) TeraTerm
(Confirmed with Japanese version of Tera Term 4.87
Available at http://sourceforge.jp/projects/ttssh2 )

VCP driver

Please install in Windows Host PC.
Execute CP210xVCPInstaller_x86/x64.exe for install before connect. USB become virtual
COM port on terminal software. Please connect to CN25 (Serial-USB Bridge CP2102) on
H3/M3 System Evaluation Board.
(Available at
http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx)

TFTP server software

It is used when Hyper Flash is written by U-Boot or Image is downloaded.

NFS server software

It is used when File system is mounted by NFS.

Rev.2.23.0
Aug. 29, 2017

Page 3 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Environmental Requirement

Recommended Environment
The following shows a Recommended Environment.
Hub

(Straight Ethernet cable)
Straight Ethernet cable

R-Car H3/M3
System Evaluation Board

USB cable (type A
to mini/micro AB)

[Linux Host PC]
TFTP server
NFS server
[Windows7 Host PC]
Terminal software to display console
(ssh to control Linux Host)
Figure 1. Recommended Environment for R-Car H3/M3 Linux BSP
Note) Functions in covered with () are optional.

Rev.2.23.0
Aug. 29, 2017

Page 4 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Environmental Requirement

2.2

Setting of dip switch

The setting of R-Car H3/M3 System Evaluation Board's dip switches is shown the following Table 2, Table 3, Table 4,
Table 5.
For Salvator-X board, please refer to “R-CarH3-SiP System Evaluation Board RTP0RC7795SIPB0011S (Salvator-X)
Setup Manual”.
For Salvator-XS board, please refer to “R-CarH3/M3-SiP System Evaluation Board RTP0RC7795SIPB0012S (SalvatorXS) Setup Manual”.
Table 2 setting of Dip switches (R-Car H3 Ver.2.0 / M3 Ver.1.1)
Switch

Switch

Number

Name

Pin1

Pin2

Pin3

Pin4

Pin5

Pin6

Pin7

Pin8

SW1

QSPI-A

OFF

SW2

QSPI-B

OFF

SW3

QSPI-C

Set(ON)

SW13

QSPI-D

set

SW4

SOFTSW

OFF

SW5

GPIO/PWM1

set

SW6

GPIO/PWM2

set

SW7

DDRBKUP-A

set*1

SW8

DDRBKUP-B

OFF

SW9

TRST#

SW10

MODESW-A

SW11

MODESW-B

SW12

OFF

set

OFF

ON*2

MODESW-C

OFF

SW14

SSI78-M/S

set

SW15

USB-SW

set

SW16

SDHI0/DBG2-A

set

JP2

SDHI0/DBG2-B

set

SW28

VDDQVA_SD0

OFF

SW17

LVDS

set

SW20

TACTSW0

SW21

TACTSW1

SW22

TACTSW2

SW23

ACCSW

SW27

PRESET#

SW29

MIPI-SW

SW30

PHYAD

OFF

*1: In after Yocto BSP v2.12.0, it is necessary to enable BKUP_TRG signal for Suspend to RAM, please set SW7 Pin-1.
Rev.2.23.0
Aug. 29, 2017

Page 5 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Environmental Requirement

*2: If debugger is connected, please set SW11-4pin off.

Table 3 setting of Dip switches (R-Car H3 Ver.1.1)
Switch

Switch

Number

Name

Pin1

Pin2

Pin3

Pin4

Pin5

Pin6

Pin7

Pin8

SW10

MODESW-A

OFF

SW11

MODESW-B

OFF

ON*1

SW12

MODESW-C

OFF

Other

Same as H3 Ver.2.0

Pin5

Pin6

Pin7

Pin8

*1: If debugger is connected, please set SW11-4pin off.

Table 4 setting of Dip switches (R-Car H3 Ver.1.0)
Switch
Number

Switch

Pin1

Pin2

Pin3

Pin4

Name

SW10

MODESW-A

OFF

SW11

MODESW-B

OFF

ON*1

SW12

MODESW-C

OFF

Other

Same as H3 Ver.2.0

Pin5

Pin6

Pin7

Pin8

*1: If debugger is connected, please set SW11-4pin off.

Table 5 setting of Dip switches (R-Car M3 Ver.1.0)
Switch

Switch

Number

Name

Pin1

Pin2

Pin3

Pin4

SW10

MODESW-A

OFF

SW11

MODESW-B

OFF

ON*1

SW12

MODESW-C

OFF

Other

Same as H3 Ver.2.0

*1: If debugger is connected, please set SW11-4pin off.

Rev.2.23.0
Aug. 29, 2017

Page 6 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

Building

Building Instructions

You can build BSP by using Yocto Project. Please execute following steps in ${WORK} directory on Linux Host PC.
Filesystem by making following instruction is the one for testing current BSP package in Renesas. Please note that
Renesas has not been verified with any other build configuration or modified recipes except “core-image-weston”
configuration which is based on upstream Yocto Project deliverables and some additional packages correspond to
gstreamer.
Note) Renesas executed following instructions with clean ${WORK}/build directory. You may use wipe-sysroot and/or
bitbake -c cleansstate to reflect modifications of configuration files for Recipe as in open source Yocto Project’s
standards, however Renesas strongly recommend to use recipe with clean ${WORK}/build directory for each
configurations because there are some implicit dependency for header files exist to keep compatibility between
application build scheme with/without proprietary software.
Step 1 installation of required commands
Ubuntu is used as Linux Host PC since Yocto Project Quick Start specifies Ubuntu as one of the distribution. In case of
that you can install the required commands as follows.
Please refer to http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html for detail.
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
build-essential chrpath socat libsdl1.2-dev xterm python-crypto

Note) There is a bitbake command in ${WORK}/poky/scripts/. Command path is available after step 6.
Note) When you use terminal interactions to build such as menuconfig under non-X terminal (ssh, etc.), please install
“screen” command package to Host PC
Note) Please set up user name and e-mail in Git. You can set up with ‘git config --global’. Please refer to online manual
for git command.

Step 2 download of required files
Required files (poky, meta-linaro) are downloaded by git clone.
$
$
$
$
$

cd ${WORK}
git clone git://git.yoctoproject.org/poky
git clone git://git.linaro.org/openembedded/meta-linaro.git
git clone git://git.openembedded.org/meta-openembedded
git clone git://github.com/renesas-rcar/meta-renesas.git

Rev.2.23.0
Aug. 29, 2017

Page 7 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

Building

Step 3 checkout
Please checkout available version of each git clone.
$ cd ${WORK}/poky
$ git checkout -b tmp yocto-2.1.2
$ cd ${WORK}/meta-linaro
$ git checkout -b tmp 2f51d38048599d9878f149d6d15539fb97603f8f
$ cd ${WORK}/meta-openembedded
$ git checkout -b tmp 55c8a76da5dc099a7bc3838495c672140cedb78e
$ cd ${WORK}/meta-renesas
$ git checkout -b tmp 52a5df36b4cd2ca0f5ec8eab9446f4f128ef727c

Note) tmp is a temporary name of a local branch. We can use checkout command without branch. Please note that HEAD
refers directly to commit (detached HEAD).

Step 4 apply patch file
Because Renesas proprietary software is using linaro-GCC, it needs to apply. Please perform patch command.
$ cd ${WORK}/meta-renesas
$ export PATCH_DIR=meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc
$ patch -p1 < \
${PATCH_DIR}/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch

$ unset PATCH_DIR

Rev.2.23.0
Aug. 29, 2017

Page 8 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

3.1

Building

In case of BSP + 3D Graphics + Multimedia package

When you use proprietary Multimedia and 3D Graphics software from Renesas, please execute as following steps.
Otherwise please skip to section 3.2 or 3.3.
Step 5 copy proprietary software into recipe directory structure
To use licensed 3D graphics software and Multimedia package from Renesas, please copy deliverables of those software
into recipe directory structure. Renesas provide shell script to copy those software.
Copy All Proprietary Software Packages to ${PKGS_DIR}:
$ mkdir ${PKGS_DIR}
$ cp ${PKGS_DIR}
Install them into recipe directory structure by shell script:
$ cd ${WORK}/meta-renesas
$ sh \
meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh \
${PKGS_DIR}
Note) Subdirectory is not supporting in ${PKGS_DIR}. Please store all packages on the root of ${PKGS_DIR}.
Note) Please use regular alphanumeric file name ([A-Za-z0-9_] e.g.) for ${PKGS_DIR} due to restrictions of current
copy script.
Step 6 execute source command
Please execute source command with oe-init-build-env for setting environment.
$ cd ${WORK}
$ source poky/oe-init-build-env
Step 7 copy bblayers.conf and local.conf
Please copy configuration files from deliverables.
$ cp ${WORK}/meta-renesas/meta-rcar-gen3/docs/sample/conf//linaro-gcc/mmp/*.conf ./conf/.
Note) is the one of the following: salvator-x
Step 8 enable 3D Graphics and Multimedia package to install GSX modules
To enable 3D Graphics packages which use GSX, please overwrite local.conf as following instructions or modify
local.conf as descriptions in ${WORK}/meta-renesas/meta-rcar-gen3/README.proprietary
To install GSX kernel module:
Overwrite local.conf
$ cp conf/local-wayland.conf conf/local.conf (For Wayland)

Rev.2.23.0
Aug. 29, 2017

Page 9 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

Building

Step 9 enable Multimedia package
Please modify configurations in ${WORK}/build/conf/local.conf by following instructions
Note) Please refer to ${WORK}/meta-renesas/meta-rcar-gen3/README.proprietary
The following standard multimedia packages are enabled
No.

Functions

Explanation

MMNGR

Memory manager driver & shared libraries

VSPM

VSP driver & FDP driver & shared libraries

VSP2

VSP2 driver

OMX

OMX common parts

To enable optional multimedia functions, please add DISTRO_FEATURES_append to ${WORK}/build/conf/local.conf
as DISTRO_FEATURES_append = “ ”.
Note) These configurations exist near the end of local.conf.
Note) DISTRO_FEATURES_append are commented out by the default. To enable functions, please uncomment it.
For example
[Disable]
#DISTRO_FEATURES_append = " h263dec_lib"
[Enable (default)]
DISTRO_FEATURES_append = " h263dec_lib”

Rev.2.23.0
Aug. 29, 2017

Page 10 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

Building

The following list is package name to enable/disable as optional multimedia functions
No.

Function name

Default
value

h264dec_lib

Enable

h264enc_lib

Disable

h265dec_lib

Disable

mpeg2dec_lib

Disable

mpeg4dec_lib

Disable

vc1dec_lib

Disable

h263dec_lib

Disable

divxdec_lib

Disable

rvdec_lib

Disable

Explanation
H264 decoder library
RTM0AC0000XV264D30SL40C
H264 encoder library
RTM0AC0000XV264E30SL40C
H265 decoder library
RTM0AC0000XV265D30SL40C
MPEG2 decoder library
RTM0AC0000XVM2VD30SL40C
MPEG4 decoder library
RTM0AC0000XVM4VD30SL40C
VC-1 decoder library
RTM0AC0000XVVC1D30SL40C
H263 decoder library
RTM0AC0000XV263D30SL40C
DivX decoder library
RTM0AC0000XVDVXD30SL40C
RealVideo decoder library
RTM0AC0000XVRLVD30SL40C

aaclcdec_lib

Enable

AAC-LC decoder library
RTM0AC0000XAAACD30SL40C

aaclcdec_mdw

Enable

AAC-LC 2ch decoder middleware library
RTM0AC0000ADAACMZ1SL40C

aacpv2dec_lib

Disable

aacPlus V2 Decoder Library
RTM0AC0000XAAAPD30SL40C

aacpv2dec_mdw

Disable

aacPlus V2 Decoder Middleware Library
RTM0AC0000ADAAPMZ1SL40C

mp3dec_lib

Disable

MP3 decoder library
RTM0AC0000XAMP3D30SL40C

mp3dec_mdw

Disable

MP3 decoder middleware library
RTM0AC0000ADMP3MZ1SL40C

wmadec_lib

Disable

WMA decoder library
RTM0AC0000XAWMAD30SL40C

wmadec_mdw

Disable

WMA decoder middleware library
RTM0AC0000ADWMAMZ1SL40C

aaclcenc_lib

Disable

AAC-LC encoder library
RTM0AC0000XAAACE30SL40C

aaclcenc_mdw

Disable

AAC-LC encoder middleware library
RTM0AC0000AEAACMZ1SL40C

flacdec_lib

Disable

FLAC decoder library
RTM0AC0000XAFLAD30SL40C

alacdec_lib

Disable

ALAC decoder library
RTM0AC0000XAALAD30SL40C

Rev.2.23.0
Aug. 29, 2017

Page 11 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions
No.

Function name

Default
value

Building

Explanation

dddec_lib

Disable

Dolby(R) Digital decoder library
RTM0AC0000XADD5D30SL40C

dddec_mdw

Disable

Dolby(R) Digital decoder middleware library
RTM0AC0000ADDD5MZ1SL40C

cmsbcm

Disable

Basic Color Management Middleware for Linux
RTM0AC0000JRCMBCV0SL40C

cmsblc

Disable

CMM3 Backlight Control Middleware for Linux
RTM0AC0000JRCMBLC0SL40C

cmsdgc

Disable

VSP2 Dynamic Gamma Correction Middleware for Linux
RTM0AC0000JRCMDGV0SL40C

adsp

Disable

ADSP Interface for Linux
RCG3AHIFL4001ZDP

avb

Disable

Ether-AVB

Rev.2.23.0
Aug. 29, 2017

Page 12 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

Building

The following list is dependent package name
No.

Function name

Type Name

Dependent Packages

h264dec_lib

RTM0AC0000XV264D30SL40C

RTM0AC0000XVCMND30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

h264enc_lib

RTM0AC0000XV264E30SL40C

RTM0AC0000XVCMNE30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

h265dec_lib

RTM0AC0000XV265D30SL40C

RTM0AC0000XVCMND30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

mpeg2dec_lib

RTM0AC0000XVM2VD30SL40C

RTM0AC0000XVCMND30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

mpeg4dec_lib

RTM0AC0000XVM4VD30SL40C

RTM0AC0000XVCMND30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

vc1dec_lib

RTM0AC0000XVVC1D30SL40C

RTM0AC0000XVCMND30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

h263dec_lib

RTM0AC0000XV263D30SL40C

RTM0AC0000XVCMND30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

divxdec_lib

RTM0AC0000XVDVXD30SL40C

RTM0AC0000XVCMND30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

rvdec_lib

RTM0AC0000XVRLVD30SL40C

RTM0AC0000XVCMND30SL40C
RTM0AC0000XCMCTL30SL40C
RCG3VUDRL4001ZDO

aaclcdec_lib

RTM0AC0000XAAACD30SL40C

RTM0AC0000XCMCTL30SL40C
RTM0AC0000XACMND30SL40C
RTM0AC0000ADAACMZ1SL40C

aaclcdec_mdw

RTM0AC0000ADAACMZ1SL40C

aacpv2dec_lib

RTM0AC0000XAAAPD30SL40C

RTM0AC0000XCMCTL30SL40C
RTM0AC0000XACMND30SL40C
RTM0AC0000ADAAPMZ1SL40C

aacpv2dec_mdw

RTM0AC0000ADAAPMZ1SL40C

mp3dec_lib

RTM0AC0000XAMP3D30SL40C

RTM0AC0000XCMCTL30SL40C
RTM0AC0000XACMND30SL40C
RTM0AC0000ADMP3MZ1SL40C

mp3dec_mdw

RTM0AC0000ADMP3MZ1SL40C

Rev.2.23.0
Aug. 29, 2017

Page 13 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions
No.

Function name

Type Name

Building

Dependent Packages

wmadec_lib

RTM0AC0000XAWMAD30SL40C

RTM0AC0000XCMCTL30SL40C
RTM0AC0000XACMND30SL40C
RTM0AC0000ADWMAMZ1SL40C

wmadec_mdw

RTM0AC0000ADWMAMZ1SL40C

aaclcenc_lib

RTM0AC0000XAAACE30SL40C

RTM0AC0000XCMCTL30SL40C
RTM0AC0000XACMND30SL40C
RTM0AC0000AEAACMZ1SL40C

aaclcenc_mdw

RTM0AC0000AEAACMZ1SL40C

flacdec_lib

RTM0AC0000XAFLAD30SL40C

RTM0AC0000XCMCTL30SL40C
RTM0AC0000XACMND30SL40C
RCG3AFLDL4001ZDO

alacdec_lib

RTM0AC0000XAALAD30SL40C

RTM0AC0000XCMCTL30SL40C
RTM0AC0000XACMND30SL40C
RCG3AFLDL4001ZDO

dddec_lib

RTM0AC0000XADD5D30SL40C

RTM0AC0000XCMCTL30SL40C
RTM0AC0000XACMND30SL40C
RTM0AC0000ADDD5MZ1SL40C

dddec_mdw

RTM0AC0000ADDD5MZ1SL40C

cmsbcm

RTM0AC0000JRCMBCV0SL40C

cmsblc

RTM0AC0000JRCMBLC0SL40C

cmsdgc

RTM0AC0000JRCMDGV0SL40C

adsp

RCG3AHIFL4001ZDP

RCG3AHPDL4001ZDO
RCG3AHFWN0101ZDP

avb

Rev.2.23.0
Aug. 29, 2017

Page 14 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

Building

Step 10 select SoC
To select SoC, please set SOC_FAMILY to ${WORK}/build/conf/local.conf as SOC_FAMILY = “”.
[H3]
SOC_FAMILY = "r8a7795"
[M3]
SOC_FAMILY = "r8a7796"

Step 11 building with bitbake
Please build as follows. The file system (core-image-weston-.tar.bz2) is created in
${WORK}/build/tmp/deploy/images// directory.
Note) is the one of the following: salvator-x
Note) Build by bitbake might need several hours under the influence of Linux Host PC performance and network
environment.
Note) The bitbake downloads some package while building. Then the bitbake might stop for network timeout or link
error. In this case, please get applicable package in ${WORK}/build/downloads directory whenever build stops by wget
command, or please review timeout definitions of package download (wget, etc.) described in
${WORK}/poky/meta/conf/bitbake.conf.
$ cd ${WORK}/build
$ bitbake core-image-weston (for Wayland)

Rev.2.23.0
Aug. 29, 2017

Page 15 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

3.2

Building

In case of BSP + 3D Graphics (without Multimedia package)

When you use licensed 3D Graphics software but will not use proprietary Multimedia software from Renesas, please
execute as following steps. Otherwise please skip to section 3.3.
Step 5 copy proprietary software into recipe directory structure
To use licensed 3D graphics software and Multimedia package from Renesas, please copy deliverables of those software
into recipe directory structure. Renesas provide shell script to copy those software.
Copy All Proprietary Software Packages to ${PKGS_DIR}:
$ mkdir ${PKGS_DIR}
$ cp ${PKGS_DIR}
Install them into recipe directory structure by shell script:
$ cd ${WORK}/meta-renesas
$ sh \
meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh \
${PKGS_DIR}
Note) Subdirectory is not supporting in ${PKGS_DIR}. Please store all packages on the root of ${PKGS_DIR}.
Note) Please use regular alphanumeric file name ([A-Za-z0-9_] e.g.) for ${PKGS_DIR} due to restrictions of current
copy script.
Step 6 execute source command
Please execute source command with oe-init-build-env for setting environment.
$ cd ${WORK}
$ source poky/oe-init-build-env

Step 7 copy bblayers.conf and local.conf
Please copy configuration files from deliverables.
$ cp ${WORK}/meta-renesas/meta-rcar-gen3/docs/sample/conf//linaro-gcc/gfx-only/*.conf ./conf/.
Note) is the one of the following: salvator-x

Step 8 enable 3D Graphics package to install GSX modules
To enable 3D Graphics packages which use GSX, please overwrite local.conf as following instructions or modify
local.conf as descriptions in ${WORK}/meta-renesas/meta-rcar-gen3/README.proprietary

Rev.2.23.0
Aug. 29, 2017

Page 16 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

Building

To install GSX kernel module:
Overwrite local.conf
$ cp conf/local-wayland.conf conf/local.conf (For Wayland)
Step 9 select SoC
To select SoC, please set SOC_FAMILY to ${WORK}/build/conf/local.conf as SOC_FAMILY = “”.
[H3]
SOC_FAMILY = "r8a7795"
[M3]
SOC_FAMILY = "r8a7796"

Step 10 building with bitbake
Please build as follows. The file system (core-image-weston-.tar.bz2) is created in
${WORK}/build/tmp/deploy/images// directory.
Note) is the one of the following: salvator-x
Note) Build by bitbake might need several hours under the influence of Linux Host PC performance and network
environment.
Note) The bitbake downloads some package while building. Then the bitbake might stop for network timeout or link
error. In this case, please get applicable package in ${WORK}/build/downloads directory whenever build stops by wget
command, or please review timeout definitions of package download (wget, etc.) described in
${WORK}/poky/meta/conf/bitbake.conf.
$ cd ${WORK}/build
$ bitbake core-image-weston (for Wayland)

Rev.2.23.0
Aug. 29, 2017

Page 17 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

3.3

Building

In case of BSP Only

When you will not use neither proprietary Multimedia software nor licensed 3D Graphics software from Renesas, please
execute as following steps.
Step 5 execute source command
Please execute source command with oe-init-build-env for setting environment.
$ cd ${WORK}
$ source poky/oe-init-build-env

Step 6 copy bblayers.conf and local.conf
Please copy configuration files from deliverables.
$ cp ${WORK}/meta-renesas/meta-rcar-gen3/docs/sample/conf//linaro-gcc/bsp/*.conf ./conf/.
Note) is the one of the following: salvator-x
Note) core-image-weston is not supported even though local-wayland.conf is provided.

Step 7 select SoC
To select SoC, please set SOC_FAMILY to ${WORK}/build/conf/local.conf as SOC_FAMILY = “”.
[H3]
SOC_FAMILY = "r8a7795"
[M3]
SOC_FAMILY = "r8a7796"

Step 8 building with bitbake
Please build as follows. The file system (core-image-minimal-.tar.bz2) is created in
${WORK}/build/tmp/deploy/images// directory.
Note) is the one of the following: salvator-x
Note) Build by bitbake might need several hours under the influence of Linux Host PC performance and network
environment.
Note) The bitbake downloads some package while building. Then the bitbake might stop for network timeout or link
error. In this case, please get applicable package in ${WORK}/build/downloads directory whenever build stops by wget
Rev.2.23.0
Aug. 29, 2017

Page 18 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Instructions

Building

command, or please review timeout definitions of package download (wget, etc.) described in
${WORK}/poky/meta/conf/bitbake.conf.
$ cd ${WORK}/build
$ bitbake core-image-minimal

Rev.2.23.0
Aug. 29, 2017

Page 19 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide 4.
IPL/Secure

Writing of IPL/Secure

4.1

Writing data
Filename

Writing of

Program Top Address

Flash Save Address

Description

bootparam_sa0.srec

0xE6320000

0x000000

Loader(Boot parameter)

bl2-.srec

0xE6304000

0x040000

Loader

cert_header_sa6.srec

0xE6320000

0x180000

Loader(Certification)

bl31-.srec

0x44000000

0x1C0000

ARM Trusted Firmware

tee-.srec

0x44100000

0x200000

OP-Tee

u-boot-elf.srec

0x50000000

0x640000

U-Boot

Note) Please refer to Chapter 5 for U-Boot.

4.2
a)

Dip-Switch
QSPI Mode

Switch

Number

Name

Pin1

Pin2

Pin3

Pin4

Pin5

Pin6

Pin7

Pin8

SW1

QSPI-A

SW2

QSPI-B

SW3

QSPI-C

set(OFF)

SW10

MODESW-A

OFF

Pin5

Pin6

Pin7

Pin8

Refer to 2.2

b) Hyper Flash Mode
Switch

Switch

Number

Name

Pin1

Pin2

Pin3

Pin4

SW1

QSPI-A

OFF

SW2

QSPI-B

OFF

SW3

QSPI-C

set(ON)

SW10

MODESW-A

4.3

Refer to 2.2

How to write

Please connect R-Car H3/M3 System Evaluation Board, Windows Host PC with terminal software for console and Linux
Host PC.
In case of R-Car H3/M3, Ethernet connector is CN22, serial connector is CN25.
Step 1 connect cable

Rev.2.23.0
Aug. 29, 2017

Page 20 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide 4.
IPL/Secure

Writing of

Connect USB Host connector of Windows Host PC that is virtual COM port to CN25 of R-Car H3/M3 System
Evaluation Board with USB cable for displaying console.

Step 2 setting the terminal software
Activate the Terminal Software on Windows Host PC. Configure the Terminal Software on Windows Host PC as
followings. Please refer to Table 1 about the VCP driver for making a USB host connector into a virtual COM port
[setting value] baud rate 115200, 8bit data, parity none, stop 1 bit, flow control none.

Step 3 write data file to Hyper Flash
A file is written in Hyper Flash in the following procedures.






Set dip switch “QSPI Mode”.
Reset board then start mini monitor.
Set dip switch (Select Hyper Flash)
SW1: ALL OFF
SW2: ALL OFF
SW3: ON
Note) SW10 does not need to change.
Execute xls2 command (load program to flash).
SALVATOR MiniMonitor V0.05 2015.08.25
Work Memory SystemRAM (H'E6328000-H'E632FFFF)
>xls2
===== Qspi/HyperFlash writing of Gen3 Board Command =============
Load Program to Spiflash
Writes to any of SPI address.
Please select,FlashMemory.
1 : QspiFlash
(U5 : S25FS128S)
2 : QspiFlash Board (CN3: S25FL512S)
3 : HyperFlash
(SiP internal)
Select (1-3)>









Select HyperFlash. Input “3”.
After "SW31 ON! Setting OK? (Push Y key) [In the case of Kriek Board]" is displayed, input "y". (R-Car M3 only)
After "SW1 SW2 All OFF! Setting OK? (Push Y key)" is displayed, input "y".
After "SW3 ON! Setting OK? (Push Y key)" is displayed, input "y".
After "Please Input Program Top Address" is displayed, input Program Top Address in 4.1 and "Enter".
After "Please Input Qspi/HyperFlash Save Address" is displayed, input Flash Save Address in 4.1 and "Enter".
After "Please send ! ('.' & CR stop load)" is displayed, In case of Tera Term, transmit u-boot-elf.srec by "file -> file
transmission(S)".

Rev.2.23.0
Aug. 29, 2017

Page 21 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide 4.
IPL/Secure






Writing of

If there are some data in writing area, "SPI Data Clear(H'FF) Check :H'00000000-0003FFFF Clear OK?(y/n)" is
displayed. Then input "y".
After "SAVE SPI-FLASH ....... complete!" is displayed, the prompt returns. It means finish.
Please repeat the xls2 command, if other files are written.
Power OFF
Set dip switch to “Hyper Flash Mode”.
Note) SW1, SW2, and SW3 are already Hyper Flash mode. Please set SW10.

4.4

IPL/Secure write

Please write the file described in Chapter 4.1 to Hyper Flash.
The data file is stored in the ${WORK}/build/tmp/deploy/images/ directory.

Rev.2.23.0
Aug. 29, 2017

Page 22 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
starting of U-Boot and Linux

Confirm

Confirm starting of U-Boot and Linux

Please connect R-Car H3/M3 System Evaluation Board, Windows Host PC with terminal software for console and Linux
Host PC with TFTP and NFS server as Figure 1. Then please confirm normal starting of U-Boot and Linux with
following step. Please refer to 2.2 for dip switch setting.
In case of R-Car H3/M3, Ethernet connector is CN22, serial connector is CN25, D-Sub connector is CN15.

Step 1 setting Linux Host PC
Please install TFTP server and NFS server in Linux Host PC with apt-get command and so on. Please set
/etc/xinetd.d/tftp of TFTP server and /etc/exports of NFS server according to your environment.

Step 2 connect cable
Connect USB Host connector of Windows Host PC that is virtual COM port to CN25 of R-Car H3/M3 System
Evaluation Board with USB cable for displaying console.

Step 3 setting the terminal software
Activate the Terminal Software on Windows Host PC. Configure the Terminal Software on Windows Host PC as
followings. Please refer to Table 1 about the VCP driver for making a USB host connector into a virtual COM port.
[setting value] baud rate 115200, 8bit data, parity none, stop 1 bit, flow control none.

Step 4 write U-Boot to Hyper Flash
Filename

Program Top Address

Flash Save Address

Description

0x50000000

0x640000

U-Boot

u-boot-elf.srec

The data file is stored in the ${WORK}/build/tmp/deploy/images/ directory.
Refer to Chapter 4.3 Step3 for write procedure.

Step 5 set U-Boot environment variables
Please refer to 2.2 for dip switch setting.
Please start U-Boot by board reset. Please set and save environment variable as follows.

Rev.2.23.0
Aug. 29, 2017

Page 23 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
starting of U-Boot and Linux

Confirm

=> setenv ethaddr xx:xx:xx:xx:xx:xx
=> setenv ipaddr 192.168.0.20
=> setenv serverip 192.168.0.1
=> setenv bootcmd 'tftp 0x48080000 Image;tftp 0x48000000 Image-;booti 0x48080000 - 0x48000000'

Note) is the following: r8a7795, r8a7796
Note) For R-Car H3 (SOC_FAMILY r8a7795), the device trees are as follow:
-

Image-r8a7795-es1-salvator-x.dtb: for R-Car H3 Ver.1.0 and Ver.1.1.

Image-r8a7795-salvator-x.dtb: for R-Car H3 Ver.2.0.

Image-r8a7795-salvator-xs.dtb: for R-Car H3 Ver.2.0 (RTP0RC7795SIPB0012S).

For R-Car M3 (SOC_FAMILY r8a7796), the device trees are as follow:
-

Image-r8a7796-salvator-x.dtb: for R-Car M3 Ver.1.0 and Ver.1.1.

Image-r8a7796-salvator-xs.dtb: for R-Car M3 Ver.1.0 and Ver.1.1 (RTP0RC7795SIPB0012S).

Step 6 change the bootargs by U-Boot
To change bootargs which passed to the kernel in boot sequence, please modify it by “setenv bootargs” command of UBoot.
=> setenv bootargs 'rw root=/dev/nfs nfsroot=192.168.0.1:/export/rfs
ip=192.168.0.20'
Note) When the screen saver starts, the system halts. By adding “consoleblank=0” in bootargs, this problem is avoidable.
Please refer to BSP release note for details.

Step 7 save environment variables
=> saveenv

Step 8 set file system
Please extract file system (core-image- weston-.tar.bz2). Please export /export directory of NFS
server.
Rev.2.23.0
Aug. 29, 2017

Page 24 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
starting of U-Boot and Linux

Confirm

$ mkdir /export/rfs
$ cd /export/rfs
$ sudo tar xvf core-image-weston(minimal)-.tar.bz2
Note) is the following: salvator-x.

Step 9 start Linux
After board reset, U-Boot is started. After countdown, Linux boot messages are displayed. Please confirm login prompt
after Linux boot messages.
Note) When MAC Address is rewritten, it is necessary to reset.
Note) In core-image-weston, please connect input device (keyboard, mouse) to USB port (CN10). In R-Car M3, only
CN10 of USB2_1 port can be used.

Rev.2.23.0
Aug. 29, 2017

Page 25 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide 6.
Toolchains

Exporting

Exporting Toolchains

Please refer Documents from Yocto Project to export Toolchains such as
http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html.
And please use build target of bitbake as “core-image-weston-sdk -c populate_sdk” to generate package.
Note) When you use “ld” directly but not via gcc (in case of building Kernel, Driver or U-Boot), please disable
LDFLAGS with ‘unset LDFLAGS’. Furthermore, in kernel build, ‘make menuconfig’ occurs error by ncurses. In this
case, please disable PKG_CONFIG_PATH with ‘unset PKG_CONFIG_PATH’.
Note) Please do not use same shell environment to other compilation/debugging purpose (also make menuconfig of linux
kernel, e.g.) but cross compilation for R-Car H3/M3 which shell environment with “source” command to setup
environment variables for the SDK. Because some environment variables for cross compilation interferes execution of
other tools on the same shell environment.
Example of instruction:
In following examples, it’s assumed that it’s already extracted and prepared recipe environment such as in the
instructions of Section 3 (must done just before execution of bitbake, at least). You may reuse ${WORK}/build while
you reuse same configuration after executing bitbake as in Section 3 for this purpose.

Step 1 configure architectures of Host PC which are installed this toolchain
Please modify SDKMACHINE description on ${WORK}/build/conf/local.conf

On ${WORK}/build/conf/local.conf
# This variable specified the architecture to build SDK/ADT items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host.
# Supported values are i686 and x86_64
#SDKMACHINE ?= "i686"
SDKMACHINE ?= "x86_64"

Note) 32bit Ubuntu 14.04 is not supported.

Rev.2.23.0
Aug. 29, 2017

Page 26 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide 6.
Toolchains

Exporting

Step 2 building toolchain package with bitbake
$ cd ${WORK}/build
$ bitbake core-image-weston-sdk -c populate_sdk
$ cp tmp/deploy/sdk/poky-glibc-x86_64-core-image-weston-sdk- aarch64toolchain-2.1.2.sh (shared dir. where able to access from each Host PCs)

Note) Please perform “bitbake core-image-minimal -c populate_sdk” in BSP Only.
Step 3 Install toolchain on each Host PCs
$ sudo (shared dir. where able to access from each Host PCs)/poky-glibcx86_64-core-image-weston-sdk-aarch64-toolchain-2.1.2.sh
[sudo] password for (INSTALL person): (password of your account)
Enter target directory for SDK (default: /opt/poky/2.1.2): (just a return)
Extracting SDK...done
Setting it up...done
SDK has been successfully set up and is ready to be used.

Step 4 setup environment variables for each compilation on each Host PCs
Please setup environment variables as follows or integrate set-up sequence into your build script or Makefile.
$
$
$
$

cd (Your working directory)
source /opt/poky/2.1.2/environment-setup-aarch64-poky-linux
export LDFLAGS=””
${CC} (Your source code).c …..

Rev.2.23.0
Aug. 29, 2017

Page 27 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
map

Memory

Memory map

Following Figure 2 to Figure 6 show memory map of this R-Car H3/M3 Linux BSP package.
Note)
-

The volume of SDRAM is total 4GB.

2GB from 0x00_4000_0000 to 0x00_BFFF_FFFF is a shadow area from 0x04_0000_0000 to 0x04_7FFF_FFFF.

The following regions are used as a secure region. It doesn’t allow U-Boot and kernel to access those regions.



63MB from 0x00_43F0_0000 to 0x00_47DF_FFFF in SDRAM



16KB from 0x00_E630_0000 to 0x00_E630_3FFF in System RAM

In case the configuration of BSP + 3D Graphics + Multimedia package, it doesn't allow to store any data in "CMA
for Lossy comp" (default: 0x00_5400_0000 - 0x00_56FF_FFFF) region which is for media playback before kernel
boots up. Any data stored in this region are read through the decompression module in AXI-Bus, so a normal data
(not a decoded frame) will be corrupted.

Rev.2.23.0
Aug. 29, 2017

Page 28 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
map

Memory

Physical Address
0x00_4000_0000

0x0

BSC

0x00_2000_0000
0x00_3000_0000
0x00_4000_0000

Option

Reserved

Secure
Region

PCI-exp
SDRAM 1GB

Certification
ARM Trusted Firmware
OP-Tee

Legacy

0x00_8000_0000

0x00_43F0_0000

0x00_47E0_0000
0x00_4800_0000

N/A

0x00_C000_0000

Reserved

0x00_E000_0000

IO area

0x01_0000_0000

Shadow area

～
～
0x04_0000_0000
0x04_4000_0000

0x00_5000_0000

U-Boot

～
SDRAM 1GB
N/A

0x04_8000_0000
N/A

Load by
IPL

0x05_0000_0000

SDRAM 1GB

0x05_4000_0000
0x00_8000_0000
N/A

0x06_0000_0000

SDRAM 1GB

0x06_4000_0000

System RAM
N/A

0x00_E630_0000
Secure
Region
Boot parameter

Load by Boot
ROM program

Hyper Flash
0x0

0x040000

IPL
0x07_0000_0000

0x180000
SDRAM 1GB

0x1C0000

0x07_4000_0000

0x200000
0x640000

N/A

Boot parameter
IPL
Certification
ARM Trusted
Firmware
OP-Tee
U-Boot

0x08_0000_0000

Figure 2. H3 memory map (Boot)
Rev.2.23.0
Aug. 29, 2017

Page 29 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
map

Memory

Physical Address
0x00_4000_0000

0x0

BSC

0x00_2000_0000
0x00_3000_0000
0x00_4000_0000

Option

Reserved

Secure
Region

PCI-exp
SDRAM 1GB

Certification
ARM Trusted Firmware
OP-Tee

Legacy

0x00_8000_0000

dtb

N/A

0x00_C000_0000

Kernel Image

Reserved

0x00_E000_0000

0x00_43F0_0000

0x00_47E0_0000
0x00_4800_0000
0x00_4808_0000

IO area

0x01_0000_0000

Shadow area

～
0x04_0000_0000
0x04_4000_0000

～
SDRAM 1GB
N/A

0x04_8000_0000
N/A
0x05_0000_0000

CMA for Lossy comp
(48MB)
Reserved (16MB)

0x00_5400_0000
0x00_5700_0000
0x00_5800_0000

CMA
(384MB)

SDRAM 1GB

0x00_7000_0000
CMA for MMP
(256MB)

0x05_4000_0000

0x00_8000_0000
N/A

0x06_0000_0000
SDRAM 1GB
0x06_4000_0000

N/A

0x07_0000_0000

SDRAM 1GB

0x07_4000_0000

N/A

0x08_0000_0000

Figure 3. H3 memory map (Linux)
Rev.2.23.0
Aug. 29, 2017

Page 30 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
map

Memory

Physical Address
0x00_4000_0000

0x0

BSC

0x00_2000_0000
0x00_3000_0000
0x00_4000_0000

Option

Reserved

Secure
Region

PCI-exp
SDRAM 2GB

Certification
ARM Trusted Firmware
OP-Tee

Legacy

0x00_C000_0000

0x00_43F0_0000

0x00_47E0_0000
0x00_4800_0000

Reserved

0x00_E000_0000

IO area

0x01_0000_0000

Shadow area

～
0x04_0000_0000

0x00_5000_0000

U-Boot

～
SDRAM 2GB

0x04_8000_0000
Load by

N/A

IPL
0x05_0000_0000

N/A

0x06_0000_0000

SDRAM 2GB
0x00_C000_0000

System RAM
0x06_8000_0000
N/A

0x00_E630_0000
Secure
Region
Boot parameter

Load by Boot
ROM program

Hyper Flash
0x0

0x040000

IPL
0x180000

0x07_0000_0000

0x1C0000
0x200000
N/A

0x640000

Boot parameter
IPL
Certification
ARM Trusted
Firmware
OP-Tee
U-Boot

0x08_0000_0000

Figure 4. M3 memory map (Boot)
Rev.2.23.0
Aug. 29, 2017

Page 31 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
map

Memory

Physical Address
0x00_4000_0000

0x0

BSC

0x00_2000_0000
0x00_3000_0000
0x00_4000_0000

Option

Reserved

Secure
Region

PCI-exp
SDRAM 2GB

Certification
ARM Trusted Firmware
OP-Tee

Legacy

0x00_C000_0000

dtb
Kernel Image

Reserved

0x00_E000_0000

0x00_43F0_0000

0x00_47E0_0000
0x00_4800_0000
0x00_4808_0000

IO area

0x01_0000_0000

Shadow area

～
0x04_0000_0000

～
SDRAM 2GB
CMA for Lossy comp
(48MB)
Reserved (16MB)

0x04_8000_0000

0x00_5400_0000
0x00_5700_0000
0x00_5800_0000

CMA
(384MB)

N/A
0x05_0000_0000

0x00_7000_0000
CMA for MMP
(256MB)
0x00_8000_0000

N/A

0x06_0000_0000

SDRAM 2GB

0x00_C000_0000
0x06_8000_0000
N/A
0x07_0000_0000

N/A

0x08_0000_0000

Figure 5. M3 memory map (Linux)
Rev.2.23.0
Aug. 29, 2017

Page 32 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
map

Memory

Note)
- Kernel region is assigned by Kernel device tree arch/arm64/boot/dts/renesas/xxx.dts and totally mapped to 4GB.
-

Kernel region consists of 4 parts: (R-Car H3)


896MB from 0x00_4800_0000 to 0x00_7FFF_FFFF



1GB from 0x05_0000_0000 to 0x05_3FFF_FFFF



1GB from 0x06_0000_0000 to 0x06_3FFF_FFFF



1GB from 0x07_0000_0000 to 0x07_3FFF_FFFF

Kernel region consists of 2 parts: (R-Car M3)


1920MB from 0x00_4800_0000 to 0x00_BFFF_FFFF



2GB from 0x06_0000_0000 to 0x06_7FFF_FFFF

There are three types of CMA regions.
They are defined in device tree (arch/arm64/boot/dts/renesas/xxxx.dts).


Default CMA region: It is for kernel, general drivers and multimedia package.
linux,cma {
compatible = "shared-dma-pool";
reusable;
reg = <0x00000000 0xXXXXXXXX 0x0 0xYYYYYYYY>;
linux,cma-default;
};
0xXXXXXXXX is start address of CMA region.
0xYYYYYYYY is size of CMA region.

Note)





128 MB in this CMA (384MB) is reserved for kernel and general drivers, and the remaining
256 MB is reserved for multimedia package.



The CMA region can be adjusted by changing the start address and the size.



Should take care of the lack of memory allocated by kernel and general drivers when reducing
the region size.

CMA region for MMP: It is for multimedia package (specific H/Ws).
mmp_reserved: linux,multimedia {
compatible = "shared-dma-pool";
reusable;
reg = <0x00000000 0xXXXXXXXX 0x0 0xYYYYYYYY>;
};
0xXXXXXXXX is start address of CMA region.
0xYYYYYYYY is size of CMA region.

Rev.2.23.0
Aug. 29, 2017

Page 33 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
map

Memory

Note)



Refer to User’s manual of Memory Manager in order to change CMA region for MMP.

CMA region for Lossy comp: It is for storing data compressed by Frame Compression Near Lossless (FCNL)
for media playback.
lossy_decompress: linux,lossy_decompress {
no-map;
reg = <0x00000000 0xXXXXXXXX 0x0 0xYYYYYYYY>;
};
0xXXXXXXXX is start address of CMA region.
0xYYYYYYYY is size of CMA region.

Note)



Refer to User’s manual of IPL in order to change CMA region for Lossy comp.

0x0

Virtual Address

User
(256TB)

0x0001_0000_0000_0000

N/A

0xFFFF_0000_0000_0000
vmalloc
vmemmap
･･･

Kernel
(256TB)

Kernel
0xFFFF_FFFF_FFFF_FFFF

･･･

Figure 6. H3/M3 memory map (Virtual)
Note)
- Kernel uses 4KB page size (VA_BITS=48) and 4 levels of translation tables. Both regions of User and Kernel
are 256TB. Refer to Documentation/arm64/memory.txt.
-

Detail information about kernel memory map in virtual address space, refer to User’s manual of Kernel.

Rev.2.23.0
Aug. 29, 2017

Page 34 of 35

CONFIDENTIAL
R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
command

U-Boot

U-Boot command

Please refer to U-Boot user's manual about available U-Boot command for R-Car H3/M3 Linux BSP. The help or “?”
command shows U-Boot command list, but be careful that it includes some unsupported command.

Rev.2.23.0
Aug. 29, 2017

Page 35 of 35

CONFIDENTIAL
REVISION HISTORY
Rev.

Linux Interface Specification Yocto recipe Start-Up Guide
User’s Manual: Software

Date

Description
Page

Summary

0.10

Sep 07. 2015



First Edition for Yocto Recipe Package with YP1.8, based on Start-Up Guide Rev 1.30
for Kernel 3.4 LTSI

0.20

Sep 30. 2015

1 Modified URL of U-Boot and Linux source code.

3 Deleted description about core-image-x11

3 step2 Changed git repository URL

3.2 Added note about not support 3D graphics package
3.2 step5,7 Changed command process

12
21, 22
0.30

Oct 30 2015

4.1 Changed U-Boot filename. u-boot.srec -> u-boot-elf.srec
7 Modified memory map (Fig2, 3)

1.1 Modified document version

2.1 Updated table1

2.1 Updated Figure1

3 Modified checkout commit id
3 step4 Updated apply patch command

8-12

3.1 Added description build procedure for MMP and 3D Graphics

4.4 Deleted note

5 step6 Added mem=2048 to bootargs
5 step8 Added note

19-21
22

6 Modified SDK revision 1.8 -> 1.8.1
7 Modified the description of the address range.
0x00_C000_0000 -> 0x00_BFFF_FFFF
7 Modified the address range and size of a secure region.

7 Modified the address of System RAM.
0x00_E630_0000 -> 0x00_E632_0000
7 Modified the load destination of Certification in HyperFlash.
System RAM -> SDRAM

24, 25

7 Modified memory map (Fig3) and update note about CMA
7 Added note about specifying mem=2048M
7 Added note about 3D graphics region

0.40

Nov 27 2015

7 Separated virtual memory map (Fig4) and note about virtual memory

3 Modified checkout commit id
3 step4 Updated apply patch command

5 step6 Added note about adding consoleblank=0 in bootargs
5 step7 Added description saveenv command
5 step9 Modified start Linux procedure

0.50

Dec 25 2015

3 step1 added python-crypto
3 setp2 added meta-openembedded

0.61

Jan 25 2016

3 Modified checkout commit id

5 step5 deleted note

5 step9 added USB channel number

3 Modified checkout commit id
3 step4 Changed patch command

3.1 step10 Fixed typo in captor name
C-1

CONFIDENTIAL
3.1 step10 Deleted note for mem=2048M in bootargs
12

3.2 step9 Deleted note for mem=2048M in bootargs

4.1 Changed Hex notation. 0xXXXX -> H’XXXX

5 step6 Deleted mem=2048M in bootargs
5 step9 Add note about XDG_RUNTIME_DIR

19-21
0.70

Feb 25 2016

Changed SDK version to 2.0 from 1.8.1

6 step3 Add note about overwrite installation

1.1 Modified document version

3 Modified checkout commit id

3.1 step5 Renewed description

3.2 step5 Renewed description

5 step8 Deleted console setting from bootargs
5 step9 Add note about writing MAC address

19-21
0.80

Mar 25 2016

5,6
8
10,11

0.90

Apr 25 2016

Changed SDK version to 2.0.1 from 2.0
2.2 Add R-Car H3 Ver.1.1 and changed setting value of SW11-4pin in Ver.1.0
3 Modified checkout commit id
3.1 step9 Add Type name of MMP and dependence package list

5 Deleted note

7 Modified memory map (Fig3) and remove the 3D Graphics specific region

Deleted the description of “mem=” and update Kernel region

all

Added description for R-Car M3. For example, R-Car H3 -> R-Car H3/M3

1.1 Modified document version
1.1 Deleted “R-Car Series, 3rd Generation Electorical Characteristics”

2.2 Add table4 for R-Car M3

3 Modified checkout commit id

3.1 Added note for R-Car M3

11-12

2.9.0

May 25 2016

3.1 step10 Added select SoC

3.2 step9 Added select SoC

3.3 step7 Added select SoC

5 step5 Changed description setenv command, and added note for SOC_FAMILY

27,28

Modified memory map(Fig2 and Fig3) of H3

29,30

Added memory map(Fig4 and Fig5) of M3

Added description of M3 kernel region

Added description of CMA region for Lossy comp

Changed Revision number rule. Document revision number is Yocto Recipe version.

2.2 Modify table4. RCar M3: DDR1600 -> DDR3200

3 Modified checkout commit id

3.1 deleted note for R-Car M3

11-12
2.10.0

Jun 27 2016

3.1 step9 Updated Multi Media Package list

3.1 step9 Fix TYPO and added aacPlus V2 decoder, ADSP, Ether-AVB

1 Updated linux source code URL

3 Modified checkout commit id

4 step3 added message for SW31 in R-Car M3

23-25
26

6 Changed version of SDK. 2.0.1 -> 2.0.2
Added note of “CMA for Lossy comp” region

C-2

CONFIDENTIAL
26,27,
29
32

Added description of 8KB Secure region from 0xE6300000
Modified memory map(Fig2 and Fig4) of H3/M3
Changed virtual address space from 39-bit to 48-bit
Modified memory map(Fig 6)

2.11.0

2.12.0

Jul 25 2016

Aug 25 2016

1.1 Modified Reference

3 Modified checkout commit id

3 step9 Updated standard multimedia package table

11-14

3 step9 Updated optional multimedia package table

4.2 Updated Dip-Switch setting for R-Car H3 Ver.1.1 and M3 Ver.1.0

5 Added description about refer to Dip-Switch setting

5 step9 Modified note for USB connector. R-Car M3 support only CN10 of USB2_2

23-24

5 Deleted description of 32bit environment

25-26

6 Deleted description of 32bit SDK

7 Updated device tree source code of CMA region for Lossy comp

1 Updated linux source code URL

1.1 Modified Reference

2.1 Updated table 1

2.2 Updated table 2

3 step1 Added note about git config

3 step3 Modified checkout commit id

11-14
25
25-26
2.15.0

Dec 07, 2016

3 step9 Updated optional multimedia package table
6 Updated note about environment variables
6 Deleted description of 32bit SDK

2.2 Added note for setting of dip switch

Table4 Added “*1” for SW11-pin4.

3 Modified checkout commit id

11-14

Fixed Type name of Dolby(R) Digital decoder middleware library

4.1 Changed U-Boot Program Top Address

5 Step 4 Changed U-Boot Program Top Address

23-24

5 Step 5 Changed dtb filename.
Added notes about R-Car H3 device trees names.

27
28-34
2.16.0

Jan 27, 2017

Mar 30, 2017

7 Updated Memory map corresponding to new BSP v3.4.0

3 Modified checkout commit id

3 step9 Updated to use H263 Dec as example

11-14

2.17.0

6 Step 2,3,4 Updated Yocto Project version to 2.1.2

3 step9 Updated optional multimedia package table to add H263 Dec

3 step9 Changed description “Independence package” to “Dependent package”

5 step9 Changed XDG_RUNTIME_DIR value to XDG_RUNTIME_DIR=/run/user/0

6 step1 Fixed typo: SDK_MACHINE -> SDKMACHINE

Changed description of variables from $foo to ${foo}

1.1 Updated related documents.
Added R-CarH3-SiP/M3-SiP System Evaluation Board Salvator-XS Hardware Manual

2.2 Added Setting of Dip switches for R-Car H3 Ver.2.0 (Salvator-X/XS board)

3 Modified checkout commit id

4.1 Change address format from H'xxxx to 0xxxxx

C-3

CONFIDENTIAL
Changed bl2-.srec Program Top Address.
24

Deleted notes about R-Car H3 device trees names.

5 step9 Corrected USB port of M3.
Deleted note about setting XDG_RUNTIME_DIR.

2.19.0

Apr 26, 2017

7 Expanded secure regions in System RAM.

7 Clarified the use of the default CMA region.

Unified the Chip version “Ver/ES/WS” to “Ver.”

Changed “U-boot” to “U-Boot”.

5-6

2.21.0
2.23.0

Jun 28, 2017
Aug 29, 2017

2.2 Updated Setting of Dip switches for R-Car M3 Ver.1.1 (Salvator-X/XS board)

3 Modified checkout commit id.

Changed description of variables from $PKGS_DIR to ${PKGS_DIR}.

Updated notes about R-Car M3 device trees names.

1.1 Modified document version

3 Modified checkout commit id.

Add “CONFIDENTIAL” mark

3 Modified checkout commit id.

C-4

CONFIDENTIAL

Linux Interface Specification Yocto recipe Start-Up Guide
User’s Manual: Software
Publication Date:

Rev.2.23.0 Aug. 29, 2017

Published by:

Renesas Electronics Corporation

http://www.renesas.com

SALES OFFICES
Refer to "http://www.renesas.com/" for the latest and detailed information.
Renesas Electronics America Inc.
2801 Scott Boulevard Santa Clara, CA 95050-2549, U.S.A.
Tel: +1-408-588-6000, Fax: +1-408-588-6130
Renesas Electronics Canada Limited
9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3
Tel: +1-905-237-2004
Renesas Electronics Europe Limited
Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K
Tel: +44-1628-585-100, Fax: +44-1628-585-900
Renesas Electronics Europe GmbH
Arcadiastrasse 10, 40472 Düsseldorf, Germany
Tel: +49-211-6503-0, Fax: +49-211-6503-1327
Renesas Electronics (China) Co., Ltd.
Room 1709, Quantum Plaza, No.27 ZhiChunLu Haidian District, Beijing 100191, P.R.China
Tel: +86-10-8235-1155, Fax: +86-10-8235-7679
Renesas Electronics (Shanghai) Co., Ltd.
Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, P. R. China 200333
Tel: +86-21-2226-0888, Fax: +86-21-2226-0999
Renesas Electronics Hong Kong Limited
Unit 1601-1611, 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong
Tel: +852-2265-6688, Fax: +852 2886-9022
Renesas Electronics Taiwan Co., Ltd.
13F, No. 363, Fu Shing North Road, Taipei 10543, Taiwan
Tel: +886-2-8175-9600, Fax: +886 2-8175-9670
Renesas Electronics Singapore Pte. Ltd.
80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore 339949
Tel: +65-6213-0200, Fax: +65-6213-0300
Renesas Electronics Malaysia Sdn.Bhd.
Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, 46050 Petaling Jaya, Selangor Darul Ehsan, Malaysia
Tel: +60-3-7955-9390, Fax: +60-3-7955-9510
Renesas Electronics India Pvt. Ltd.
No.777C, 100 Feet Road, HAL II Stage, Indiranagar, Bangalore, India
Tel: +91-80-67208700, Fax: +91-80-67208777
Renesas Electronics Korea Co., Ltd.
12F., 234 Teheran-ro, Gangnam-Gu, Seoul, 135-080, Korea
Tel: +82-2-558-3737, Fax: +82-2-558-5141

http://www.renesas.com

■営業お問合せ窓口

※営業お問合せ窓口の住所は変更になることがあります。最新情報につきましては、弊社ホームページをご覧ください。

ルネサス エレクトロニクス株式会社 〒135-0061 東京都江東区豊洲3-2-24（豊洲フォレシア）

■技術的なお問合せおよび資料のご請求は下記へどうぞ。
総合お問合せ窓口：https://www.renesas.com/contact/

Linux Interface Specification
Yocto recipe Start-Up Guide

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : Yes
Encryption                      : Standard V4.4 (128-bit)
User Access                     : Print, Copy, Annotate, Fill forms, Extract, Print high-res
Author                          : Renesas Electronics Corporation
Create Date                     : 2017:08:28 11:37:07+07:00
Modify Date                     : 2017:08:28 11:39:11+07:00
Has XFA                         : No
XMP Toolkit                     : Adobe XMP Core 5.2-c001 63.139439, 2010/09/27-13:37:26
Metadata Date                   : 2017:08:28 11:39:11+07:00
Creator Tool                    : Adobe Acrobat 10.1.1
Format                          : application/pdf
Creator                         : Renesas Electronics Corporation
Title                           : R-Car H3/M3 Series User Manual: Linux Interface Specification Yocto recipe Start-Up Guide
Document ID                     : uuid:5fff23ab-78e1-4a40-9973-ae1432dcb45c
Instance ID                     : uuid:cffb7e7f-ab98-4f44-96be-86863e1dc47d
Producer                        : Adobe Acrobat 10.1.1
Page Count                      : 48

EXIF Metadata provided by EXIF.tools

R Car H3/M3 Series User Manual: Linux Interface Specification Yocto Recipe Start Up Guide RENESAS RCH3M3 Startup UME V2.23.0

Navigation menu

Versions of this User Manual:

Views

Navigation