Introduction

RDK Servies Services are nothing but the RDK components are implemented as Thunder Nano Services and maintained in RDK Central's GitHub https://github.com/rdkcentral/rdkservices

Initially, this is started in the Comcast side and validated on the RPi reference platform and the Yocto recipe is maintained only in meta-rdk-video layer.  Recently RDK services are made open-source and available in GitHub . Alsoso, the recipe to avail this on CMF community https://code.rdkcentral.com/r/plugins/gitiles/components/generic/rdk-oe/community (meta-cmf-video /+/refs/heads/rdk-next/recipes-extended/rdkservices/layer) as rdkservices_git.bbappend points  which points to GitHub's repository.

Currently, RDK services is are excluded from Thunder Image builds and this depends with ServiceManager and WPE WebKit for (OpenCDM Implementation)

RDK Services is work on top of RDK Shell which is an application management native component.

Yocto Build Steps

repo init -u https://code.rdkcentral.com/r/manifests -b rdk-next -m rdkv-nosrc.xml
repo sync -j `nproc` -c --no-clone-bundle --no-tags
MACHINE=raspberrypi-rdk-mc source meta-cmf-raspberrypi/setupenvironmentsetup-environment

# remove meta-wpe from BBLAYERS (as it provides wpeframework-plugins)
sed -i '/meta-wpe/d' conf/bblayers.conf

# enable rdkshell distro feature
echo 'DISTRO_FEATURES_append = " rdkshell"' >> conf/local.conf

# firebolt-image build
bitbake rdk-firebolt-mediaclient-image

...