Skip to end of metadata
Go to start of metadata

Host Setup

Refer to the link for host setup details: Host Setup

Build Setup

build setup
repo init -u https://code.rdkcentral.com/r/manifests -b dunfell -m rdkv-nosrc.xml
repo sync -j `nproc` --no-clone-bundle --no-tags

Image Build

    image build
    MACHINE=raspberrypi-rdk-mc source meta-cmf-raspberrypi/setup-environment
    bitbake rdk-generic-mediaclient-wpe-image
    image build
    MACHINE=raspberrypi-rdk-hybrid source meta-cmf-raspberrypi/setup-environment
    bitbake rdk-generic-hybrid-wpe-image
    image build
    MACHINE=raspberrypirdkhybrefapp source meta-cmf-raspberrypi/setup-environment
    bitbake rdk-generic-hybrid-refapp-image

    The generated image resides under the directory build-<MACHINE>/tmp/deploy/images/<MACHINE> of the Yocto workspace

    Flash Procedure

    The micro SD card should not have any partition while flashing the image. The complete memory of the card should be free

    # of - output file (the device file for the inserted micro SD card
    bzcat <IMAGE_NAME>-<MACHINE>.wic.bz2 | sudo dd of=/dev/sdb bs=4M iflag=fullblock oflag=direct conv=fsync

    Known Issue

    • Cobalt is crashed upon launching over RDK Shell

    10 Comments

    1. Compile fail on rdkshell

      meta-rdk-video/recipes-graphics/rdkshell/rdkshell_git.bb:do_compile) failed with exit code '1'

      | /home/sjolly/rdk-next-v/build-raspberrypi-rdk-mc/tmp/work/cortexa7t2hf-neon-vfpv4-rdk-linux-gnueabi/rdkshell/1.x+gitAUTOINC+90c9c837fc-r0/git/rdkshellimage.cpp:24:10: fatal error: jpeglib.h: No such file or directory

      |    24 | #include <jpeglib.h>

      1. Hi Stenal,

        It's a known issue. it was fixed at 48437 but not yet merged. In such a way other errors also been fixed and the respective cherrypick commands were given on this page. Please find the 'apply bug fixes' bar and click 'Expand Source' to find the commands.

    2. May be helpful for someone building.

      Error: 

      bits/c++config.h: No such file or directory

      Fix:

      sudo apt-get install gcc-multilib g++-multilib

    3. Anyone facing issues with the new fresh build?

      ERROR: Unable to start bitbake server (None)

      ERROR: Server log for this session (build-raspberrypi-rdk-mc/bitbake-cookerdaemon.log):

      --- Starting bitbake server pid 36076 at 2020-12-21 18:54:01.106073 ---

      ERROR: ParseError at ..build-raspberrypi-rdk-mc/conf/local.conf:247: Could not include required file conf/distro/include/##RDK_FLAVOR##.inc
      1. Rarely it happens. every bitbake execution locks the environment and contact server so, if another attempt of bitbake done without completion of the previous, the lock will not be released and causes this error. A hack I can suggest to remove bitbake.lock under build directory and try

    4. I've built a hybrid image for the Pi and flashed it. It boots, but the wired network isn't getting an IP address.

      There are also a few errors in "/opt/logs/wpeframework.log" that are preventing wpeframework from running, such as:

      • "/usr/lib/libwayland-egl.so.0" doesn't exist; there is a "libwayland-egl.so.1".
      • westeros-gl: wstGLInit: unable to resolve eglGetDisplay
      • Essos error during initialization: Error. Failed to create a platform context

      Are these problems with my build or is this the current state of the dunfell image?

      1. Hi Steve Ford,

        1. RDK uses a preferred network interface (PNI) controller which enables only 1 network interface at a time and the default is eth0 so, please ensure the ethernet is connected. If wifi has to be used, just ensure ethernet is disconnected and restart the device to get wlan0 interface get up. wifi connection can be tried with the org.rdk.Wifi service's JSON RPC commands given in the user manual User Manual - RDK Services on RPi#926141268
        2. There is a fix made to address the preload libraries for vc4graphics support and it got merged recently. Also the main constraint in yocto 3.1 RPi builds is RDKshell is not yet supported on vc4graphics. This is the current state.
        1. Thanks Moorthy Baskar, I found the fix and rebuilt the image yesterday. Networking is now fine, so I don't know what the problem was the first time; I'm using a wired connection and it was all connected up, but anyway, it seems ok now.

          In my new image, starting the wpeframework.service is still failing, so I guess this is the RDKShell problem you mentioned.

          Given the remaining problems, does this mean that a morty build is the only one that's currently usable?

          1. Hi Steve Ford

            RDKShell crash issue been fixed. The fix is submitted for review in Github https://github.com/rdkcentral/RDKShell/pull/58 also the same applied as a patch on RDK builds (please find the apply bug fixes commands). From the fix, RDKShell crash issue been resolved but it seems that there is a flickering in UI and also webprocess been crashed when try to load playback related UIs like youtube, Metro apps and soon).
            If you really want to explore other RDK services, please change the autostart to false in RDKShell service (/etc/WPEFramework/plugins/RDKShell.json) file. Also a referenceapp.service (systemd service) that runs a script to launch the Switcher App UI on top RDK Shell which can also be stopped to explore other features.

    5. meta-openembedded dunfell branch introduces GUPnP v 1.2.4 but XUPnP RDK component has GUPnP support till with 1.2.2 version. So, RDK dunfell manifest switches meta-openembedded layer dunfell branch to rdk/dunfell branch