Difference between revisions of "R-Car/Boards/Kingfisher"

From eLinux.org
Jump to: navigation, search
(FAQ)
(Add Android BSP)
 
(34 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
{{Template:R-Car-Gen3-Navbox}}
 
{{TOC right}}
 
{{TOC right}}
[[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]  
+
[[Category:R-Car]]
 +
[[Category:R-Car Gen3]]
  
 
== Introduction ==
 
== Introduction ==
 
This is the official Wiki for Kingfisher Infotainment Board.
 
This is the official Wiki for Kingfisher Infotainment Board.
 +
Kingfisher Infotainment Board is an expansion board for R-Car Starter Kit.
 +
 +
== Topic ==
 +
{{Template:R-Car-Gen3-KF-Topic}}
  
 
== Hardware ==
 
== Hardware ==
Line 48: Line 54:
 
*HDMI
 
*HDMI
 
** This board equipped with a HDMI transmitter (ADV7513BSWZ) which support HDMI1.4a.
 
** This board equipped with a HDMI transmitter (ADV7513BSWZ) which support HDMI1.4a.
** The maximum resolution is 1920x1080i and it connected Digital output port (RGB888) on R-Car Starter Kit.
+
** The maximum resolution is 1920x1080i or 1280x720p and it connected Digital output port (RGB888) on R-Car Starter Kit.
 
* Power supply: 12V, 9 Amps
 
* Power supply: 12V, 9 Amps
 
** The main power supply domain must be connected to an external AC adapter. The voltage is +12V DC.
 
** The main power supply domain must be connected to an external AC adapter. The voltage is +12V DC.
Line 54: Line 60:
  
 
== Where to buy ==
 
== Where to buy ==
Kingfisher board and GMSL Camera board(*) can be ordered from following distributors:
+
* Kingfisher board can be ordered from following distributors:
  
[http://www.shimafuji.co.jp/en/products/1416 Click to buy Kingfisher board from SHIMAFUJI Electric] - World Wide <br/>
+
[http://www.shimafuji.co.jp/en/products/1416 Click to buy Kingfisher board from SHIMAFUJI Electric] - World Wide - Available <br/>
 +
[https://www.marutsu.co.jp/GoodsDetail.jsp?q=SBEV-RCAR-KF-M06&salesGoodsCode=1556087&shopNo=3 Click to buy Kingfisher board from Marutsu] - Japan only - Available <br/>
  
(*) GMSL Camera board info: http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02
+
*GMSL Camera board can be ordered from following distributors: <br/>
 +
[http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02 Click to buy Kingfisher board from SHIMAFUJI Electric] - World Wide - Available <br/>
  
 
<!--[https://www.marutsu.co.jp/pc/i/839824/ Click to buy Kingfisher board from Marutsu Electric] - Japan only <br/>-->
 
<!--[https://www.marutsu.co.jp/pc/i/839824/ Click to buy Kingfisher board from Marutsu Electric] - Japan only <br/>-->
Line 65: Line 73:
 
== Official board documentation ==
 
== Official board documentation ==
  
*[http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/ Board Manual]
+
*[http://www.shimafuji.co.jp/en/products/ Board Manual]
  
 
== Change point ==
 
== Change point ==
Line 113: Line 121:
 
</ol>
 
</ol>
  
== How to build ==
+
== Kingfisher Yocto BSP ==
=== Build image ===
+
Refer to [[R-Car/Boards/Kingfisher/Yocto-Gen3 | Yocto page]] for steps necessary for making and running a Yocto image.
<ol>
 
<li>Create a directory and switch to it <br/>
 
Warning! Yocto builds require a lot of disk space (up to 100 GB). Make sure you have got enough before starting the build.
 
<pre>
 
mkdir build || exit
 
cd build
 
WORK=`pwd`
 
echo $WORK
 
</pre>
 
</li>
 
<li>Clone basic Yocto layers:
 
<pre>
 
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 clone git://github.com/CogentEmbedded/meta-rcar.git
 
</pre>
 
</li>
 
 
 
<li>
 
Switch to proper branches/commits
 
<ol>
 
<li>
 
For Yocto v2.23.1
 
<pre>
 
cd $WORK/poky
 
git checkout -b tmp yocto-2.1.3
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 55c8a76da5dc099a7bc3838495c672140cedb78e
 
cd $WORK/meta-linaro
 
git checkout -b tmp 2f51d38048599d9878f149d6d15539fb97603f8f
 
cd $WORK/meta-renesas
 
git checkout -b tmp 7acbf5e2f99c59478adbc73c6a40d314589a3009
 
cd $WORK/meta-rcar
 
git checkout -b v2.23.1 remotes/origin/v2.23.1
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.9.0
 
<pre>
 
cd $WORK/poky
 
git checkout -b tmp 342fbd6a3e57021c8e28b124b3adb241936f3d9d
 
cd $WORK/meta-openembedded
 
git checkout -b tmp dacfa2b1920e285531bec55cd2f08743390aaf57
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp fd078b6ece537d986852cb827bd21e022a797b2f
 
cd $WORK/meta-rcar
 
git checkout -b v3.9.0 remotes/origin/v3.9.0
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.13.0 (Note: https://elinux.org/R-Car/Boards/Yocto-Gen3#Known_issues_and_limitations (No.3))<br>
 
This BSP for Kingfisher includes short-term workaround.<br>
 
It improves stability on Uboot but performance down.
 
<pre>
 
cd $WORK/poky
 
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp 00f70f062aace04c051fa92d3cd7b887718fc313
 
cd $WORK/meta-rcar
 
git checkout -b v3.13.0 remotes/origin/v3.13.0
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.15.0
 
<pre>
 
cd $WORK/poky
 
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp 8af0b7d6e445b532088a068dc012757001be3a1f
 
cd $WORK/meta-rcar
 
git checkout -b v3.15.0 remotes/origin/v3.15.0
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.19.0
 
<pre>
 
cd $WORK/poky
 
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp 20fcc94a8d05eda80250f27e87aaa3cfc3275300
 
cd $WORK/meta-rcar
 
git checkout -b v3.19.0 remotes/origin/v3.19.0
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.21.0 <span style="color:#ff0000">(2019/12/26 updated)</span>
 
<pre>
 
cd $WORK/poky
 
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp ad3a8cfee5b6a6fab17cf1c6e5af851eaec75bd7
 
cd $WORK/meta-rcar
 
git checkout -b v3.21.0 remotes/origin/v3.21.0
 
 
 
[Linux BSP] Edit two Yocto recipe files as follows.
 
1. meta-renesas/meta-rcar-gen3/recipes-kernel/linux/linux-renesas_4.14.bb (Line 12,13,14,15)
 
2. meta-renesas/meta-rcar-gen3/recipes-kernel/linux-libc-headers/linux-libc-headers_4.14.bb (Line 5,6,7,8)
 
<Before>
 
  RENESAS_BSP_URL = " ¥
 
  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git"
 
  BRANCH = "v4.14.75-ltsi/rcar-3.9.6"
 
  SRCREV = "1d76a004d3a19367669b861559c1fbbf546b3065"
 
<After>
 
  RENESAS_BSP_URL = " ¥
 
  git://github.com/renesas-rcar/linux-bsp.git"
 
  BRANCH = "v4.14.75-ltsi/rcar-3.9.7"
 
  SRCREV = "59ccbcefaebb4a33110e11fb87f3811cd59f192d"
 
 
 
[LINUX BSP IPL] Edit one Yocto recipe file as follows.
 
meta-renesas/meta-rcar-gen3/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb (Line 14,15,16)
 
<Before>
 
  BRANCH = "rcar_gen3"
 
  SRC_URI = "git://github.com/renesas-rcar/arm-trusted-firmware.git;branch=${BRANCH}"
 
  SRCREV = "236f8fbb57af7f899980bbd5a03feb12d6462970"
 
<After>
 
  BRANCH = "rcar_gen3"
 
  SRC_URI = "git://github.com/renesas-rcar/arm-trusted-firmware.git;branch=${BRANCH}"
 
  SRCREV = "c8b88aa5dc11be44dee1f67a894bb0076fb5f1db"</pre>
 
</li>
 
</ol>
 
Another versions are not tested for compatibility.
 
Legacy BSP instruction can be found here [[R-Car/Boards/Kingfisher-legacy | R-Car Kingfisher legacy]]
 
</li>
 
 
 
<li>
 
This step is only for Yocto v2.23.1.
 
Apply Linaro-GCC patch file:
 
<pre>
 
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
 
</pre>
 
</li>
 
<li>
 
Unzip [https://www.renesas.com/us/en/solutions/automotive/rcar-download/rcar-demoboard.html downloaded] proprietary driver modules to $WORK/proprietary folder.<br/>
 
You should see the following files:
 
<ol>
 
<li>
 
For Yocto v2.23.1
 
<pre>
 
$ ls -1 $WORK/proprietary
 
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170828.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20170828.zip
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.9.0
 
<pre>
 
$ ls -1 $WORK/proprietary/*.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20180627.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20180627.zip
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.13.0
 
<pre>
 
$ ls -1 $WORK/proprietary/*.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20181029.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20181029.zip
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.15.0
 
<pre>
 
$ ls -1 $WORK/proprietary/*.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20181225.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20181225.zip
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.19.0
 
<pre>
 
$ ls -1 $WORK/proprietary/*.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20190507.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20190507.zip
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.21.0
 
<pre>
 
$ ls -1 $WORK/proprietary/*.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20190722.zip
 
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20190722.zip
 
</pre>
 
</li>
 
</ol>
 
</li>
 
 
 
<li>
 
Populate meta-renesas with proprietary software packages.
 
<pre>
 
export PKGS_DIR=$WORK/proprietary
 
cd $WORK/meta-renesas
 
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
 
unset PKGS_DIR
 
</pre>
 
</li>
 
 
 
<li>
 
Setup build environment
 
<pre>
 
cd $WORK
 
source poky/oe-init-build-env
 
</pre>
 
</li>
 
 
 
<li>
 
Prepare default configuration files.
 
<ol>
 
<li>
 
For Yocto v2.23.1
 
<pre>
 
[m3ulcb]
 
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/*.conf ./conf/
 
[h3ulcb]
 
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/*.conf ./conf/
 
 
 
cd $WORK/build
 
cp conf/local-wayland.conf conf/local.conf
 
</pre>
 
</li>
 
<li>
 
For Yocto v3.9.0 or later
 
<pre>
 
[m3ulcb]
 
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/mmp/*.conf ./conf/
 
[h3ulcb]
 
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/*.conf ./conf/
 
 
 
cd $WORK/build
 
cp conf/local-wayland.conf conf/local.conf
 
</pre>
 
NOTE: extra configuration examples are available in the following directory:
 
<pre>
 
$WORK/meta-rcar/meta-rcar-gen3-adas/docs/sample/conf/
 
</pre>
 
</li>
 
</ol>
 
 
 
<li>
 
Edit $WORK/build/conf/local.conf to enable/disable graphics and multimedia proprietary drivers support
 
</li>
 
 
 
<li>
 
Edit local.conf with evaluation packages requirements:
 
<ol>
 
<li>
 
For Yocto v2.23.1 or later (to enable EVA_ prefix during packages install)
 
<pre>
 
DISTRO_FEATURES_append = " use_eva_pkg"
 
</pre>
 
</li>
 
</ol>
 
</li>
 
 
 
<li>
 
Add layer meta-rcar <br/>
 
<pre>
 
bitbake-layers add-layer ../meta-rcar/meta-rcar-gen3-adas
 
</pre>
 
</li>
 
 
 
<li>
 
Start the build <br />
 
<pre>
 
bitbake core-image-weston
 
</pre>
 
</li>
 
 
 
<li>
 
Building image can take up to a few hours depending on your host system performance.<br>
 
After the build has been completed successfully, you should see the output similar to:
 
<pre class="bash">
 
NOTE: Tasks Summary: Attempted 4704 tasks of which 31 didn't need to be rerun and all succeeded.
 
</pre>
 
and the command prompt should return.
 
</li>
 
 
 
<li>
 
Bitbake has generated all the necessary files in ./tmp/deploy/images directory. <br/>
 
You can verify its content:
 
<pre class="bash">
 
$ ls -1 `find ./tmp/deploy/images/m3ulcb/ -maxdepth 1 -type l -print`
 
./tmp/deploy/images/m3ulcb/core-image-weston-m3ulcb.cpio.gz
 
./tmp/deploy/images/m3ulcb/core-image-weston-m3ulcb.ext4
 
./tmp/deploy/images/m3ulcb/core-image-weston-m3ulcb.manifest
 
./tmp/deploy/images/m3ulcb/core-image-weston-m3ulcb.tar.bz2
 
./tmp/deploy/images/m3ulcb/Image
 
./tmp/deploy/images/m3ulcb/Image-m3ulcb.bin
 
./tmp/deploy/images/m3ulcb/Image-r8a7796-m3ulcb-kf.dtb
 
./tmp/deploy/images/m3ulcb/modules-m3ulcb.tgz
 
./tmp/deploy/images/m3ulcb/u-boot.bin
 
./tmp/deploy/images/m3ulcb/u-boot-elf-m3ulcb.srec
 
./tmp/deploy/images/m3ulcb/u-boot-elf.srec
 
./tmp/deploy/images/m3ulcb/u-boot-m3ulcb.bin
 
</pre>
 
'''Image''' is a Kernel image, '''*.dtb''' is a blob file,  '''core-image-weston-m3ulcb.tar.bz2''' is the rootfs, '''modules-m3ulcb.tgz''' are kernel modules.
 
</li>
 
<li>
 
You can now proceed with running Yocto images
 
</li>
 
</ol>
 
 
 
After all these steps you can start working with boards and apps.
 
 
 
=== Build with MOST ===
 
MOST and GPS share the same R-CAR SoC pins and GPS is used by default. <br/>
 
In order to use MOST one need to perform h/w modifications on KF board:
 
<pre>
 
- M04, M05
 
move resistor from R661 -> R660
 
move resistor from R663 -> R662
 
- M06
 
Slide SW7 to "MOST" side.
 
</pre>
 
And enable MOST in BSP by adding option to local.conf:
 
<pre>
 
KF_ENABLE_MOST = "1"
 
</pre>
 
 
 
=== Build with SD3 (CN47) ===
 
SD3 and WIFI share the same R-CAR SoC resource and WIFI is used by default. <br/>
 
In order to use SD on CN47 instead WIFI add following option to local.conf:
 
<pre>
 
KF_ENABLE_SD3 = "1"
 
</pre>
 
 
 
=== Build with LVDS panel(CN49) ===
 
Yocto v3.13.0 or later supports the following LVDS panels.
 
<pre>
 
BD101LCC1 - Boundary Devices BD101LCC1 1280x800 panels [default]
 
TX31D200VM0BAA - KOE TX31D200VM0BAA 1280x480 panel
 
AA104XD12 - Mitsubishi AA104XD12 1024x768 panel
 
AA121TD01 - Mitsubishi AA121TD01 1280x800 panel
 
</pre>
 
How to select:<br>
 
Add following option to local.conf:
 
<pre>
 
KF_PANEL_MODEL = "TX31D200VM0BAA"
 
or
 
KF_PANEL_MODEL = "AA104XD12"
 
or
 
KF_PANEL_MODEL = "AA121TD01"
 
</pre>
 
 
 
=== Build SDK ===
 
After building image run this command to build SDK
 
<pre>
 
bitbake core-image-weston -c populate_sdk
 
</pre>
 
After build success the SDK installation script must appears in ./tmp/deploy/sdk directory:
 
<pre>
 
tmp/deploy/sdk/poky-glibc-x86_64-core-image-weston-aarch64-toolchain-2.1.3.sh
 
</pre>
 
To install SDK run this command and follow instructions on the screen:
 
<pre>
 
./tmp/deploy/sdk/poky-glibc-x86_64-core-image-weston-aarch64-toolchain-2.1.3.sh
 
</pre>
 
 
 
== Build scripts examples ==
 
<ol>
 
 
 
<li> Build preparation
 
<ol>
 
<li> For Yocto v2.23.1
 
<pre>
 
#!/bin/sh
 
 
 
mkdir build || exit
 
cd build
 
WORK=`pwd`
 
echo $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
 
git clone git://github.com/CogentEmbedded/meta-rcar.git
 
 
 
cd $WORK/poky
 
git checkout -b tmp yocto-2.1.3
 
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 7acbf5e2f99c59478adbc73c6a40d314589a3009
 
cd $WORK/meta-rcar
 
git checkout -b v2.23.1 remotes/origin/v2.23.1
 
 
 
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
 
 
 
cd $WORK/
 
PKGS_DIR=$WORK/proprietary
 
cd $WORK/meta-renesas
 
#sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR
 
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
 
</pre>
 
</li>
 
<li> For Yocto v3.9.0
 
<pre>
 
#!/bin/sh
 
 
 
mkdir build || exit
 
cd build
 
WORK=`pwd`
 
echo $WORK
 
  
git clone git://git.yoctoproject.org/poky
+
== Kingfisher Android BSP ==
git clone git://git.linaro.org/openembedded/meta-linaro.git
+
Refer to [[R-Car/Boards/Kingfisher/Android | Android page]] for steps necessary for making and running a Android image.
git clone git://git.openembedded.org/meta-openembedded
 
git clone git://github.com/renesas-rcar/meta-renesas
 
git clone git://github.com/CogentEmbedded/meta-rcar.git
 
 
 
cd $WORK/poky
 
git checkout -b tmp 342fbd6a3e57021c8e28b124b3adb241936f3d9d
 
cd $WORK/meta-openembedded
 
git checkout -b tmp dacfa2b1920e285531bec55cd2f08743390aaf57
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp fd078b6ece537d986852cb827bd21e022a797b2f
 
cd $WORK/meta-rcar
 
git checkout -b v3.9.0 remotes/origin/v3.9.0
 
 
 
cd $WORK/
 
PKGS_DIR=$WORK/proprietary
 
cd $WORK/meta-renesas
 
#sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR
 
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
 
</pre>
 
</li>
 
<li> For Yocto v3.13.0
 
<pre>
 
#!/bin/sh
 
 
 
mkdir build || exit
 
cd build
 
WORK=`pwd`
 
echo $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 clone git://github.com/CogentEmbedded/meta-rcar.git
 
 
 
cd $WORK/poky
 
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp 00f70f062aace04c051fa92d3cd7b887718fc313
 
cd $WORK/meta-rcar
 
git checkout -b v3.13.0 remotes/origin/v3.13.0
 
 
 
cd $WORK/
 
PKGS_DIR=$WORK/proprietary
 
cd $WORK/meta-renesas
 
#sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR
 
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
 
</pre>
 
</li>
 
<li> For Yocto v3.15.0
 
<pre>
 
#!/bin/sh
 
 
 
mkdir build || exit
 
cd build
 
WORK=`pwd`
 
echo $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 clone git://github.com/CogentEmbedded/meta-rcar.git
 
 
 
cd $WORK/poky
 
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp 8af0b7d6e445b532088a068dc012757001be3a1f
 
cd $WORK/meta-rcar
 
git checkout -b v3.15.0 remotes/origin/v3.15.0
 
 
 
cd $WORK/
 
PKGS_DIR=$WORK/../proprietary
 
cd $WORK/meta-renesas
 
#sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR
 
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
 
</pre>
 
</li>
 
<li> For Yocto v3.19.0
 
<pre>
 
#!/bin/sh
 
 
 
mkdir build || exit
 
cd build
 
WORK=`pwd`
 
echo $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 clone git://github.com/CogentEmbedded/meta-rcar.git
 
 
 
cd $WORK/poky
 
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp 20fcc94a8d05eda80250f27e87aaa3cfc3275300
 
cd $WORK/meta-rcar
 
git checkout -b v3.19.0 remotes/origin/v3.19.0
 
 
 
cd $WORK/
 
PKGS_DIR=$WORK/../proprietary
 
cd $WORK/meta-renesas
 
#sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR
 
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
 
</pre>
 
</li>
 
<li> For Yocto v3.21.0
 
<pre>
 
#!/bin/sh
 
 
 
mkdir build || exit
 
cd build
 
WORK=`pwd`
 
echo $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 clone git://github.com/CogentEmbedded/meta-rcar.git
 
 
 
cd $WORK/poky
 
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc
 
cd $WORK/meta-openembedded
 
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23
 
cd $WORK/meta-linaro
 
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885
 
cd $WORK/meta-renesas
 
git checkout -b tmp ad3a8cfee5b6a6fab17cf1c6e5af851eaec75bd7
 
cd $WORK/meta-rcar
 
git checkout -b v3.21.0 remotes/origin/v3.21.0
 
 
 
cd $WORK/
 
PKGS_DIR=$WORK/../proprietary
 
cd $WORK/meta-renesas
 
#sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR
 
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
 
</pre>
 
</li>
 
</ol>
 
</li>
 
 
 
<li> Building yocto
 
<ol>
 
<li> For Yocto v2.23.1
 
<pre>
 
#!/bin/sh
 
 
 
cd build
 
WORK=`pwd`
 
echo $WORK
 
 
 
cd $WORK
 
source poky/oe-init-build-env
 
 
 
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/*.conf ./conf/.
 
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/*.conf ./conf/.
 
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/*.conf ./conf/.
 
 
 
cd $WORK/build
 
cp conf/local-wayland.conf conf/local.conf
 
echo "DISTRO_FEATURES_append = \" use_eva_pkg\"" >> $WORK/build/conf/local.conf
 
# uncomment for ADAS HAD board only:
 
#echo "MACHINE_FEATURES_append = \" h3ulcb-had\"" >> $WORK/build/conf/local.conf
 
 
 
bitbake-layers add-layer ../meta-rcar/meta-rcar-gen3-adas
 
 
 
bitbake core-image-weston
 
bitbake core-image-weston -c populate_sdk
 
</pre>
 
</li>
 
</ol>
 
<ol>
 
<li> For Yocto v3.9.0 or later
 
<pre>
 
#!/bin/sh
 
 
 
cd build
 
WORK=`pwd`
 
echo $WORK
 
 
 
cd $WORK
 
source poky/oe-init-build-env
 
 
 
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/*.conf ./conf/.
 
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/*.conf ./conf/.
 
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/*.conf ./conf/.
 
 
 
cd $WORK/build
 
cp conf/local-wayland.conf conf/local.conf
 
echo "DISTRO_FEATURES_append = \" use_eva_pkg\"" >> $WORK/build/conf/local.conf
 
# uncomment for ADAS HAD board only:
 
#echo "MACHINE_FEATURES_append = \" h3ulcb-had\"" >> $WORK/build/conf/local.conf
 
 
 
bitbake-layers add-layer ../meta-rcar/meta-rcar-gen3-adas
 
 
 
bitbake core-image-weston
 
bitbake core-image-weston -c populate_sdk
 
</pre>
 
</li>
 
</ol>
 
 
 
</li>
 
 
 
</ol>
 
 
 
== Running Yocto images ==
 
Refer to [https://elinux.org/R-Car/Boards/Yocto-Gen3#Running_Yocto_images "Running Yocto images"] of Yocto-Gen3. <br/>
 
 
 
[NOTE] DTB file for Kingfisher: Image-r8a7795-h3ulcb<span style="color:#ff0000">-kf</span style>.dtb, Image-r8a7795-h3ulcb<span style="color:#ff0000">-4x2g-kf</span style>.dtb(*), Image-r8a7796-m3ulcb<span style="color:#ff0000">-kf</span style>.dtb<br/>
 
(*) The "4x2g" means DDR8GiB SK board. Refer to [https://elinux.org/R-Car/Boards/H3SK#H3SK_has_several_kinds_of_boards "H3 SK variation"]. <br/>
 
 
 
==S/W support status==
 
{| class="wikitable"
 
! Functions !! Yocto v2.23.1 !! Yocto v3.7.0 !! Yocto v3.9.0 !! Yocto v3.15.0 !! Yocto v3.19.0 !! Yocto v3.21.0
 
|-
 
| WiFi || ok || ok || ok || ok || ok || ok
 
|-
 
| Bluetooth || ok || ok || ok  || ok || ok || ok
 
|-
 
| Gyro || ok || ok || ok || ok || ok || ok
 
|-
 
| GPS || ok || ok || ok || ok || ok || ok
 
|-
 
| CAN || ok || ok || ok || ok || ok || ok
 
|-
 
| LVDS Camera(CN10/CN11) || ok || ok || ok || ok || ok || ok
 
|-
 
| CMOS Camera || ok || ok || ok || ok || ok || ok
 
|-
 
| Raspberry Pi camera Rev 1.3 || ok || ok || ok || ok || ok || ok
 
|-
 
| Raspberry Pi camera Rev 2 || - || - || - || ok || ok || ok
 
|-
 
| USB2.0(CN13) Host || ok || ok || ok || ok || ok || ok
 
|-
 
| USB2.0(CN13) Func(g_mass_storage) || ok || ok || ok || ok || ok || ok
 
|-
 
| USB3.0(CN2) Host || ok (H3 only) || ok (H3 only) || ok (H3 only) ||ok (H3 only) || ok (H3 only) || ok (H3 only)
 
|-
 
| Multichannel Audio || ok || ok || ok || ok || ok || ok
 
|-
 
| HDMI Out || ok || ok || ok || ok || ok || ok
 
|-
 
| LVDS Out || ok || ok || ok || ok || ok || ok
 
|-
 
| Serial(CN4) || ok || ok || ok || ok || ok || ok
 
|-
 
| Mini PCIe || ok || ok || ok || ok || ok || ok
 
|-
 
| M.2 || ok || ok || ok || ok|| ok || ok
 
|-
 
| MOST || ok || ok || ok || ok || ok || ok
 
|-
 
|}
 
 
 
Note: <br />
 
"ok" - Function succeeded in the simple test as below.<br />
 
"NT" - Function wasn't tested
 
 
 
== How to test some capabilities ==
 
 
 
===WiFi===
 
To check wifi and scan available WAPs run:
 
  $ ifconfig wlan0 up
 
  $ iwlist wlan0 scan
 
 
 
===Bluetooth===
 
Ex 1)To check bluetooth and scan available BT devices run:
 
  $ hciconfig hci0 up
 
  $ hcitool -i hci0 scan
 
 
 
Ex 2) BT-Audio
 
<pre>
 
root@h3ulcb:~# bluetoothctl
 
[NEW] Controller C8:DF:84:4C:84:98 h3ulcb [default]
 
Agent registered
 
[bluetooth]# power on
 
Changing power on succeeded
 
[bluetooth]# agent on
 
Agent is already registered
 
[bluetooth]# default-agent   
 
Default agent request successful
 
[bluetooth]# scan on
 
Discovery started
 
..(snip)..  !!! <-- Please look for taget device !!!
 
[bluetooth]# scan off
 
..(snip)..
 
[bluetooth]# pair <MAC address of target device>
 
..(snip)..
 
Request confirmation
 
[agent] Confirm passkey 285311 (yes/no): yes
 
..(snip)..
 
Pairing successful
 
[bluetooth]# connect <MAC address of target device>
 
..(snip)..
 
Connection successful
 
..(snip)..
 
[Target device name]# quit
 
</pre>
 
Please play music on target device.
 
 
 
===Gyro===
 
  $ cat /sys/bus/iio/devices/iio\:device0/*_raw (Accelerometer, Magnetometer)
 
  $ cat /sys/bus/iio/devices/iio\:device1/*_raw (Gyroscope)
 
 
 
===GPS===
 
$ cat /dev/ttySC3 (Yocto v2.23.1)
 
$ cat /dev/ttySC2 (Yocto v3.x)
 
 
 
===CAN===
 
Ex) loop back<br>
 
Connect the following pins of CN17 and CN18:
 
  CN17 1pin - CN18 1pin
 
  CN17 2pin - CN18 2pin
 
  (*)Note: SW2 ON of KF. (defalt:ON)
 
 
 
  $ ip link set can0 up type can bitrate 125000
 
  $ ip link set can1 up type can bitrate 125000
 
  $ candump can0&
 
  $ cangen can1
 
  can0  08D  [3]  B5 F4 3C
 
  can0  34E  [3]  7C A1 70
 
  can0  717  [6]  95 C5 67 4A 41 42
 
  can0  7F1  [8]  CA B9 E9 3E AE 71 FC 52
 
 
 
===Serial===
 
Ex) loop back<br>
 
For KF M03: Connect the following pins on CN4:
 
pin3(RxD) - pin5(TxD)
 
pin4(RTS) - pin6(CTS)
 
 
 
For KF M04 or later: Connect the following pins on CN4:
 
pin2(TxD) - pin4(RxD)
 
pin1(RTS) - pin3(CTS)
 
 
 
For Yocto v2.23.1:
 
$ stty -F /dev/ttySC2 -echo
 
$ stty -F /dev/ttySC2
 
speed 9600 baud; line = 0;
 
-brkint -imaxbel
 
-echo
 
$ cat /dev/ttySC2 &
 
$ echo  123435452345 > /dev/ttySC2
 
123435452345
 
 
 
For Yocto v3.x:
 
$ stty -F /dev/ttySC3 -echo
 
$ stty -F /dev/ttySC3
 
speed 9600 baud; line = 0;
 
-brkint -imaxbel
 
-echo
 
$ cat /dev/ttySC3 &
 
$ echo  123435452345 > /dev/ttySC3
 
123435452345
 
 
 
===LVDS Camera===
 
<GMSL>
 
Camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02 GMSL02]
 
Camera: IMI RDACM21-01
 
Camera: [https://leopardimaging.com/product/autonomous-camera/maxim-gmsl-cameras/li-ov10635-gmsl/ Leopard Imaging LI-OV10635-GMSL]
 
or
 
<FPD Link>
 
Camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#FPDL01 FPDL01]
 
Camera: IMI RDACM24-01
 
 
 
*Note:
 
  H3 can use CN10 and CN11
 
  M3 can use CN10
 
 
 
<ol>
 
<li> When you use a Leopard Imaging camera, add some parameters to bootargs.
 
{| class="wikitable"
 
! Leopard Imagin camera type name!! bootargs
 
|-
 
| LI-OV10635-GMSL || ov106xx.dvp_order=0
 
|-
 
| (IMI) RDACM21 ||
 
|-
 
|}
 
</li>
 
</ol>
 
 
 
Ex1)<br>
 
  $ killall weston
 
  $ capture -d /dev/video0 -F -f rgb32 -L 0 -T 0 -W 1280 -H 1080 -c 1000 -z
 
 
 
Ex2)<br>
 
  1. RDACM21-01/RDACM24-1
 
  $ gst-launch-1.0 v4l2src device=/dev/video0 io-mode=dmabuf ! video/x-raw,format=BGRA,width=1280,height=1080,framerate=30/1 ! waylandsink
 
 
 
  2. LI-OV10635-GMSL
 
  $ gst-launch-1.0 v4l2src device=/dev/video0 io-mode=dmabuf ! video/x-raw,format=BGRA,width=1280,height=800,framerate=30/1 ! waylandsink
 
 
 
===CMOS Camera===
 
Ex)<br>
 
  $ systemctl stop weston
 
  $ capture -d /dev/video0 -F -f rgb32 -L 0 -T 0 -W 1280 -H 720 -c 1000 -t 60 -z
 
 
 
===Raspberry Pi camera Rev 1.3(OV5647) / 2(IMX219)===
 
In case of v2(IMX219):<br>
 
Add the following option to local.conf: <br>
 
<pre>
 
KF_ENABLE_IMX219 = "1"
 
</pre>
 
 
 
Ex)<br>
 
  $ systemctl stop weston                                                               
 
  $ capture -d /dev/video0 -o -f bggr8 -W 2592 -H 1944 -c 1 -t 30 > video.bggr
 
  [ 2475.196942] rcar_csi2 fea80000.csi2: Timeout of reading the PHY clock lane
 
  [ 2475.203851] rcar_csi2 fea80000.csi2: Timeout of reading the PHY data lane
 
 
 
  Ubuntu PC$ ./bayer2rgb  -i video.bggr -o video.rgb24 -w 2592 -v 1944 -b 8 -f BGGR
 
  * https://github.com/jdthomas/bayer2rgb.git
 
  Ubuntu PC$ rawtoppm -rgb 2592 1944 video.rgb24 > video24.ppm
 
  Ubuntu PC$ display video24.ppm
 
 
 
===Multichannel Audio===
 
Ex1) CN12/32 on KF
 
  $ speaker-test -c 8 -t wav -W /usr/share/sounds/alsa/
 
Ex2)
 
  <KF>
 
  $ pactl set-default-sink pcm3168a_output
 
  $ speaker-test -c 8 -t wav -W /usr/share/sounds/alsa/
 
  <SK>
 
  $ pactl set-default-sink ak4613_output
 
  $ amixer -c 1 sset "DVC Out" 10%
 
  $ speaker-test -c 2 -t wav -W /usr/share/sounds/alsa/
 
Ex3)
 
  <KF>
 
  $ paplay -d pcm3168a_output sample.wav
 
  <SK>
 
  $ amixer -c 1 sset "DVC Out" 10%
 
  $ paplay -d ak4613_output sample.wav
 
 
 
===MOST===
 
Ex)<br>
 
1. Connect OS81092 board(Physical+ Interface Board OS81092) and CN22 of KF. <br>
 
2. Connect Audio board(OS81092 Audio Demo Board) and OS819092 board with exclusive cable. <br>
 
3. Connect Audio board and CN5 of SK with USB cable. <br>
 
4. Run the linux kernel <br>
 
5. cd /usr/share/most/ <br>
 
6. ./most_setup.sh
 
<pre>
 
$./most_setup.sh
 
--Setting up RX channel with MLB[  217.636328] aim_sound: PCM format is 16-bit stereo
 
addr 0x03 (0x06)--
 
--S[  217.642675] aim_sound: PCM format is 16-bit stereo
 
etting up TX channel wit[  217.649647] aim_sound: PCM format is 16-bit stereo
 
h MLB addr 0x04 (0x08)--
 
--Setting up TX channel with MLB addr 0x06 (0x0C)--
 
--Creating char devices--
 
--Creating ALSA devices--
 
</pre>
 
7../setup-audio-50 &
 
<pre>
 
$./setup-audio-50 &
 
Configuration:
 
        Timing Slave (Audio Sink)
 
! ET_NS_MSVAL_ERROR a MSVAL Error is reported from the NS: 0x0010 MSVAL_ERR_STARTUP_FAILED
 
MSVAL_E_SHUTDOWN
 
App reset
 
MSVAL_E_SHUTDOWN
 
App reset
 
! ET_NS_MSVAL_ERROR a MSVAL Error is reported from the NS: 0x0011 MSVAL_ERR_STARTUP_BUSY
 
! ET_NS_MSVAL_ERROR a MSVAL Error is reported from the NS: 0x0011 MSVAL_ERR_STARTUP_BUSY
 
(snip)
 
</pre>
 
8. Push the "Switch" button on the Audio board
 
<pre>
 
-> MostAllowRemoteAccess(allow)
 
-> SourceInfo.Status 1 (Inst_ID: 0x1, FB: 0x24, Adr: 0x400)
 
-> SourceInfo.Status 2 (Inst_ID: 0x1, FB: 0x24, Adr: 0x400)
 
-> Amplifier.Volume.Set 100
 
</pre>
 
9. Push the "Switch" button on the Audio board again
 
<pre>
 
<- FB_AuxIn_Allocate_StartResult Node: 0x01, Ifn: 0x02
 
</pre>
 
10. Push the "Switch" button on the Audio board again
 
<pre>
 
<- FB_AuxIn_Allocate_StartResult Node: 0x01, Ifn: 0x01
 
</pre>
 
11. ./most_play.sh ${PATH}/hoge.mp3 5
 
<pre>
 
$./most_play.sh /home/root/hoge.mp3 5
 
Setting pipeline to PAUSED ...
 
Pipeline is PREROLLING ...
 
Redistribute latency...
 
Pipeline is PREROLLED ...
 
Setting pipeline to PLAYING ...
 
New clock: GstAudioSinkClock
 
</pre>
 
===Radio===
 
ex) FM Radio
 
 
 
If radio module is used for the first time, updating radio module firmware is required.
 
 
 
Updating firmware is not required after the second time.
 
$ si_init
 
$ si_firmware_update ( Update firmware of radio module.)
 
$ si_fm
 
$ si_preset <FM Radio frequency> ( In Tokyo, Japan, 91600 is Nippon Cultural Broadcasting. )
 
  
 
== Connection-confirmed Hardware information ==
 
== Connection-confirmed Hardware information ==
Line 1,076: Line 134:
 
|-
 
|-
 
| CN10, CN11
 
| CN10, CN11
  || LVDS camera || IMI RDACM21(Need camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02 GMSL02])<br>Leopard Imaging LI-OV10635-GMSL (Need camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02 GMSL02])<br>IMI RDACM24 (Need camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#FPDL01 FPDL01])<br>
+
  || LVDS camera || IMI RDACM21(Need camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02 GMSL02])<br>Leopard Imaging LI-OV10635-GMSL (Need camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02 GMSL02])<br>Entron [https://elinux.org/R-Car/Boards/Kingfisher#FAQ S001A190CM0A](Need camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02 GMSL02])<span style="color:#ff0000"> NEW </span style><br>IMI RDACM24 (Need camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#FPDL01 FPDL01])<br>
 
|-
 
|-
 
| CN15 || Mini PCIe || Intel 512AN-MMW
 
| CN15 || Mini PCIe || Intel 512AN-MMW
Line 1,088: Line 146:
 
| CN22 || MOST || "Physical+ Interface Board OS81092" and "OS81092 Audio Demo Board"
 
| CN22 || MOST || "Physical+ Interface Board OS81092" and "OS81092 Audio Demo Board"
 
|-
 
|-
| CN29 || CMOS camera || https://www.amazon.com/Arducam-Megapixels-OV5642-Sensor-Camera/dp/B013JO53AU
+
| CN29 || CMOS camera || https://www.amazon.com/dp/B013JO53AU
 +
|-
 +
| CN16 || GPS antenna || https://www.amazon.com/dp/B07R6NL5G6
 +
|-
 +
| CN42 || Radio antenna || https://www.amazon.co.jp/dp/B073R7P8QB
 
|}
 
|}
  
Line 1,297: Line 359:
 
http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware<br/>
 
http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware<br/>
 
</ol>
 
</ol>
 +
 +
== Q&A site ==
 +
http://renesasrulz.com/r-car-h3-m3-cockpit/
 +
 +
== FAQ page ==
 +
https://elinux.org/R-Car/Boards/Yocto-Gen3-CommonFAQ
  
 
== FAQ ==
 
== FAQ ==
<ol>
+
 
<li>Failed to DRAM initialize (-1).<br/>
+
=== How to get the SA001 Camera ===
If you face the following error please update(*) IPL and u-boot to the latest versopm.
 
<pre>
 
NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.12
 
NOTICE:  BL2: PRR is R-Car M3 ES1.0
 
NOTICE:  BL2: Boot device is HyperFlash(80MHz)
 
NOTICE:  BL2: LCM state is CM
 
NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x52
 
NOTICE:  BL2: DDR3200(rev.0.20)[COLD_BOOT]..1
 
NOTICE:  BL2: Failed to DRAM initialize (-1).
 
ERROR: 
 
ERROR:  BL2: System WDT overflow, occured address is 0xe630d3cc
 
</pre>
 
(*)How to update<br/>
 
http://elinux.org/R-Car/Boards/Kingfisher#How_to_update_of_Sample_Loader_and_MiniMonitor<br/>
 
http://elinux.org/R-Car/Boards/M3SK#Flashing_firmware<br/>
 
http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware<br/>
 
</li>
 
<li> How to get the SA001 Camera<br/>
 
 
S001A Camera Specification:<br/>
 
S001A Camera Specification:<br/>
 +
http://www.entroninc.com/prouduct.html<br/>
 
(S001 is the same camera with S002, just connector slightly different)<br/>
 
(S001 is the same camera with S002, just connector slightly different)<br/>
 
- Image Sensor : AR0140AT<br/>
 
- Image Sensor : AR0140AT<br/>
Line 1,325: Line 376:
 
- Resolution : 1280x728<br/><br/>
 
- Resolution : 1280x728<br/><br/>
 
This camera cannot be purchased from the online shop.<br/>
 
This camera cannot be purchased from the online shop.<br/>
If you want to get the Entron S001A190CM0A camera, please contact to "RenesasJa" from "Email this user" of following site.<br/>
+
If you want to get the Entron S001A190CM0A camera, <br>
https://elinux.org/User:RenesasJa<br/>
+
please contact to "RenesasJa" from https://elinux.org/Special:EmailUser/RenesasJa<br>
 
Please fill in the followings in the email.<br/>
 
Please fill in the followings in the email.<br/>
 
- Name<br/>
 
- Name<br/>
Line 1,336: Line 387:
 
Quantities are limited.<br/>
 
Quantities are limited.<br/>
 
Please understand that we cannot sell this camera to everyone.<br/>
 
Please understand that we cannot sell this camera to everyone.<br/>
</li>
 
 
</ol>
 
</ol>
  
Line 1,343: Line 393:
 
<li> USB3.0(CN2) cannot use with M3 SK.
 
<li> USB3.0(CN2) cannot use with M3 SK.
 
</li>
 
</li>
This is a limitation of M3 SK. (H3 SK can use USB3.0)
+
: Please refer to the [[R-Car/Boards/Yocto-Gen3-CommonFAQ/I_can%27t_use_usb3.0(CN2)_with_Kingfisher_%2B_R-Car_Starter_Kit_Pro(M3SK).]].
 
<li> H/W limitations
 
<li> H/W limitations
 
<pre>
 
<pre>
Line 1,359: Line 409:
 
SBEV-RCAR-KF-M03 and SBEV-RCAR-KF -S03 boards may not turn on even if you turn on SW6.<br>
 
SBEV-RCAR-KF-M03 and SBEV-RCAR-KF -S03 boards may not turn on even if you turn on SW6.<br>
 
In that case please turn on SW6 again.
 
In that case please turn on SW6 again.
</li>
 
<li>(SW limitation)Raspberry Pi camera <br>
 
v2(Sony IMX219) camera does not support. (v1(ov5647)is supported)<br>
 
--> Yocto v3.9.0 or later support v2 camera.
 
 
</li>
 
</li>
 
</ol>
 
</ol>

Latest revision as of 23:31, 28 September 2020


Introduction

This is the official Wiki for Kingfisher Infotainment Board. Kingfisher Infotainment Board is an expansion board for R-Car Starter Kit.

Topic

Kingfisher Board Stock Information

  • Global Disty(Shimafuji) : Available
  • Japan Disty (Marutsu) : Available
    • Click here for detail

    New Camera Support

  • Yocto v3.21.0 supports the new Entron S001A190CM0A camera.
    • Please refer to FAQ for how to purchase.

    SW Release Information

    Board name SW name Release date Note
    R-Car Starter Kit ( Premier / Pro ) Yocto v4.1.0 2020/08/06 This version does not support MMP.
    GFX(except for Wayland/weston) is supported from 2020/09/23.
    Yocto v3.21.0 2019/07/09 New R-Car Starter Kit Pro(RTP8J77961ASKB0SK0SA05A) is supported from 2020/07/10.
    Kingfisher Infotainment Board Android P [New!!] 2020/09/29 Only R-Car Starter Kit Premier(R-Car H3) + Kingfisher is supported.
    Yocto v3.21.0 2019/08/07 To check for latest information, please refer to the meta-rcar.
    New R-Car Starter Kit Pro(RTP8J77961ASKB0SK0SA05A) is supported from 2020/08/02.
    Yocto v4.1.0 2020/10/23 This version does not support MMP.



    Hardware

    This section contains information about Kingfisher Board hardware.

    Board Layout

    Kfisher top specs.png

    Kfisher bot specs.png

    Hardware Features

    • Ethernet AVB phy
      • KSZ9031 phy
    • MOST interface
      • Support both 3-pin and 6-pin MLB interface
      • Pinout compatible with Microchip evaluation boards
    • LVDS camera interface
      • MAX9286 or TI960 deserializers
      • MIPI CSI2 bus
      • 5V, 9V or 12V selectable supply voltage for camera with current limiting
    • High quality 24-bit audio codec PCM3168A
      • 8 input channels (4 stereo jacks for microphone connection)
      • 6 line out channels (RCA connectors)
      • 6 HP outputs (3 stereo jack connectors for direct headphones connection)
      • 44100/48000 Hz sampling frequency
    • Two USB 3.0 ports
    • USB OTG port
    • SD card slot
      • SD card slot(CN47) supports only 3.3 signal voltage(= Default/High speed class only).
        • If you want to use other cards please use the slot(CN6) on the Starter Kit board.
    • Si4689 base AM/FM/DAB radio
      • Digital audio interface to R-Car M2 CPU
      • Additional flash storage for fast radio boot
      • Supply for active DAB antennas with current limit (5 or 12 V)
    • GPS/GLONASS receiver
      • Serial and i2c interface to R-Car
    • 9-axis sensor:
      • 3D digital linear acceleration sensor
      • 3D digital angular rate sensor
      • 3D digital magnetic sensor
    • WiFi/BT module Texas Instruments WL1837
    • HDMI
      • This board equipped with a HDMI transmitter (ADV7513BSWZ) which support HDMI1.4a.
      • The maximum resolution is 1920x1080i or 1280x720p and it connected Digital output port (RGB888) on R-Car Starter Kit.
    • Power supply: 12V, 9 Amps
      • The main power supply domain must be connected to an external AC adapter. The voltage is +12V DC.
      • DO NOT USE R-Car Starter kit AC adapter to connect this board or this board AC adapter to connect R-Car Starter kit. If connect wrong AC adapter then it has serious damage to the board.

    Where to buy

    • Kingfisher board can be ordered from following distributors:

    Click to buy Kingfisher board from SHIMAFUJI Electric - World Wide - Available
    Click to buy Kingfisher board from Marutsu - Japan only - Available

    • GMSL Camera board can be ordered from following distributors:

    Click to buy Kingfisher board from SHIMAFUJI Electric - World Wide - Available


    Official board documentation

    Change point

    Function M03 Board to M04 Board M04 Board to M05 Board M05 Board to M06 Board
    USB2.0 No difference No difference Change filter(L9), Diode(D6,D7)
    WIFI Unmount SMA connector(CN45,CN46) No difference No difference
    BLUETOOTH ADD Level conversion IC(U116) / Support BT AUDIO(HFP) No difference No difference
    SD CARD Change Power IC(U106) / Not support SD1.8V No difference Change Diode(D44,D45)
    SERIAL Change connector shape(CN4 Male to Female) No difference Change Diode(D19~D23)
    FPDLink No difference Delete function No difference
    Audio In No difference No difference Change Diode(D15~D17)
    Audio Out No difference No difference Delete Diode(D24~D40)
    POWER AMP ADD Reset Signal(nVRST) Delete function -
    MOST ADD Level conversion IC(U118) No difference Change MOST ↔ GPS Function select register (R661~R663) to select SW (SW7)
    GPS No difference No difference Change MOST ↔ GPS Function select register (R661~R663) to select SW (SW7)
    I2C No difference No difference Chabge I2C repeater (U1, U4)
    ETHER ADD Level conversion IC(U117) Delete function No difference

    The M06 board has improved the I2C error problem, Fixed a rare start-up problem when turned power on

      < Major modification on M06 >
    1. I2C error modification
      - Replace I2C repeater
      - Changing the resistance value
    2. Booting NG modification
      - Power stabilization
      - Sequence correction the kingfisher board start-up after StarterKit.
    3. Change of MOST-GPS switching method (SW 7)

    Kingfisher Yocto BSP

    Refer to Yocto page for steps necessary for making and running a Yocto image.

    Kingfisher Android BSP

    Refer to Android page for steps necessary for making and running a Android image.

    Connection-confirmed Hardware information

    Connector No Function name Connection confirmed Hardware
    CN7 LVDS display BD101LCC1 https://boundarydevices.com/product/bd101lcc1-10-1-1280x800-display/
    CN10, CN11 LVDS camera IMI RDACM21(Need camera board: GMSL02)
    Leopard Imaging LI-OV10635-GMSL (Need camera board: GMSL02)
    Entron S001A190CM0A(Need camera board: GMSL02) NEW
    IMI RDACM24 (Need camera board: FPDL01)
    CN15 Mini PCIe Intel 512AN-MMW
    CN5 M.2 Transcend TS128GMTE850
    CN48 Raspberry Pi camera Raspberry Pi camera Rev 1.3(OV5647)
    Raspberry Pi camera Rev 2.0(IMX219)
    CN49 HDMI display GeChic Onlap 1502x, 1503x
    CN22 MOST "Physical+ Interface Board OS81092" and "OS81092 Audio Demo Board"
    CN29 CMOS camera https://www.amazon.com/dp/B013JO53AU
    CN16 GPS antenna https://www.amazon.com/dp/B07R6NL5G6
    CN42 Radio antenna https://www.amazon.co.jp/dp/B073R7P8QB

    How to update of Sample Loader and MiniMonitor

    New version:

     Sample Loader: V3.02
     MiniMonitor: V3.02
    

    Down load:

    File:UpdateFile v302.zip
    

    [Note]

    Sample Loader and MiniMonitor version of LATEST SK is V5.08.
    DON'T update those SK.(You can update firmware(*) while SK and KF connected)
    Please check carefully before updating.
    

    Why update?:

    ComEx Mechanical Specification: Durability: 30 mating cycles.
    This new version(V3.02) can update firmware(*) while keeping Starter Kit(SK) and Kingfisher(KF) connected.
    
    (*)firmware: bootparam_sa0.srec, bl2-h3ulcb/m3ulcb.srec, cert_header_sa6.srec, bl31-h3ulcb/m3ulcb.srec, tee-h3ulcb/m3ulcb.srec, u-boot-elf.srec 
    


    How to update:

    1. Power off the KF and remove SK from KF
    2. Turn off SW5
      Remove SK from KF
      
    3. Set SW of SK as follows:
    4. SW1:OFF
      SW6:OFF/OFF/OFF/OFF
      SW2:OFF/OFF/OFF/OFF
      
    5. Power on the SK (This means that you need to prepare a 5V AC-adapter for SK)
    6. Press SW8
      SCIF Download mode starts
      
    7. Send the following file from console(Ex: minicom):
    8. type "ctrl+A S" and select upload method "ascii", then choose file for uploading the following file.
      Case of M3SK:
      	BoardID_Writer_SCIF_64bit_ID=0x10(StarterKit-Pro_Rev1.0).mot
      Case of H3SK:
      	BoardID_Writer_SCIF_64bit_ID=0x58(StarterKit-Premier_Rev1.0OB).mot
      
      NOTE: Under Linux, if you got problem transferring this file, it may because of special character in its name.
      
      Solution is to open a new terminal then manually launch the transfer with the following command with double quote around filename (Ex: serial link on ttyUSB0 for M3SK):
      # /usr/bin/ascii-xfr -dsv "BoardID_Writer_SCIF_64bit_ID=0x10(StarterKit-Pro_Rev1.0).mot" > /dev/ttyUSB0
      

      You can confirm the following log (Ex: M3SK):

      +---------------------------------+
      |  Board ID Writer V01 2017.06.23 |
      +---------------------------------+
       Product Code : R-Car M3 ES1.0
      
       Now Board ID : Unknown Board Rev7 (0xFF)
       New Board ID : Starter Kit Rev0 (0x10)
       Wrote Board ID : Starter Kit Rev0 (0x10)
      
      Writer Program End.
      
    9. Power off the SK
    10. Press SW8
      
    11. Set SW as follows:
    12. M3SK = SW6:OFF/ON/OFF/OFF
      H3SK = SW6:OFF/OFF/OFF/OFF
      
    13. Power on the SK
    14. Press SW8
      SCIF Download mode starts
      
    15. Send the following file from console:
    16. type "ctrl+A S" and select upload method "ascii", then choose file for uploading the following file.
      Case of M3SK:
      	AArch32_Gen3_H3_M3_Scif_MiniMon_V3.02.mot
      Case of H3SK:
      	AArch64_Gen3_H3_M3_Scif_MiniMon_V3.02.mot
      

      You can confirm the following log (Ex: M3SK):

      R-Car Gen3 Scif Download MiniMonitor V3.02 2017.07.04
       Work Memory     : SystemRAM
       Board Judge     : Used Board-ID	<-- Attention!!
       DDR_Init        : boardcnf[3] Starter Kit (M3SIP)
       Board Name      : Starter Kit Pro
       Product Code    : R-Car M3 ES1.0
      
      >
      
    17. Flash AArch64_Gen3_H3_M3_SPI_LOADER_V3.02.mot. In console execute xls command (load program to hyper flash) and provide the following inputs:
    18. xls
      1
      y
      y
      y
      1
      type "ctrl+A S" and select upload method "ascii", then choose file for uploading "AArch64_Gen3_H3_M3_SPI_LOADER_V3.02.mot", after upload finished press y key
      
    19. Flash AArch64_Gen3_Spi_MiniMon_V3.02_E6330000.mot. In console execute xls command (load program to hyper flash) and provide the following inputs:
    20. xls
      1
      y
      y
      y
      3
      e6330000
      type "ctrl+A S" and select upload method "ascii", then choose file for uploading "AArch64_Gen3_Spi_MiniMon_V3.02_E6330000.mot", after upload finished press y key
      
    21. Power off the SK
    22. Press SW8
      
    23. Verify Sample Loader and MiniMonitor version
    24. SW1:OFF
      M3SK
       SW6[1]=OFF, SW6[2]=OFF, SW6[3]=OFF, SW6[4]=ON
      H3SK
       ws1.0: SW6[all]=OFF
       ws1.1/ws2.0: SW6[1]=ON, SW6[2]=ON, SW6[3]=OFF, SW6[4]=ON
      
      Press SW8
      

      You can confirm the following log (Ex: H3SK):

      R-Car Gen3 Sample Loader V3.02 2017.07.04		<-- !! V3.02 !!
       For Salvator , Kriek , and StarterKit.
       Board Judge     : Used Board-ID
       DDR_Init        : boardcnf[7] Salvator / Starter Kit (H3SIP_VER2.0)
       INITIAL SETTING : Starter Kit Premier / R-Car H3 ES2.0
       CPU             : AArch64 CA57
       DRAM            : LPDDR4 DDR3200
       DEVICE          : QSPI Flash(S25FS128) at 40MHz DMA
       BOOT            : Normal Boot
       BACKUP          : DDR Cold Boot
       jump to 0xE6330000
      
      R-Car Gen3 MiniMonitor V3.02 2017.07.04		<-- !! V3.02 !!
       Work Memory     : SystemRAM
       Board Name      : Starter Kit Premier
       Product Code    : R-Car H3 ES2.0
      
      >
      
    25. Set SW(Kernel boot mode) as follows:
    26. SW1:ON
      M3SK = SW6[all]:ON
      H3SK
       ws1.0 = SW6:OFF/OFF/OFF/ON
       ws1.1 = SW6:ON/OFF/ON/ON
       ws2.0 = SW6[all]:ON
      
    27. You can update the firmware with SK connected to KF.
    28. How to update:
      http://elinux.org/R-Car/Boards/M3SK#Flashing_firmware
      http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware

    Q&A site

    http://renesasrulz.com/r-car-h3-m3-cockpit/

    FAQ page

    https://elinux.org/R-Car/Boards/Yocto-Gen3-CommonFAQ

    FAQ

    How to get the SA001 Camera

    S001A Camera Specification:
    http://www.entroninc.com/prouduct.html
    (S001 is the same camera with S002, just connector slightly different)
    - Image Sensor : AR0140AT
    - ISP : AP0101
    - Resolution : 1280x728

    This camera cannot be purchased from the online shop.
    If you want to get the Entron S001A190CM0A camera,
    please contact to "RenesasJa" from https://elinux.org/Special:EmailUser/RenesasJa
    Please fill in the followings in the email.
    - Name
    - Company name
    - Email address
    - Why you need it (as detailed as possible)
    - Required quantity
    <Caution>
    Quantities are limited.
    Please understand that we cannot sell this camera to everyone.

    Known Issues

    1. USB3.0(CN2) cannot use with M3 SK.
    2. Please refer to the R-Car/Boards/Yocto-Gen3-CommonFAQ/I_can't_use_usb3.0(CN2)_with_Kingfisher_+_R-Car_Starter_Kit_Pro(M3SK)..
    3. H/W limitations
      - Board type name: "SBEV-RCAR-KF-M03"
       1. MOST is not supported.
      
      - Board type name: "SBEV-RCAR-KF-M03" and "SBEV-RCAR-KF-S03"
       1. BT-Audio(HFP)is not supported.
      
      - Board type name: "SBEV-RCAR-KF-M03", "SBEV-RCAR-KF-S03" and "SBEV-RCAR-KF-M04"
       1. Cannot use JTAG(CN3 on SK).
      
    4. Power supply
      SBEV-RCAR-KF-M03 and SBEV-RCAR-KF -S03 boards may not turn on even if you turn on SW6.
      In that case please turn on SW6 again.