Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Author

RDK-M

Approver


Version

1.0

State

Release version

Date

Sept 14, 2020

...


Host Setup

...

 1.1.Setting up the Host Environment

Pre-Requisites

...

Requirement

...

Remarks

...

Linux

...

32 bit Ubuntu 16.04 OS

...

Fee HDD Space

...

Minimum 100GB Free Memory

...

Oracle Virtual Box

...

4.3.18 or higher

...

Wireless Adapter

...

Brand Name:

Tenda ralink & Model Number:W311MI

TPLink Archer T4U AC1200

...

USB to Ethernet Switch

...

To connect with Ethernet Switch & Multiple Clients

NOTE: Observing fetch errors in VMs with Ubuntu14.x. Thus, suggesting to use VMs with Ubuntu16.x or higher.

Building

Note: Cloning the code before login once to code.rdkcentral.com, user would get the Authentication error, even though the account is in good standing and has all the required access. Please login to code.rdkcentral.com before attempting to clone.

To build, follow below instructions

Create workspace directory

Code Block
languagebash
themeDJango
mkdir <workspace dir>
cd <workspace dir>

Follow below instructions to create build with external sources

Code Block
languagebash
themeDJango
repo init -u 

 1.1.1.Install OS - Ubuntu-16.04

This step is for one time setup for downloading & building RDK-B Emulator in a standalone machine.

  • Download Ubuntu-16.04.

1.1.2.Install the following packages for setting up your host VM

The instructions provided below are meant to be executed via the command line on an Ubuntu machine:

$     sudo apt-get  install   build-essential gettext bison libfile-slurp-perl gawk libncurses-dev autoconf flex doxygen libtool automake  libpcre3-dev zlib1g-dev libbz2-dev subversion minicom putty libssl-dev rpm python-pexpect python-svn python-argparse vim tofrodos meld dos2unix cmake uuid-dev ruby transfig libglib2.0-dev xutils-dev lynx-cur gperf autopoint  python-dulwich  python-dev curl vim diffstat texinfo chrpath openjdk-7-jre

1.1.3.Configure bash as default command interpreter for shell scripts

$     sudo dpkg-reconfigure dash

Select “No”
To choose bash, when the prompt asks if you want to use dash as the default system shell - select “No”

1.1.4.Configure Git

Upgrade your Git version to 1.8.x or higher

On Ubuntu 16.04 LTS, if you are unable to upgrade your git version using apt-get, then follow the below steps in order to upgrade  

$     sudo apt-get install python-software-properties

$     sudo add-apt-repository ppa:git-core/ppa

$     sudo apt-get update

$     sudo apt-get install git

 Once git is installed, configure your name and email using the below commands

$          git config --global user.email "you@example.com"

$          git config --global user.name "Your Name"

1.1.5.Configure repo

In order to use Yocto build system, first you need to make sure that repo is properly installed on the machine:

$          mkdir ~/bin

$          PATH=~/bin:$PATH

$          curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo

$          chmod a+x ~/bin/repo

Trivia: Repo is a repository management tool that is built on top of Git. Its main purpose is to help manage projects that consist of many Git repositories, it can also be used to manage uploads to the CMF Gerrit instance and automate aspects of the development workflow.

Repo does not replace Git, it simply aids management of projects that contain multiple Git repositories into a single local working directory. Git will still be used for local operation such as commits etc.

Repo manages this for you by means of an XML based Manifest file. The Manifest file defines which repositories the project uses and links to appropriate revisions of each git repository, i.e where the upstream repositories reside and where they should be cloned locally. It is the manifest.xml (or default.xml) that determines which Git repositories and revisions repo will manage. This manifest.xml file is hosted in a Git repository along with all the other git repositories.

1.1.6.Setting up .netrc for RDK emulator

CMF git uses https. This step prevents the password prompt every now and then during code checkout and build.

Create a file .netrc in home directory.

$vi .netrc

The contents of the .netrc should be as follows:

machine code.rdkcentral.com

login <YOUR_USERNAME>

password <YOUR_PASSWORD>

1.2.Downloading Source Code & Building

1.2.1.Downloading Source Code

Following commands fetch the source code of emulator using repo tool

$ mkdir emulator && cd emulator

Please use the following repo init command

...

https://code.rdkcentral.com/r/manifests -m rdkb-extsrc.

...

xml -b rdk-next

...



repo sync -j4 --no-clone-bundle

...

1.2.2.Building

...



MACHINE=qemux86broadband source meta-cmf/setup-environment

...

There are different kinds of builds listed. Please read the options and select the number of the build you need.

  • Select option  for qemux86broadband-morty, for building  RDK-B emulator.

Next, you would need to initiate the build using the following command:

...



bitbake rdk-generic-broadband-morty-image

On Successful build,  the ROOTFS the ROOTFS (in vmdk format) would be available at the following reference location based on the build type:-       ${HOME}/emulator.

Panel
borderColorblack
bgColorWhite
borderStyledashed

<workspace dir>/build-qemux86broadband-morty/tmp/deploy/images/qemux86broadband-morty/rdk-generic-broadband-image-qemux86broadband-morty-<timestamp>.vmdk