Media Gateway Hybrid (Raspberry Pi) Build Instructions – Morty

Created on April 16, 2018

Copyright 2016 RDK Management, LLC. All rights reserved. The contents of this document are RDK Management, LLC Proprietary and Confidential and may not be distributed or otherwise disclosed without prior written permission of RDK Management, LLC.

Build Instruction

Follow the below link for RDK Media Gateway (Hybrid) image using Yocto build framework for RaspberryPi platform

RDK-V (Raspberry Pi) Yocto Build Instructions – Morty

10 responses to “Media Gateway Hybrid (Raspberry Pi) Build Instructions – Morty”

  1. Z-TUNG LAM, DINH says:


    Hi Z-Immaneni Kanthikiran , Gayathri ,

    I have been following your guideline  as below:

    $ repo init -u https://code.rdkcentral.com/r/manifests -m rdkv-raspberrypi.xml -b morty
    $ repo sync -j4 --no-clone-bundle

    # Wait for the repo has been syned. During the source pull, I have seen some errors – and I thought it was some connection errors, so I tried the repo sync command several times.

    $ source meta-cmf-raspberrypi/setup-environment

           → Select the raspberrypi-rdk-mc-westeros.conf option.


    build-raspberrypi-rdk-mc-westeros$ bitbake rdk-generic-mediaclient-westeros-wpe-image

    The build could run a litte bit, but I always get below errors:

    /usr/include/bits/floatn.h:75:1: error: unknown machine mode '__TC__'
    | /usr/include/bits/floatn.h:87:9: error: unknown type name '__float128'

    I have searched out from Google but not find the proper solution yet.

    Some snipped log from my procedure:

    // Bitbake log:

    Build Configuration:
    BB_VERSION = "1.32.0"
    BUILD_SYS = "x86_64-linux"
    NATIVELSBSTRING = "Ubuntu-18.04"
    TARGET_SYS = "arm-rdk-linux-gnueabi"
    MACHINE = "raspberrypi-rdk-mc-westeros"
    DISTRO = "rdk"
    DISTRO_VERSION = "2.0"
    TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7"
    TARGET_FPU = "hard"
    meta-metrological = "HEAD:c8a66ff9e2d6c480d0f2f17408cea1d7cadc4885"
    meta-raspberrypi = "HEAD:8db3240ba2b06f4f3e850d63a51b66f45f5e962a"
    meta-cmf = "HEAD:cda1cd07449ab9a7d76ced05820ce9806f82153b"
    meta-cmf-video-restricted = "HEAD:b5a4af851f77dbbc711ac3de6fcc244a7c7078a1"
    meta-cmf-video = "HEAD:d633e4eec7a3da16676f5be5c6cc0a2efdd6b8d6"
    meta-cmf-restricted = "HEAD:d8866fa1c8b0a295b477bb528e55b7afecd198ea"
    meta-cmf-qt5 = "HEAD:afd0f92998835a9fd9be8f97a4c3da5d05165d8f"
    meta-cmf-raspberrypi = "HEAD:e4552b0e9ea8cb4a710f14b0681f586fa46d3425"
    meta-rtlwifi = "HEAD:9af3c5e5a36ce366bb124da73c7ffd03c5acafe8"
    meta-rdk = "HEAD:b56fb127dfb99de09a36623b72dd1e4b87e6c5c7"
    meta-qt5 = "HEAD:139dfc4c6627a8abe5b26611fc0fc23da2e1ded8"
    meta-browser = "HEAD:1569eeb9cc1b87632abbf35fbb05f4ac4eeb3987"
    meta-java = "HEAD:5f4e053d2ab8e5db5a2825715cf78736b9196ddf"
    meta-webserver
    meta-multimedia
    meta-filesystems
    meta-oe
    meta-networking = "HEAD:153f85093c660eb3fbdd36db556d25d1bba59c1c"
    meta = "HEAD:32ec41c1efa5ecc806141a1f4fea5a8587c9fe12"
    meta-virtualization = "HEAD:912b50a9f66037d124bc51231a2156467996737d"
    meta-rdk-restricted = "HEAD:153cb21ae857686ed4f2fb0d9b57854702062804"
    meta-rdk-video = "HEAD:6a7203c98f14235568968fb9ccd9107d38321381"
    meta-rdk-ext = "HEAD:b4c5d65adea37c87f4a4f19d34dedfd66f6e8dc2"
    meta-python = "HEAD:153f85093c660eb3fbdd36db556d25d1bba59c1c"

    // I am using Ubuntu 18.04 on laptop HP-ProBook-650-G1.

    // The tree view of raspberrypi.

    $ tree -L 2 meta-cmf-raspberrypi/
    meta-cmf-raspberrypi/
    ├── conf
    │   ├── distro
    │   ├── include
    │   ├── layer.conf
    │   └── machine
    ├── licenses
    │   ├── Comcast
    │   └── RDK
    ├── LICENSES.TXT
    ├── recipes-bsp
    │   └── bootfiles
    ├── recipes-ccsp
    │   ├── ccsp
    │   ├── hal
    │   └── util
    ├── recipes-common
    │   └── rfc
    ├── recipes-connectivity
    │   ├── dibbler
    │   ├── hostapd
    │   ├── lirc
    │   ├── nfs-utils
    │   ├── openssh
    │   ├── openssl
    │   └── wpa-supplicant
    ├── recipes-containers
    │   └── lxc-container-generator
    ├── recipes-core
    │   ├── busybox
    │   ├── dbus
    │   ├── dropbear
    │   ├── images
    │   ├── packagegroups
    │   └── systemd
    ├── recipes-devtools
    │   ├── binutils
    │   ├── e2fsprogs
    │   ├── gdb
    │   ├── lua
    │   └── php
    ├── recipes-extended
    │   ├── aamp
    │   ├── appmanager
    │   ├── devicesettings
    │   ├── dvrmgr
    │   ├── gst-plugins-playersinkbin
    │   ├── gst-plugins-rdk-subtec
    │   ├── gstqamtunersrc
    │   ├── hdhomerun
    │   ├── iarmmgrs
    │   ├── libaio
    │   ├── lighttpd
    │   ├── logrotate
    │   ├── mediaframework
    │   ├── mediastreamer
    │   ├── networkmgr
    │   ├── packagegroups
    │   ├── rdkapps
    │   ├── storagemanager
    │   ├── sysint
    │   ├── tdk
    │   ├── tdkb
    │   ├── websocket-ipplayer2
    │   ├── wifi-client-hal
    │   └── xupnp
    ├── recipes-gnome
    │   └── librsvg
    ├── recipes-graphics
    │   ├── pxcore-libnode
    │   ├── userland
    │   ├── westeros
    │   └── westeros-soc
    ├── recipes-kernel
    │   └── linux
    ├── recipes-multimedia
    │   └── gstreamer
    ├── recipes-oem
    │   └── mfrlibs
    ├── recipes-protocols
    │   ├── net-snmp
    │   └── quagga
    ├── recipes-qt
    │   └── servicemanager
    ├── recipes-rdkb
    │   └── sysint-broadband
    ├── recipes-support
    │   ├── dnsmasq
    │   ├── gmp
    │   ├── libpcre
    │   ├── nettle
    │   ├── network-hotplug
    │   ├── parodus
    │   └── parodus2snmp
    ├── recipes-thirdparty
    │   └── tr69
    ├── recipes-wpe
    │   ├── wpe
    │   ├── wpe-backend
    │   ├── wpe-backend-rdk
    │   ├── wpebackend-rdk
    │   ├── wpelauncher
    │   ├── wpe-launcher
    │   ├── wpeservice
    │   ├── wpewebkit
    │   └── wpe-webkit
    └── setup-environment

    Thanks and Regards,

    Tung Lam

  2. Akshay Kumar Coimbatore Balaji says:


    Hello Z-TUNG LAM, DINH , did you manage to identify the root cause of the problem and resolve it?

  3. Z-George Joseph says:


    Akshay Kumar Coimbatore Balaji Try using a docker container to do a build. I did face the issue mentioned by Z-TUNG LAM, DINH. Somehow the build system native headers seem to get picked up in the build when done on an Ubuntu machine. 

    • Akshay Kumar Coimbatore Balaji says:

      Hello George, I also managed to resolve the issue by using a docker. Thank you for the suggestion!

  4. Mude Krishna Naick says:


    Hi Akshay Kumar Coimbatore Balaji and Z-George Joseph

    I’m also facing same issue mentioned by Z-TUNG LAM, DINH  and please suggest me  the procedure to solve the issue.

    I’m not aware docker container build procedure to solve this issue and please suggest me the procedure.

    Many thanks for considering my request.

    Thanks & Regards,

    Krishna.

    • Z-TUNG LAM, DINH says:

      Hi,

      I have to re-install lower edition of Ubuntu (16.04) to build other RDK projects, and all are OK now. I have no time to test with this RPI platform yet. 

  5. Akshay Kumar Coimbatore Balaji says:


    Mude Krishna Naick , if you are not using docker, please execute the following commands:

    sudo apt-get update

    sudo apt install gcc-multilib g++-multilib

    This might resolve your problem.

  6. Z-Keerthi says:


    Akshay Kumar Coimbatore Balaji I have tried installing those packages and the error persists . Doing it on docker isnt an option for what we are trying to do. Any other suggestions ? Z-TUNG LAM, DINH 

    • Z-TUNG LAM, DINH says:

      Hi,

      I have to re-install lower edition of Ubuntu (16.04) to build other RDK projects, and all are OK now. I have no time to test with this RPI platform yet. 

Leave a Reply

Your email address will not be published.

Go To Top