R-Car/Boards/Yocto-Gen3

From eLinux.org
< R-Car
Revision as of 14:55, 8 June 2016 by Cogente (talk | contribs) (edit3)
Jump to: navigation, search

This page contains information on building and running Yocto on Renesas R-Car H3 Salvator-X, Renesas R-Car H3 Salvator-X.View, Renesas R-Car H3 H3ULCB, Renesas R-Car H3 H3ULCB.View and Renesas R-Car H3 H3ULCB.HAD boards.

Yocto versions

Poky-2.0.1 is supported. Specific commit of meta-openembedded is required.

Preliminary steps

  1. Download proprietary graphics and multimedia drivers from Renesas. Evaluation version is available at http://www.renesas.com/secret/r_car_download/rcar_demoboard.jsp
    Graphic drivers are required for X11 and Wayland. Multimedia drivers are optional.

  2. Install required packages
    Ubuntu and Debian
    sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
         build-essential chrpath socat libsdl1.2-dev xterm python-crypto
    
    Fedora
    sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \
         diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath \
         ccache perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue socat \
         SDL-devel xterm
    

    Refer to Yocto Project Quick Start for more information.

Building the BSP for Renesas R-Car Salvator-X, Salvator-X.View, H3ULCB, H3ULCB.View and H3ULCB.HAD

  1. Create a directory and switch to it
    Warning! Yocto builds require a lot of disk space (up to 100 GB). Make sure you have got enough before starting the build.
    mkdir build
    cd build
    export WORK=`pwd`
    
  2. Clone basic Yocto layers:
    cd $WORK
    git clone git://git.yoctoproject.org/poky
    git clone git://git.openembedded.org/meta-openembedded
    git clone git://git.linaro.org/openembedded/meta-linaro.git
    
  3. Switch to proper branches/commits
    cd $WORK/poky
    git checkout -b tmp 65306b0bfc1afd0de9b1d470fd78c8c69f55f791
    cd $WORK/meta-openembedded
    git checkout -b tmp cb7e68f2a39fa6f24add48fc7b8d38fb7291bb44
    cd $WORK/meta-linaro
    git checkout -b tmp acf4f1f701e07670ec88435897a74f88dbe8ba87
    
    

    Another versions are not tested for compatibility.

  4. Clone Renesas BSP layer and switch to the proper branch:
    cd $WORK
    git clone git://github.com/CogentEmbedded/meta-renesas-gen3.git meta-renesas
    
  5. Apply Linaro-GCC patch file:
    cd $WORK/meta-renesas
    export PATCH_DIR=meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc
    patch -p1 < ${PATCH_DIR}/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch
    unset PATCH_DIR
    
  6. Download proprietary driver modules from http://www.renesas.com/secret/r_car_download/rcar_demoboard.jsp and unzip them to $WORK/proprietary folder.
    You should see the following files:
    $ ls -1 $WORK/proprietary
    R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160526.tar.gz
    R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20160526.tar.gz
    
  7. Populate meta-renesas with proprietary software packages.
    PKGS_DIR=$WORK/proprietary
    cd $WORK/meta-renesas
    sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
    
  8. Setup build environment
    cd $WORK
    source poky/oe-init-build-env
    
  9. Prepare default configuration files.
    cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/<salvator-x|h3ulcb>/linaro-gcc/mmp/*.conf ./conf/
    

    For weston/wayland:

    cd $WORK/build
    cp conf/local-wayland.conf conf/local.conf
    

    For X11:

    cd $WORK/build
    cp conf/local-x11.conf conf/local.conf
    
  10. Edit $WORK/build/conf/local.conf to enable/disable graphics and multimedia proprietary drivers support
  11. For H3ULCB board only:

    1. Edit local.conf to select IO configuration (by default only H3ULCB board peripherals are enabled):
      MACHINE_FEATURES_append = " h3ulcb-view" (use this append for View IO configuration)
      

      or

      MACHINE_FEATURES_append = " h3ulcb-had" (use this append for HAD IO configuration)
      

    For Salvator-X board only:

    1. Edit local.conf to select IO configuration (by default only Salvator-X board peripherals are enabled):
      MACHINE_FEATURES_append = " salvator-x-view" (use this append for View IO configuration)
      
  12. Edit local.conf to build only lib64, since evaluation packages do not include lib32 support:
    IMAGE_INSTALL_remove += " lib32-weston lib32-packagegroup-multimedia-libs lib32-omx-user-module lib32-libdrm lib32-libdrm-kms lib32-gles-user-module"
    
  13. Start the build
    For weston/wayland:
    bitbake core-image-weston
    

    For X11:

    bitbake core-image-x11
    
  14. Building image can take upto a few hours depending on your host system performance.
    After the build has been completed successfuly, you should see the output similar to:
    NOTE: Tasks Summary: Attempted 4704 tasks of which 31 didn't need to be rerun and all succeeded.
    

    and the command prompt should return.

  15. Bitbake has generated all the necessary files in ./tmp/deploy/images directory.
    You can verify its content:
    $ ls -1 `find ./tmp/deploy/images/h3ulcb/ -maxdepth 1 -type l -print`
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.cpio.gz
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.ext4
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.manifest
    ./tmp/deploy/images/h3ulcb/core-image-weston-h3ulcb.tar.bz2
    ./tmp/deploy/images/h3ulcb/Image
    ./tmp/deploy/images/h3ulcb/Image-h3ulcb.bin
    ./tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb.dtb
    ./tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb-had.dtb
    ./tmp/deploy/images/h3ulcb/Image-r8a7795-h3ulcb-view.dtb
    ./tmp/deploy/images/h3ulcb/modules-h3ulcb.tgz
    ./tmp/deploy/images/h3ulcb/u-boot.bin
    ./tmp/deploy/images/h3ulcb/u-boot-elf-h3ulcb.srec
    ./tmp/deploy/images/h3ulcb/u-boot-elf.srec
    ./tmp/deploy/images/h3ulcb/u-boot-h3ulcb.bin
    

    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.

  16. You can now boot R-Car H3 H3ULCB board over TFTP and NFS

Known issues and limitations

TBD