R-Car/Boards/Yocto

From eLinux.org
< R-Car
Revision as of 19:31, 2 September 2018 by Ygohda (talk | contribs) (Preliminary steps)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This page contains information on building and running Yocto on Renesas R-Car E2 SILK, Renesas R-Car M2 Porter and Renesas R-Car H2 Stout boards.

Yocto versions

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

Preliminary steps

  1. Download evaluation version of proprietary graphics and multimedia drivers from Renesas.

    To download Multimedia and Graphics library, please use the following link:
    https://www.renesas.com/en-eu/software/D3017410.html
    To download related Linux drivers, please use the following link:
    https://www.renesas.com/img/solutions/automotive/rcar-demoboard/R-Car_Series_Evaluation_Software_Package_of_Linux_Drivers-201512281.zip

    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
    
    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 SILK, Porter and Stout

  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.
    export WORK=<path-to-your-build-directory>
    mkdir $WORK
    cd $WORK
    
  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 yocto-1.6.1
    cd $WORK/meta-openembedded
    git checkout -b tmp dca466c074c9a35bc0133e7e0d65cca0731e2acf
    cd $WORK/meta-linaro
    git checkout -b tmp 8a0601723c06fdb75e62aa0f0cf15fc9d7d90167
    

    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.git
    cd meta-renesas
    git checkout -b tmp origin/v1.10.0
    
  5. Unzip downloaded proprietary driver modules to $WORK/proprietary folder.
    You should see the following files:
    [builduser@builduser meta-renesas-lcb]$ ls -lh $WORK/proprietary
    total 8.1M
    -rw-r--r-- 1 builduser builduser 5.8M Dec 28 17:21 R-Car_Series_Evaluation_Software_Package_for_Linux-20160920.tar.gz
    -rw-r--r-- 1 builduser builduser 2.3M Dec 28 17:21 R-Car_Series_Evaluation_Software_Package_of_Linux_Drivers-20151228.tar.gz
    
  6. Populate meta-renesas with graphics drivers.
    cd $WORK/meta-renesas/meta-rcar-gen2
    ./copy_gfx_software_<board>.sh ../../proprietary
    
  7. Populate meta-renesas with multimedia drivers.
    cd $WORK/meta-renesas/meta-rcar-gen2
    ./copy_mm_software_lcb.sh ../../proprietary
    
  8. Setup build environment
    cd $WORK
    source poky/oe-init-build-env
    
  9. Prepare default configuration files.
    cd $WORK/meta-renesas/meta-rcar-gen2/templates/<board>
    cp bblayers.conf $WORK/build/conf/bblayers.conf
    

    For weston/wayland:

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

    For X11:

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

    1. Edit local.conf to select version of OpenGL ES:
      OPENGLES3 = “0” (use “1” for OpenGL ES3.0, or “0” for OpenGL ES2.0)
      
    2. Edit local.conf to select IO configuration (by default only stout cpu board peripherals are enabled):
      MACHINE_FEATURES_append = " stout-full" (use this append for full IO configuration)
      

      or

      MACHINE_FEATURES_append = " stout-view" (use this append for view IO configuration)
      

      or

      MACHINE_FEATURES_append = " stout-had" (use this append for HAD IO configuration)
      
  12. Start the build
    For weston/wayland:
    bitbake core-image-weston
    

    For X11:

    bitbake core-image-x11
    
  13. 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.

  14. Bitbake has generated all the necessary files in ./tmp/deploy/images directory.
    You can verify its content:
    [builduser]$ ls -lh `find ./tmp/deploy/images/silk/ -maxdepth 1 -type l -print`
    lrwxrwxrwx. 1 builduser builduser 50 Dec  9 02:47 ./tmp/deploy/images/silk/core-image-x11-silk.manifest -> core-image-x11-silk-20141208223655.builduserfs.manifest
    lrwxrwxrwx. 1 builduser builduser 49 Dec  9 02:47 ./tmp/deploy/images/silk/core-image-x11-silk.tar.bz2 -> core-image-x11-silk-20141208223655.builduserfs.tar.bz2
    lrwxrwxrwx. 1 builduser builduser 84 Dec  9 02:43 ./tmp/deploy/images/silk/modules-silk.tgz -> modules--3.10+git2eba9c2b1f02bec3295b27f8415575da00d5ffce-r0-silk-20141208223655.tgz
    lrwxrwxrwx. 1 builduser builduser 52 Dec  9 02:46 ./tmp/deploy/images/silk/u-boot.bin -> u-boot-silk-v2013.01.01+gitAUTOINC+74b16badc2-r0.bin
    lrwxrwxrwx. 1 builduser builduser 52 Dec  9 02:46 ./tmp/deploy/images/silk/u-boot-silk.bin -> u-boot-silk-v2013.01.01+gitAUTOINC+74b16badc2-r0.bin
    lrwxrwxrwx. 1 builduser builduser 83 Dec  9 02:43 ./tmp/deploy/images/silk/uImage -> uImage--3.10+git2eba9c2b1f02bec3295b27f8415575da00d5ffce-r0-silk-20141208223655.bin
    lrwxrwxrwx. 1 builduser builduser 83 Dec  9 02:43 ./tmp/deploy/images/silk/uImage+dtb -> uImage+dtb--3.10+git2eba9c2b1f02bec3295b27f8415575da00d5ffce-r0-silk-20141208223655
    lrwxrwxrwx. 1 builduser builduser 91 Dec  9 02:43 ./tmp/deploy/images/silk/uImage-r8a7794-silk.dtb -> uImage--3.10+git2eba9c2b1f02bec3295b27f8415575da00d5ffce-r0-r8a7794-silk-20141208223655.dtb
    lrwxrwxrwx. 1 builduser builduser 83 Dec  9 02:43 ./tmp/deploy/images/silk/uImage-silk.bin -> uImage--3.10+git2eba9c2b1f02bec3295b27f8415575da00d5ffce-r0-silk-20141208223655.bin
    lrwxrwxrwx. 1 builduser builduser 79 Dec  9 02:43 ./tmp/deploy/images/silk/zImage -> zImage--3.10+git2eba9c2b1f02bec3295b27f8415575da00d5ffce-r0-silk-20141208223655
    lrwxrwxrwx. 1 builduser builduser 83 Dec  9 02:43 ./tmp/deploy/images/silk/zImage+dtb -> zImage+dtb--3.10+git2eba9c2b1f02bec3295b27f8415575da00d5ffce-r0-silk-20141208223655
    

    modules-silk.tgz is compressed Kernel image, core-image-x11-silk.tar.bz2 is the rootfs, modules-silk.tgz are kernel modules.

  15. You can now boot R-Car E2 SILK board over TFTP and NFS

Running Yocto image

Linux kernel can be booted from microSD card or from TFTP. Root FS can be mounted from micro SD card or via NFS.

Loading kernel via TFTP and rootfs via NFS

Follow these steps to setup working TFTP and NFS server:

  1. Setup a TFTP server.

    Ubuntu

    Install tftpd-hpa package along with tftp tools:

    sudo apt-get install tftp tftpd-hpa
    

    Fedora

    1. Install necessary packages:
      sudo yum install tftp-server tftp
      

      tftp-server is a part of xinetd. See Fedora manual for more information.

    2. Enable TFTP server:
      sudo vi /etc/xinetd.d/tftp 
      
      Set
      disable = no
      Save file and exit.
    3. Start xinetd:
      sudo systemctl start xinetd.service
      sudo systemctl enable xinetd.service
      
  2. Copy uImage and uImage-r8a7794-silk.dtb from $WORK/build/tmp/deploy/images/silk/ to TFTP server root.

    Ubuntu

    cp $WORK/build/tmp/deploy/images/silk/uImage /srv/tftp/
    cp $WORK/build/tmp/deploy/images/silk/uImage-r8a7794-silk.dtb /srv/tftp/
    

    Fedora

    cp $WORK/build/tmp/deploy/images/silk/uImage /var/lib/tftpboot/
    cp $WORK/build/tmp/deploy/images/silk/uImage-r8a7794-silk.dtb /var/lib/tftpboot/
    
  3. Verify that TFTP server is working.
    tftp localhost -c get uImage && ls uImage
    
  4. Setup NFS server.

    Debian/Ubuntu

    1. Install necessary packages:
      sudo apt-get install nfs-kernel-server nfs-common
      
    2. Start NFS server:
      sudo /etc/init.d/nfs-kernel-server start
      

    Fedora

    1. Install necessary packages:
      sudo yum install nfs-utils
      
    2. Enable and start nfs server:
      sudo systemctl enable rpcbind.service 
      sudo systemctl enable nfs-server.service 
      sudo systemctl enable nfs-lock.service 
      sudo systemctl enable nfs-idmap.service
      sudo systemctl start rpcbind.service 
      sudo systemctl start nfs-server.service 
      sudo systemctl start nfs-lock.service 
      sudo systemctl start nfs-idmap.service
      
  5. Export root FS to NFS. (Change IMAGE and MACHINE to fit your build).
    1. Unpack rootfs to a dedicated directory:
      IMAGE=weston|x11|sato|directfb
      MACHINE=silk|porter
      NFS_ROOT=/nfs/${MACHINE}
      sudo mkdir -p "${NFS_ROOT}"
      sudo rm -rf "${NFS_ROOT}"/*
      sudo tar -xjf "${WORK}/build/tmp/deploy/images/${MACHINE}/core-image-${IMAGE}-${MACHINE}.tar.bz2" -C "${NFS_ROOT}"
      sync
      
    2. Edit /etc/exports:
      sudo vi /etc/exports
      

      add

      /nfs/silk	*(rw,no_subtree_check,sync,no_root_squash,no_all_squash)
      /nfs/porter	*(rw,no_subtree_check,sync,no_root_squash,no_all_squash)
      

      Save the file and exit.

    3. Force NFS server to re-read /etc/exports
      sudo exportfs -a
  6. Verify that NFS is working.
    [builduser@buildmachine ~]$ showmount -e localhost
    Export list for localhost:
    /nfs/silk *
    /nfs/porter *
    
  7. Boot into U-Boot command prompt
    For SILK board
    1. Make sure SW9 is on pin 1 side.
      Switch pin layout
    2. Connect to serial console over microUSB using minicom or picocom.
    3. Switch the board on or reset it. Press any key to stop U-Boot automatic countdown.

    Refer to SILK board page for more information.

    For Porter board
    1. TBD

    NOTE: Stout board does not have extra switches to select boot device (e.g. primary and secondary/backup QSPI Flash)

  8. Configure Ethernet, TFTP, and kernel command line in U-Boot:
    setenv ipaddr <board-ip>
    setenv serverip <your-computer-ip>
    setenv bootcmd 'tftp 0x40007fc0 uImage; tftp 0x40f00000 uImage-r8a7794-silk.dtb; bootm 0x40007fc0 - 0x40f00000'
    setenv bootargs 'console=ttySC10,38400 ignore_loglevel rw root=/dev/nfs nfsroot=<your-computer-ip>:<nfs-path>,nfsvers=3 ip=<board-ip>:<your-computer-ip>::255.255.255.0:silk vmalloc=384M'
    saveenv
    

    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.
    For example:

    setenv ipaddr 192.168.1.3
    setenv serverip 192.168.1.2
    setenv bootcmd 'tftp 0x40007fc0 uImage; tftp 0x40f00000 uImage-r8a7794-silk.dtb; bootm 0x40007fc0 - 0x40f00000'
    setenv bootargs 'console=ttySC10,38400 ignore_loglevel rw root=/dev/nfs nfsroot=192.168.1.2:/nfs/silk,nfsvers=3 ip=192.168.1.3:192.168.1.2::255.255.255.0:silk vmalloc=384M'
    saveenv
    

    The last command writes the configuration to SPI flash.

    => saveenv                                                                                                                                  
    Saving Environment to SPI Flash...                                                                                                          
    SF: Detected S25FL512S with page size 256 KiB, total 64 MiB                                                                                 
    Erasing SPI flash...Writing to SPI flash...done 
    

    You can also use

    dhcp
    

    command to obtain information from DHCP server.
    Note: You can always see the environment with printenv command. Refer to U-Boot manual for details.

  9. Verify the connection over Ethernet from U-Boot:
    ping <your-computer-ip>
    

    You should see:

    => ping 192.168.1.2                                                                                                                
    sh_eth Waiting for PHY auto negotiation to complete... done
    sh_eth: 100Base/Full
    Using sh_eth device
    host 192.168.1.2 is alive
    
  10. Reset the board by pushing SW5 "Reset".
  11. The board should boot the kernel:
    SILK SPI_LOADER V0.07c 2014.10.20                                                                                                           
    DEVICE S25FL512                                                                                                                             
                                                                                                                                                
                                                                                                                                                
    U-Boot 2013.01.01-g74b16ba-dirty (Dec 23 2014 - 15:31:50)                                                                                   
                                                                                                                                                
    CPU: Renesas Electronics R8A7794 rev 1.0                                                                                                    
    Board: Silk Board                                                                                                                           
                                                                                                                                                
    DRAM:  1 GiB                                                                                                                                
    MMC:   sh_mmcif: 0, sh-sdhi: 1                                                                                                              
    SF: Detected S25FL512S with page size 256 KiB, total 64 MiB                                                                                 
    In:    serial                                                                                                                               
    Out:   serial                                                                                                                               
    Err:   serial                                                                                                                               
    Net:   sh_eth                                                                                                                               
    Hit any key to stop autoboot:  0                                                                                                            
    sh_eth Waiting for PHY auto negotiation to complete... done                                                                                 
    sh_eth: 100Base/Full                                                                                                                        
    Using sh_eth device                                                                                                                         
    TFTP from server 192.168.1.2; our IP address is 192.168.1.3                                                                             
    Filename 'uImage'.                                                                                                                          
    Load address: 0x40007fc0                                                                                                                    
    Loading: #################################################################                                                                  
             #################################################################                                                                  
             #################################################################                                                                  
             ##############################################                                                                                     
             3.5 MiB/s                                                                                                                          
    done                                                                                                                                        
    Bytes transferred = 3525472 (35cb60 hex)                                                                                                    
    sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth                                                                                    
    sh_eth Waiting for PHY auto negotiation to complete... done                                                                                 
    sh_eth: 100Base/Full                                                                                                                        
    Using sh_eth device                                                                                                                         
    TFTP from server 192.168.1.2; our IP address is 192.168.1.3                                                                             
    Filename 'uImage-r8a7794-silk.dtb'.                                                                                                         
    Load address: 0x40f00000                                                                                                                    
    Loading: ##                                                                                                                                 
             3 MiB/s                                                                                                                            
    done                                                                                                                                        
    Bytes transferred = 24859 (611b hex)                                                                                                        
    ## Booting kernel from Legacy Image at 40007fc0 ...                                                                                         
       Image Name:   Linux-3.10.31-ltsi                                                                                                         
       Image Type:   ARM Linux Kernel Image (uncompressed)                                                                                      
       Data Size:    3525408 Bytes = 3.4 MiB                                                                                                    
       Load Address: 40008000                                                                                                                   
       Entry Point:  40008000                                                                                                                   
       Verifying Checksum ... OK                                                                                                                
    ## Flattened Device Tree blob at 40f00000                                                                                                   
       Booting using the fdt blob at 0x40f00000                                                                                                 
       XIP Kernel Image ... OK                                                                                                                  
    OK                                                                                                                                          
       Loading Device Tree to 40ef6000, end 40eff11a ... OK                                                                                     
                                                                                                                                                
    Starting kernel ...                                                                                                                         
    

Loading kernel and rootfs from microSD card

Both kernel and root FS can be loaded from a microSD card. The approach requires only a console cable. No Ethernet connection is needed.

  1. Find a reliable microSD card with an adapter to fit your computer. 4 GB should be enough for the task.
  2. Plug the SD card into you computer. Locate the proper device for it, typically /dev/mmcblk0. Use
    dmesg | tail
    

    to print latest messages if in doubt.
    WARNING! Be very careful. Do not select you root partition or any other device with important information. It may be destroyed!
    Double-check that device name is correct by mounting and examining it's content.

  3. Make sure the SD card doesn't contain any important files.
    WARNING! Next step may erase the SD card completely. All files my be lost.
  4. Format the card with one partition with EXT3 file system.
    TBD Update this page with a script which formats the card
  5. Copy root fs to the sd card:
    SD=<path-to-your-device-partition>
    SD_ROOT=/tmp/sd-tool
    sudo umount "${SD}"
    sudo mkdir -p "${SD_ROOT}"
    sudo mount "${SD}" "${SD_ROOT}"
    sudo rm -rf "${SD_ROOT}"/*
    sudo cp "${BUILDDIR}/tmp/deploy/images/${MACHINE}/uImage+dtb" "${SD_ROOT}/boot/"
    sudo tar -xjf "${BUILDDIR}/tmp/deploy/images/${MACHINE}/core-image-${IMAGE}-${MACHINE}.tar.bz2" -C "${SD_ROOT}"
    sudo umount "${SD}"
    
  6. Insert the SD card into microSD slot on the board.
  7. Boot the board into U-Boot command prompt. Refer to section Boot into U-Boot command prompt
  8. Configure kernel command line in U-Boot:
    (For Silk board)
    setenv bootcmd 'ext4load mmc 1:1 0x40007fc0 /boot/uImage+dtb; bootm 0x40007fc0'
    setenv bootargs 'console=ttySC10,38400 ignore_loglevel rw rootfstype=ext3 root=/dev/mmcblk0p1 rootwait vmalloc=384M'
    saveenv
    

    (For Porter board)

    setenv bootcmd 'ext4load mmc 1:1 0x40007fc0 /boot/uImage+dtb; bootm 0x40007fc0'
    setenv bootargs 'console=ttySC6,38400 ignore_loglevel rw rootfstype=ext3 root=/dev/mmcblk0p1 rootwait vmalloc=384M'
    saveenv
    

    (For Stout board)

    setenv bootcmd 'ext4load mmc 0:1 0x40007fc0 /boot/uImage+dtb; bootm 0x40007fc0'
    setenv bootargs 'console=ttySC0,38400 ignore_loglevel rw rootfstype=ext3 root=/dev/mmcblk0p1 rootwait vmalloc=384M video=HDMI-A-1:1024x768-32@60'
    saveenv
    

    The last command writes the configuration to SPI flash.

    => saveenv                                                                                                                                  
    Saving Environment to SPI Flash...                                                                                                          
    SF: Detected S25FL512S with page size 256 KiB, total 64 MiB                                                                                 
    Erasing SPI flash...Writing to SPI flash...done 
    
  9. Reset the board by pushing SW5 "Reset" on SILK, SWTBD "Reset" on Porter or SW2 "Reset" on Stout
  10. The board should boot the kernel:
    SILK SPI_LOADER V0.07c 2014.10.20                                                                                                           
    DEVICE S25FL512                                                                                                                             
                                                                                                                                                
                                                                                                                                                
    U-Boot 2013.01.01-g74b16ba-dirty (Dec 23 2014 - 15:31:50)                                                                                   
                                                                                                                                                
    CPU: Renesas Electronics R8A7794 rev 1.0                                                                                                    
    Board: Silk Board                                                                                                                           
                                                                                                                                                
    DRAM:  1 GiB                                                                                                                                
    MMC:   sh_mmcif: 0, sh-sdhi: 1                                                                                                              
    SF: Detected S25FL512S with page size 256 KiB, total 64 MiB                                                                                 
    In:    serial                                                                                                                               
    Out:   serial                                                                                                                               
    Err:   serial                                                                                                                               
    Net:   sh_eth                                                                                                                               
    Hit any key to stop autoboot:  0                                                                                                            
    3534603 bytes read in 498 ms (6.8 MiB/s)                                                                                                    
    ## Booting kernel from Legacy Image at 40007fc0 ...                                                                                         
       Image Name:   'Linux-3.10.31-ltsi'                                                                                                       
       Image Type:   ARM Linux Kernel Image (uncompressed)                                                                                      
       Data Size:    3534539 Bytes = 3.4 MiB                                                                                                    
       Load Address: 40008000                                                                                                                   
       Entry Point:  40008000                                                                                                                   
       Verifying Checksum ... OK                                                                                                                
       XIP Kernel Image ... OK                                                                                                                  
    OK                                                                                                                                          
                                                                                                                                                
    Starting kernel ...      
    

Multiboot

U-Boot allows multiboot configurations. U-Boot can try different boot commands one by one until find the first working command. Use command line interface to configure u-boot. Dual source (MMC and NFS) boot configuration for Silk:

setenv mkBootcmdMMC 'setenv bootcmd ext4load mmc 1:1 0x40007fc0 /boot/uImage+dtb\; bootm 0x40007fc0'
setenv mkBootargsMMC 'setenv bootargs console=ttySC10,38400 ignore_loglevel rw rootfstype=ext3 root=/dev/mmcblk0p1 rootwait vmalloc=384M'
setenv mkBootcmdTFTP 'setenv bootcmd tftp 0x40007fc0 uImage+dtb.silk\; bootm 0x40007fc0'
setenv mkBootargsNFS 'setenv bootargs console=ttySC10,38400 ignore_loglevel rw root=/dev/nfs nfsroot=192.168.1.27:/nfs/silk,nfsvers=3 ip=192.168.1.107:192.168.1.27::255.255.255.0:silk vmalloc=384M'
setenv bootMMC 'run mkBootargsMMC; run mkBootcmdMMC; run bootcmd' 
setenv bootNET 'run mkBootargsNFS; run mkBootcmdTFTP; run bootcmd'
setenv bootcmd 'run bootMMC; run bootNET'

For Porter and Stout mkBootcmdMMC, mkBootargsMMC, mkBootcmdTFTP and mkBootargsNFS should be correctly changed according to their bootcmds and bootargs

Adding Qt5 in Yocto image

  1. Clone meta-qt5 layer and switch to proper commit:
    cd $WORK
    git clone git://github.com/CogentEmbedded/meta-qt5.git
    cd meta-qt5
    git checkout 9b3e5474882a782589bd9842459e6945a7c0a588
    
  2. Include necessary for Qt5 layers (meta-qt5, meta-openembedded/meta-ruby) in your $WORK/build/conf/bblayers.conf, then BBLAYERS must look like this:
    BBLAYERS ?= " \
      ${TOPDIR}/../poky/meta \
      ${TOPDIR}/../poky/meta-yocto \
      ${TOPDIR}/../poky/meta-yocto-bsp \
      ${TOPDIR}/../meta-renesas/meta-rcar-gen2 \
      ${TOPDIR}/../meta-renesas \
      ${TOPDIR}/../meta-openembedded/meta-oe \
      ${TOPDIR}/../meta-openembedded/meta-multimedia \
      ${TOPDIR}/../meta-linaro/meta-linaro-toolchain \
      ${TOPDIR}/../meta-qt5 \
      ${TOPDIR}/../meta-openembedded/meta-ruby \
      "
    
  3. Add following packages in $WORK/build/conf/local.conf:
    IMAGE_INSTALL_append = " \
        qtbase \
        qtbase-fonts \
        qtbase-plugins \ 
        qtdeclarative \
        qtdeclarative-qmlplugins \
        qtdeclarative-plugins \
        qtquick1 \
        qtquick1-qmlplugins \ 
        qtquick1-plugins \
        qtwayland \
        qtwayland-plugins \
        qtbase-examples \ 
    "
    

    Note that your project may require additional packages, see meta-qt5/recipes-qt for available packages.

  4. After successful build you must be able to run Qt5 examples on target:
    export LD_PRELOAD=/usr/lib/libEGL.so
    export XDG_RUNTIME_DIR=/run/user/root
    export QT_QPA_PLATFORM=wayland-egl
    
    /usr/share/qt5/examples/opengl/cube/cube
    

Customizing Yocto image with additional packages from current setup

  1. If you wish to add some package, but you don't know how it exactly named, this command will be helpful:
    # Check if certain package is present on current Yocto Setup
    bitbake -s | grep <pkg>
    # Example for boost package
    bitbake -s | grep boost
    boost                                              :1.55.0-r0                          
    boost-native                                       :1.55.0-r0      
    

    Note that *-native packages are build for usage on your host machine (for SDK or other packages build)

  2. After that, if this package exists, add desired package name to IMAGE_INSTALL variable in your $WORK/build/conf/local.conf:
    # Example for boost package
    IMAGE_INSTALL_append = " boost "
    

Known issues and limitations

TBD