Page History

...

Introduction

Briefly describe in general terms the system/application and the purpose for which it is intended, written in non-technical terminology. Consider including a high-level architecture diagram for the system. The description should include, but is not limited to, the following:

• Key features or major functions/use cases performed by the system/application
• Architecture of the system in non-technical terms (e.g., client server, Web-based, etc.)
• System environment or special conditions

Environment Setup

• Set-up Considerations

<Briefly describe and graphically depict as appropriate the equipment, communications, and network configuration of the system in a way that a non-technical user can understand>

• User Access Considerations

<Briefly describe and graphically depict as appropriate the equipment, communications, and network configuration of the system in a way that a non-technical user can understand>

• Accessing the System

<Provide detailed information and describe the procedures necessary to access the system. If applicable, include how to get a user ID and log on to the system, as well as the actions a user must take to change and/or reset a password.>

• System Work Flow

<Describe how system flow is happening mentioning checkpoints which can be verified during flow to ensure system is working as expected>

• Exiting the System

<Mention the validation artifacts that are essential to ensure the functionality is working as expected. Also any limitation while closing the validation process>

Executing System

Describe the specific system function or feature in detail and depict graphically by including screen prints and descriptive narrative as appropriate. Ensure each screen print is captioned and has an associated tag providing appropriate alternative text

Follow the above for sub feature / use cases

Troubleshooting

• Error Messages

<Identify the error messages that a user may receive and the likely cause(s) and/or possible corrective actions for the error>

• Special Considerations

The EvoStream Media Server is much more than a multi-format, multi-protocol server that delivers your media rich content across multiple screens and platforms. The RDK camera software runs on RPi-0 device. This page dedicated to bringing up and validation of EMS functionality in R-Pi Zero. 

Required Equipment

• Raspberry Pi 0 Device
• SD Card
• Power Cable
• OTG Cable
• Standard USB keyboard
• Mini HDMI connector
• HDMI Cable
• Television set/monitor with HDMI input

System Setup

Image Added

Please refer below link for RPI-0 Environment setup

EMS Flow - Environment Setup Diagram

Image Added

Build Procedure

$ repo init -u "https://code.rdkcentral.com/r/rdkcmf/manifests" -m rdkc-nosrc.xml -b master

$ repo sync

$ source meta-cmf-raspberrypi/setup-environment

select meta-cmf-raspberrypi/conf/machine/raspberrypi0-rdk-camera.conf

$ bitbake rdk-generic-camera-image

Image Flash Procedure

$ sudo dd if="Image Name" of="Device Name" bs=4M

Example:

sudo dd if=rdk-generic-camera-image_default_20200130060729.rootfs.rpi-sdimg of=/dev/sdb bs=4M

EMS Validation Procedure

STEP 1:

Add require SSID and PSK in /etc/wpa_supplicant.conf file in below format

network={

ssid="username"

psk="password"

}

Image Added

STEP 2:

Reboot the Target

After Reboot don't do step 1 and 2.

Note : Step 1 & 2 is only applicable for fresh target boot-up with new image.

STEP 3:

Modify needed resolution in ems configuration file

Supported Resolution:

SD:

Width - 640 , Height - 480

Width - 720 , Height - 576

HD:

Width - 1280 , Height - 720

FULL HD  :

Width - 1920 , Height - 1080

Modify resolution in below configuration file

cd /usr/bin/evo/bin

vi ems.conf

Image Added

After resolution modification need to reboot the target.

Note: This step is not necessary,it is depends on your resolution validation.

STEP 4:

WiFi connection is must needed for EMS validation.

Check WiFi connection by using below command.

ifconfig

Image Added

STEP 5:

check loaded module by using below command

lsmod

Image Added

STEP 6:

check camera device there or not by using below command

ls /dev/video0

Image Added

STEP 7:

On Bowser of PC:
http://dh-livevid-dev.comcast.com/bryan/demov3/evoplayersTest.html
Need to modify roomid as rpi0

Image Added

Press "PLAY" button in WebBrowser page.

Image Added

We can able to see the capturing content on WebBrowser.

...