You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »


RDK-V Emulator Users Guide


Copyright 2015 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.

Document Status 



Document Control Number

D10-20141105

Document Title

RDK Emulator Users Guide

Version

D05

Date

2015/02/23

Status

Issued (I)

Distribution

RDK licensees & ASP Members

Document Status Codes



Work in Progress (WIP)

An incomplete document designed to guide discussion and generate feedback that may include several alternative requirements for consideration.

Draft (D)

A document in specification format considered largely complete, but lacking review. Drafts are susceptible to substantial change during the review process.

Pre-Issued (Pre I)

A revision of a document circulated for review or approval prior to release, but not approved for distribution

Issued (I)

A stable document, which has undergone rigorous review and is suitable for product design and development 
It will serve as a basis for testing requirements.

Legal Notices


This document is provided under the terms and conditions of the RDK License Agreement, License Agreement for Software Integration Kit, License Agreement for Set-top Box Software Integration Kit.

RDK Management LLC is not responsible for any liability of any nature whatsoever resulting from or arising out of any use or reliance upon this specification. This document is furnished on an "AS IS" basis, and RDK Management, LLC does not provide any representation or warranty, express or implied, regarding its accuracy, completeness, or fitness for a particular purpose."

Table of Contents


Introduction


RDK (Reference Design Kit) is an integrated set of software components, tools and documentation that help in the development of the software stack for set-top box based on the standard Linux operating system which is designed to meet the requirements of the latest generation media servers and clients.

The RDK emulator is an x86 based implementation of the RDK software stack. It is primarily targeted towards the RDK development community (integrators, component developers and application developers) that attempts to simplify the process of working with the RDK software stack without the need for a reference hardware platform.  The key applications in the RDK Emulator are the rmfApp, Media streamer and the RDK-Browser. As RDK emulator runs on desktop computers, applications can be tested and debugged before trying to deploy them to real devices.

Purpose of this Document


The purpose of this document is to enable RDK users and developers to be able to bring up the RDK stack and emulator on the PC platform. The document also includes step-by-step procedures to setup & build RDK Emulator

Audience


The intended audience includes the MSO teams, developers and external vendors responsible for the development of firmware and applications for RDK-based Set Top Boxes 

Scope


Scope of this document includes understanding RDK Emulator and  functionalities, supported build types and to run and test in Virtual Box environment.

Limitations


RDK Emulator does not support all components of RDK 2.0 stack .Currently RDK Emulator supports mediaframework, media-streamer,RDK-Browser and RDK-Logger, XRE components.

Known Issues


  • During video playback, performance issues are there due to video scaling.
  • Also In rmfApp , while playing video through hnsource or qamsource , application may crash once EOS is reached.
  • It has been seen that open source package mirror repos may go down temporarily or may be blocked by local corporate firewalls. Please try the build again at a later time or after resolving local firewall issues. One test would be to access the failing url on the web browser and see if the site is up. This can help isolate local issues.

Abbreviations and Acronyms


The following table describes the acronyms and abbreviations used in this document

Abbreviation/Acronym

Description

RDK

Reference Development Kit

VM

Virtual Machine

VBox

Virtual Box

QAM

Quadrature Amplitude Modulation

STB

Set Top Box

XRE

Cross-Platform Runtime Environment

HDD

Hard Disk Drive

EOS

End of Stream

SPTS

Single Program Transport Stream

MPTS

Multi-Program Transport Stream

UPNP

Universal Plug and Play

Overview of RDK Emulator


  • Executes on x86-based platforms including virtualization environments such as Virtual Box and QEMU.
  • Multiple build types - media client, hybrid etc
  • Supports the RDK Browser startup application.
  • Up to date with the RDK generic trunk and any x86-specific platform code.
  • Built using Yocto and RDK build frameworks

Key Features


  • RMF Support
  • RDK Browser as start up application supporting playback of local TS file.
  • Video/Audio playback using fbdevsink and autoaudiosink gstreamer elements.
  • Remote control - x86-based QT application that is useful for  navigation  in RDK Browser and XRE Applications
  • Support for X2 guide.

Supported Build Types



Build Types

RDK Components Involved

Features/Applications Supported

Final Image Name

Startup Application

 RDK Mediaclient

  1. rdklogger,
  2. mediaframework
  3. rdkbrowser
  1. rmfApp (Hnsource,Mediaplayersink)
  2. rdkbrowser

rdk-generic-mediaclient-image-qemux86.vmdk

RDK-Browser

  RDK Hybrid

  1. rdklogger,
  2. mediaframework
  3. mediastreamer
  4. Rdkbrowser
  1. rmfApp (Hnsource,qamsource,mediaplayersink)
  2. rdkbrowser
  3. rmfStreamer ( Http+DLNA Server Support)

rdk-generic-hybrid-image-qemux86.vmdk

RDK-Browser

Build Setup Instructions


Setting up the Host Environment


How to Build#SettinguptheHostEnvironment

Downloading Source Code & Building


RDK-V Emulator Build Instructions#VEmulatorBuildInstructions-Yocto2.2(Morty)supportinRDKEmulator

Bringing up the Emulator on Virtual Box


Host Requirements

RequirementRemarks
Linux                           32/64 bit Ubuntu 16.04 operating system
Free HDD SpaceMinimum 100GB Free Memory
Oracle Virtual Box4.3.18 or higher

Install Virtual Box and follow the following steps to bring up RDK Emulator on Virtual Box:

In the following steps, it is recommended to review the description and screenshot completely before proceeding with steps.

STEP 1: Create your new VM Instance:

  • Open Virtualbox

  • Select New [A popup will come up]

  • Select Type as ‘Linux’

  • Select Version as ‘Other Linux (32 Bit)’

  • Click on “Next”

  • Choose a Memory Size of 512 MB


  • Use an existing virtual hard drive file which would be your newly built image in *.vmdk format and create your VM:

STEP 2: Configure your new VM Instance:

  • Click on “Settings” tab to configure your new VM instance

  • Configure your VMs network settings
  • Choose “Bridged Adapter” mode as shown in the screenshot below

STEP 3: Create an external hard drive:

Your VM has been built with very limited hard drive space. In order to run emulator and play video files, you need to copy your video files into the file system for playback. For this, you will need to setup a virtual external hard drive.

  • Select the vm instance on the main menu of Virtual Box
  • Click Settings -> Storage -> Add Hard disk [icon]
  • Click ‘Create new disk’ (Note: In the screenshot below, "Choose existing disk" may seem highlighted. Please select "Create new disk")


  • Select VDI (VirtualBox Disk Image) as your Hard Drive file type:

  • Select "Dynamically allocated" storage: 

STEP 4: Formatting and partitioning your new external hard drive:

  • Boot up your VM
  • Your emulator VM boots up to show the RDK Browser HTML application which can be used to select and launch multiple other applications using the Tab key & Enter key
  • Use BACKSPACE to come out of Readme, WatchTV, iHeartRadio and Sample Video
  • To come out of the X2 guide, use Ctrl+Backspace
  • In order to learn your VM IP, use the RDK Browser application “tab” key to chose the various applications. Choose Device Info which will provide you the IP address as shown in the screenshot below:

  • Once you have the IP address you may SSH into your VM from your linux shell console. Use root as the ssh user.
  • Use the “mount” command to see the current status of connected hard disks
$ mount

  • Use fdisk command to list out connected hard drives. You may note that in the screenshot below, there are two hard drives listed. hda and hdb. hdb is the external hard drive that we have created in the previous step.
$ fdisk -l

  • Use fdisk to create your new hard disk partition
$ fdisk /dev/hdb

Review the description of the steps during fdisk operation below and the following screenshot for reference before proceeding.

  • Use fdisk to create your new hard disk partition
    • Use the command "n" to add a new partition
$ Command (m for help): n
    • Select partition type as the suggested default "p" for primary partition

$ Partition type:

p primary (0 primary, 0 extended, 4 free)

e extended

Select (default p): p

    • Set your partition number as the suggested default. In the example case: 1
$ Partition number (1-4, default 1): 1
    • Press "Enter" key for First sector & Last sector prompts
    • Select the command "p" to print the partition table on screen for review
$ Command (m for help): p
    • Select the command "w" to write the partition table to disk and exit fdisk
$ Command (m for help): w



  • Format your newly created partition with ext3 file system
$ mkfs.ext3 /dev/hdb1

  • Create a folder for mounting your new partition at /ext_hdd
  • Mount your newly created hard disk partition to /ext_hdd

$ mkdir /ext_hdd

$ mount /dev/hdb1 /ext_hdd

STEP 5: Copy a Single Program Transport stream to your file system to be used for emulator video playback.

  • Pre-requisite to the step is assumed that /ext_hdd is already mounted with the external hard disk partition on your emulator VM
  • Copy your SPTS video file from your host machine to /ext_hdd folder on the emulator VM 
  • Note: The following command is performed from your Host Machine
$ scp <your_spts_file_name>.ts root@<your_emulator_vm_ip>:/ext_hdd
  • Back on your emulator VM, create a link in /opt/www/ to point to the external hard drive at its mount point /ext_hdd
$ ln -sf /ext_hdd/<your_spts_file_name> <your_spts_file_name>
  • In the screenshot below<your_spts_file_name> is assumed to be "received_spts1.ts" as an example.

 

Usage Instructions


Logging into your VM


As described in the previous section, you can log in to your emulator VM from your Host Machine using the ssh command.

$ ssh root@x.x.x.x

Note: In order to learn the IP address of your VM, use the RDK Browser application “tab” key to navigate to "Device Info" which will provide you the IP address. Press "Enter" key to enter Device Info

Using rmfApp


Introduction


The rmfApp application is supported for all build types. Once you SSH into your emulator VM, you can play a video stream located at a url using a source and a sink.

Where is rmfApp?

rmfApp is located in the folder: /usr/bin on your emulator VM

How to run rmfApp?

Navigate to the folder /usr/bin and run rmf App using command ./rmfApp. After the initial log statements when the rmfApp starts up, press "Enter" key to get the rmfApp prompt - "rmfApp>"

rmfApp Command Line Options

root@qemux86:~# rmfApp [-source SOURCE] [-sink SINK] [other options] url

SOURCE can be: hnsource,qamsource

SINK can be:   mediaplayersink 

Other options include:
•        -recordingId <id>: id of recording to create where <id> is a decimal number
•        -recordingTitle <title>: title of recording

Example Sequence of rmfApp usage

Before using rmfApp, it will be better to terminate rdkbrowser as it may impact the performance of playback. You may use the systemctl command to terminate rdkbrowser as shown below.

$ systemctl stop rdkbrowser.service

rmfApp is located in the directory /usr/bin. Navigate to the directory containing the rmfApp:

$ cd /usr/bin

Launch RMF App using the command below:

$ ./rmfApp

Once the app is launched, press enter again to get the prompt "rmfApp->":

$ rmfApp->
NOTE:

Note 1: There is an additional step required prior to using the emulator because it is built without the gsttee module in gst-plugins-rdk:

Before invoking rmfapp, it is necessary to set the environment variable 'USE_GENERIC_GSTREAMER_TEE' to 'TRUE', so that mediaframework uses the generic gsttee that is built from Open Source gstreamer: 

example : 

root@qemux86hyb-morty:/usr/bin# export USE_GENERIC_GSTREAMER_TEE=TRUE root@qemux86hyb-morty:/usr/bin# ./rmfApp 

Note 2: In the streaming scenario it is necessary to kill the rmfStreamer process on the hybrid image, which is started automatically, and invoke it manually as illustrated below : 

Streaming Scenario : 

Hybrid : 

barracuda:~> ssh root@193.120.91.104

root@qemux86hyb-morty:/#

root@qemux86hyb-morty:/# export USE_GENERIC_GSTREAMER_TEE=TRUE root@qemux86hyb-morty:/# cd /usr/bin root@qemux86hyb-morty:/usr/bin# ps -aef  | grep rmf root@qemux86hyb-morty:/usr/bin#kill -9 <pid> root@qemux86hyb-morty:/usr/bin# ./rmfStreamer 

IP Client : 

barracuda:~> ssh root@193.120.91.132

root@qemux86mc-morty:/#

root@qemux86mc-morty:/# export USE_GENERIC_GSTREAMER_TEE=TRUE root@qemux86mc-morty:/# cd /usr/bin root@qemux86mc-morty:/usr/bin# ./rmfApp

rmfApp->launch -source hnsource -sink mediaplayersink

http://193.120.91.104:8080/vldms/tuner?ocap_locator=ocap://0x125d


Simulated Live Playback on a Hybrid Emulator


In a simulated live playback, the following rmfApp command maybe used to playback the local SPTS video file:

launch -source qamsource -sink mediaplayersink ocap://0x125d

Where 

  • source : qamsource
  • sink; mediaplayersink
  • url: ocap://0x125d
$ rmfApp-> launch –source qamsource –sink mediaplayersink ocap://0x125d

Simulated Playback on a Hybrid Emulator


launch –source hnsource –sink mediaplayersink http://127.0.0.1:50050/received_spts1.ts

Where

$ rmfApp-> launch –source hnsource –sink mediaplayersink http://127.0.0.1:50050/received_spts1.ts

Simulated Live Playback on a Media Client Emulator


 In a simulated live playback, the following rmfApp command maybe used to playback the local SPTS video file:

 launch –source hnsource –sink mediaplayersink http://<HYBRID IP>:8080/vldms/tuner?ocap_locator=ocap://0x125d

 Where  

  • source : hnsource
  • sink; mediaplayersink
  • url: http://<HYBRID IP>:8080/vldms/tuner?ocap_locator=ocap://0x125d
$ launch –source hnsource –sink mediaplayersink http://<HYBRID IP>:8080/vldms/tuner?ocap_locator=ocap://0x125d

Scheduling & Playing Back Recordings from the Media Client using Recording ID


RDK recordings on the Hybrid device are created from a cloud-based scheduler using json messages. Once the recordings are created, the rmfApp on the media client device can be used to playback the newly recorded media content. 

This section outlines the use case:

Step 1: Preconditions / Prerequisites: 

  • As the hybrid VM has very limited memory and as recordings are by default stored in /opt/data/, you should create a new directory /ext_hdd/data within the external hard drive that we had set up earlier and also create a soft link to /opt/data

mkdir -p /ext_hdd/data

ln -sf /ext_hdd/data /opt/data

NoteThe above directory and the soft link needs to be in place each time before scheduling recordings. 

 Your recordings will get created in the following path on the Hybrid VM:

/opt/data/OCAP_MSV/0/0/DEFAULT_RECORDING_VOLUME/test

/opt/data/OCAP_MSV/0/0/DEFAULT_RECORDING_VOLUME/test/chunks

If there is a media file created in the /chunks folder above, then the recordings have been successfully created.

Step 2: Launching rmfStreamer on Hybrid VM

There are multiple scripts in the folder /usr/bin. There are two scripts for launching rmfStreamer:

  • rmfstreamer
  • rmfStreamer

Note that the name of each file is similar apart from the usage of upper case and lowercase "s" in each file name.

Launch rmfStreamer using the script: rmfstreamer

cd /usr/bin/

sh rmfstreamer

if you run in into issues accessing rmfstreamer, then change the access permissions of file appropriately:

chmod 777 rmfstreamer

Once rmfStreamer starts, you will see log print statements on the console.

Step 3: Start playback of recorded content on Hybrid emulator from your Media Client emulator

Now you can playback from the media client using the rmfApp on the media client VM using the following sample commands:

cd /usr/bin

./rmfApp

rmfApp> launch -source hnsource -sink mediaplayersink http://<hybird_vm_ip>:8080/vldms/test?rec_id=6

Note: Where the recording id is "6" as set in the schedule.json message from the server. Users may write a small application to simulate the scheduler server json messages.


Westeros and WPE-webkit Support on RDKV Emulator

RDK emulator supports westeros compositor and renderer module as westeros-renderer-gl

Building WPE-image:


# To build the same for different build types, use the below command
  
#Hybrid
MACHINE=qemux86hyb-morty source meta-cmf/setup-environment
bitbake rdk-generic-hybrid-wpe-image
To test WPE image from the VM console

1)Boot the VM in NAT mode and ssh in to the VM to get the console as mentioned above.

ex: ssh -p 2222 root@localhost

2)Then type the following command

To support westeros surface width and height are HD so emulator need to set HD resolution

To enable support for 1280x720 resolution in emulator please follow the steps mentioned in this page.
This will help us in adding custom resolution in Virtual Box.

Applications testing over westeros Compositor

1) ssh login to the Emulator

Westeros compositor will  run automatically in startup of Emulator image

run following commands in terminal for manual starting the compositor on Emulator if needed

$ mkdir -p /run/user/0
$ export XDG_RUNTIME_DIR=/run/user/0/
$ westeros --renderer <renderer module> --display <socket-name> &
$ westeros --renderer /usr/lib/libwesteros_render_gl.so.0.0.0 --display WPE &
$ gdisplay start
$ export WAYLAND_DISPLAY=WPE

for Dunfell Emulator
---------------------
$ mkdir -p /run/user/0
$ export XDG_RUNTIME_DIR=/run/user/0/
Add the below line in westeros-init.sh
export LD_PRELOAD=/usr/lib/libwesteros_gl.so.0.0.0
$ westeros --renderer /usr/lib/libwesteros_render_gl.so.0.0.0 --display WPE &

Run the commands
westeros-init.sh
westeors_test


westeros compositor will launch

Testing Westeros_compositor

to test westeros compositor with simple egl test apliaction

run westeros_test


# After Launching westeros compositor in emulator
$ export XDG_RUNTIME_DIR=/run/user/0/
$ export WAYLAND_DISPLAY=WPE
$ westeros_test
(or)
$ westeros_test --display WPE



Testing Videosink on Westeros Compositor


$ export XDG_RUNTIME_DIR=/run/user/0/
$ export WAYLAND_DISPLAY=WPE

#Check the plugin in image
$ gst-inspect-1.0 westerossink

# To play the video and render on westeros compositor
$ gst-launch-1.0 playbin uri=http://localhost:50050/received_spts1.ts videosink=westerossink


  • No labels