https://elinux.org/api.php?action=feedcontributions&user=Khiem.renesas&feedformat=atomeLinux.org - User contributions [en]2024-03-29T10:35:01ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=Testing_Presentations&diff=537726Testing Presentations2020-11-04T03:33:40Z<p>Khiem.renesas: Add a Fuego presentation from OSSJ 2017</p>
<hr />
<div>='''Kernel CI'''=<br />
<br />
== Bootstraping a Local KernelCI [ELC 2019] ==<br />
'''Presenter:''' Michał Gałka, Collabora <br><br />
'''Summary:'''<br />
This presentation will go through the process of setting up a minimal <br><br />
local development/testing environment that's suitable for running the <br><br />
KernelCI phases of build, boot, test and results collection. <br><br />
<br />
* [https://elinux.org/images/8/86/Bootstraping_Local_KernelCI.pdf PDF] | [https://www.youtube.com/watch?v=ApoTzhc1IY0 VIDEO]<br />
<br />
== BoFs: Kernel Testing for Upstream with kernelci.org [ELC 2019] ==<br />
'''Presenter:''' Kevin Hilman, Linaro <br><br />
'''Summary:'''<br />
This presentation provides information about build failing, <br><br />
boot failing and display build status. <br><br />
<br />
* [https://elinux.org/images/f/ff/Kernelci.pdf PDF] | [https://elinux.org/images/f/ff/Kernelci.pdf VIDEO]<br />
<br />
== Introducing the "Lab in a Box" Concept [ELC 2018] ==<br />
'''Presenter:''' Patrick Titiano & Kevin Hillman, Baylibre <br><br />
'''Summary:'''<br />
This presentation provides information about the quality <br><br />
level without the leveraging CI and test automation. <br><br />
<br />
* [https://elinux.org/images/b/b4/Introducing_The_%E2%80%9CLab_in_a_Box%E2%80%9D_Concept_%28ELC-2018-Portland%29.pdf PDF] | [https://www.youtube.com/watch?v=aavoHUpzBGU VIDEO]<br />
<br />
== BoF: kernelci.org: A Million Kernel Boots and Counting [ELC 2016]==<br />
'''Presenter:''' Kevin Hilman, BayLibre <br><br />
'''Summary:'''<br />
This BoF will provide a very brief overview and current status of kernelci<br><br />
<br />
* [https://elinux.org/images/f/f6/Hilman.pdf PDF] | [https://youtu.be/37t-U0PGNlw VIDEO]<br />
<br />
== Mark Brown, Linaro & Kevin Hilman, BayLibre [ELCE 2016] ==<br />
'''Presenter:''' Kernelci.org Needs YOU! <br><br />
'''Summary:'''<br />
This presentation provides information about kernelci.org, <br><br />
Lab setup, and LAVA v2 installations. <br><br />
<br />
* [https://elinux.org/images/b/b9/Brown.pdf PDF] | [https://youtu.be/xaQuNM01YNo?list=PLbzoR-pLrL6pRFP6SOywVJWdEHlmQE51q VIDEO]<br />
<br />
== Building a Bards Farm: Continuous Integration and Remote Control [ELCE 2016] ==<br />
'''Presenter: ''' Antoine Tenart & Quentin Schulz, Free Electrons<br><br />
'''Summary:'''<br />
This talk will describe the Kernel CI goals and infrastructure<br> <br />
and how it communicates with our farm using LAVA. It gives a feedback<br> <br />
on how boards farm designed and present its second use case: remote<br> <br />
control of boards.<br />
<br />
* [https://elinux.org/images/0/09/Building_a_Bards_Farm.pdf PDF] | [https://youtu.be/sJvusc6jz4w?list=PLbzoR-pLrL6pRFP6SOywVJWdEHlmQE51q VIDEO]<br />
<br />
== BoFs: Kernel Testing for Upstream with kernelci.org [ELC 2015]==<br />
'''Presenter:''' Kevin Hilman, Linaro <br><br />
'''Summary:'''<br />
This BoF will provide a very brief overview on Kernel upstreaming as <br><br />
part of KernelCI project. <br><br />
<br />
* [https://elinux.org/images/f/ff/Kernelci.pdf PDF]<br />
<br />
== BoFs: Kernel Testing for Upstream with kernelci.org [ELC 2015]==<br />
'''Presenter:''' Kevin Hilman, Linaro <br><br />
'''Summary:'''<br />
This BoF will provide a very brief overview on Kernel upstreaming as <br><br />
part of KernelCI project. <br><br />
<br />
* [https://elinux.org/images/f/ff/Kernelci.pdf PDF]<br />
<br />
==BoFs: kernelci.org [ELCE 2015] ==<br />
'''Presenter:''' Kevin Hilman, Linaro <br><br />
'''Summary:'''<br />
This presentation provides information about the upstream kernel CI <br><br />
and the current state of the upstream tree. <br><br />
<br />
* [https://elinux.org/images/f/ff/Kernelci.pdf PDF] | [https://www.youtube.com/watch?v=F66Ff93503E VIDEO]<br />
<br />
= '''FUEGO''' =<br />
<br />
== Fuego test sytem [ELC 2019] ==<br />
'''Presenter:''' Hirotaka Motai, Mitsubishi Electric Corp. <br><br />
'''Summary:'''<br />
This presentation provides information about the run-time logger in Fuego by showing the actual use cases and functional checking. <br><br />
<br />
* [https://elinux.org/images/a/a4/ELC19_Automated_run-time_regression_testing_with_Fuego_HirotakaMotai-190821d.pdf PDF] | [https://www.youtube.com/watch?v=RPBNBwPc7mo VIDEO]<br />
<br />
== Testing with Volcanoes - Fuego+LAVA Going Distributed [ELC 2017] ==<br />
'''Presenter:''' Jan-Simon Moeller, The Linux Foundation<br><br />
'''Summary:'''<br />
This presentation provides information about the features of the combined infrastructure and highlights the tools and work done <br><br />
to integrate both tools. <br><br />
<br />
* [https://elinux.org/images/8/88/ELC-jsmoeller-2017-02-TESTING-VULCANOES-LAVA-FUEGO.pdf PDF] | [https://youtu.be/IA6cBIGuHm4 VIDEO]<br />
<br />
== Enhance Fuego Test Efficiency by Applying Additional Software & Hardware Solutions [OSSJ 2017] ==<br />
'''Presenter:''' Khiem Nguyen, Renesas Corporation <br><br />
'''Summary:'''<br />
This presentation provides information about integrating more software services and hardware solutions (controller for development boards)<br />
to enhance the test automation efficiency. <br><br />
<br />
* [https://elinux.org/images/1/13/OSSJ_Renesas_Fuego_enhancement_KhiemNguyen_20170531_Rev1.0.pdf PDF]<br />
<br />
= '''Automation''' =<br />
== Automated Testing Laboratory for Embedded Linux Distributions [ELC 2016] ==<br />
<br />
'''Presenter:''' Pawel Wieczorek, Samsung R&D Institute Poland <br><br />
'''Summary:'''<br />
This talk provides information about problems faced while building automatic testing infrastructure for Tizen operating <br><br />
system images. <br><br />
<br />
* [https://elinux.org/images/1/1e/Wieczorek.pdf PDF] | [https://youtu.be/KTiXNQbVefI VIDEO]<br />
<br />
== Automated Flashing and Testing for Continuous Integration [ELC 2015] ==<br />
'''Presenter:''' Igor Stoppa, Intel <br><br />
'''Summary:'''<br />
This presentation provides information about verifying a software image on an appropriate target hardware device and <br><br />
hardware configuration. <br><br />
<br />
* [https://elinux.org/images/7/7b/Automated_Flashing_and_Testing_for_Continuous_Integration.pdf PDF]<br />
<br />
== Automated Testing with ktest.pl (Embedded Edition) [ELC 2012] ==<br />
'''Presenter:''' Steven Rostedt, Red Hat<br><br />
'''Summary:'''<br />
This presentation provides information about write to build, install, boot, and test kernel remotely. <br><br />
<br />
* [https://elinux.org/images/f/fd/Automated_Testing_with_ktest.pl_%28Embedded_Edition%29.pdf PDF]<br />
<br />
== Distributed Cross Platform Test Automation [ELC 2006] ==<br />
'''Presenter:''' William Marone <br><br />
'''Summary:'''<br />
This presentation provides information about test AXFS functionality, quickly build, run test, and across multiple architectures <br><br />
and kernels. <br><br />
<br />
* [http://DistributedCrossPlatformTest.pdf PDF]<br />
<br />
= '''Board Farms''' =<br />
<br />
== Grabbing Audio and Video on a Board Farm [ELCE 2018] ==<br />
'''Presenter:''' Krzysztof Opasiak, Samsung R&D Institute Poland <br><br />
'''Summary:'''<br />
This presentation provides information about audio and video capture <br><br />
capabilities and unified remote access to any Single Board Computer. <br><br />
<br />
* [https://youtu.be/mw79nfp7ARE VIDEO]<br />
<br />
== Farming together [ELCE 2017] ==<br />
'''Presenter: '''Andrew Murray, Witekio <br><br />
'''Summary:'''<br />
This presentation will provide an overview of the Witekio farm<br> <br />
highlighting the challenges faced - both in hardware challenges<br><br />
(connecting boards to farms) and software challenges.<br />
<br />
* [https://elinux.org/images/5/52/BoF-FarmingTogether.pdf PDF] | [https://youtu.be/-oO9y2HnoYs VIDEO]<br />
<br />
= '''Others''' =<br />
<br />
== Testing Laboratory Layers [ELC 2019] ==<br />
'''Presenter:''' Paweł Wieczorek, Samsung R&D Institute Poland <br><br />
'''Summary:'''<br />
These slides cover API design decisions for testing laboratories focusing on the SLAV test lab stack case and shifting to a user-centric perspective and possible outcome of such process.<br />
<br />
* [https://elinux.org/images/3/3c/Test_Lab_API.pdf PDF] | [https://www.youtube.com/watch?v=gWVp9JqVTog VIDEO]<br />
<br />
== Tips for Writing Good Tests for Linux [ELC 2018] ==<br />
'''Presenter:''' Tim Bird, Sony Corporation <br><br />
'''Summary:'''<br />
This talk will review and compare different test writing frameworks, <br><br />
including kself-test, LTP and Fuego, and describe each one's strengths <br><br />
and weaknesses. A basic introduction to writing a test in each one will be given.<br><br />
<br />
* [https://elinux.org/images/6/60/Tips-for-Writing-Good-Tests-for-Linux-2018-03-ELC.pdf PDF] | [https://www.youtube.com/watch?v=NzJFwCUGJtc VIDEO]<br />
<br />
== Testing Remote Embedded Devices Made Easy Using Open-Hardware MuxPi [ELC 2018] ==<br />
'''Presenter:''' Pawel Wieczorek, Samsung R&D Institute Poland <br><br />
'''Summary:'''<br />
This talk covers a fresh open hardware approach at providing remote access to embedded devices and the new Tizen GNU/Linux <br><br />
distribution's testing laboratory. <br><br />
<br />
* [https://elinux.org/images/4/42/Piece_of_cake.pdf PDF] | [https://www.youtube.com/watch?v=Hx9MEhR05cU VIDEO]<br />
<br />
== Impact of Platform Firmware on Linux Kernel [ELC 2018] ==<br />
'''Presenter:''' Megha Dey & Sal Praneeth Prakhya, Intel <br><br />
'''Summary:'''<br />
This presentation introduces LUV (Linux UEFI Validation); a unified <br><br />
framework of several open-source test-suites packaged into a cohesive <br><br />
and easy-to-use product that aims to help firmware developers uncover <br><br />
bugs in the implementation of UEFI firmware at critical levels of the s/w stack. <br><br />
<br />
* [https://elinux.org/images/b/b7/Impact_of_platform_firmware_on_linux_kernel.pdf PDF] | [https://www.youtube.com/watch?v=7aME1lxY71Q VIDEO]<br />
<br />
== Keynote: The Maintainer's Paradox [ELC 2018] ==<br />
'''Presenter:''' Tim Bird, Sr. Software Engineer, Sony <br><br />
'''Summary:'''<br />
The overall goal is to improve Linux for use in consumer electronics <br><br />
products, by improving Linux system testing, directing technical initiatives <br><br />
of the Linux Foundation and encouraging companies to participate in the open <br><br />
source community. <br><br />
<br />
* [https://elinux.org/images/4/4e/The-Maintainers-Paradox-2018-ELC-Tim-Bird.pdf PDF] | [https://www.youtube.com/watch?v=7aME1lxY71Q VIDEO]<br />
<br />
== From Zero to First Test in Your Own LAVA Laboratory in less than 45 minutes [ELC 2017] ==<br />
'''Presenter:''' Pawel Wieczorek, Samsung R&D Institute Poland <br><br />
'''Summary:'''<br />
This presentation talks about setting up one's own Test Lab using LAVA <br><br />
<br />
* [https://elinux.org/images/8/84/From_zero_to_first_test_in_your_own_LAVA_laboratory.pdf PDF] | [https://www.youtube.com/g4Hw5I2sk3A VIDEO]<br />
<br />
== Herd Your Boards, Become a Farmer [ELCE 2016] ==<br />
'''Presenter:''' Geert Uytterhoeven, Glider bvba<br><br />
'''Summary:'''<br />
This presentation provides information about organizing development boards in a board farm, and about board farm requirements and challenges.<br><br />
It offers practical solutions for overcoming issues related to controlling, powering, monitoring, and automating boards in your farm.<br />
<br />
* [[Media:Herd Your Boards.pdf|PDF]] | [https://youtu.be/kwqmjeqAx-E?list=PLbzoR-pLrL6pRFP6SOywVJWdEHlmQE51q VIDEO]<br />
<br />
== Linux Integrated System Analysis (LISA) & Friends [ELC 2016] ==<br />
'''Presenter:''' Patrick Bellasi, ARM Ltd <br><br />
'''Summary:'''<br />
This presentation provides information about the new Linux integrated system analysis framework for easier development and ideal <br><br />
for detailed debug scenarios. <br><br />
<br />
* [https://elinux.org/images/1/12/Bellasi.pdf PDF] | [https://youtu.be/m949uduHHsw VIDEO]<br />
<br />
== Linux Kernel Selftest Framework - Quality Control for New Releases [ELC 2015] ==<br />
<br />
'''Presenter:''' Shuah Khan, Samsung <br><br />
'''Summary:'''<br />
This presentation provides information about running the kselftest,kselftest git, installation of the self-test, and run test from <br><br />
the install location. <br><br />
<br />
* [https://elinux.org/images/6/61/Linux_Kernel_Selftest_Framework_-_Quality_Control_for_New_Releases.pdf PDF]<br />
<br />
== Kernel Testing Tools and Techniques [ELC 2013] ==<br />
<br />
'''Presenter:''' Matt Porter, Texas Instruments, Inc <br><br />
'''Summary:'''<br />
This presentation provides information about frameworks, lab tools, techniques of the open test, autotest, Jenkins, ktest. <br><br />
<br />
* [https://elinux.org/images/3/31/Elc2013_Porter.pdf PDF] | [http://free-electrons.com/blog/elc-2013-videos VIDEO]</div>Khiem.renesashttps://elinux.org/index.php?title=File:OSSJ_Renesas_Fuego_enhancement_KhiemNguyen_20170531_Rev1.0.pdf&diff=537721File:OSSJ Renesas Fuego enhancement KhiemNguyen 20170531 Rev1.0.pdf2020-11-04T03:29:18Z<p>Khiem.renesas: This is the presentation file from OSSJ 2017.
Original URL: https://static.sched.com/hosted_files/ossjapan2017/d6/OSSJ_Renesas_Fuego_enhancement_KhiemNguyen_20170531_Rev1.0.pdf</p>
<hr />
<div>== Summary ==<br />
This is the presentation file from OSSJ 2017.<br />
Original URL: https://static.sched.com/hosted_files/ossjapan2017/d6/OSSJ_Renesas_Fuego_enhancement_KhiemNguyen_20170531_Rev1.0.pdf</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=501796R-Car2019-10-17T09:33:58Z<p>Khiem.renesas: /* R-Car U-Boot */ Update the URL of git repo</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3NSK|R-Car Starter Kit Pro(M3N)]]<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: https://github.com/renesas-rcar/linux-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
NOTE: The git repo at git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git become outdated from Oct 2019.<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git@gitlab.denx.de:u-boot/custodians/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git@gitlab.denx.de:u-boot/custodians/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
{| class="wikitable"<br />
|+ Latest R-Car Gen3 Community BSP<br />
|-<br />
|'''Yocto Project (YP) releases'''<br />
|'''Branch name'''<br />
|'''Tag name'''<br />
|'''For build instructions, refer to'''<br />
|-<br />
|'''YP 2.5 (codename: sumo)''' <br />
|sumo-dev<br />
|sumo-Yocto-v3.15.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.6 (codename: thud)''' <br />
|thud-dev<br />
|thud-Yocto-v3.21.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.7 (codename: warrior)''' <br />
|warrior-dev<br />
|warrior-Yocto-v3.19.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 3.0 (codename: zeus)''' <br />
|zeus-dev<br />
|zeus-M2-Yocto-v3.21.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/zeus-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/zeus-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|}<br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [https://docs.automotivelinux.org/docs/en/master/getting_started/reference/getting-started/machines/renesas.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
= R-Car Connected Car SDK =<br />
<br />
See [[R-Car/Connected Car SDK startup guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car/Boards/U-Boot-Gen3&diff=501791R-Car/Boards/U-Boot-Gen32019-10-17T09:30:45Z<p>Khiem.renesas: /* Obtain U-Boot sources */ Update the URL of git repo</p>
<hr />
<div>{{TOC right}}<br />
<br />
== Introduction ==<br />
<br />
This is the Wiki for the U-Boot on Renesas R-Car Gen3 SoCs and boards .<br />
Refer to the [[R-Car]] page for information about Renesas' R-Car SoC family.<br />
<br />
== Supported boards ==<br />
<br />
As of U-Boot 2019.04, the following boards are supported:<br />
{| class="wikitable"<br />
|+ Supported boards in U-Boot 2019.04<br />
|-<br />
! Board !! U-Boot defconfig || Update procedure<br />
|-<br />
| [[R-Car/Boards/H3SK|R8A7795 H3 ULCB]] || r8a7795_ulcb_defconfig || [[R-Car/Boards/H3SK#Flashing_firmware|Flashing firmware]]<br />
|-<br />
| [[R-Car/Boards/M3SK|R8A7796 M3 ULCB]] || r8a7796_ulcb_defconfig || [[R-Car/Boards/M3SK#Flashing_firmware|Flashing firmware]]<br />
|-<br />
| [[R-Car/Boards/Salvator-X|R8A7795 H3 Salvator-X]]/[[R-Car/Boards/Salvator-XS|XS]] ES2.0+ || r8a7795_salvator-x_defconfig || N/A<br />
|-<br />
| [[R-Car/Boards/Salvator-X|R8A7796 M3-W Salvator-X]]/[[R-Car/Boards/Salvator-XS|XS]] || r8a7796_salvator-x_defconfig || N/A<br />
|-<br />
| [[R-Car/Boards/Salvator-X|R8A77965 M3-N Salvator-X]]/[[R-Car/Boards/Salvator-XS|XS]] || r8a77965_salvator-x_defconfig || N/A<br />
|-<br />
| [[R-Car/Boards/Eagle|R8A77970 V3M Eagle]] || r8a77970_eagle_defconfig || N/A<br />
|-<br />
| [[R-Car/Boards/Ebisu|R8A77990 E3 Ebisu]] || r8a77990_ebisu_defconfig || N/A<br />
|-<br />
| [[R-Car/Boards/Draak|R8A77995 D3 Draak]] || r8a77995_draak_defconfig || N/A<br />
|}<br />
<br />
! WARNING: R-Car R8A7795 H3 ES1.x is NOT supported!<br />
<br />
== Building U-Boot manually ==<br />
<br />
Building U-Boot can be done manually by using the U-Boot sources. This process does NOT produce IPL/ATF/BL binaries, only U-Boot binary is produced.<br />
<br />
=== Prerequisites ===<br />
<br />
* Running mainline U-Boot is only supported with IPL/ATF/BL revision 2.23 and newer.<br />
* ARM cross-compiler is mandatory to build U-Boot.<br />
<br />
=== ARM cross-compiler ===<br />
<br />
Debian and Ubuntu includes an ARM cross-compiler in its standard package feed. You can install it as follows:<br />
<br />
apt-get install gcc-aarch64-linux-gnu<br />
<br />
Other distributions likely also provide ARM cross-compilers. Consult distro-specific documentation for details.<br />
<br />
=== Obtain U-Boot sources ===<br />
<br />
The preferred method of obtaining U-Boot sources is through git VCS, using git protocol:<br />
<br />
git clone git@gitlab.denx.de:u-boot/u-boot.git<br />
<br />
or via HTTPS:<br />
<br />
git clone https://gitlab.denx.de/u-boot/u-boot.git<br />
<br />
Finally, check out the version of U-Boot that will be used for the build:<br />
<br />
cd u-boot<br />
git checkout -b my_working_branch v2019.04<br />
<br />
U-Boot [https://gitlab.denx.de/u-boot/u-boot/-/tags git tags] also provides snapshots.<br />
<br />
=== Prepare build environment ===<br />
<br />
Before building U-Boot for R-Car Gen3 system, the following environment variables need to be configured:<br />
<br />
export ARCH=arm64<br />
export CROSS_COMPILE=aarch64-linux-gnu-<br />
<br />
The later variable must match the prefix of the Aarch64 cross-toolchain installed on your system, the example above is valid for Debian and Ubuntu,<br />
<br />
=== Build U-Boot ===<br />
<br />
The U-Boot sources must be configured for a particular supported platform. List of supported platforms and matching U-Boot defconfigs is available at [[R-Car/Boards/U-Boot-Gen3#Supported_boards|supported boards]].<br />
<br />
make r8a779x_y_defconfig<br />
<br />
for example to configure U-Boot sources for R8A7795 H3 ULCB board:<br />
<br />
make r8a7795_ulcb_defconfig<br />
<br />
Once configured, U-Boot sources can be compiled to produce u-boot.bin and u-boot-elf.srec:<br />
<br />
make<br />
<br />
To speed up build process, -jN option can be passed to make to start multiple jobs at the same time, this is beneficial especially on SMP systems. The following example starts up to (number of CPUs in a system + 1) jobs, which is the recommended amount:<br />
<br />
make -j`expr \`nproc\` + 1`<br />
<br />
== Flashing U-Boot ==<br />
<br />
Each platform has a slightly different process for updating the content of the flash. The [[R-Car/Boards/U-Boot-Gen3#Supported_boards|list of supported boards]] contains links to instructions for updating each supported board.<br />
<br />
== U-Boot recovery SPL ==<br />
<br />
=== Preparation ===<br />
<br />
Mainline U-Boot supports generating SPL binary which can be uploaded in SCIF loader mode and used e.g. to recover a blank system. During standard U-Boot build, the recovery SPL is generated in "spl/u-boot-spl.scif" .<br />
<br />
The recovery SPL itself uses Ymodem upload to quickly download additional blobs and execute them on the system, namely ATF BL2 and U-Boot proper. It is thus required to have a terminal program capable of Ymodem upload.<br />
<br />
The recovery SPL uses patched ATF BL2 to initialize the system and then jump back to Ymodem upload. It is thus required to build an ATF with patch [https://github.com/marex/arm-trusted-firmware/commit/ced85c01d886cc39f51cc9dd3bae72e7061886a7 rcar_gen3: plat: Add support for jumping to U-Boot SPL from BL2] for use with the recovery SPL. The patch makes the BL2 jump back into the U-Boot SPL instead of continuing with the regular boot. This is necessary to make it possible to load U-Boot via Ymodem upload as the next step. The resulting ATF binary must be wrapped into U-Boot uImage format to work with the SPL:<br />
<br />
mkimage -A arm -O arm-trusted-firmware -T firmware -C none -a 0xe6304000 -e 0xe6304000 -n "BL2" -d build/rcar/release/bl2.bin bl2.uimage<br />
<br />
U-Boot binary must be wrapped in a similar way. However, it is recommended to compress the U-Boot binary first, to further speed up the Ymodem upload. The decompression on the SPL side is much faster, while the Ymodem upload is the bottleneck here.<br />
<br />
gzip -9 u-boot.bin<br />
mkimage -A arm -T firmware -C gzip -O u-boot -a 0x50000000 -e 0 -n "U-Boot" -d u-boot.bin.gz u-boot.gz.img<br />
<br />
The result of this preparation are three files, "spl/u-boot-spl.scif", "bl2.uimage" and "u-boot.gz.img", which are required for the recovery.<br />
<br />
=== Recovery ===<br />
<br />
The first step is to put the system into SCIF loader mode, e.g. by flipping MD pins or erasing the first HF/QSPI NOR erase block. After reset or power cycle, the system will enter the SCIF loader mode:<br />
<br />
SCIF Download mode (w/o verification)<br />
(C) Renesas Electronics Corp.<br />
<br />
-- Load Program to SystemRAM ---------------<br />
please send !<br />
<br />
Next, send the "u-boot-spl.scif" file via ASCII upload. U-Boot SPL will start and request Ymodem upload.<br />
<br />
U-Boot SPL 2019.07-rc4-00155-gb02ecd04f5 (Jun 15 2019 - 15:27:14 +0200)<br />
Trying to boot from UART<br />
CCC<br />
<br />
At this point, send the "bl2.uimage" file. ATF BL2 will start, perform the<br />
system initialization and drop back into the U-Boot SPL Ymodem upload.<br />
<br />
Loaded 128765 bytes<br />
INFO: ARM GICv2 driver initialized<br />
...<br />
NOTICE: BL2: Normal boot<br />
U-Boot SPL 2019.07-rc4-00155-gb02ecd04f5 (Jun 15 2019 - 15:27:14 +0200)<br />
Trying to boot from UART<br />
CCC<br />
<br />
At this point, send the "u-boot.gz.img" file. U-Boot proper will start<br />
and the user is free to update the system via any supported method, e.g.<br />
ethernet, USB, serial and so on.<br />
<br />
Loaded 414300 bytes<br />
<br />
<br />
U-Boot 2019.07-rc4-00155-gb02ecd04f5 (Jun 15 2019 - 15:27:24 +0200)<br />
<br />
CPU: Renesas Electronics R8A7795 rev 2.0<br />
Model: Renesas Salvator-X board based on r8a7795 ES2.0+<br />
DRAM: 3.9 GiB<br />
MMC: sd@ee100000: 0, sd@ee140000: 1, sd@ee160000: 2<br />
Loading Environment from MMC... OK<br />
In: serial@e6e88000<br />
Out: serial@e6e88000<br />
Err: serial@e6e88000<br />
Net: eth0: ethernet@e6800000<br />
Hit any key to stop autoboot: 0<br />
=><br />
<br />
Once the system has been updated, power cycle the system.</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=501786R-Car2019-10-17T08:51:49Z<p>Khiem.renesas: /* Renesas R-Car Gen 3 BSP Tree */ Update the official URL of git repo</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3NSK|R-Car Starter Kit Pro(M3N)]]<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: https://github.com/renesas-rcar/linux-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
NOTE: The git repo at git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git become outdated from Oct 2019.<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
{| class="wikitable"<br />
|+ Latest R-Car Gen3 Community BSP<br />
|-<br />
|'''Yocto Project (YP) releases'''<br />
|'''Branch name'''<br />
|'''Tag name'''<br />
|'''For build instructions, refer to'''<br />
|-<br />
|'''YP 2.5 (codename: sumo)''' <br />
|sumo-dev<br />
|sumo-Yocto-v3.15.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.6 (codename: thud)''' <br />
|thud-dev<br />
|thud-Yocto-v3.21.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.7 (codename: warrior)''' <br />
|warrior-dev<br />
|warrior-Yocto-v3.19.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 3.0 (codename: zeus)''' <br />
|zeus-dev<br />
|zeus-M2-Yocto-v3.21.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/zeus-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/zeus-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|}<br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [https://docs.automotivelinux.org/docs/en/master/getting_started/reference/getting-started/machines/renesas.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
= R-Car Connected Car SDK =<br />
<br />
See [[R-Car/Connected Car SDK startup guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=497951R-Car2019-08-29T04:18:46Z<p>Khiem.renesas: /* R-Car Yocto */ Update latest Yocto Community YBSP based on YP 2.6 (thud)</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3NSK|R-Car Starter Kit Pro(M3N)]]<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
{| class="wikitable"<br />
|+ Latest R-Car Gen3 Community BSP<br />
|-<br />
|'''Yocto Project (YP) releases'''<br />
|'''Branch name'''<br />
|'''Tag name'''<br />
|'''For build instructions, refer to'''<br />
|-<br />
|'''YP 2.5 (codename: sumo)''' <br />
|sumo-dev<br />
|sumo-Yocto-v3.15.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.6 (codename: thud)''' <br />
|thud-dev<br />
|thud-Yocto-v3.21.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.7 (codename: warrior)''' <br />
|warrior-dev<br />
|warrior-Yocto-v3.19.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|}<br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [https://docs.automotivelinux.org/docs/en/master/getting_started/reference/getting-started/machines/renesas.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
= R-Car Connected Car SDK =<br />
<br />
See [[R-Car/Connected Car SDK startup guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=494016R-Car2019-06-20T23:54:21Z<p>Khiem.renesas: /* R-Car Automotive Grade Linux */ Fix the broken link to AGL documentation</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3NSK|R-Car Starter Kit Pro(M3N)]]<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
{| class="wikitable"<br />
|+ Latest R-Car Gen3 Community BSP<br />
|-<br />
|'''Yocto Project (YP) releases'''<br />
|'''Branch name'''<br />
|'''Tag name'''<br />
|'''For build instructions, refer to'''<br />
|-<br />
|'''YP 2.5 (codename: sumo)''' <br />
|sumo-dev<br />
|sumo-Yocto-v3.15.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.6 (codename: thud)''' <br />
|thud-dev<br />
|thud-Yocto-v3.19.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.7 (codename: warrior)''' <br />
|warrior-dev<br />
|warrior-Yocto-v3.19.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|}<br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [https://docs.automotivelinux.org/docs/en/master/getting_started/reference/getting-started/machines/renesas.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=493991R-Car2019-06-20T05:13:53Z<p>Khiem.renesas: /* R-Car Yocto */ Create table for Community YBSP and add latest Yocto Community YBSP based on YP 2.7 (warrior)</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3NSK|R-Car Starter Kit Pro(M3N)]]<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
{| class="wikitable"<br />
|+ Latest R-Car Gen3 Community BSP<br />
|-<br />
|'''Yocto Project (YP) releases'''<br />
|'''Branch name'''<br />
|'''Tag name'''<br />
|'''For build instructions, refer to'''<br />
|-<br />
|'''YP 2.5 (codename: sumo)''' <br />
|sumo-dev<br />
|sumo-Yocto-v3.15.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.6 (codename: thud)''' <br />
|thud-dev<br />
|thud-Yocto-v3.19.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|'''YP 2.7 (codename: warrior)''' <br />
|warrior-dev<br />
|warrior-Yocto-v3.19.0<br />
|[https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/warrior-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md]<br />
|-<br />
|}<br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [http://docs.automotivelinux.org/master/docs/getting_started/en/dev/reference/machines/R-Car-Starter-Kit-gen3.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=492861R-Car2019-05-31T06:53:02Z<p>Khiem.renesas: </p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3NSK|R-Car Starter Kit Pro(M3N)]]<br />
|<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.19.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [http://docs.automotivelinux.org/master/docs/getting_started/en/dev/reference/machines/R-Car-Starter-Kit-gen3.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=492856R-Car2019-05-31T06:24:44Z<p>Khiem.renesas: /* R-Car Yocto */ Update latest Yocto Community YBSP based on YP 2.6 (thud)</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.19.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [http://docs.automotivelinux.org/master/docs/getting_started/en/dev/reference/machines/R-Car-Starter-Kit-gen3.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=488016R-Car2019-03-29T09:40:18Z<p>Khiem.renesas: /* R-Car Yocto */ Update latest Yocto Community YBSP based on YP 2.5 (sumo)</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [http://docs.automotivelinux.org/master/docs/getting_started/en/dev/reference/machines/R-Car-Starter-Kit-gen3.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=Japan_Technical_Jamboree_68&diff=486561Japan Technical Jamboree 682019-03-07T03:34:54Z<p>Khiem.renesas: /* Agenda */ Add links to 2 presentation slides (PDF, in English)</p>
<hr />
<div>{| cellpadding="0" cellspacing="0" border="0"<br />
|-<br />
|[[Image:headTitle_LFCEWG.png]]<br />
|-<br />
| style="text-align:right" |<span style="font-size:large">Date: March 8th / 日付: 3月8日(金)</span><br />
* At Nakano Sunplaza / 於、中野サンプラザ<br />
* Please join "celinux-dev" mailinglist to get the latest announcement.<br />
* "celinux-dev" メーリングリストにこのイベント関係のアナウンスが流れます。ぜひ参加してください。<br />
** [http://lists.celinuxforum.org/mailman/listinfo/celinux-dev How to join the mailing list.]<br />
|-<br />
|[[Image:J_Jam_SessionProp.gif]]<br />
|-<br />
|style="text-align:right" |[[Japan TJ Session Proposal|<span style="color:red">Session proposal how-to. / 提案の方法</span>]]<br />
|}<br />
= Introduction / はじめに =<br />
* The Japan Technical Jamboree is a forum-wide technical meeting of the CE Workgroup of the Linux Foundation. This meeting will be located conveniently in Japan and use Japanese as the native language of the event. <br />
* A general guidance page is available. / 初めての方はこちらもお読みください。<br />
** [[Japan Technical Jamboree Guidance]] (Japanese/English)<br />
== Special remarks for non Japanese speakers ==<br />
* This page is Japanese/English bilingual. Please allow some contents on this page are not translated into English because of this event is Japan regional one, though we try to place English translation.<br />
* If you would like to perform your presentation in English, we also welcome you to join! We hope you to speak slowly without any complicated expressions. Most Japanese developers are capable to understand plain English.<br />
<br />
== Why Jamboree / ジャンボリーに寄せる思い ==<br />
<br />
* [[Media:IntroducingCEWG_2015.pdf|"'''Hop-Step-Jump''' Strategy (pdf file)"]]<br />
<br />
* [[Media:IntroducingCEWG_2015.pdf|"Here"]] please find an introductory material of CE Workgroup explaining "Why Jamboree". It is one of important event for us for "Hop-Step-Jump" strategy to let embedded system developers jumping into open community. We know many of you are too busy to collaborate with open communities because of your daily jobs. And you may be concerned for your language skill or technical knowledge. Then we prepared this Jamboree as the entry point for those people to the open community. You may speak in Japanese. You do not need to worry about your technical skill. But we strongly would like encouraging you to come to the international stage like Embedded Linux Conference which is the stage of "Hop" to the global open community!<br />
<br />
* It is not the place only for Consumer electronics field but also we greatly welcome other domain embedded system developers and more. Even if you are working for super computer or enterprise server system, you will be welcomed! '''Let's enjoy OSS together!!'''<br />
<br />
* [[Media:IntroducingCEWG_2015.pdf|"このスライド"]]はCE Workgroupの説明資料からの抜粋です。この中でCEWGがジャンボリーにかける思いを説明しています。組み込みシステム開発にあたられている皆さんは日々の仕事に追われて大変に忙しい毎日を送られている事、良く知っています。また、英語の問題、または本当に技術的な実力があるのだろうか(ほとんどの場合無用な心配ですが)といった心配もあって、なかなかOSSコミュニティーとの交流を始める勇気が湧かない、というのが現実ではないでしょうか。そのような皆さんのために、CEWGは、その前身のCE Linux Forumの時代から、日本で日本語で技術ディスカッションをする場(ジャンボリー)を'''ホップ'''の場として、世界中の組み込みOSS開発者が集まる場、Embedded Linux Conference (US/Europe)を'''ステップ'''の場として、OSS開発者のグローバルなコミュニティーに'''ジャンプ'''できるような場を設けています。<br />
<br />
* この場は決して、Consumer Electronics関係の皆さんだけのものではありません。たとえば自動車関係、産業機器関係、医療機器関係などより広範な組み込みシステム関係の皆さん、さらにはスーパーコンピュータやエンタープライズシステムなどに関わられている皆さんの参加もこころから歓迎します。'''Let's enjoy OSS together!!'''<br />
<br />
== Previous Jamboree ==<br />
* Please look into the wiki page. / 下記のWikiページをご覧ください。<br />
** [[Japan Technical Jamboree 67]]<br />
<br />
== Hash tag on Twitter ==<br />
* '''#CELFJP'''<br />
<br />
<!--<br />
* togetter (Previous Japan Jamboree)<br />
** https://togetter.com/li/1177235<br />
--><br />
<br />
= Date and venue... / 日付・場所... =<br />
{|<br />
|+<br />
|-<br />
| style="vertical-align:top" |<br />
[[Image:NakanoSunplaza2.jpg]]<br />
| style="vertical-align:top; background-color:#F0F0F0" width=90% |<br />
* Date '''March 8th, 2019'''<br />
** '''Starting at 10 am'''<br />
* At '''''Nakano Sunplaza / 8F Training Room 2''''' / 会場 '''''中野サンプラザ / 8階・研修室2'''''<br />
** Nakano Sunplaza is located just close to '''Nakano''' station (JR/Tokyo Metoro ).<br />
** http://www.sunplaza.jp/ (Japanese)<br />
* Admission: '''''Free of charge''''' / 参加費用: '''''無料'''''<br />
* Registration: '''''Not Required''''' / 参加登録: '''''不要'''''<br />
* Not limited for CE Workgroup members. / CE Workgroup会員以外も参加・セッション持ち込み共に可能<br />
* Coordinators / 世話役 (Your inquiries in English welcome)<br />
** Hisao Munakata / 宗像尚郎 (hisao_dot_munakata_dot_vt(a)renesas_dot_com) <br />
** Satoru Ueda / 上田理 (Satoru_dot_Ueda(a)jp_dot_sony_dot_com)<br />
|}<br />
== Registration / 参加登録 ==<br />
* No registration required / 参加登録は要りません。<br />
<br />
= Main Topics =<br />
* Embedded Linux Conference Europe is coming! [https://events.linuxfoundation.org/events/elc-openiot-europe-2018/ ELC-E 2018] .<br />
<br />
= Agenda / 進行 =<br />
== Agenda ==<br />
<br />
{|<br />
|+<br />
! style="text-align:left; background-color:#B0FFB0; width:50" | Time<br />
! style="text-align:left; background-color:#B0FFB0; width:70%" | Title and presenter<br />
! style="text-align:left; background-color:#B0FFB0" | Notes<br />
Presentation Materials<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 10:00..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* Opening / 連絡事項<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 10:15am..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Status of Embedded Linux'''<br />
* '''Tim Bird'''<br />
** Recent Status of Embedded Linux technologies (in slides) <br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* [[Media:Status-of-embedded Linux-2018-11-JJ67.pdf|PDF_English]]<br />
* (In English / 英語のセッションです)<br />
* [[Image:Youtube.png]] [[Image:Us_flagSymbol.gif]] [https://youtu.be/1crGEo0dBJs Video]<br />
|-<br />
| style="vertical-align:top; background-color:#B0B0FF" | 11:30..<br />
| style="vertical-align:top; background-color:#B0B0FF" | Lunch<br />
| style="vertical-align:top; background-color:#B0B0FF" |<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 1:00pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Let's look into debootstrap'''<br />
* '''Hideki Yamane''' (SIOS Technology, Inc. / Debian Project)<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 1:30pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Running the AVS device SDK on NuttX/LC823450 '''<br><br />
~Linux向けアプリケーションソフトウェアをNuttXで動作させる~<br />
* '''Masayuki Ishikawa''' (Sony Corp.)<br />
** https://github.com/alexa/avs-device-sdk/wiki<br />
** Linux 環境向けに用意された Alexa Audio Voice Service を NuttX 上で動作させます。'''<font color=red>NuttXがPosixとの互換性が高い</font>'''ことはこのようなアドバンテージがあります。<br />
** また併せて nghttp2 が'''<font color=red>他からネットワーク系のモジュールを持ち込まなくてもNuttX環境のみで動作する</font>'''ことなども注目してください。<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 2:15pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Yocto projectを使ったCustom Linux imageのつくりかた(仮)'''<br />
* '''Toshifumi NISHINAGA''' (NTT Communications)<br />
** Yocto projectを用いてCustom Linux imageを作る方法について話す予定です。<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 3:15pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''DebianにおけるSDカードへの書込み回数の低減方法 (How to reduce the number of write io to SD card on Debian)'''<br />
* '''Masahiro YAMADA''' (Toshiba Memory)<br />
** Debian使用時におけるSDカードへの意図していない書込みを、設定だけで極力減らす方法と、その副作用の紹介<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 4:00pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''An Approach to Manage AGL OSS License Compliance'''<br />
* '''Thuy Tran''' (Renesas)<br />
** The talk discusses about open-source tools which support scanning OSS license/copyright in the build CI workflow.<br><br />
:: The generated output, i.e. the SPDX documents, can help automate the OSS license management in AGL community.<br />
** 3/5,6のAGL AMMで発表する内容を話します。英語での発表となります。<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* [https://static.sched.com/hosted_files/aglammjapan2019/c2/Renesas_ThuyTran_OSS_License_Management_AGL_AMM_Japan_2019.pdf PDF_English]<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 4:40pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Use RAUC as AGL SOTA Solution'''<br />
* '''Thu Nguyen''' (Renesas)<br />
** The talk shares the experiences of using RAUC as a Software update solution for AGL software.<br />
** 3/5,6のAGL AMMで発表する内容を話します。英語での発表となります。<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* [https://static.sched.com/hosted_files/aglammjapan2019/5b/Renesas_ThuNguyen_Use_RAUC_as_AGL_SOTA.pdf PDF_English]<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 5:30pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Optimizing Inter-node Communication in ROS2'''<br />
* '''Ren Morita''' (Future University Hakodate)<br />
** Robot Operating System (ROS) 2.0におけるノード間通信を最適化する研究について紹介します。<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* [https://ieeexplore.ieee.org/document/8607261 A paper in English] <br />
* [https://ipsj.ixsq.nii.ac.jp/ej/?action=pages_view_main&active_action=repository_view_main_item_detail&item_id=186424&item_no=1&page_id=13&block_id=8 A paper in Japanese]<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 6:00pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''NuttXにまつわる「ある」紹介'''<br />
* '''(Mr. K)'''<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 6:30pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Call for session'''<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* [[Japan TJ Session Proposal|<span style="color:red">Session proposal how-to. / 提案の方法</span>]]<br />
* Link to presentation material<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 9:00pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''<<DEAD LIMIT>> Venue booked until 9:00 pm.'''<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
|}<br />
<br />
* Please be noted above time table is just a guideline and may be shifted. / 上記の時間割は目安です。かなり前後する可能性がありますので、あらかじめご承知おきください。<br />
<br />
== Special Remarks ==<br />
* Please place some detail descriptions about each presentation topics.<br />
: こちらに各プレゼンテーションの詳細などを記載してください。<br />
<br />
* togetter<br />
<br />
<!--<br />
** [http://togetter.com/li/1055101 Summary of twitter]<br />
--><br />
<br />
= Ask for your help / お願い =<br />
== Presentation Materials ==<br />
* We wish you to prepare the materials in English. / 出来るだけプレゼンテーション資料は英語で表記してください。絶対ではありませんが、日本語が理解できない方に対しての配慮が出来ればと思います。<br />
* Please leave your material in this wiki site after the event. / ジャンボリー終了後、プレゼンテーション資料はこのWikiに残してください。<br />
== English Translation Volunteer ==<br />
* If you can help the translation volunteer from Japanese to English, we would be very much appreciated! / 日本語を英訳していただくボランティアを大歓迎します!<br />
<br />
[[Category:Japan Technical Jamboree]]<br />
[[Category:Events]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car/Boards/Yocto-Gen3/v3.21.0&diff=486371R-Car/Boards/Yocto-Gen3/v3.21.02019-03-01T02:53:02Z<p>Khiem.renesas: Update the URL to R-Car Starter Kit(s)</p>
<hr />
<div>{{TOC right}}<br />
This page contains information on building and running Yocto on:<br />
* [[R-Car/Boards/H3SK | Renesas R-Car-H3 Starter Kit Premier]] (unofficial name - H3ULCB), https://www.renesas.com/us/en/solutions/automotive/adas/solution-kits/r-car-starter-kit.html<br />
* [[R-Car/Boards/M3SK | Renesas R-Car-M3 Starter Kit Pro]] (unofficial name - M3ULCB), https://www.renesas.com/us/en/solutions/automotive/adas/solution-kits/r-car-starter-kit.html<br />
<br />
'''NOTE: USE OFFICIAL DOCUMENTATION provided with R-Car BSPs FOR H3SK/M3SK boards'''<br />
== Yocto versions ==<br />
[http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=yocto-2.1.3 Poky-2.1.3] is supported with Yocto v2.23.1. <br/><br />
[http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=yocto-2.4.2 Poky-2.4.2] is supported with Yocto v3.9.0. <br/><br />
[http://git.yoctoproject.org/cgit/cgit.cgi/poky/tag/?id=yocto-2.4.3 Poky-2.4.3] is supported with Yocto v3.13.0 and v3.15.0. <br/><br />
Specific commit of meta-openembedded is required.<br />
<br />
== Preliminary steps ==<br />
<ol><br />
<li>Download evaluation version of proprietary graphics and multimedia drivers from Renesas.<br/><br />
<br/><br />
To download Multimedia and Graphics library and related Linux drivers, please use the following link:<br/><br />
https://www.renesas.com/us/en/solutions/automotive/rcar-download/rcar-demoboard.html<br/><br />
<br/><br />
Graphic drivers are required for Wayland. Multimedia drivers are optional.<br/><br />
<br/><br />
</li><br />
<br />
<li> Install required packages<br />
===== Ubuntu and Debian =====<br />
<pre><br />
sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \<br />
build-essential chrpath socat libsdl1.2-dev xterm python-crypto cpio python python3 \<br />
python3-pip python3-pexpect xz-utils debianutils iputils-ping libssl-dev<br />
</pre><br />
<br />
===== Fedora =====<br />
<pre><br />
sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \<br />
diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath \<br />
ccache perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue socat \<br />
SDL-devel xterm python-crypto cpio python python3 python3-pip python3-pexpect \<br />
ghc-lzma-conduit iputils openssl<br />
</pre><br />
Refer to [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html#packages Yocto Project Quick Start] for more information.<br />
</li><br />
</ol><br />
<br />
== Building the BSP for Renesas H3 Starter Kit, M3 Starter Kit ==<br />
NOTE: to have ADAS View and HAD Solution kits supported follow instructions: [[R-Car/Boards/Yocto-Gen3-ADAS | R-Car Yocto Gen3 ADAS]]<br />
<ol><br />
<li>Create a directory and switch to it <br/><br />
Warning! Yocto builds require a lot of disk space (up to 100 GB). Make sure you have got enough before starting the build.<br />
<pre><br />
mkdir build<br />
cd build<br />
export WORK=`pwd`<br />
</pre><br />
</li><br />
<li>Clone basic Yocto layers:<br />
<pre><br />
cd $WORK<br />
git clone git://git.yoctoproject.org/poky<br />
git clone git://git.openembedded.org/meta-openembedded<br />
git clone git://git.linaro.org/openembedded/meta-linaro.git<br />
git clone git://github.com/renesas-rcar/meta-renesas<br />
</pre><br />
</li><br />
<br />
<li><br />
Switch to proper branches/commits<br />
<ol><br />
<li><br />
For Yocto v2.23.1<br />
<pre><br />
cd $WORK/poky<br />
git checkout -b tmp yocto-2.1.3<br />
cd $WORK/meta-openembedded<br />
git checkout -b tmp 55c8a76da5dc099a7bc3838495c672140cedb78e<br />
cd $WORK/meta-linaro<br />
git checkout -b tmp 2f51d38048599d9878f149d6d15539fb97603f8f<br />
cd $WORK/meta-renesas<br />
git checkout -b tmp 7acbf5e2f99c59478adbc73c6a40d314589a3009<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.9.0<br />
<pre><br />
cd $WORK/poky<br />
git checkout -b tmp 342fbd6a3e57021c8e28b124b3adb241936f3d9d<br />
cd $WORK/meta-openembedded<br />
git checkout -b tmp dacfa2b1920e285531bec55cd2f08743390aaf57<br />
cd $WORK/meta-linaro<br />
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885<br />
cd $WORK/meta-renesas<br />
git checkout -b tmp fd078b6ece537d986852cb827bd21e022a797b2f<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.13.0 (Note: https://elinux.org/R-Car/Boards/Yocto-Gen3#Known_issues_and_limitations (No.3))<br />
<pre><br />
cd $WORK/poky<br />
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc<br />
cd $WORK/meta-openembedded<br />
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23<br />
cd $WORK/meta-linaro<br />
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885<br />
cd $WORK/meta-renesas<br />
git checkout -b tmp 00f70f062aace04c051fa92d3cd7b887718fc313<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.15.0 (Note: https://elinux.org/R-Car/Boards/Yocto-Gen3#Known_issues_and_limitations (No.4))<br />
<pre><br />
cd $WORK/poky<br />
git checkout -b tmp 7e7ee662f5dea4d090293045f7498093322802cc<br />
cd $WORK/meta-openembedded<br />
git checkout -b tmp 352531015014d1957d6444d114f4451e241c4d23<br />
cd $WORK/meta-linaro<br />
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885<br />
cd $WORK/meta-renesas<br />
git checkout -b tmp 8af0b7d6e445b532088a068dc012757001be3a1f<br />
</pre><br />
</li><br />
</ol><br />
Another versions are not tested for compatibility.<br />
Legacy BSP instruction can be found here [[R-Car/Boards/Yocto-Gen3-legacy | R-Car Yocto Gen3 legacy]]<br />
</li><br />
<br />
<li><br />
Apply Linaro-GCC patch file:<br />
<ol><br />
<li><br />
For Yocto v2.23.1<br />
<pre><br />
cd $WORK/meta-renesas<br />
export PATCH_DIR=meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc<br />
patch -p1 < ${PATCH_DIR}/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch<br />
unset PATCH_DIR<br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<li><br />
Download proprietary driver modules to $WORK/proprietary folder.<br/><br />
You should see the following files:<br />
<ol><br />
<li><br />
For Yocto v2.23.1<br />
<pre><br />
$ ls -1 $WORK/proprietary/*.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170828.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20170828.zip<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.9.0<br />
<pre><br />
$ ls -1 $WORK/proprietary/*.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20180627.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20180627.zip<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.13.0<br />
<pre><br />
$ ls -1 $WORK/proprietary/*.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20181029.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20181029.zip<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.15.0<br />
<pre><br />
$ ls -1 $WORK/proprietary/*.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20181225.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20181225.zip<br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<li><br />
Populate meta-renesas with proprietary software packages.<br />
<pre><br />
export PKGS_DIR=$WORK/proprietary<br />
cd $WORK/meta-renesas<br />
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR<br />
unset PKGS_DIR<br />
</pre><br />
</li><br />
<br />
<li><br />
Setup build environment<br />
<pre><br />
cd $WORK<br />
source poky/oe-init-build-env<br />
</pre><br />
</li><br />
<br />
<li><br />
Prepare default configuration files.<br />
<ol><br />
<li><br />
For Yocto v2.23.1<br />
<pre><br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/<h3ulcb|m3ulcb>/linaro-gcc/mmp/*.conf ./conf/<br />
cd $WORK/build<br />
cp conf/local-wayland.conf conf/local.conf<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.9.0 or later<br />
<pre><br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/<h3ulcb|m3ulcb>/poky-gcc/mmp/*.conf ./conf/<br />
cd $WORK/build<br />
cp conf/local-wayland.conf conf/local.conf<br />
</pre><br />
</li><br />
</ol><br />
<br />
<li><br />
(Edit $WORK/build/conf/local.conf to enable/disable graphics and multimedia proprietary drivers support)<br />
</li><br />
<br />
<li><br />
Edit local.conf with evaluation packages requirements:<br />
<ol><br />
<li><br />
For Yocto v2.23.1 or later (to enable EVA_ prefix during packages install)<br />
<pre><br />
DISTRO_FEATURES_append = " use_eva_pkg"<br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<br />
<li><br />
Start the build <br /><br />
<pre><br />
bitbake core-image-weston<br />
</pre><br />
</li><br />
<br />
<li><br />
Building image can take up to a few hours depending on your host system performance.<br><br />
After the build has been completed successfully, you should see the output similar to:<br />
<pre class="bash"><br />
NOTE: Tasks Summary: Attempted 4704 tasks of which 31 didn't need to be rerun and all succeeded.<br />
</pre><br />
and the command prompt should return.<br />
</li><br />
<br />
<li><br />
Bitbake has generated all the necessary files in ./tmp/deploy/images directory. <br/><br />
You can verify its content:<br />
<pre class="bash"><br />
$ ls -1 `find ./tmp/deploy/images/h3ulcb/ -maxdepth 1 -type l -print`<br />
./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.cpio.gz<br />
./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.ext4<br />
./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.manifest<br />
./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.tar.bz2<br />
./tmp/deploy/images/h3ulcb/Image<br />
./tmp/deploy/images/h3ulcb/Image-h3ulcb.bin<br />
./tmp/deploy/images/h3ulcb/Image-r8a7795-es1-h3ulcb.dtb<br />
./tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb-4x2g.dtb<br />
./tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb.dtb<br />
./tmp/deploy/images/h3ulcb/modules-h3ulcb.tgz<br />
./tmp/deploy/images/h3ulcb/u-boot.bin<br />
./tmp/deploy/images/h3ulcb/u-boot-elf-h3ulcb.srec<br />
./tmp/deploy/images/h3ulcb/u-boot-elf.srec<br />
./tmp/deploy/images/h3ulcb/u-boot-h3ulcb.bin<br />
</pre><br />
'''Image''' is a Kernel image, '''*.dtb''' is a blob file, '''core-image-weston-h3ulcb.tar.bz2''' is the rootfs, '''modules-h3ulcb.tgz''' are kernel modules.<br />
</li><br />
<li><br />
You can now proceed with running Yocto images<br />
</li><br />
</ol><br />
<br />
==OpenCL support==<br />
The following page describes how to enable OpenCL and Caffe support:<br />
[[R-Car/Boards/Yocto-Gen3/OpenCL]]<br />
<br />
== Build SDK ==<br />
After building BSP you may build SDK:<br />
<pre><br />
bitbake core-image-weston -c populate_sdk<br />
</pre><br />
After build finished the SDK installation script may be found in following path:<br />
<pre><br />
tmp/deploy/sdk/poky-glibc-x86_64-core-image-weston-aarch64-toolchain-*.sh<br />
</pre><br />
Install SDK by run the following command and follow instructions on the screen:<br />
<pre><br />
./tmp/deploy/sdk/poky-glibc-x86_64-core-image-weston-aarch64-toolchain-*.sh<br />
</pre><br />
<br />
== Running Yocto images ==<br />
Linux kernel can be booted from microSD card or from TFTP. Root FS can be mounted from micro SD card or via NFS.<br />
<br />
=== Loading kernel via TFTP and rootfs via NFS ===<br />
Follow these steps to setup working TFTP and NFS server:<br />
<ol><br />
<li><br />
Setup a TFTP server.<br />
==== Ubuntu ====<br />
Install '''tftpd-hpa''' package along with tftp tools:<br />
<pre><br />
sudo apt-get install tftp tftpd-hpa<br />
</pre><br />
<br />
==== Fedora ====<br />
<ol><br />
<li><br />
Install necessary packages:<br />
<pre><br />
sudo yum install tftp-server tftp<br />
</pre><br />
tftp-server is a part of xinetd. See [http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/ch13s05s03.html Fedora manual] for more information.<br />
</li><br />
<li><br />
Enable TFTP server:<br />
<pre><br />
sudo vi /etc/xinetd.d/tftp <br />
</pre><br />
Set <pre>disable = no</pre> Save file and exit.<br />
</li><br />
<li><br />
Start xinetd:<br />
<pre><br />
sudo systemctl start xinetd.service<br />
sudo systemctl enable xinetd.service<br />
</pre><br />
</li><br />
</ol><br />
<br />
</li><br />
<br />
<li><br />
Copy '''Image''' and '''Image-r8a7795-h3ulcb.dtb''' (for ws2.0 silicon) and/or '''Image-r8a7795-h3ulcb-4x2g.dtb''' (for RTP0RC77951SKBX010SA03(DDR 8GiB)) and/or '''Image-r8a7795-es1-h3ulcb.dtb''' (for ws1.1) from $WORK/build/tmp/deploy/images/h3ulcb/ to TFTP server root.<br />
==== Ubuntu ====<br />
<pre><br />
cp $WORK/build/tmp/deploy/images/h3ulcb/Image /srv/tftp/<br />
cp $WORK/build/tmp/deploy/images/h3ulcb/Image-r8a7795-es1-h3ulcb.dtb /srv/tftp/<br />
cp $WORK/build/tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb.dtb /srv/tftp/<br />
cp $WORK/build/tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb-4x2g.dtb /srv/tftp/<br />
</pre><br />
<br />
==== Fedora ====<br />
<pre><br />
cp $WORK/build/tmp/deploy/images/h3ulcb/Image /var/lib/tftpboot/<br />
cp $WORK/build/tmp/deploy/images/h3ulcb/Image-r8a7795-es1-h3ulcb.dtb /var/lib/tftpboot/<br />
cp $WORK/build/tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb.dtb /var/lib/tftpboot/<br />
cp $WORK/build/tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb-4x2g.dtb /var/lib/tftpboot/<br />
</pre><br />
[http://elinux.org/R-Car/Boards/H3SK#H3SK_has_two_kinds_of_boards/ Which is my H3SK board WS2.0 or WS1.1?]<br />
</li><br />
<br />
<li><br />
Verify that TFTP server is working.<br />
<pre><br />
tftp localhost -c get Image && ls Image<br />
</pre><br />
</li><br />
<br />
<li><br />
Setup NFS server.<br />
==== Debian/Ubuntu ====<br />
<ol><br />
<li><br />
Install necessary packages:<br />
<pre><br />
sudo apt-get install nfs-kernel-server nfs-common<br />
</pre><br />
</li><br />
<li><br />
Start NFS server:<br />
<pre><br />
sudo /etc/init.d/nfs-kernel-server start<br />
</pre><br />
</li><br />
</ol><br />
<br />
==== Fedora ====<br />
<ol><br />
<li><br />
Install necessary packages:<br />
<pre><br />
sudo yum install nfs-utils<br />
</pre><br />
</li><br />
<li><br />
Enable and start nfs server:<br />
<pre><br />
sudo systemctl enable rpcbind.service <br />
sudo systemctl enable nfs-server.service <br />
sudo systemctl enable nfs-lock.service <br />
sudo systemctl enable nfs-idmap.service<br />
sudo systemctl start rpcbind.service <br />
sudo systemctl start nfs-server.service <br />
sudo systemctl start nfs-lock.service <br />
sudo systemctl start nfs-idmap.service<br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<br />
<li><br />
Export root FS to NFS. (Change IMAGE and MACHINE to fit your build).<br />
<ol><br />
<li><br />
Unpack rootfs to a dedicated directory:<br />
<pre><br />
IMAGE=weston<br />
MACHINE=h3ulcb|m3ulcb<br />
NFS_ROOT=/nfs/${MACHINE}<br />
sudo mkdir -p "${NFS_ROOT}"<br />
sudo rm -rf "${NFS_ROOT}"/*<br />
sudo tar -xjf "${WORK}/build/tmp/deploy/images/${MACHINE}/core-image-${IMAGE}-${MACHINE}-*.tar.bz2" -C "${NFS_ROOT}"<br />
sync<br />
</pre><br />
</li><br />
<li><br />
Edit '''/etc/exports''':<br />
<pre><br />
sudo vi /etc/exports<br />
</pre><br />
add<br />
<pre><br />
/nfs/h3ulcb *(rw,no_subtree_check,sync,no_root_squash,no_all_squash)<br />
/nfs/m3ulcb *(rw,no_subtree_check,sync,no_root_squash,no_all_squash)<br />
</pre><br />
Save the file and exit.<br />
</li><br />
<li><br />
Force NFS server to re-read /etc/exports<br />
<pre>sudo exportfs -a</pre><br />
</li><br />
</ol><br />
</li><br />
<li><br />
Verify that NFS is working.<br />
<pre><br />
[builduser@buildmachine ~]$ showmount -e localhost<br />
Export list for localhost:<br />
/nfs/h3ulcb *<br />
/nfs/m3ulcb *<br />
</pre><br />
</li><br />
<br />
<li><span id="Boot into U-Boot command prompt">Boot into U-Boot command prompt</span><br />
<br />
<ol><br />
<li><br />
Connect to serial console over microUSB using minicom or picocom.<br />
</li><br />
<li><br />
Switch the board on or reset it. Press any key to stop U-Boot automatic countdown.<br />
</li><br />
</ol><br />
Refer to [[R-Car/Boards/H3SK#Power_on_the_board_and_go_to_U-Boot_prompt|H3SK board page]], [[R-Car/Boards/M3SK#Power_on_the_board_and_go_to_U-Boot_prompt|M3SK board page]] for more information.<br />
</li><br />
<br />
<li><br />
Configure Ethernet, TFTP, and kernel command line in U-Boot:<br />
<!--setenv ethaddr xx:xx:xx:xx:xx:xx<br />
Replace xx:xx:xx:xx:xx:xx with the MAC address of your board. It should be on the sticker on top of the Ethernet port.<br/><br />
--><br />
<pre><br />
setenv ipaddr <board-ip><br />
setenv serverip <your-computer-ip><br />
setenv bootcmd 'tftp 0x48080000 Image; tftp 0x48000000 Image-r8a7795-h3ulcb.dtb; booti 0x48080000 - 0x48000000'<br />
setenv bootargs 'ignore_loglevel rw root=/dev/nfs nfsroot=<your-computer-ip>:<nfs-path>,nfsvers=3 ip=<board-ip>:<your-computer-ip>::255.255.255.0:h3ulcb'<br />
saveenv<br />
</pre><br />
Replace <board-ip> with the proper IP address for the board. Replace <your-computer-ip> with the IP address of your computer, where tftp and nfs servers are installed. Replace <nfs-path> with the exported path of the root FS. <br/> For example:<br />
<pre><br />
setenv ipaddr 192.168.1.3<br />
setenv serverip 192.168.1.2<br />
setenv bootcmd 'tftp 0x48080000 Image; tftp 0x48000000 Image-r8a7795-h3ulcb.dtb; booti 0x48080000 - 0x48000000'<br />
setenv bootargs 'ignore_loglevel rw root=/dev/nfs nfsroot=192.168.1.2:/nfs/h3ulcb,nfsvers=3 ip=192.168.1.3:192.168.1.2::255.255.255.0:h3ulcb'<br />
saveenv<br />
</pre><br />
You can also use<br />
<pre><br />
dhcp<br />
</pre><br />
command to obtain information from DHCP server.<br/><br />
'''Note:''' You can always see the environment with ''printenv'' command. Refer to [http://www.denx.de/wiki/U-Boot/Documentation U-Boot manual] for details.<br />
</li><br />
<br />
<li><br />
Verify the connection over Ethernet from U-Boot:<br />
<pre><br />
ping <your-computer-ip><br />
</pre><br />
You should see:<br />
<pre><br />
=> ping 192.168.1.2 <br />
ravb:0 is connected to ravb. Reconnecting to ravb<br />
ravb Waiting for PHY auto negotiation to complete.. done<br />
ravb: 100Base/Full<br />
Using ravb device<br />
host 192.168.1.2 is alive<br />
</pre><br />
</li><br />
<br />
<li><br />
Reset the board by pushing reset button<br />
<br/><br />
Refer to [[R-Car/Boards/H3SK#Power_on_the_board_and_go_to_U-Boot_prompt|H3SK board page]], [[R-Car/Boards/M3SK#Power_on_the_board_and_go_to_U-Boot_prompt|M3SK board page]] for more information.<br />
</li><br />
<br />
<li><br />
The board should boot the kernel:<br />
<pre><br />
NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.10<br />
NOTICE: BL2: PRR is R-Car H3 ES1.0<br />
NOTICE: BL2: Boot device is HyperFlash(80MHz)<br />
NOTICE: BL2: LCM state is CM<br />
NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x52<br />
NOTICE: BL2: DDR1600(rev.0.10)<br />
NOTICE: BL2: DRAM Split is 4ch<br />
NOTICE: BL2: QoS is default setting(rev.0.32)<br />
NOTICE: BL2: Lossy Decomp areas<br />
NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570<br />
NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0<br />
NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0<br />
NOTICE: BL2: v1.1(release):c2f9fc9<br />
NOTICE: BL2: Built : 00:36:25, Nov 20 2016<br />
NOTICE: BL2: Normal boot<br />
NOTICE: BL2: dst=0xe631a1a8 src=0x8180000 len=512(0x200)<br />
NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)<br />
NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)<br />
NOTICE: BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)<br />
NOTICE: BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)<br />
<br />
<br />
U-Boot 2015.04 (Nov 20 2016 - 00:54:11)<br />
<br />
CPU: Renesas Electronics R8A7795 rev 1.0<br />
Board: H3ULCB<br />
I2C: ready<br />
DRAM: 3.9 GiB<br />
MMC: sh-sdhi: 0, sh-sdhi: 1<br />
In: serial<br />
Out: serial<br />
Err: serial<br />
Net: ravb<br />
Hit any key to stop autoboot: 0 <br />
ravb Waiting for PHY auto negotiation to complete.. done<br />
ravb: 100Base/Full<br />
BOOTP broadcast 1<br />
BOOTP broadcast 2<br />
BOOTP broadcast 3<br />
DHCP client bound to address 192.166.10.31 (1287 ms)<br />
Using ravb device<br />
TFTP from server 192.166.10.1; our IP address is 192.166.10.31<br />
Filename 'Image'.<br />
Load address: 0x48080000<br />
Loading: #################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
#################################################################<br />
####################################################<br />
627 KiB/s<br />
done<br />
Bytes transferred = 13905920 (d43000 hex)<br />
ravb:0 is connected to ravb. Reconnecting to ravb<br />
ravb Waiting for PHY auto negotiation to complete. done<br />
ravb: 100Base/Full<br />
Using ravb device<br />
TFTP from server 192.166.10.1; our IP address is 192.166.10.31<br />
Filename 'Image-r8a7795-h3ulcb.dtb'.<br />
Load address: 0x48000000<br />
Loading: #############<br />
12.7 KiB/s<br />
done<br />
Bytes transferred = 66470 (103a6 hex)<br />
## Flattened Device Tree blob at 48000000<br />
Booting using the fdt blob at 0x48000000<br />
Using Device Tree in place at 0000000048000000, end 00000000480133a5<br />
<br />
Starting kernel ... <br />
</pre><br />
</li><br />
</ol><br />
<br />
==How to prepare and boot from eMMC/SD card==<br />
<br />
This section describes steps that are necessary for preparing and booting from SD card. <br />
<br />
===Preparing eMMC/SD card===<br />
In order to prepare you SD card, follow these instructions on host machine: <br />
<br />
1. Partion your SD card to set 1 partition and ID=83 (Linux) <br />
<br/><br />
Make sure the SD card doesn't contain any important files.<br />
<br/><br />
<span style="color:#ff0000">'''WARNING!''' These steps may erase the SD card completely. All files my be lost.</span><br />
<br />
$ fdisk /dev/mmcblk0<br />
-> d<br />
-> n<br />
-> p<br />
-> 1<br />
-> t<br />
-> 83<br />
<br />
2. Format this partition to ext3 (or ext4)<br />
<br />
$ mkfs.ext3 /dev/mmcblk0p1<br />
<br />
3. Mount this partition on your host to any directory and upack the core-image-weston-*.tar.bz2 into mounted folder.<br />
<br />
$ mount /dev/mmcblk0p1 /mnt<br />
$ cd <your_yocto_build_directory><br />
$ tar xfj build/tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb-*.rootfs.tar.bz2 -C /mnt<br />
<br />
NOTE: probably you need to be a root user, hence use "sudo"<br />
<br />
===Configure U-Boot to boot from SD card===<br />
<br />
Proper U-Boot command to boot from SD:<br />
# setenv bootargs 'rw root=/dev/mmcblk1p1 rootfstype=ext3 rootwait'<br />
# ext2load mmc 0:1 0x48080000 /boot/Image<br />
# ext2load mmc 0:1 0x48000000 /boot/Image-r8a7795-h3ulcb.dtb<br />
# booti 0x48080000 - 0x48000000<br />
<br />
Note from user: When I created my image with mkfs.ext3, and booted with rootfstype=ext3, the kernel could not<br />
find mount the filesystem. The kernel boot gave an error message:<br />
"EXT4-fs (mmcblk1p1): couldn't mount as ext3 due to feature incompatibilities".<br />
I switched to 'rootfstype=ext4' in my bootargs, and the kernel booted OK.<br />
<br />
Example of U-Boot environment variables:<br />
baudrate=115200<br />
bootargs_emmc=rw root=/dev/mmcblk0p1 rootfstype=ext3 rootwait<br />
bootargs_nfs=rw root=/dev/nfs rootwait ip=dhcp<br />
bootargs_sd0=rw root=/dev/mmcblk1p1 rootfstype=ext3 rootwait<br />
bootcmd=run bootcmd_sd0<br />
bootcmd_emmc=set bootargs ${bootargs_emmc};ext2load mmc 1:1 0x48080000 /boot/Image;ext2load mmc 1:1 0x48000000 /boot/${dtb};run booti_cmd<br />
bootcmd_nfs=set bootargs ${bootargs_nfs};bootp 0x48080000 Image;tftp 0x48000000 ${dtb};run booti_cmd<br />
bootcmd_sd0=set bootargs ${bootargs_sd0};ext2load mmc 0:1 0x48080000 /boot/Image;ext2load mmc 0:1 0x48000000 /boot/${dtb};run booti_cmd<br />
bootdelay=3<br />
booti_cmd=booti 0x48080000 - 0x48000000<br />
dtb=Image-r8a7795-h3ulcb.dtb<br />
ethact=ravb<br />
ethaddr=2E:09:0A:00:BE:11<br />
fdt_high=0xffffffffffffffff<br />
initrd_high=0xffffffffffffffff<br />
stderr=serial<br />
stdin=serial<br />
stdout=serial<br />
ver=U-Boot 2015.04 (Sep 23 2016 - 13:45:29)<br><br />
Environment size: 1092/131068 bytes<br />
<br />
To verify the SD card, type the following in U-Boot prompt:<br />
=> mmc dev 0 <br />
switch to partitions #0, OK<br />
mmc0 is current device<br />
=> mmc info<br />
Device: sh-sdhi<br />
Manufacturer ID: 3<br />
OEM: 5344<br />
Name: SL64G <br />
Tran Speed: 50000000<br />
Rd Block Len: 512<br />
SD version 3.0<br />
High Capacity: Yes<br />
Capacity: 59.5 GiB<br />
Bus Width: 4-bit<br />
Erase Group Size: 512 Bytes<br />
=> ext2ls mmc 0:1 /boot<br />
<DIR> 4096 .<br />
<DIR> 4096 ..<br />
<SYM> 32 Image<br />
14039040 Image-4.9.0-yocto-standard<br />
69584 Image-r8a7795-h3ulcb.dtb<br />
<br />
== Build scripts examples ==<br />
<ol><br />
<br />
<li> Build preparation<br />
<br /><br />
YOCTO_VERSION and META_VERSION must be changed depending your Yocto version.<br />
<pre><br />
#!/bin/sh<br />
<br />
# Create a directory and switch to it<br />
mkdir build<br />
cd build<br />
WORK=`pwd`<br />
echo $WORK<br />
<br />
# For Yocto v2.23.1<br />
YOCTO_VERSION=yocto-2.1.3<br />
META_VERSION=krogoth<br />
<br />
# For Yocto v3.9.0<br />
#YOCTO_VERSION=yocto-2.4.2<br />
#META_VERSION=rocko<br />
<br />
# For Yocto v3.13.0 and v3.15.0<br />
#YOCTO_VERSION=yocto-2.4.3<br />
#META_VERSION=rocko<br />
<br />
# Clone basic Yocto layers in parallel<br />
git clone -b $YOCTO_VERSION --depth 1 git://git.yoctoproject.org/poky &<br />
git clone -b $META_VERSION --depth 1 git://git.linaro.org/openembedded/meta-linaro.git &<br />
git clone -b $META_VERSION --depth 1 git://git.openembedded.org/meta-openembedded &<br />
git clone -b $META_VERSION --depth 1 git://github.com/renesas-rcar/meta-renesas &<br />
<br />
# Wait for all clone operations<br />
wait<br />
<br />
# Apply Linaro-GCC patch file (The patch only adds README.linaro)<br />
cd $WORK/meta-renesas<br />
export PATCH_DIR=meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc<br />
patch -p1 < ${PATCH_DIR}/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch<br />
unset PATCH_DIR<br />
<br />
# Make sure proprietary driver modules are downloaded to $WORK/proprietary folder<br />
# If the modules are not downloaded, copy_evaproprietary_softwares.sh warns it<br />
# See https://www.renesas.com/en-us/solutions/automotive/rcar-demoboard.html (need to login!)<br />
# $ ls -1 $WORK/proprietary/*.zip<br />
# R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170828.zip<br />
# R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20170828.zip<br />
<br />
# Populate meta-renesas with proprietary software packages<br />
cd $WORK/meta-renesas<br />
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $WORK/proprietary<br />
</pre><br />
</li><br />
<br />
<li> Building yocto for H3ULCB board<br />
<ol><br />
<li> For Yocto v2.23.1<br />
<pre><br />
#!/bin/sh<br />
<br />
cd build<br />
WORK=`pwd`<br />
echo $WORK<br />
<br />
cd $WORK<br />
source poky/oe-init-build-env<br />
<br />
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/*.conf ./conf/.<br />
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/*.conf ./conf/.<br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/*.conf ./conf/.<br />
<br />
cd $WORK/build<br />
cp conf/local-wayland.conf conf/local.conf<br />
echo "DISTRO_FEATURES_append = \" use_eva_pkg\"" >> $WORK/build/conf/local.conf<br />
<br />
bitbake core-image-weston<br />
</pre><br />
</li><br />
</ol><br />
<ol><br />
<li> For Yocto v3.9.0 or later<br />
<pre><br />
#!/bin/sh<br />
<br />
cd build<br />
WORK=`pwd`<br />
echo $WORK<br />
<br />
cd $WORK<br />
source poky/oe-init-build-env<br />
<br />
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/*.conf ./conf/.<br />
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/*.conf ./conf/.<br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/*.conf ./conf/.<br />
<br />
cd $WORK/build<br />
cp conf/local-wayland.conf conf/local.conf<br />
echo "DISTRO_FEATURES_append = \" use_eva_pkg\"" >> $WORK/build/conf/local.conf<br />
<br />
bitbake core-image-weston<br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<br />
</ol><br />
<br />
== FAQ ==<br />
=== Discussion site ===<br />
http://elinux.org/Talk:R-Car/Boards/Yocto-Gen3<br />
<br />
=== How do I increase USB bandwidth ===<br />
<ol><br />
<br />
<li> Download:<br><br />
M3SK [[File:M3v10_usb20_iso_mode.zip]]<br><br />
H3SK WS1.1 (RTP0RC7795SKBX0010SA00) [[File:H3v11_usb20_iso_mode.zip]]<br><br />
H3SK WS2.0 (RTP0RC77951SKBX010SA00) [[File:H3v20_usb20_iso_mode.zip]]<br><br />
</li><br />
<br />
<li> Setting<br />
<pre><br />
<Install Driver><br />
$ modprobe qos<br />
<Change directory to csv path><br />
$ cd /path_to_csv<br />
<Store QoS parameters to QoS SRAM><br />
$ qos_tp setall file.csv<br />
<Reflect Qos SRAM to QoS controller><br />
$ qos_tp switch<br />
</pre><br />
</li><br />
</ol><br />
=== How do access to USB memory from U-boot(Yocto v3.13.0 or later)===<br />
<ol><br />
<li>Some USB memory may not be recognized.<br />
<pre><br />
=> usb start<br />
starting USB...<br />
USB0: USB EHCI 1.10<br />
scanning bus 0 for devices... EHCI timed out on TD - token=0x80008d80<br />
<br />
USB device not accepting new address (error=80000000)<br />
1 USB Device(s) found<br />
scanning usb for storage devices... 0 Storage Device(s) found<br />
=><br />
</pre><br />
</li><br />
<li>[How to fix] Set the "usb_pgood_delay 2000" variable<br />
<pre><br />
=> setenv usb_pgood_delay 2000<br />
=> saveenv<br />
=> reset<br />
=> usb start<br />
</pre><br />
</li><br />
</ol><br />
<br />
== Known issues and limitations ==<br />
<ol><br />
<li> [SW limitation] Yocto v3.4 or later doesn't support RTP0RC7795SKBX0010SA00(H3 v1.1 Starter Kit).<br/><br />
Please use the H3 v2.0 SK<br/><br />
<br/><br />
<li> [Known issue] <br />
If you encounter a kernel hang-up while using Yocto v3.4.0 or later, please refer to the following pages.<br><br />
H3 SK: No.1 of https://elinux.org/R-Car/Boards/H3SK#Known_Issues<br><br />
M3 SK: No.2 of https://elinux.org/R-Car/Boards/M3SK#Known_Issues<br />
</li><br />
<br/><br />
<li> [SW limitations] Yocto v3.13.0<br/><br />
<ol><br />
<li>[U-boot]Reading environment variables from eMMC may fail.<br />
<pre><br />
Loading Environment from MMC... *** Warning - No block device, using default environment<br />
</pre><br />
</li><br />
<li>[U-boot]SD SDR50/104 card may not be recognized.<br />
<pre><br />
Ex)<br />
=> ext4ls mmc 0<br />
timeout during DMA<br />
timeout during DMA<br />
timeout during DMA<br />
timeout during DMA<br />
timeout during DMA<br />
error during DMA<br />
** Unrecognized filesystem type **<br />
=><br />
</pre><br />
</li><br />
<!--<br />
<li>[U-boot]Some USB memory may not be recognized.<br />
<pre><br />
=> usb start<br />
starting USB...<br />
USB0: USB EHCI 1.10<br />
scanning bus 0 for devices... EHCI timed out on TD - token=0x80008d80<br />
<br />
USB device not accepting new address (error=80000000)<br />
1 USB Device(s) found<br />
scanning usb for storage devices... 0 Storage Device(s) found<br />
=><br />
</pre><br />
[How to fix] Set the "usb_pgood_delay 2000" variable<br />
<pre><br />
=> setenv usb_pgood_delay 2000<br />
=> saveenv<br />
=> reset<br />
=> usb start<br />
</pre><br />
</li><br />
--><br />
<li>[Kernel] When using GStreamer, once playing audio at specific sampling rate, the audio with a different sampling rate cannot be played back. And some movie files cannot be played back.<br />
<pre><br />
Ex)<br />
root@m3ulcb:~# gst-launch-1.0 filesrc location=sample.wav ! wavparse ! audioconvert ! alsasink<br />
Setting pipeline to PAUSED ...<br />
Pipeline is PREROLLING ...<br />
[ 273.920848] rcar_sound ec500000.sound: SSI parent/child should use same rate<br />
[ 273.927930] rcar_sound ec500000.sound: ssi[0] : prepare error -22<br />
[ 273.934055] rcar_sound ec500000.sound: ASoC: cpu DAI prepare error: -22<br />
ERROR: from element /GstPipeline:pipeline0/GstAlsaSink:alsasink0: Could not get/set sett<br />
ings from/on resource.<br />
Additional debug info:<br />
../../../gst-plugins-base-1.12.2/ext/alsa/gstalsasink.c(617): set_hwparams (): /GstPipel<br />
ine:pipeline0/GstAlsaSink:alsasink0:<br />
Unable to set hw params for playback: Invalid argument<br />
ERROR: pipeline doesn't want to preroll.<br />
Setting pipeline to NULL ...<br />
Freeing pipeline ...<br />
root@m3ulcb:~# <br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<li> [SW limitations] Yocto v3.15.0<br/><br />
<ol><br />
<li>[U-boot]Reading environment variables from eMMC on M3 Starter Kit may fail.<br />
<pre><br />
communication out of sync<br />
</pre><br />
</li><br />
<li> [U-boot]Reading environment variables from eMMC on H3 v2 Starter Kit may fail.<br />
<pre><br />
Loading Environment from MMC... timeout during DMA<br />
*** Warning - !read failed, using default environment<br />
</pre><br />
Workaround patch: https://github.com/u-boot/u-boot/commit/f58d6771a2afad71594c1264aadde461210a4675<br><br />
U-boot binary [[File:u-boot-elf-h3ulcb-WA.zip]]<br><br><br />
</li><br />
</ol><br />
</li><br />
</ol></div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=486366R-Car2019-03-01T01:36:50Z<p>Khiem.renesas: /* Introduction */ Fixed broken links</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Ebisu|Ebisu]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[https://www.renesas.com/us/en/solutions/automotive.html Renesas Automotive Products / Solutions]<br />
*[https://www.renesas.com/us/en/solutions/automotive/car-information-system.html Renesas Car Information Terminal Applications]<br />
*[https://www.renesas.com/us/en/support/partners/r-car-consortium.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - High End<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid Range<br />
| '''M1A''' - R8A7778<br />
| '''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
| '''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
| '''E3''' - R8A77990<br />
|-<br />
|'''"D"''' - Dashboard<br />
|<br />
|<br />
| '''D3''' - R8A77995<br />
|-<br />
|'''"V"''' - Vision<br />
|<br />
| '''V2H''' - R8A7792<br />
| '''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car E3'''<br />
|[[R-Car/Boards/Ebisu|Ebisu]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.9.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [http://docs.automotivelinux.org/master/docs/getting_started/en/dev/reference/machines/R-Car-Starter-Kit-gen3.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=486191R-Car2019-02-28T12:01:20Z<p>Khiem.renesas: /* R-Car Automotive Grade Linux */ Add link to build AGL distribution for R-Car Starter Kit(s).</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[http://am.renesas.com/applications/automotive/index.jsp Renesas Automotive Products / Solutions]<br />
*[http://am.renesas.com/applications/automotive/cis/cis_highend/index.jsp Renesas Car Information Terminal Applications]<br />
*[http://r-car-consortium.renesas.com/jpn/index.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - Premium/High end<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid range<br />
| '''M1A''' - R8A7778<br />
|'''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
|'''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry class<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
|<br />
|-<br />
|'''"V"''' - ADAS<br />
|<br />
|'''V2H''' - R8A7792<br />
|'''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.9.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction.<br />
: To start an AGL distribution on R-Car Porter board, please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
: To start an AGL distribution on R-Car Starter Kit(s), please check AGL documentation [http://docs.automotivelinux.org/master/docs/getting_started/en/dev/reference/machines/R-Car-Starter-Kit-gen3.html here].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=486186R-Car2019-02-28T11:50:13Z<p>Khiem.renesas: /* Renesas R-Car Gen 3 BSP Tree */ Fixed typo. Update to latest R-Car Gen 3 BSP release tag.</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[http://am.renesas.com/applications/automotive/index.jsp Renesas Automotive Products / Solutions]<br />
*[http://am.renesas.com/applications/automotive/cis/cis_highend/index.jsp Renesas Car Information Terminal Applications]<br />
*[http://r-car-consortium.renesas.com/jpn/index.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - Premium/High end<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid range<br />
| '''M1A''' - R8A7778<br />
|'''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
|'''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry class<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
|<br />
|-<br />
|'''"V"''' - ADAS<br />
|<br />
|'''V2H''' - R8A7792<br />
|'''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 3 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.9.2<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.9.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction and R-Car Porter board can be used to start an AGL distribution. Please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=486181R-Car2019-02-28T07:27:42Z<p>Khiem.renesas: /* R-Car Genivi */ Update the link to build GDP Master for the Renesas R-Car SoCs (Gen2 and Gen3)</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[http://am.renesas.com/applications/automotive/index.jsp Renesas Automotive Products / Solutions]<br />
*[http://am.renesas.com/applications/automotive/cis/cis_highend/index.jsp Renesas Car Information Terminal Applications]<br />
*[http://r-car-consortium.renesas.com/jpn/index.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - Premium/High end<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid range<br />
| '''M1A''' - R8A7778<br />
|'''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
|'''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry class<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
|<br />
|-<br />
|'''"V"''' - ADAS<br />
|<br />
|'''V2H''' - R8A7792<br />
|'''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.2.1<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.9.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction and R-Car Porter board can be used to start an AGL distribution. Please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: https://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here]. Information on building GDP Master for the Renesas R-Car SoCs can be found [https://at.projects.genivi.org/wiki/display/GDP/GDP+Master here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=486176R-Car2019-02-28T06:58:55Z<p>Khiem.renesas: /* LTSI (Long Term Support Initiative) */ Update the link to LTSI kernel releases.</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[http://am.renesas.com/applications/automotive/index.jsp Renesas Automotive Products / Solutions]<br />
*[http://am.renesas.com/applications/automotive/cis/cis_highend/index.jsp Renesas Car Information Terminal Applications]<br />
*[http://r-car-consortium.renesas.com/jpn/index.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - Premium/High end<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid range<br />
| '''M1A''' - R8A7778<br />
|'''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
|'''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry class<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
|<br />
|-<br />
|'''"V"''' - ADAS<br />
|<br />
|'''V2H''' - R8A7792<br />
|'''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - https://ltsi.linuxfoundation.org/ .For all LTSI kernel releases, refer to [https://ltsi.linuxfoundation.org/software/releases/ https://ltsi.linuxfoundation.org/software/releases].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.2.1<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.9.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction and R-Car Porter board can be used to start an AGL distribution. Please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: http://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here].<br />
Information on building GDP for R-Car M2 Porter can be found [https://at.projects.genivi.org/wiki/display/GDP/Renesas+R-Car+M2+Porter+Hardware+Setup+and+Software+Installation here] and E2 Silk [https://at.projects.genivi.org/wiki/display/GDP/Renesas+R-Car+E2+Silk+Hardware+Set+Up+And+Software+Installation here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=486171R-Car2019-02-28T04:56:49Z<p>Khiem.renesas: /* R-Car Yocto */ Add Yocto release based on YP 2.6 (Thud)</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* [[R-Car/Boards/M3NSK |R-Car Starter Kit Pro(M3N)]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[http://am.renesas.com/applications/automotive/index.jsp Renesas Automotive Products / Solutions]<br />
*[http://am.renesas.com/applications/automotive/cis/cis_highend/index.jsp Renesas Car Information Terminal Applications]<br />
*[http://r-car-consortium.renesas.com/jpn/index.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - Premium/High end<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid range<br />
| '''M1A''' - R8A7778<br />
|'''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
|'''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry class<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
|<br />
|-<br />
|'''"V"''' - ADAS<br />
|<br />
|'''V2H''' - R8A7792<br />
|'''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - http://ltsi.linuxfoundation.org/ . Refer to [http://ltsi.linuxfoundation.org/releases/ltsi-tree/4.1.17-ltsi/stable-release 4.1.17-LTSI] and [http://ltsi.linuxfoundation.org/releases/ltsi-tree/3.14.28-ltsi/stable-release 3.14.28-LTSI].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.2.1<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.9.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
:Yocto Project 2.6 (codename: thud)<br />
::Branch: thud-dev<br><br />
::Tag: thud-Yocto-v3.15.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/thud-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction and R-Car Porter board can be used to start an AGL distribution. Please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: http://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here].<br />
Information on building GDP for R-Car M2 Porter can be found [https://at.projects.genivi.org/wiki/display/GDP/Renesas+R-Car+M2+Porter+Hardware+Setup+and+Software+Installation here] and E2 Silk [https://at.projects.genivi.org/wiki/display/GDP/Renesas+R-Car+E2+Silk+Hardware+Set+Up+And+Software+Installation here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=Japan_Technical_Jamboree_68&diff=485781Japan Technical Jamboree 682019-02-20T07:50:08Z<p>Khiem.renesas: Append 2 presentations into Agenda</p>
<hr />
<div>{| cellpadding="0" cellspacing="0" border="0"<br />
|-<br />
|[[Image:headTitle_LFCEWG.png]]<br />
|-<br />
| style="text-align:right" |<span style="font-size:large">Date: March 8th / 日付: 3月8日(金)</span><br />
* At Nakano Sunplaza / 於、中野サンプラザ<br />
* Please join "celinux-dev" mailinglist to get the latest announcement.<br />
* "celinux-dev" メーリングリストにこのイベント関係のアナウンスが流れます。ぜひ参加してください。<br />
** [http://lists.celinuxforum.org/mailman/listinfo/celinux-dev How to join the mailing list.]<br />
|-<br />
|[[Image:J_Jam_SessionProp.gif]]<br />
|-<br />
|style="text-align:right" |[[Japan TJ Session Proposal|<span style="color:red">Session proposal how-to. / 提案の方法</span>]]<br />
|}<br />
= Introduction / はじめに =<br />
* The Japan Technical Jamboree is a forum-wide technical meeting of the CE Workgroup of the Linux Foundation. This meeting will be located conveniently in Japan and use Japanese as the native language of the event. <br />
* A general guidance page is available. / 初めての方はこちらもお読みください。<br />
** [[Japan Technical Jamboree Guidance]] (Japanese/English)<br />
== Special remarks for non Japanese speakers ==<br />
* This page is Japanese/English bilingual. Please allow some contents on this page are not translated into English because of this event is Japan regional one, though we try to place English translation.<br />
* If you would like to perform your presentation in English, we also welcome you to join! We hope you to speak slowly without any complicated expressions. Most Japanese developers are capable to understand plain English.<br />
<br />
== Why Jamboree / ジャンボリーに寄せる思い ==<br />
<br />
* [[Media:IntroducingCEWG_2015.pdf|"'''Hop-Step-Jump''' Strategy (pdf file)"]]<br />
<br />
* [[Media:IntroducingCEWG_2015.pdf|"Here"]] please find an introductory material of CE Workgroup explaining "Why Jamboree". It is one of important event for us for "Hop-Step-Jump" strategy to let embedded system developers jumping into open community. We know many of you are too busy to collaborate with open communities because of your daily jobs. And you may be concerned for your language skill or technical knowledge. Then we prepared this Jamboree as the entry point for those people to the open community. You may speak in Japanese. You do not need to worry about your technical skill. But we strongly would like encouraging you to come to the international stage like Embedded Linux Conference which is the stage of "Hop" to the global open community!<br />
<br />
* It is not the place only for Consumer electronics field but also we greatly welcome other domain embedded system developers and more. Even if you are working for super computer or enterprise server system, you will be welcomed! '''Let's enjoy OSS together!!'''<br />
<br />
* [[Media:IntroducingCEWG_2015.pdf|"このスライド"]]はCE Workgroupの説明資料からの抜粋です。この中でCEWGがジャンボリーにかける思いを説明しています。組み込みシステム開発にあたられている皆さんは日々の仕事に追われて大変に忙しい毎日を送られている事、良く知っています。また、英語の問題、または本当に技術的な実力があるのだろうか(ほとんどの場合無用な心配ですが)といった心配もあって、なかなかOSSコミュニティーとの交流を始める勇気が湧かない、というのが現実ではないでしょうか。そのような皆さんのために、CEWGは、その前身のCE Linux Forumの時代から、日本で日本語で技術ディスカッションをする場(ジャンボリー)を'''ホップ'''の場として、世界中の組み込みOSS開発者が集まる場、Embedded Linux Conference (US/Europe)を'''ステップ'''の場として、OSS開発者のグローバルなコミュニティーに'''ジャンプ'''できるような場を設けています。<br />
<br />
* この場は決して、Consumer Electronics関係の皆さんだけのものではありません。たとえば自動車関係、産業機器関係、医療機器関係などより広範な組み込みシステム関係の皆さん、さらにはスーパーコンピュータやエンタープライズシステムなどに関わられている皆さんの参加もこころから歓迎します。'''Let's enjoy OSS together!!'''<br />
<br />
== Previous Jamboree ==<br />
* Please look into the wiki page. / 下記のWikiページをご覧ください。<br />
** [[Japan Technical Jamboree 67]]<br />
<br />
== Hash tag on Twitter ==<br />
* '''#CELFJP'''<br />
<br />
<!--<br />
* togetter (Previous Japan Jamboree)<br />
** https://togetter.com/li/1177235<br />
--><br />
<br />
= Date and venue... / 日付・場所... =<br />
{|<br />
|+<br />
|-<br />
| style="vertical-align:top" |<br />
[[Image:NakanoSunplaza2.jpg]]<br />
| style="vertical-align:top; background-color:#F0F0F0" width=90% |<br />
* Date '''March 8th, 2019'''<br />
** '''Starting at 10 am'''<br />
* At '''''Nakano Sunplaza / 8F Training Room 2''''' / 会場 '''''中野サンプラザ / 8階・研修室2'''''<br />
** Nakano Sunplaza is located just close to '''Nakano''' station (JR/Tokyo Metoro ).<br />
** http://www.sunplaza.jp/ (Japanese)<br />
* Admission: '''''Free of charge''''' / 参加費用: '''''無料'''''<br />
* Registration: '''''Not Required''''' / 参加登録: '''''不要'''''<br />
* Not limited for CE Workgroup members. / CE Workgroup会員以外も参加・セッション持ち込み共に可能<br />
* Coordinators / 世話役 (Your inquiries in English welcome)<br />
** Hisao Munakata / 宗像尚郎 (hisao_dot_munakata_dot_vt(a)renesas_dot_com) <br />
** Satoru Ueda / 上田理 (Satoru_dot_Ueda(a)jp_dot_sony_dot_com)<br />
|}<br />
== Registration / 参加登録 ==<br />
* No registration required / 参加登録は要りません。<br />
<br />
= Main Topics =<br />
* Embedded Linux Conference Europe is coming! [https://events.linuxfoundation.org/events/elc-openiot-europe-2018/ ELC-E 2018] .<br />
<br />
= Agenda / 進行 =<br />
== Agenda ==<br />
<br />
{|<br />
|+<br />
! style="text-align:left; background-color:#B0FFB0; width:50" | Time<br />
! style="text-align:left; background-color:#B0FFB0; width:70%" | Title and presenter<br />
! style="text-align:left; background-color:#B0FFB0" | Notes<br />
Presentation Materials<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 10:00..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* Opening / 連絡事項<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 10:15am..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Status of Embedded Linux'''<br />
* '''Tim Bird'''<br />
** Recent Status of Embedded Linux technologies (in slides) <br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* [[Media:Status-of-embedded Linux-2018-11-JJ67.pdf|PDF_English]]<br />
* (In English / 英語のセッションです)<br />
* [[Image:Youtube.png]] [[Image:Us_flagSymbol.gif]] [https://youtu.be/1crGEo0dBJs Video]<br />
|-<br />
| style="vertical-align:top; background-color:#B0B0FF" | 11:30..<br />
| style="vertical-align:top; background-color:#B0B0FF" | Lunch<br />
| style="vertical-align:top; background-color:#B0B0FF" |<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 1:00pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Let's look into debootstrap'''<br />
* '''Hideki Yamane''' (SIOS Technology, Inc. / Debian Project)<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 1:30pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Running the AVS device SDK on NuttX/LC823450 '''<br><br />
~Linux向けアプリケーションソフトウェアをNuttXで動作させる~<br />
* '''Masayuki Ishikawa''' (Sony Corp.)<br />
** https://github.com/alexa/avs-device-sdk/wiki<br />
** Linux 環境向けに用意された Alexa Audio Voice Service を NuttX 上で動作させます。'''<font color=red>NuttXがPosixとの互換性が高い</font>'''ことはこのようなアドバンテージがあります。<br />
** また併せて nghttp2 が'''<font color=red>他からネットワーク系のモジュールを持ち込まなくてもNuttX環境のみで動作する</font>'''ことなども注目してください。<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 2:15pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Yocto projectを使ったCustom Linux imageのつくりかた(仮)'''<br />
* '''Toshifumi NISHINAGA''' (NTT Communications)<br />
** Yocto projectを用いてCustom Linux imageを作る方法について話す予定です。<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 3:15pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''DebianにおけるSDカードへの書込み回数の低減方法 (How to reduce the number of write io to SD card on Debian)'''<br />
* '''Masahiro YAMADA''' (Toshiba Memory)<br />
** Debian使用時におけるSDカードへの意図していない書込みを、設定だけで極力減らす方法と、その副作用の紹介<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 4:00pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''An Approach to Manage AGL OSS License Compliance'''<br />
* '''Thuy Tran''' (Renesas)<br />
** The talk discusses about open-source tools which support scanning OSS license/copyright in the build CI workflow.<br><br />
:: The generated output, i.e. the SPDX documents, can help automate the OSS license management in AGL community.<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 4:40pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Use RAUC as AGL SOTA Solution'''<br />
* '''Thu Nguyen''' (Renesas)<br />
** The talk shares the experiences of using RAUC as a Software update solution for AGL software.<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
|-<br />
| style="vertical-align:top; background-color:#F0F0F0" | 5:30pm..<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
'''Call for session'''<br />
| style="vertical-align:top; background-color:#F0F0F0" |<br />
* [[Japan TJ Session Proposal|<span style="color:red">Session proposal how-to. / 提案の方法</span>]]<br />
* Link to presentation material<br />
|-<br />
|}<br />
<br />
* Please be noted above time table is just a guideline and may be shifted. / 上記の時間割は目安です。かなり前後する可能性がありますので、あらかじめご承知おきください。<br />
<br />
== Special Remarks ==<br />
* Please place some detail descriptions about each presentation topics.<br />
: こちらに各プレゼンテーションの詳細などを記載してください。<br />
<br />
* togetter<br />
<br />
<!--<br />
** [http://togetter.com/li/1055101 Summary of twitter]<br />
--><br />
<br />
= Ask for your help / お願い =<br />
== Presentation Materials ==<br />
* We wish you to prepare the materials in English. / 出来るだけプレゼンテーション資料は英語で表記してください。絶対ではありませんが、日本語が理解できない方に対しての配慮が出来ればと思います。<br />
* Please leave your material in this wiki site after the event. / ジャンボリー終了後、プレゼンテーション資料はこのWikiに残してください。<br />
== English Translation Volunteer ==<br />
* If you can help the translation volunteer from Japanese to English, we would be very much appreciated! / 日本語を英訳していただくボランティアを大歓迎します!<br />
<br />
[[Category:Japan Technical Jamboree]]<br />
[[Category:Events]]</div>Khiem.renesashttps://elinux.org/index.php?title=Board_Farm&diff=475046Board Farm2018-09-14T01:32:22Z<p>Khiem.renesas: /* Community */</p>
<hr />
<div>Here is some information about board farms.<br />
<br />
= Community =<br />
At the Embedded Linux Conference Europe 2017 Andrew Murray held a BoF session titled [https://osseu17.sched.com/event/CezG/farming-together-andrew-murray-witekio Farming Together]. The purpose of this BoF was to bring together people that are actively working on board farms to create a community, to knowledge share and to start a collaborative effort. <br />
<br />
Add your name and contact information if you would like to be notified when an e-mail list is created,<br />
or are generally interested in this topic:<br />
* Andrew Murray - <amurray (at) witekio.com> *<br />
* Tim Bird - <tim.bird (at) sony.com> *<br />
* Robert Schwebel <r.schwebel (at) pengutronix.de> *<br />
* Arnout Vandecappelle - <arnout at mind dot be> -- doesn't have a board farm but is interested<br />
* Mirza Krak - <mirza.krak (at) endian.se> *<br />
* Alan Bennett - <alan (at) opensourcefoundries.com><br />
* Geert Uytterhoeven - <geert (at) linux-m68k.org> *<br />
* Andrea Scian - <andrea.scian (at) dave.eu><br />
* Kieran Bingham - <kbingham (at) kernel.org> *<br />
* Jan Lübbe - <j.luebbe (at) pengutronix.de> *<br />
* Marco Cavallini - <m.cavallini (at) koansoftware.com><br />
* Kevin Hilman - <khilman (at) baylibre.com><br />
* Bill Mills - <wmills (at) ti.com><br />
* Tom Gall - <tom.gall (at) linaro.org><br />
* Stephano Cetola - <stephano.cetola (at) linux.intel.com><br />
* Mike Holmes - <mike.holmes (at) linaro.org><br />
* Matteo Vit - <matteo.vit (at) dev.starwaredesign.com><br />
* Attie Grande - <attie (at) argentum-systems.co.uk><br />
* Roland Hieber <r <dot> hieber <at> pengutronix <dot> de><br />
* Tim Orling <ticotimo (at) gmail (dot) com><br />
* Ryan Arnold <ryan <dot> arnold <at> linaro <dot> org><br />
* Behan Webster <behanw (at) converseincode (dot) com><br />
* Michal Simek <monstr (at) monstr (dot) eu><br />
* Krzysztof Kozlowski <krzk (at) kernel (dot) org><br />
* Jagan Teki <jagan (at) openedev (dot) com><br />
* Heiko Schocher <hs (at) denx (dot) de><br />
* Khiem Nguyen <khiem.nguyen.xt (at) renesas.com><br />
<br />
* = have seen this person on the e-mail list, or already subscribed.<br />
<br />
== Mailing list ==<br />
Discussions on this topic have started at on the "Automated Testing" mailing list of the Yocto Project<br />
* See https://lists.yoctoproject.org/listinfo/automated-testing<br />
<br />
== Next meeting ==<br />
To be determined.<br />
<br />
Maybe at Plumbers 2018, Connect, or ELCE 2018<br />
<br />
See [[Automated Testing Summit]]<br />
<br />
= Actions =<br />
* define API between test framework and DUT controller layer?<br />
** pduclient?<br />
** [http://labgrid.org labgrid]?<br />
** ebfarm?<br />
** [https://github.com/russdill/ttypersist ttypersist: provides an application a fake socket for misbehaving ttys]<br />
** [[ttc]]<br />
** libvirt<br />
** r4d<br />
* survey of existing tools, hardware, practices<br />
* create a definition for an "automated testing" stack - see [[Automated Testing Stack]]<br />
** start with definitions from SLAV?<br />
** identify different areas of test automation operation<br />
<br />
= Presentations =<br />
If you know of a presentation on this topic, please add it below:<br />
* "Test Standards - Can Fuego, Lava and others agree?" by Tim Bird at Linaro Connect SFO 2017<br />
** description: Tim proposes several areas of standardization collaboration between different Linux test initiatives<br />
** [http://fuegotest.org/ffiles/Test-Standards-LC-2017.pdf Slides] and [https://www.youtube.com/watch?v=uwWSijtVsLE Video]<br />
* "Herd Your Boards, Become a Farmer" by Geert Uytterhoeven at ELCE2016<br />
** [[Media:Herd_Your_Boards.pdf | Slides]] and [https://youtu.be/kwqmjeqAx-E Video]<br />
* "Automation beyond Testing and Embedded System Validation" by Jan Luebbe (Pengutronix) at ELCE2017<br />
** [[Media:PRE-trunk-ELCE-Automation-beyond-Testing.pdf | Slides ]] and [https://www.youtube.com/watch?v=S0EJJM5bVUY&list=PLbzoR-pLrL6pISWAq-1cXP4_UZAyRtesk&index=21 Video]<br />
* Introduction to kernelCI.org<br />
** [http://baylibre.com/intro-kernelci/ Blog Article] and [https://youtu.be/kSe5GMJvqOI Video]<br />
* Piece of cake - testing remote embedded devices made easy with MuxPi by Paweł Wieczorek at FOSDEM 2018<br />
** [https://fosdem.org/2018/schedule/event/remote_embedded_testing/attachments/slides/2149/export/events/attachments/remote_embedded_testing/slides/2149/Piece_of_cake.pdf Slides] and [https://fosdem.org/2018/schedule/event/remote_embedded_testing Details]<br />
<br />
= Best Practices =<br />
<br />
= Issues/Requirements =<br />
<br />
= Misc / Tools = <br />
* New horizontally scalable CI system built with Containers and container orchestration technologies in mind - https://github.com/OpenSourceFoundries/jobserv / http://connect.linaro.org/resource/sfo17/sfo17-217/<br />
<br />
= Hardware =<br />
== SD muxers ==<br />
* [http://www.pengutronix.de/en/2017-10-23-usb-sd-mux-automated-sd-card-juggler.html USB-SD-Mux] by Pengutronix<br />
* [https://wiki.tizen.org/SD_MUX SD-MUX] by Tizen (deprecated - see MuxPi)<br />
* [https://wiki.tizen.org/MuxPi MuxPi] by Tizen (MuxPi is the successor to SD-MUX)<br />
<br />
Kevin Hilman mentioned (at ELCE 2017) wifi SDCards as a way to handle the SD mux problem.<br />
Was he referring to something like these? http://techpp.com/2015/04/28/wifi-sd-cards-camera/ <br />
<br />
== power control ==<br />
* usb board with switchable power<br />
** ykush - 3 port USB power switcher - https://www.yepkit.com/products/ykush<br />
* [https://dlidirect.com/products/web-power-switch-7 Web Power Switch] by Digital Loggers<br />
** control program by Tim Bird: [[File:Powerswitch-set.sh]]<br />
* [https://energenie4u.co.uk/catalogue/product/ENER011 Energenie Power Management System (USB controlled 4-way power switch +2 always on) (UK)]<br />
<br />
== relays/buttons ==<br />
* [https://github.com/geertu/Optoboard 8-Channel Opto-Isolator Board for Board Farm Control]<br />
* [https://www.digital-loggers.com/din.html DIN Relay IV by Digital Loggers]<br />
** This uses the same control protocol as the Web Power Switch mentioned above<br />
* [https://www.kmtronic.com/lan-ethernet-ip-8-channels-web-relay-board.html KMTronic 8-channel IP relay controller]<br />
* [https://www.waveshare.com/rpi-relay-board.htm Raspberry Pi relay board]<br />
<br />
== multi-function ==<br />
* [http://baylibre.com/acme/ BayLibre ACME cape] - power and temperature measurement with different probes (USB, Jack power cable, HE10)<br />
* [[Sony_Debug_Assist_board]] - Open Hardware design by Sony for multi-function DUT controller (USB, serial, power, buttons)<br />
** connection to host = USB<br />
* [https://wiki.tizen.org/MuxPi MuxPi] by Tizen Open Hardware design by Samsung for multi-function DUT controller (serial, power, buttons, network?)<br />
** connection to host = network<br />
* [https://lava.coreboot.org/static/docs/v1/lmp_test_guide.html LAVA-LMP suite of boards]:<br />
** LAVA-LMP LSGPIO - tests GPIO audio hot-plug, SPI bug - can do boot source selection, switch actuation simulation LED state confirmation, scanned keypress simulation<br />
** LAVA-LMP ETH+SATA - for testing 10/100 Ethernet and SATA connect and disconnect testing<br />
** LAVA-LMP HDMI - for testing HDMI hot-plug test, EDID: monitor emulation and activity recording, and more<br />
** LAVA-LMP SD MUX - for SD-related testing (bootloader, SD card hot-plug testing) <br />
<br />
== USB mega-ports ==<br />
A few people are using these:<br />
* [https://www.amazon.com/Manhattan-Port-USB-Hub-161718/dp/B0074024XU Manhattan Mondohub 28-port USB hub]<br />
<br />
== USB switchers ==<br />
* [https://lava.coreboot.org/static/docs/v1/lmp_test_guide.html LAVA-LMP USB] - allows switching USB connections to a DUT<br />
<br />
== gpio controllers ==<br />
<br />
== unsorted LAVA hardware helpers ==<br />
See https://lava.coreboot.org/static/docs/v1/lmp_test_guide.html<br />
*<br />
<br />
= Software =<br />
* Labgrid : http://labgrid.readthedocs.io - http://labgrid.org<br />
* CI-RT : https://ci-rt.linutronix.de<br />
* R4D : https://github.com/ci-rt/r4d - https://github.com/ci-rt/libr4d<br />
* Libvirt : https://github.com/ci-rt/libvirt-debian<br />
* Jenkins plugin : https://github.com/ci-rt/libvirt-slave-plugin<br />
* ttc : https://github.com/tbird20d/ttc - documentation at: [[Ttc_Program_Usage_Guide]]<br />
* tbot : https://github.com/hsdenx/tbot - http://www.tbot.tools/main.html<br />
* SLAV stack : ??? (Pawel's thing - see [[Media:Piece_of_cake.pdf]]<br />
<br />
= Notes =<br />
* spend money on USB serial adapter cables - cheap adapters sometimes drop connections and are a pain to debug<br />
** FTDI cables seem to work well.<br />
<br />
= Farm Survey =<br />
Tim Bird is conducting a survey of Farm hardware (DUT controllers). See this page: [[Board Farm Survey]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car&diff=474571R-Car2018-09-10T03:47:35Z<p>Khiem.renesas: Update information of R-Car Yocto session</p>
<hr />
<div>{{TOC right}}<br />
<br />
'''<span style="color:#008000;">Jump to R-Car boards pages</span>''' <sub>[[File:Arrow Right-Down.svg|19px|frameless]]</sub><br />
<br />
* [[R-Car/Boards/Alt|Alt]]<br />
* [[R-Car/Boards/BOCK-W|BOCK-W]]<br />
* [[R-Car/Boards/Draak|Draak]]<br />
* [[R-Car/Boards/Gose|Gose]]<br />
* [[R-Car/Boards/Koelsch|Koelsch]]<br />
* [[R-Car/Boards/Lager|Lager]]<br />
* [[R-Car/Boards/Marzen|Marzen]]<br />
* [[R-Car/Boards/Porter |Porter]]<br />
* [[R-Car/Boards/Salvator-X|Salvator-X]]<br />
* [[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
* [[R-Car/Boards/SILK|SILK]]<br />
* [[R-Car/Boards/M3SK |R-Car Starter Kit Pro]]<br />
* [[R-Car/Boards/H3SK |R-Car Starter Kit Premier]]<br />
* Gen2 ADAS boards:<br />
** [[R-Car/Boards/Blanche|Blanche]]<br />
** [[R-Car/Boards/Wheat|Wheat]]<br />
** [[R-Car/Boards/Stout|ADAS Starter Kit (Stout)]]<br />
** [[R-Car/Boards/Stout:View|ADAS Surround View Kit]]<br />
* Gen3 ADAS boards ([[R-Car/Boards/Yocto-Gen3-ADAS|common instructions]]):<br />
** [[R-Car/Boards/Salvator-X-view|Salvator-X View Kit]]<br />
** [[R-Car/Boards/ADAS-View-Solution-Kit |ADAS View Solution Kit]]<br />
** [[R-Car/Boards/HAD-Solution-Kit |HAD Solution Kit]]<br />
** [[R-Car/Boards/Kingfisher|Kingfisher Infotainment Board]]<br />
** [[R-Car/Boards/Eagle|V3M Eagle Board]]<br />
** [[R-Car/Boards/V3MSK |R-Car V3M Starter Kit]]<br />
** [[R-Car/Boards/Condor|V3H Condor Board]]<br />
** [[R-Car/Boards/V3HSK |R-Car V3H Starter Kit]]<br />
<br />
= Introduction = <br />
<br />
This is starting page for Embedded Linux on Renesas R-Car family of automotive embedded SoCs. Main goal is to make information on R-Car SoCs friendly, easy to access for embedded developers, enthusiasts. It does not aim to replace official Renesas support.<br />
<br />
Links below could be used to get familiar with Renesas Automotive SoCs and R-Car Concortia:<br />
*[http://am.renesas.com/applications/automotive/index.jsp Renesas Automotive Products / Solutions]<br />
*[http://am.renesas.com/applications/automotive/cis/cis_highend/index.jsp Renesas Car Information Terminal Applications]<br />
*[http://r-car-consortium.renesas.com/jpn/index.html R-Car Consortium]<br />
<br />
Detailed information regarding R-Car SoCs (including roadmap, technical and marketing documents, BSPs and middleware) can be obtained directly from Renesas representative.<br />
<br />
= R-Car SoCs =<br />
{| class="wikitable"<br />
|+ Renesas R-Car SoC variants (Generations)<br />
|-<br />
|<br />
| '''Generation 1'''<br />
| '''Generation 2'''<br />
| '''Generation 3'''<br />
|-<br />
|'''"H"''' - Premium/High end<br />
| '''H1''' - R8A7779<br />
| '''H2''' - R8A7790<br />
| '''H3''' - R8A7795 (or R8J7795)<br />
|-<br />
|'''"M"''' - Mid range<br />
| '''M1A''' - R8A7778<br />
|'''M2-W''' - R8A7791<br/>'''M2-N''' - R8A7793<br />
|'''M3-W''' - R8A77960<br/>'''M3-N''' - R8A77965<br />
|-<br />
|'''"E"''' - Entry class<br />
| '''E1'''<br />
| '''E2''' - R8A7794<br />
|<br />
|-<br />
|'''"V"''' - ADAS<br />
|<br />
|'''V2H''' - R8A7792<br />
|'''V3M''' - R8A77970<br/>'''V3H''' - R8A77980<br />
|}<br />
<br />
The [[R-Car/Devices|R-Car devices]] pages lists the peripheral devices available in the R-Car SoCs along with usage information and test procedures.<br />
<br />
= R-Car Boards =<br />
<br />
== Generation 1 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen1 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H1''' <br />
|[[R-Car/Boards/Marzen|Marzen]]<br />
|Geuze<br />
|-<br />
|'''R-Car M1A'''<br />
|[[R-Car/Boards/BOCK-W|BOCK-W]]<br />
|Milan<br />
|-<br />
|'''R-Car E1'''<br />
| Silverstone<br />
| <br />
|}<br />
<br />
== Generation 2 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen2 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H2''' <br />
|[[R-Car/Boards/Lager|Lager]]<br />
|[[File:65px-Stout_top.png|65px|link=R-Car/Boards/Stout]]<br/>[[R-Car/Boards/Stout |ADAS Starter Kit (Stout)]]<br/>[[R-Car/Boards/Stout:View| ADAS Surround View Kit]]<br />
|-<br />
|-<br />
|'''R-Car M2-W'''<br />
|[[R-Car/Boards/Koelsch|Koelsch]]<br />
|[[File:65px-Porter_top.png|65px|link=R-Car/Boards/Porter]]<br/>[[R-Car/Boards/Porter |Porter]]<br />
|-<br />
|-<br />
|'''R-Car M2-N'''<br />
|[[R-Car/Boards/Gose|Gose]]<br />
|<br />
|-<br />
|'''R-Car E2'''<br />
| [[R-Car/Boards/Alt|Alt]]<br />
| [[File:65px-Silk_top.png|65px|link=R-Car/Boards/SILK]]<br/>[[R-Car/Boards/SILK | SILK]]<br />
|-<br />
|'''R-Car V2H'''<br />
| [[R-Car/Boards/Blanche|Blanche]]<br />
| [[File:65px-Wheat_top.png|65px|link=R-Car/Boards/Wheat]]<br/>[[R-Car/Boards/Wheat | Wheat]]<br />
|-<br />
|}<br />
<br />
== Generation 3 ==<br />
<br />
{| class="wikitable"<br />
|+ Renesas R-Car Gen3 evaluation boards<br />
|-<br />
|<br />
|'''Standard'''<br />
|'''Low Cost Boards (LCB)'''<br />
|-<br />
|'''R-Car H3''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/H3SK| R-Car Starter Kit Premier]]<br />
|-<br />
|'''R-Car M3-W''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|[[R-Car/Boards/M3SK|R-Car Starter Kit Pro]]<br />
|-<br />
|'''R-Car M3-N''' <br />
|[[R-Car/Boards/Salvator-X|Salvator-X]]<br/>[[R-Car/Boards/Salvator-XS|Salvator-XS]]<br />
|<br />
|-<br />
|'''R-Car V3M''' <br />
|[[R-Car/Boards/Eagle|Eagle]]<br />
|[[R-Car/Boards/V3MSK|Starter Kit]]<br />
|-<br />
|'''R-Car V3H''' <br />
|[[R-Car/Boards/Condor|Condor]]<br />
|[[R-Car/Boards/V3HSK|Starter Kit]]<br />
|-<br />
|'''R-Car D3'''<br />
|[[R-Car/Boards/Draak|Draak]]<br />
|<br />
|-<br />
|}<br />
<br />
= R-Car Linux =<br />
<br />
== Upstream ==<br />
<br />
Renesas mainline R-Car Linux tree is maintained by [http://horms.org/about_me.shtml Simon Horman]<br />
<br />
Start here to get latest/closest upstream kernel:<br />
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
e.g. pull development branch: git clone -b devel git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git<br />
<br />
=== Branches ===<br />
* '''next'''<br />
** Patches queued up for the forthcoming Kernel release<br />
** This is included in linux-next and complies with its rules<br />
** It is a feeder for submissions (pull requests) to the ARM-SoC maintainers<br />
** It is generally based on the latest rc1 release but may be based on a later rc release in order to provide a working kernel for ARM (32-bit) and ARM64 based Renesas SoCs.<br />
* '''devel'''<br />
** All patches queued up for submission to the ARM-SoC maintainers<br />
** This is a feeder for the next branch and allows patches to be queued up during times when updates to the next branch are not appropriate<br />
** Based on a merge of the next branch and the latest rc or full release<br />
* '''*-for-vX.Y'''<br />
** Individual patch-queues for the ARM-SoC maintainers as per their requirements for patches to be broken out into branches<br />
** Patches are targeted at kernel version X.Y<br />
** Merged into next or devel<br />
* '''topic/*'''<br />
** Branches for specific new features<br />
** Pushed when the features are under review of otherwise not queued up for submission to the ARM-SoC maintainers<br />
* other<br />
** Temporary branches typically for testing purposes<br />
<br />
=== Hardware Support Status (Incomplete) ===<br />
* [[Renesas-MMC-Enabled-Speeds|Enabled Speeds for MMC Devices on R-Car Gen 2 and 3]]<br />
<br />
== R-Car Community==<br />
*Mailing list - via kernel.org [mailto:majordomo@vger.kernel.org?body=subscribe linux-renesas-soc Majordomo].<br />
Archives available here: http://dir.gmane.org/gmane.linux.kernel.renesas-soc , http://www.spinics.net/lists/linux-renesas-soc/<br />
<br />
== LTSI (Long Term Support Initiative) ==<br />
<br />
Renesas SoCs and boards are supported as part of LTSI project - http://ltsi.linuxfoundation.org/ . Refer to [http://ltsi.linuxfoundation.org/releases/ltsi-tree/4.1.17-ltsi/stable-release 4.1.17-LTSI] and [http://ltsi.linuxfoundation.org/releases/ltsi-tree/3.14.28-ltsi/stable-release 3.14.28-LTSI].<br />
<br />
== Renesas R-Car Gen 2 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-backport.git. Check out the latest R-Car Gen 2 BSP release tag.<br />
<br />
for example: rcar-gen2/v1.9.7<br />
<br />
== Renesas R-Car Gen 3 BSP Tree ==<br />
<br />
Renesas R-Car Gen 2 BSP Tree located at: git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git.<br />
Check out the latest R-Car Gen 3 BSP release tag.<br />
<br />
for example: rcar-3.2.1<br />
<br />
= R-Car U-Boot =<br />
<br />
For Gen3 see [[R-Car/Boards/U-Boot-Gen3|U-Boot-Gen3]].<br />
<br />
R-Car U-Boot mainline development is done using git://git.denx.de/u-boot-sh.git tree. It is maintained by Nobuhiro Iwamatsu.<br />
<br />
e.g. pull renesas/bsp/rcar-gen2-1.8.0 branch and build U-Boot for Lager/Koelsch/Alt boards<br />
git clone -b renesas/bsp/rcar-gen2-1.8.0 git://git.denx.de/u-boot-sh.git<br />
<br />
build example<br />
make O=/tmp/build clean<br />
make O=/tmp/build mrproper<br />
make O=/tmp/build gose_config<br />
make O=/tmp/build all<br />
<br />
= R-Car Yocto =<br />
<br />
*For Gen3, see [[R-Car/Boards/Yocto-Gen3|Yocto-Gen3]]<br />
*Community BSP following official Yocto Project versions<br />
<ol>Refer to README.md for release policy and build instructions.<br><br />
To integrate evaluation version of proprietary graphics and multimedia drivers from Renesas, refer to README.evaproprietary.md.<br><br />
Repository location: https://github.com/renesas-rcar/meta-renesas.git<br><br />
Latest release:<br />
:Yocto Project 2.5 (codename: sumo)<br />
::Branch: sumo-dev<br><br />
::Tag: sumo-Yocto-v3.9.0<br><br />
::Build instructions are described at [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.md README.md] and [https://github.com/renesas-rcar/meta-renesas/blob/sumo-dev/meta-rcar-gen3/README.evaproprietary.md README.evaproprietary.md].<br><br />
</ol><br />
<br />
*Renesas Yocto/Poky distribution<br />
<ol>Renesas Yocto/Poky distribution is maintained by Takamitsu Honda.<br><br />
To get started with Yocto on R-Car Gen2 platform - pull git://git.yoctoproject.org/meta-renesas tree<br><br />
If you pulled complete Yocto/poky trees, you should be able to kick-off a build using the 'oe-init-build-env' script in Poky. <br><br />
<br />
Update bblayers.conf by adding the meta-renesas and meta-rcar-gen2 layer. e.g.:<br />
<pre><br />
BBLAYERS ?= " \<br />
<path to layer>/poky/meta \<br />
<path to layer>/poky/meta-yocto \<br />
<path to layer>/poky/meta-yocto-bsp \<br />
<path to layer>/meta-renesas \<br />
<path to layer>/meta-renesas/meta-rcar-gen2 \<br />
"<br />
</pre><br />
<br />
To build a specific target BSP configure the associated machine in local.conf:<br />
<pre><br />
MACHINE ?= "<supported board name>" (lager, koelsch, gose, alt)<br />
</pre><br />
Build the target file system image using bitbake:<br />
<pre><br />
$ bitbake core-image-minimal<br />
</pre><br />
</ol><br />
<br />
= R-Car Automotive Grade Linux =<br />
<br />
Automotive Grade Linux (AGL) is a Linux Foundation Workgroup dedicated to creating open source software solutions for automotive applications.<br />
AGL is based on Yocto project for its construction and R-Car Porter board can be used to start an AGL distribution. Please check [[/Boards/Porter#Which_operating_systems.2Fdistributions_can_be_used_with_R-Car_M2_Porter_board.3F|this page]].<br />
<br />
= R-Car Genivi =<br />
''GENIVI® is a nonprofit industry alliance committed to driving the broad adoption of specified, open source, In-Vehicle Infotainment (IVI) software''.<br />
Source: http://www.genivi.org/<br />
<br />
As a service to the community Renesas maintains a git repository containing a R-Car Yocto BSP with the changes required for the standard Yocto BSP to work with the [https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines Genivi Yocto Baseline] and [https://at.projects.genivi.org/wiki/pages/viewpage.action?pageId=11567210 Genivi Development Platform (GDP)] already integrated. It is supported on a best effort basis.<br />
<br />
You can find more information about building the Genivi Yocto Baseline for various Genivi versions in the Alliance pages for meta-ivi [https://at.projects.genivi.org/wiki/display/PROJ/Meta+ivi+BSPs+for+Specific+Hardware here].<br />
Information on building GDP for R-Car M2 Porter can be found [https://at.projects.genivi.org/wiki/display/GDP/Renesas+R-Car+M2+Porter+Hardware+Setup+and+Software+Installation here] and E2 Silk [https://at.projects.genivi.org/wiki/display/GDP/Renesas+R-Car+E2+Silk+Hardware+Set+Up+And+Software+Installation here].<br />
<br />
= R-Car Virtualization =<br />
<br />
See [[R-Car/Virtualization]].<br />
<br />
= R-Car Tizen =<br />
<br />
TBD ''Renesas R-Car [[Tizen]] is already available via tizen.org trees. Add detailed instructions how to get started with Tizen for R-Car''<br />
<br />
= R-Car Android =<br />
<br />
TBD ''This section will be added later''<br />
<br />
= R-Car Emotion Recognition Engine SDK =<br />
<br />
See [[R-Car/Emotion Recognition Engine SDK Image preparation guide]]<br />
<br />
[[Category:Automotive]]</div>Khiem.renesashttps://elinux.org/index.php?title=R-Car/Boards/Kingfisher&diff=474346R-Car/Boards/Kingfisher2018-09-06T01:06:26Z<p>Khiem.renesas: /* Known Issues */</p>
<hr />
<div>{{TOC right}}<br />
<br />
== Introduction ==<br />
This is the official Wiki for Kingfisher Infotainment Board.<br />
<br />
== Hardware ==<br />
<br />
This section contains information about Kingfisher Board hardware.<br />
<br />
===Board Layout===<br />
<br />
[[File:Kfisher top specs.png|802px]]<br />
<br> <br><br />
[[File:Kfisher bot specs.png|802px]]<br />
<br />
=== Hardware Features ===<br />
* Ethernet AVB phy<br />
** KSZ9031 phy<br />
* MOST interface<br />
** Support both 3-pin and 6-pin MLB interface<br />
** Pinout compatible with Microchip evaluation boards<br />
* LVDS camera interface<br />
** MAX9286 or TI960 deserializers<br />
** MIPI CSI2 bus<br />
** 5V, 9V or 12V selectable supply voltage for camera with current limiting<br />
* High quality 24-bit audio codec PCM3168A<br />
** 8 input channels (4 stereo jacks for microphone connection)<br />
** 6 line out channels (RCA connectors)<br />
** 6 HP outputs (3 stereo jack connectors for direct headphones connection)<br />
** 44100/48000 Hz sampling frequency<br />
* Two USB 3.0 ports<br />
* USB OTG port<br />
* SD card slot<br />
** SD card slot(CN47) supports only 3.3 signal voltage(= Default/High speed class only).<br />
*** If you want to use other cards please use the slot(CN6) on the Starter Kit board.<br />
* Si4689 base AM/FM/DAB radio<br />
** Digital audio interface to R-Car M2 CPU<br />
** Additional flash storage for fast radio boot<br />
** Supply for active DAB antennas with current limit (5 or 12 V)<br />
* GPS/GLONASS receiver<br />
** Serial and i2c interface to R-Car<br />
* 9-axis sensor:<br />
** 3D digital linear acceleration sensor<br />
** 3D digital angular rate sensor<br />
** 3D digital magnetic sensor<br />
* WiFi/BT module Texas Instruments WL1837<br />
*HDMI<br />
** This board equipped with a HDMI transmitter (ADV7513BSWZ) which support HDMI1.4a.<br />
** The maximum resolution is 1920x1080i and it connected Digital output port (RGB888) on R-Car Starter Kit.<br />
* Power supply: 12V, 9 Amps<br />
** The main power supply domain must be connected to an external AC adapter. The voltage is +12V DC.<br />
** <span style="color:#ff0000">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.</span><br />
<br />
== Where to buy ==<br />
Kingfisher board and GMSL Camera board(*) can be ordered from following distributors:<br />
<br />
[http://www.shimafuji.co.jp/Kingfisher/indexEN.html Click to buy Kingfisher board from SHIMAFUJI Electric] - World Wide <br/><br />
<br />
(*) GMSL Camera board info: http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02<br />
<br />
[https://www.marutsu.co.jp/pc/i/839824/ Click to buy Kingfisher board from Marutsu Electric] - Japan only <br/><br />
[https://www.chip1stop.com/USA/en/view/dispDetail/DispDetail?partId=SMFJ-0000001&keyword=SBEV-RCAR-KF-S03 Click to buy Kingfisher board from chip1stop]<br />
<br />
== Official board documentation ==<br />
<br />
*[http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/ Board Manual]<br />
<br />
== Change point ==<br />
{| class="wikitable"<br />
! Function !! M03 Board to M04 Board !! M04 Board to M05 Board<br />
|-<br />
| WIFI || Unmount SMA connector(CN45,CN46) || No difference<br />
|-<br />
| BLUETOOTH || ADD Level conversion IC(U116) / Support BT AUDIO(HFP) || No difference<br />
|-<br />
| SD CARD || Change Power IC(U106) / Not support SD1.8V || No difference<br />
|-<br />
| SERIAL || Change connector shape(CN4 Male to Female) || No difference<br />
|-<br />
| FPDLink || No difference || Delete function<br />
|- <br />
| POWER AMP || ADD Reset Signal(nVRST) || Delete function<br />
|- <br />
| MOST || ADD Level conversion IC(U118) || No difference<br />
|- <br />
| ETHER || ADD Level conversion IC(U117) || Delete function<br />
|}<br />
<br />
== How to build ==<br />
=== Build image ===<br />
<ol><br />
<li>Create a directory and switch to it <br/><br />
Warning! Yocto builds require a lot of disk space (up to 100 GB). Make sure you have got enough before starting the build.<br />
<pre><br />
mkdir build || exit<br />
cd build<br />
WORK=`pwd`<br />
echo $WORK<br />
</pre><br />
</li><br />
<li>Clone basic Yocto layers:<br />
<pre><br />
cd $WORK<br />
git clone git://git.yoctoproject.org/poky<br />
git clone git://git.linaro.org/openembedded/meta-linaro.git<br />
git clone git://git.openembedded.org/meta-openembedded<br />
git clone git://github.com/renesas-rcar/meta-renesas<br />
git clone git://github.com/CogentEmbedded/meta-rcar.git<br />
</pre><br />
</li><br />
<br />
<li><br />
Switch to proper branches/commits<br />
<ol><br />
<li><br />
For Yocto v2.23.1<br />
<pre><br />
cd $WORK/poky<br />
git checkout -b tmp yocto-2.1.3<br />
cd $WORK/meta-openembedded<br />
git checkout -b tmp 55c8a76da5dc099a7bc3838495c672140cedb78e<br />
cd $WORK/meta-linaro<br />
git checkout -b tmp 2f51d38048599d9878f149d6d15539fb97603f8f<br />
cd $WORK/meta-renesas<br />
git checkout -b tmp 7acbf5e2f99c59478adbc73c6a40d314589a3009<br />
cd $WORK/meta-rcar<br />
git checkout -b v2.23.1 remotes/origin/v2.23.1<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.9.0<br />
<pre><br />
cd $WORK/poky<br />
git checkout -b tmp 342fbd6a3e57021c8e28b124b3adb241936f3d9d<br />
cd $WORK/meta-openembedded<br />
git checkout -b tmp dacfa2b1920e285531bec55cd2f08743390aaf57<br />
cd $WORK/meta-linaro<br />
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885<br />
cd $WORK/meta-renesas<br />
git checkout -b tmp fd078b6ece537d986852cb827bd21e022a797b2f<br />
cd $WORK/meta-rcar<br />
git checkout -b v3.9.0 remotes/origin/v3.9.0<br />
</pre><br />
</li><br />
</ol><br />
Another versions are not tested for compatibility.<br />
Legacy BSP instruction can be found here [[R-Car/Boards/Kingfisher-legacy | R-Car Kingfisher legacy]]<br />
</li><br />
<br />
<li><br />
This step is only for Yocto v2.23.1.<br />
Apply Linaro-GCC patch file:<br />
<pre><br />
cd $WORK/meta-renesas<br />
export PATCH_DIR=meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc<br />
patch -p1 < ${PATCH_DIR}/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch<br />
unset PATCH_DIR<br />
</pre><br />
</li><br />
<li><br />
Unzip [https://www.renesas.com/us/en/solutions/automotive/rcar-download/rcar-demoboard.html downloaded] proprietary driver modules to $WORK/proprietary folder.<br/><br />
You should see the following files:<br />
<ol><br />
<li><br />
For Yocto v2.23.1<br />
<pre><br />
$ ls -1 $WORK/proprietary<br />
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20170828.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20170828.zip<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.9.0<br />
<pre><br />
$ ls -1 $WORK/proprietary/*.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20180627.zip<br />
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20180627.zip<br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<br />
<li><br />
Populate meta-renesas with proprietary software packages.<br />
<pre><br />
export PKGS_DIR=$WORK/proprietary<br />
cd $WORK/meta-renesas<br />
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR<br />
unset PKGS_DIR<br />
</pre><br />
</li><br />
<br />
<li><br />
Setup build environment<br />
<pre><br />
cd $WORK<br />
source poky/oe-init-build-env<br />
</pre><br />
</li><br />
<br />
<li><br />
Prepare default configuration files.<br />
<ol><br />
<li><br />
For Yocto v2.23.1<br />
<pre><br />
[m3ulcb]<br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/*.conf ./conf/<br />
[h3ulcb]<br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/*.conf ./conf/<br />
<br />
cd $WORK/build<br />
cp conf/local-wayland.conf conf/local.conf<br />
</pre><br />
</li><br />
<li><br />
For Yocto v3.9.0<br />
<pre><br />
[m3ulcb]<br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/m3ulcb/poky-gcc/mmp/*.conf ./conf/<br />
[h3ulcb]<br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/*.conf ./conf/<br />
<br />
cd $WORK/build<br />
cp conf/local-wayland.conf conf/local.conf<br />
</pre><br />
</li><br />
</ol><br />
<br />
<li><br />
Edit $WORK/build/conf/local.conf to enable/disable graphics and multimedia proprietary drivers support<br />
</li><br />
<br />
<li><br />
Edit local.conf with evaluation packages requirements:<br />
<ol><br />
<li><br />
For Yocto v2.23.1 and later (to enable EVA_ prefix during packages install)<br />
<pre><br />
DISTRO_FEATURES_append = " use_eva_pkg"<br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<br />
<li><br />
Add layer meta-rcar <br/><br />
<pre><br />
bitbake-layers add-layer ../meta-rcar/meta-rcar-gen3-adas<br />
</pre><br />
</li><br />
<br />
<li><br />
Start the build <br /><br />
<pre><br />
bitbake core-image-weston<br />
</pre><br />
</li><br />
<br />
<li><br />
Building image can take up to a few hours depending on your host system performance.<br><br />
After the build has been completed successfully, you should see the output similar to:<br />
<pre class="bash"><br />
NOTE: Tasks Summary: Attempted 4704 tasks of which 31 didn't need to be rerun and all succeeded.<br />
</pre><br />
and the command prompt should return.<br />
</li><br />
<br />
<li><br />
Bitbake has generated all the necessary files in ./tmp/deploy/images directory. <br/><br />
You can verify its content:<br />
<pre class="bash"><br />
$ ls -1 `find ./tmp/deploy/images/m3ulcb/ -maxdepth 1 -type l -print`<br />
./tmp/deploy/images/m3ulcb/core-image-weston-m3ulcb.cpio.gz<br />
./tmp/deploy/images/m3ulcb/core-image-weston-m3ulcb.ext4<br />
./tmp/deploy/images/m3ulcb/core-image-weston-m3ulcb.manifest<br />
./tmp/deploy/images/m3ulcb/core-image-weston-m3ulcb.tar.bz2<br />
./tmp/deploy/images/m3ulcb/Image<br />
./tmp/deploy/images/m3ulcb/Image-m3ulcb.bin<br />
./tmp/deploy/images/m3ulcb/Image-r8a7796-m3ulcb-kf.dtb<br />
./tmp/deploy/images/m3ulcb/modules-m3ulcb.tgz<br />
./tmp/deploy/images/m3ulcb/u-boot.bin<br />
./tmp/deploy/images/m3ulcb/u-boot-elf-m3ulcb.srec<br />
./tmp/deploy/images/m3ulcb/u-boot-elf.srec<br />
./tmp/deploy/images/m3ulcb/u-boot-m3ulcb.bin<br />
</pre><br />
'''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.<br />
</li><br />
<li><br />
You can now proceed with running Yocto images<br />
</li><br />
</ol><br />
<br />
After all these steps you can start working with boards and apps.<br />
<br />
=== Build with MOST ===<br />
MOST and GPS share the same R-CAR SoC pins and GPS is used by default. <br/><br />
In order to use MOST one need to perform h/w modifications on KF board:<br />
<pre><br />
move resistor from R661 -> R660<br />
move resistor from R663 -> R662<br />
</pre><br />
And enable MOST in BSP by adding option to local.conf:<br />
<pre><br />
KF_ENABLE_MOST = "1"<br />
</pre><br />
<br />
=== Build with SD3 (CN47) ===<br />
SD3 and WIFI share the same R-CAR SoC resource and WIFI is used by default. <br/><br />
In order to use SD on CN47 instead WIFI add following option to local.conf:<br />
<pre><br />
KF_ENABLE_SD3 = "1"<br />
</pre><br />
<br />
=== Build SDK ===<br />
After building image run this command to build SDK<br />
<pre><br />
bitbake core-image-weston -c populate_sdk<br />
</pre><br />
After build success the SDK installation script must appears in ./tmp/deploy/sdk directory:<br />
<pre><br />
tmp/deploy/sdk/poky-glibc-x86_64-core-image-weston-aarch64-toolchain-2.1.3.sh<br />
</pre><br />
To install SDK run this command and follow instructions on the screen:<br />
<pre><br />
./tmp/deploy/sdk/poky-glibc-x86_64-core-image-weston-aarch64-toolchain-2.1.3.sh<br />
</pre><br />
<br />
== Build scripts examples ==<br />
<ol><br />
<br />
<li> Build preparation<br />
<ol><br />
<li> For Yocto v2.23.1<br />
<pre><br />
#!/bin/sh<br />
<br />
mkdir build || exit<br />
cd build<br />
WORK=`pwd`<br />
echo $WORK<br />
<br />
git clone git://git.yoctoproject.org/poky<br />
git clone git://git.linaro.org/openembedded/meta-linaro.git<br />
git clone git://git.openembedded.org/meta-openembedded<br />
git clone git://github.com/renesas-rcar/meta-renesas.git<br />
git clone git://github.com/CogentEmbedded/meta-rcar.git<br />
<br />
cd $WORK/poky<br />
git checkout -b tmp yocto-2.1.3<br />
cd $WORK/meta-linaro<br />
git checkout -b tmp 2f51d38048599d9878f149d6d15539fb97603f8f<br />
cd $WORK/meta-openembedded<br />
git checkout -b tmp 55c8a76da5dc099a7bc3838495c672140cedb78e<br />
cd $WORK/meta-renesas<br />
git checkout -b tmp 7acbf5e2f99c59478adbc73c6a40d314589a3009<br />
cd $WORK/meta-rcar<br />
git checkout -b v2.23.1 remotes/origin/v2.23.1<br />
<br />
cd $WORK/meta-renesas<br />
export PATCH_DIR=meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc<br />
patch -p1 < ${PATCH_DIR}/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch<br />
unset PATCH_DIR<br />
<br />
cd $WORK/<br />
PKGS_DIR=$WORK/proprietary<br />
cd $WORK/meta-renesas<br />
#sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR<br />
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR<br />
</pre><br />
</li><br />
<li> For Yocto v3.9.0<br />
<pre><br />
#!/bin/sh<br />
<br />
mkdir build || exit<br />
cd build<br />
WORK=`pwd`<br />
echo $WORK<br />
<br />
git clone git://git.yoctoproject.org/poky<br />
git clone git://git.linaro.org/openembedded/meta-linaro.git<br />
git clone git://git.openembedded.org/meta-openembedded<br />
git clone git://github.com/renesas-rcar/meta-renesas<br />
git clone git://github.com/CogentEmbedded/meta-rcar.git<br />
<br />
cd $WORK/poky<br />
git checkout -b tmp 342fbd6a3e57021c8e28b124b3adb241936f3d9d<br />
cd $WORK/meta-openembedded<br />
git checkout -b tmp dacfa2b1920e285531bec55cd2f08743390aaf57<br />
cd $WORK/meta-linaro<br />
git checkout -b tmp 75dfb67bbb14a70cd47afda9726e2e1c76731885<br />
cd $WORK/meta-renesas<br />
git checkout -b tmp fd078b6ece537d986852cb827bd21e022a797b2f<br />
cd $WORK/meta-rcar<br />
git checkout -b v3.9.0 remotes/origin/v3.9.0<br />
<br />
cd $WORK/<br />
PKGS_DIR=$WORK/proprietary<br />
cd $WORK/meta-renesas<br />
#sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh -f $PKGS_DIR<br />
sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR<br />
</pre><br />
</li><br />
</ol><br />
</li><br />
<br />
<li> Building yocto<br />
<ol><br />
<li> For Yocto v2.23.1<br />
<pre><br />
#!/bin/sh<br />
<br />
cd build<br />
WORK=`pwd`<br />
echo $WORK<br />
<br />
cd $WORK<br />
source poky/oe-init-build-env<br />
<br />
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/bsp/*.conf ./conf/.<br />
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/gfx-only/*.conf ./conf/.<br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/linaro-gcc/mmp/*.conf ./conf/.<br />
<br />
cd $WORK/build<br />
cp conf/local-wayland.conf conf/local.conf<br />
echo "DISTRO_FEATURES_append = \" use_eva_pkg\"" >> $WORK/build/conf/local.conf<br />
# uncomment for ADAS HAD board only:<br />
#echo "MACHINE_FEATURES_append = \" h3ulcb-had\"" >> $WORK/build/conf/local.conf<br />
<br />
bitbake-layers add-layer ../meta-rcar/meta-rcar-gen3-adas<br />
<br />
bitbake core-image-weston<br />
bitbake core-image-weston -c populate_sdk<br />
</pre><br />
</li><br />
</ol><br />
<ol><br />
<li> For Yocto v3.9.0<br />
<pre><br />
#!/bin/sh<br />
<br />
cd build<br />
WORK=`pwd`<br />
echo $WORK<br />
<br />
cd $WORK<br />
source poky/oe-init-build-env<br />
<br />
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/bsp/*.conf ./conf/.<br />
#cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/gfx-only/*.conf ./conf/.<br />
cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/h3ulcb/poky-gcc/mmp/*.conf ./conf/.<br />
<br />
cd $WORK/build<br />
cp conf/local-wayland.conf conf/local.conf<br />
echo "DISTRO_FEATURES_append = \" use_eva_pkg\"" >> $WORK/build/conf/local.conf<br />
# uncomment for ADAS HAD board only:<br />
#echo "MACHINE_FEATURES_append = \" h3ulcb-had\"" >> $WORK/build/conf/local.conf<br />
<br />
bitbake-layers add-layer ../meta-rcar/meta-rcar-gen3-adas<br />
<br />
bitbake core-image-weston<br />
bitbake core-image-weston -c populate_sdk<br />
</pre><br />
</li><br />
</ol><br />
<br />
</li><br />
<br />
</ol><br />
<br />
==S/W support status==<br />
{| class="wikitable"<br />
! Functions !! Yocto v2.23.1 !! Yocto v3.7.0 !! Yocto v3.9.0<br />
|-<br />
| WiFi || ok || ok || ok <br />
|-<br />
| Bluetooth || ok || ok || ok <br />
|-<br />
| Gyro || ok || ok || ok<br />
|-<br />
| GPS || ok || ok || ok <br />
|-<br />
| CAN || ok || ok || ok <br />
|-<br />
| LVDS Camera(CN10/CN11) || ok || ok || ok <br />
|-<br />
| CMOS Camera || ok || ok || ok<br />
|-<br />
| Raspberry Pi camera Rev 1.3 || ok || ok || ok<br />
|-<br />
| USB2.0(CN13) Host || ok || ok || ok<br />
|-<br />
| USB2.0(CN13) Func(g_mass_storage) || ok || ok || ok<br />
|-<br />
| USB3.0(CN2) Host || ok (H3 only) || ok (H3 only) || ok (H3 only)<br />
|-<br />
| Multichannel Audio || ok || ok || ok <br />
|-<br />
| HDMI Out || ok || ok || ok<br />
|-<br />
| LVDS Out || ok || ok || ok<br />
|-<br />
| Serial(CN4) || ok || ok || ok<br />
|-<br />
| Mini PCIe || ok || ok || ok<br />
|-<br />
| M.2 || ok || ok || ok<br />
|-<br />
| MOST || ok || ok || ok<br />
|-<br />
|}<br />
<br />
Note: <br /><br />
"ok" - Function succeeded in the simple test as below.<br /><br />
"NT" - Function wasn't tested<br />
<br />
== How to test some capabilities ==<br />
<br />
===WiFi===<br />
To check wifi and scan available WAPs run:<br />
$ ifconfig wlan0 up<br />
$ iwlist wlan0 scan<br />
<br />
===Bluetooth===<br />
To check bluetooth and scan available BT devices run:<br />
$ hciconfig hci0 up<br />
$ hcitool -i hci0 scan<br />
<br />
===Gyro===<br />
$ cat /sys/bus/iio/devices/iio\:device0/*_raw (Accelerometer, Magnetometer)<br />
$ cat /sys/bus/iio/devices/iio\:device1/*_raw (Gyroscope)<br />
<br />
===GPS===<br />
$ cat /dev/ttySC3 (Yocto v2.23.1)<br />
$ cat /dev/ttySC2 (Yocto v3.x)<br />
<br />
===CAN===<br />
Ex) loop back<br><br />
Connect the following pins of CN17 and CN18:<br />
CN17 1pin - CN18 1pin<br />
CN17 2pin - CN18 2pin<br />
(*)Note: SW2 ON of KF. (defalt:ON)<br />
<br />
$ ip link set can0 up type can bitrate 125000<br />
$ ip link set can1 up type can bitrate 125000<br />
$ candump can0&<br />
$ cangen can1<br />
can0 08D [3] B5 F4 3C<br />
can0 34E [3] 7C A1 70<br />
can0 717 [6] 95 C5 67 4A 41 42<br />
can0 7F1 [8] CA B9 E9 3E AE 71 FC 52<br />
<br />
===Serial===<br />
Ex) loop back<br><br />
For KF M03: Connect the following pins on CN4:<br />
pin3(RxD) - pin5(TxD)<br />
pin4(RTS) - pin6(CTS)<br />
<br />
For KF M04 or later: Connect the following pins on CN4:<br />
pin2(TxD) - pin4(RxD)<br />
pin1(RTS) - pin3(CTS)<br />
<br />
For Yocto v2.23.1:<br />
$ stty -F /dev/ttySC2 -echo<br />
$ stty -F /dev/ttySC2<br />
speed 9600 baud; line = 0;<br />
-brkint -imaxbel<br />
-echo<br />
$ cat /dev/ttySC2 &<br />
$ echo 123435452345 > /dev/ttySC2<br />
123435452345<br />
<br />
For Yocto v3.x:<br />
$ stty -F /dev/ttySC3 -echo<br />
$ stty -F /dev/ttySC3<br />
speed 9600 baud; line = 0;<br />
-brkint -imaxbel<br />
-echo<br />
$ cat /dev/ttySC3 &<br />
$ echo 123435452345 > /dev/ttySC3<br />
123435452345<br />
<br />
===LVDS Camera===<br />
<GMSL><br />
Camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#GMSL02 GMSL02]<br />
Camera: IMI RDACM21-01<br />
or<br />
<FPD Link><br />
Camera board: [http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#FPDL01 FPDL01]<br />
Camera: IMI RDACM24-01<br />
<br />
*Note:<br />
H3 can use CN10 and CN11<br />
M3 can use CN10<br />
<br />
Ex1)<br><br />
$ killall weston<br />
$ capture -d /dev/video0 -F -f rgb32 -L 0 -T 0 -W 1280 -H 1080 -c 1000 -z<br />
<br />
Ex2)<br><br />
$ gst-launch-1.0 v4l2src device=/dev/video0 io-mode=dmabuf ! video/x-raw,format=BGRA,width=1280,height=1080,framerate=30/1 ! waylandsink<br />
<br />
===CMOS Camera===<br />
Ex)<br><br />
$ systemctl stop weston<br />
$ capture -d /dev/video0 -F -f rgb32 -L 0 -T 0 -W 1280 -H 720 -c 1000 -t 60 -z<br />
<br />
===Raspberry Pi camera Rev 1.3===<br />
Ex)<br><br />
$ systemctl stop weston <br />
$ capture -d /dev/video0 -o -f bggr8 -W 2592 -H 1944 -c 1 -t 30 > video.bggr <br />
[ 2475.196942] rcar_csi2 fea80000.csi2: Timeout of reading the PHY clock lane<br />
[ 2475.203851] rcar_csi2 fea80000.csi2: Timeout of reading the PHY data lane<br />
<br />
Ubuntu PC$ ./bayer2rgb -i video.bggr -o video.rgb24 -w 2592 -v 1944 -b 8 -f BGGR<br />
* https://github.com/jdthomas/bayer2rgb.git<br />
Ubuntu PC$ rawtoppm -rgb 2592 1944 video.rgb24 > video24.ppm<br />
Ubuntu PC$ display video24.ppm<br />
<br />
===Multichannel Audio===<br />
Ex1) CN12/32 on KF<br />
$ speaker-test -c 8 -t wav -W /usr/share/sounds/alsa/<br />
Ex2)<br />
<KF><br />
$ pactl set-default-sink pcm3168a_output<br />
$ speaker-test -c 8 -t wav -W /usr/share/sounds/alsa/<br />
<SK><br />
$ pactl set-default-sink ak4613_output <br />
$ amixer -c 1 sset "DVC Out" 10%<br />
$ speaker-test -c 2 -t wav -W /usr/share/sounds/alsa/<br />
Ex3)<br />
<KF><br />
$ paplay -d pcm3168a_output sample.wav<br />
<SK><br />
$ amixer -c 1 sset "DVC Out" 10%<br />
$ paplay -d ak4613_output sample.wav<br />
<br />
===MOST===<br />
Ex)<br><br />
1. Connect OS81092 board(Physical+ Interface Board OS81092) and CN22 of KF. <br><br />
2. Connect Audio board(OS81092 Audio Demo Board) and OS819092 board with exclusive cable. <br><br />
3. Connect Audio board and CN5 of SK with USB cable. <br><br />
4. Run the linux kernel <br><br />
5. cd /usr/share/most/ <br><br />
6. ./most_setup.sh<br />
<pre><br />
$./most_setup.sh <br />
--Setting up RX channel with MLB[ 217.636328] aim_sound: PCM format is 16-bit stereo<br />
addr 0x03 (0x06)--<br />
--S[ 217.642675] aim_sound: PCM format is 16-bit stereo<br />
etting up TX channel wit[ 217.649647] aim_sound: PCM format is 16-bit stereo<br />
h MLB addr 0x04 (0x08)--<br />
--Setting up TX channel with MLB addr 0x06 (0x0C)--<br />
--Creating char devices--<br />
--Creating ALSA devices--<br />
</pre><br />
7../setup-audio-50 &<br />
<pre><br />
$./setup-audio-50 &<br />
Configuration:<br />
Timing Slave (Audio Sink)<br />
! ET_NS_MSVAL_ERROR a MSVAL Error is reported from the NS: 0x0010 MSVAL_ERR_STARTUP_FAILED<br />
MSVAL_E_SHUTDOWN<br />
App reset<br />
MSVAL_E_SHUTDOWN<br />
App reset<br />
! ET_NS_MSVAL_ERROR a MSVAL Error is reported from the NS: 0x0011 MSVAL_ERR_STARTUP_BUSY<br />
! ET_NS_MSVAL_ERROR a MSVAL Error is reported from the NS: 0x0011 MSVAL_ERR_STARTUP_BUSY<br />
(snip)<br />
</pre><br />
8. Push the "Switch" button on the Audio board<br />
<pre><br />
-> MostAllowRemoteAccess(allow)<br />
-> SourceInfo.Status 1 (Inst_ID: 0x1, FB: 0x24, Adr: 0x400)<br />
-> SourceInfo.Status 2 (Inst_ID: 0x1, FB: 0x24, Adr: 0x400)<br />
-> Amplifier.Volume.Set 100<br />
</pre><br />
9. Push the "Switch" button on the Audio board again<br />
<pre><br />
<- FB_AuxIn_Allocate_StartResult Node: 0x01, Ifn: 0x02<br />
</pre><br />
10. Push the "Switch" button on the Audio board again<br />
<pre><br />
<- FB_AuxIn_Allocate_StartResult Node: 0x01, Ifn: 0x01<br />
</pre><br />
11. ./most_play.sh ${PATH}/hoge.mp3 5<br />
<pre><br />
$./most_play.sh /home/root/hoge.mp3 5<br />
Setting pipeline to PAUSED ...<br />
Pipeline is PREROLLING ...<br />
Redistribute latency...<br />
Pipeline is PREROLLED ...<br />
Setting pipeline to PLAYING ...<br />
New clock: GstAudioSinkClock<br />
</pre><br />
<br />
== Connection-confirmed Hardware information ==<br />
{| class="wikitable"<br />
! Connector No !! Function name !! Connection confirmed Hardware<br />
|-<br />
| CN7 || LVDS display || MITSUBISHI AA121TD01<br />
|-<br />
| CN10, CN11<br />
|| LVDS camera || IMI RDACM21(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><br />
|-<br />
| CN15 || Mini PCIe || Intel 512AN-MMW<br />
|-<br />
| CN48 || Raspberry Pi camera || Raspberry Pi camera Rev 1.3(OV5647)<br />
|-<br />
| CN49 || HDMI display || GeChic Onlap 1502x, 1503x<br />
|-<br />
| CN22 || MOST || "Physical+ Interface Board OS81092" and "OS81092 Audio Demo Board"<br />
|-<br />
| CN29 || CMOS camera || https://www.amazon.com/Arducam-Megapixels-OV5642-Sensor-Camera/dp/B013JO53AU<br />
|}<br />
<br />
== How to update of Sample Loader and MiniMonitor ==<br />
New version:<br />
<pre><br />
Sample Loader: V3.02<br />
MiniMonitor: V3.02<br />
</pre><br />
<br />
Down load:<br />
[[File:UpdateFile_v302.zip]]<br />
<br />
Why update?:<br />
<pre><br />
ComEx Mechanical Specification: Durability: 30 mating cycles.<br />
This new version(V3.02) can update the firmware(*) while keeping Starter Kit(SK) and Kingfisher(KF) connected.<br />
(*)firmware: bootparam_sa0.srec, bl2-h3ulcb/m3ulcb.srec, cert_header_sa6.srec, bl31-h3ulcb/m3ulcb.srec, tee-h3ulcb/m3ulcb.srec, u-boot-elf.srec <br />
</pre><br />
<br />
<br />
How to update:<br />
<ol><br />
<br />
<li> Power off the KF and remove SK from KF<br />
</li><br />
<pre><br />
Turn off SW5<br />
Remove SK from KF<br />
</pre><br />
<br />
<li> Set SW of SK as follows:<br />
</li><br />
<pre><br />
SW1:OFF<br />
SW6:OFF/OFF/OFF/OFF<br />
SW2:OFF/OFF/OFF/OFF<br />
</pre><br />
<br />
<li> Power on the SK (This means that you need to prepare a [https://elinux.org/R-Car/Boards/H3SK#Hardware_Features 5V AC-adapter] for SK)<br />
</li><br />
<pre><br />
Press SW8<br />
SCIF Download mode starts<br />
</pre><br />
<br />
<li> Send the following file from console(Ex: minicom):<br />
</li><br />
<pre><br />
type "ctrl+A S" and select upload method "ascii", then choose file for uploading the following file.<br />
Case of M3SK:<br />
BoardID_Writer_SCIF_64bit_ID=0x10(StarterKit-Pro_Rev1.0).mot<br />
Case of H3SK:<br />
BoardID_Writer_SCIF_64bit_ID=0x58(StarterKit-Premier_Rev1.0OB).mot<br />
</pre><br />
<br />
<pre><br />
NOTE: Under Linux, if you got problem transferring this file, it may because of special character in its name.<br />
<br />
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):<br />
# /usr/bin/ascii-xfr -dsv "BoardID_Writer_SCIF_64bit_ID=0x10(StarterKit-Pro_Rev1.0).mot" > /dev/ttyUSB0<br />
</pre><br />
<br />
You can confirm the following log (Ex: M3SK):<br />
<pre><br />
+---------------------------------+<br />
| Board ID Writer V01 2017.06.23 |<br />
+---------------------------------+<br />
Product Code : R-Car M3 ES1.0<br />
<br />
Now Board ID : Unknown Board Rev7 (0xFF)<br />
New Board ID : Starter Kit Rev0 (0x10)<br />
Wrote Board ID : Starter Kit Rev0 (0x10)<br />
<br />
Writer Program End.<br />
</pre><br />
<br />
<li> Power off the SK<br />
</li><br />
<pre><br />
Press SW8<br />
</pre><br />
<br />
<li> Set SW as follows:<br />
</li><br />
<pre><br />
M3SK = SW6:OFF/ON/OFF/OFF<br />
H3SK = SW6:OFF/OFF/OFF/OFF<br />
</pre><br />
<br />
<li> Power on the SK<br />
</li><br />
<pre><br />
Press SW8<br />
SCIF Download mode starts<br />
</pre><br />
<br />
<li> Send the following file from console:<br />
</li><br />
<pre><br />
type "ctrl+A S" and select upload method "ascii", then choose file for uploading the following file.<br />
Case of M3SK:<br />
AArch32_Gen3_H3_M3_Scif_MiniMon_V3.02.mot<br />
Case of H3SK:<br />
AArch64_Gen3_H3_M3_Scif_MiniMon_V3.02.mot<br />
</pre><br />
You can confirm the following log (Ex: M3SK):<br />
<pre><br />
R-Car Gen3 Scif Download MiniMonitor V3.02 2017.07.04<br />
Work Memory : SystemRAM<br />
Board Judge : Used Board-ID <-- Attention!!<br />
DDR_Init : boardcnf[3] Starter Kit (M3SIP)<br />
Board Name : Starter Kit Pro<br />
Product Code : R-Car M3 ES1.0<br />
<br />
><br />
</pre><br />
<br />
<li> 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:<br />
</li><br />
<pre><br />
xls<br />
1<br />
y<br />
y<br />
y<br />
1<br />
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<br />
</pre><br />
<br />
<li> Flash AArch64_Gen3_Spi_MiniMon_V3.02_E6330000.mot. In console execute xls command (load program to hyper flash) and provide the following inputs:<br />
</li><br />
<pre><br />
xls<br />
1<br />
y<br />
y<br />
y<br />
3<br />
e6330000<br />
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<br />
</pre><br />
<br />
<li> Power off the SK<br />
</li><br />
<pre><br />
Press SW8<br />
</pre><br />
<br />
<li> Verify Sample Loader and MiniMonitor version<br />
</li><br />
<pre><br />
SW1:OFF<br />
M3SK<br />
SW6[1]=OFF, SW6[2]=OFF, SW6[3]=OFF, SW6[4]=ON<br />
H3SK<br />
ws1.0: SW6[all]=OFF<br />
ws1.1/ws2.0: SW6[1]=ON, SW6[2]=ON, SW6[3]=OFF, SW6[4]=ON<br />
</pre><br />
<pre><br />
Press SW8<br />
</pre><br />
You can confirm the following log (Ex: H3SK):<br />
<pre><br />
R-Car Gen3 Sample Loader V3.02 2017.07.04 <-- !! V3.02 !!<br />
For Salvator , Kriek , and StarterKit.<br />
Board Judge : Used Board-ID<br />
DDR_Init : boardcnf[7] Salvator / Starter Kit (H3SIP_VER2.0)<br />
INITIAL SETTING : Starter Kit Premier / R-Car H3 ES2.0<br />
CPU : AArch64 CA57<br />
DRAM : LPDDR4 DDR3200<br />
DEVICE : QSPI Flash(S25FS128) at 40MHz DMA<br />
BOOT : Normal Boot<br />
BACKUP : DDR Cold Boot<br />
jump to 0xE6330000<br />
<br />
R-Car Gen3 MiniMonitor V3.02 2017.07.04 <-- !! V3.02 !!<br />
Work Memory : SystemRAM<br />
Board Name : Starter Kit Premier<br />
Product Code : R-Car H3 ES2.0<br />
<br />
><br />
</pre><br />
<br />
<li> Set SW(Kernel boot mode) as follows:<br />
</li><br />
<pre><br />
SW1:ON<br />
M3SK = SW6[all]:ON<br />
H3SK<br />
ws1.0 = SW6:OFF/OFF/OFF/ON<br />
ws1.1 = SW6:ON/OFF/ON/ON<br />
ws2.0 = SW6[all]:ON<br />
</pre><br />
<br />
<li> You can update the firmware with SK connected to KF.<br />
</li><br />
How to update:<br/><br />
http://elinux.org/R-Car/Boards/M3SK#Flashing_firmware<br/><br />
http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware<br/><br />
</ol><br />
<br />
== FAQ ==<br />
<ol><br />
<li>Failed to DRAM initialize (-1).<br/><br />
If you face the following error please update(*) IPL and u-boot to the latest versopm.<br />
<pre><br />
NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.12<br />
NOTICE: BL2: PRR is R-Car M3 ES1.0<br />
NOTICE: BL2: Boot device is HyperFlash(80MHz)<br />
NOTICE: BL2: LCM state is CM<br />
NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x52<br />
NOTICE: BL2: DDR3200(rev.0.20)[COLD_BOOT]..1<br />
NOTICE: BL2: Failed to DRAM initialize (-1).<br />
ERROR: <br />
ERROR: BL2: System WDT overflow, occured address is 0xe630d3cc<br />
</pre><br />
(*)How to update<br/><br />
http://elinux.org/R-Car/Boards/Kingfisher#How_to_update_of_Sample_Loader_and_MiniMonitor<br/><br />
http://elinux.org/R-Car/Boards/M3SK#Flashing_firmware<br/><br />
http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware<br/><br />
</li><br />
</ol><br />
<br />
== Known Issues ==<br />
<ol><br />
<li> USB3.0(CN2) cannot use with M3 SK.<br />
</li><br />
Refer to: http://elinux.org/R-Car/Boards/M3SK#Known_Issues<br />
<li> H/W limitations<br />
<pre><br />
- Board type name: "SBEV-RCAR-KF-M03"<br />
1. MOST is not supported.<br />
<br />
- Board type name: "SBEV-RCAR-KF-M03" and "SBEV-RCAR-KF-S03"<br />
1. BT-Audio(HFP)is not supported.<br />
<br />
- Board type name: "SBEV-RCAR-KF-M03", "SBEV-RCAR-KF-S03" and "SBEV-RCAR-KF-M04"<br />
1. Cannot use JTAG(CN3 on SK).<br />
</pre><br />
</li><br />
<li>Power supply <br><br />
SBEV-RCAR-KF-M03 and SBEV-RCAR-KF -S03 boards may not turn on even if you turn on SW6.<br><br />
In that case please turn on SW6 again.<br />
</li><br />
<li>(SW limitation)Raspberry Pi camera <br><br />
v2(Sony IMX219) camera does not support. (v1(ov5647)is supported)<br />
</li><br />
</ol></div>Khiem.renesashttps://elinux.org/index.php?title=Automated_Testing_Summit_2018&diff=467536Automated Testing Summit 20182018-04-13T02:21:02Z<p>Khiem.renesas: /* wanted attendees */</p>
<hr />
<div>This is a public planning page for the Automated Testing Summit<br />
<br />
= 2018 meeting =<br />
Coordinated by: Tim Bird<br />
<br />
Action items:<br />
* Determine attendees<br />
** create "wanted attendees" list<br />
** ask for interested parties<br />
* Determine venue<br />
** ask candidate attendees about which event, length, format works best for them<br />
<br />
* see who's interested in coming<br />
* send e-mail to find out which event, format, etc.<br />
<br />
= Venue (candidates) =<br />
* Plumbers 2018 - Vancouver, Canada - Nov 13-15<br />
* ELC Europe 2018 - Edinburgh, Scotland - Oct 22-24<br />
<br />
Note: For Plumbers, ATS would be a micro-conference during the event.<br />
For ELC Europe, ATS could be before, during or after the event.<br />
<br />
= Attendees =<br />
<br />
== wanted attendees ==<br />
* Pawel Wieczorek (Samsung) - SLAV<br />
* Kevin Hillman (BayLibre) - KernelCI, lab-in-a-box<br />
* Tom Gall (Linaro) - LKFT<br />
* [[User:Codehelp|Neil Willliams]] (Linaro) - LAVA<br />
* Jan Lübbe (Pengutronix) - Labgrid<br />
* Tim Bird (Sony) - Fuego, ttc<br />
* Andrew Murray (Witekio) - started this initiative<br />
* Daniel Sangorrin (Toshiba) - Fuego/CIP<br />
* [[User:Khiem.renesas|Khiem Nguyen]] (Renesas) - LTSI testing<br />
* more people from industry<br />
** (comcast? - ask Khem for contact (done))<br />
<br />
== possible invitees ==<br />
* Yannick Brosseau (Facebook) -<br />
* Dmitry Vyokov (Google) - KASAN, syskaller testing<br />
* Kenji Tadano (Mitsubishi)<br />
* Kengo Ibe (Mitsubishi)<br />
* Shuah Khan (Samsung) - kselftest<br />
* Cyril Hrubis (?) - LTP<br />
* someone from yocto? (who?)<br />
* someone from buildroot? (Thomas Petazzoni?) (is the buildroot community interested in this?)<br />
* someone from U-Boot? (Tom Rini/Stephen Warren/Simon Glass)?<br />
<br />
== interested in attending ==<br />
Please add your preferred co-located conference (ELCE, Plumbers, or something else), if you have one.<br />
<br />
* Geert Uytterhoeven - general board farm (ELCE or FOSDEM)<br />
* Kieran Bingham - general board farm<br />
* Jan-Simon Möller - general board farm, especially LAVA & KernelCI<br />
* Marco Cavallini (Koan) - general board farm<br />
* Chris Fiege (Pengutronix) - board farm hardware, special development tools (USB-SD-Mux, ...)<br />
* Michal Simek (Xilinx) - general board farm<br />
* Punnaiah Choudary Kalluri (Xilinx) - general board farm<br />
* [[User:Codehelp|Neil Willliams]] (Linaro) - LAVA<br />
* Tim Bird (Sony) - Fuego, ttc (either ELCE or Plumbers is OK)<br />
* Carlos Hernandez (Texas Instruments) - manages board farm at TI<br />
* Otavio Salvador (O.S. Systems) - (prefers ELCE)<br />
* Jan Lübbe (Pengutronix) - labgrid (prefers just after ELCE)<br />
* Milosz Wasilewski (Linaro) - LKFT (ELCE or FOSDEM are fine) - can cover LKFT if Tom can't make it<br />
* Muhammad Shafique (Mentor) - general board farm, LAVA & KernelCI<br />
* Mirza Krak (Endian Technologies AB) - (ELCE or FOSDEM)<br />
* Tim Orling (Yocto Project) - (ELCE, possibly Plumbers)<br />
* Matt Hart (Linaro) - board farm, PDUDaemon, LAVA and KernelCI<br />
* Rouven Czerwinski (Pengutronix) - labgrid (prefers just after ELCE)<br />
* Mark Brown (Linaro) - Board farm stuff, kernelci, consuming results<br />
* Alan Bennett (Open Source Foundries) - (prefers ELCE)<br />
* Tyler Baker (Open Source Foundries)<br />
* Manuel Traut (Linuxtronix) - r4d, jenkins, ci-rt<br />
* Anna-Maria Gleixner (Linuxtronix) - r4d<br />
* Zhenfeng Zhao (Wind River) - (either ELCE or Plumbers is fine)<br />
* Shuah Khan (Samsung) - kselftest (Linaro connect?)<br />
<br />
= Agenda (brainstorming) =<br />
Here is some brainstorming on an agenda...<br />
<br />
* board farm survey (lightning talks)<br />
** what are people using?<br />
** what works?<br />
** what's missing?<br />
*** board discovery/lab introspection?<br />
* layers and interfaces<br />
** what layers are supported, needed?<br />
** any way to leverage/separate/isolate existing software?<br />
* what tests need to be supported?<br />
** boot-time<br />
** run-time<br />
** package-based (package unit tests)<br />
** driver (hardware specific?)<br />
*** requiring specialized hardware external to board (e.g. canbus simulator, hdmi frame-grabber)<br />
** multinode<br />
*** how to allocate/schedule multiple pieces of equipment for a test (e.g. 2 or more nodes for a network test)<br />
* results reporting<br />
** centralized server and API to it (kernelCI json?)<br />
* sharing tests<br />
* how to define standards<br />
** de-facto only? (dominant project? (cough, LAVA))<br />
** documents?<br />
* survey of existing projects, and what pieces they focus on (or don't)</div>Khiem.renesas