RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
...
...
As an Appdeveloper you want to test and run your DAC Application on a set of real Hardware Reference devices. So you need such device and host image of that device. If your app code complies with DAC app contract for binary compatibility it should be able to run on the various RDK Video Accelerator Devices provided these run firmware images (=monolitic software image) that also live up to that DAC contract for binary compatibility. The RDK6.1 monolitic software releases live up to that contract (as of RDK6.1_RC2 Feb 2024), contains UI to browse and install DAC apps from RDKM catalog and is advised/required to be loaded on those Video Accelerator Devices.
The RPI4 is the open source community Video Accelerator that RDK-M supports. We have asked RDK-M to make made available such a pre-build of such rdk6.1 lib32-rdk-generic-mediaclient-wpe-image software image for rpi so that you can just load these images this image on your rpi4 device and can start testing. (without having to spend any time on building such image from scratch) (see our request in Re: Raspberry Pi 4 RDK6 Release Notes )
Unfortunately at this moment, you still need to build such firmware image from scratch and you can't download prebuild image yet. That is why we add here section with instructions/link on how to build such firmware image.
To get your hands on other Video Accelerator HWs and their RDK6.1 SW images, we refer you to RDKM
We will be installing and running DAC apps on the RPI so we need a good host image. The most recent RDK6 mediaclient image is ideal for this.
The below commands must be run in an Ubuntu 18.04 environment with the necessary pre-requisites installed to run Bitbake. See here for the exact dependencies needed:
https://docs.yoctoproject.org/ref-manual/system-requirements.html#ubuntu-and-debian
For RPI3:
Code Block | ||
---|---|---|
| ||
mkdir rpi3_mediaclient_nosrc_rdk6
cd rpi3_mediaclient_nosrc_rdk6
# Install 'repo' tool from: https://android.googlesource.com/tools/repo
repo init --no-clone-bundle -u https://code.rdkcentral.com/r/manifests -b rdk6-main -m rdkv-nosrc.xml
repo sync --no-clone-bundle -j$(getconf _NPROCESSORS_ONLN)
MACHINE=raspberrypi-rdk-mc source meta-cmf-raspberrypi/setup-environment
bitbake rdk-generic-mediaclient-image |
For RPI4:
Code Block | ||
---|---|---|
| ||
mkdir rpi4_mediaclient_nosrc_rdk6
cd rpi4_mediaclient_nosrc_rdk6
# Install 'repo' tool from: https://android.googlesource.com/tools/repo
repo init --no-clone-bundle -u https://code.rdkcentral.com/r/manifests -b rdk6-main -m rdkv-nosrc.xml
repo sync --no-clone-bundle -j$(getconf _NPROCESSORS_ONLN)
MACHINE=raspberrypi4-64-rdk-android-mc source meta-cmf-raspberrypi/setup-environment
bitbake lib32-rdk-generic-mediaclient-wpe-image |
...
This prebuilt is available in via this link https://wiki.rdkcentral.com/download/attachments/80261869/rdk-generic-mediaclient-wpe-tdk-image-raspberrypi4-64-rdk-android-mc-6.1.0.wic.bz2 See RDK6.1 rpi4 release notes wiki Raspberry Pi 4 RDK6.1 Release Notes#Downloadapre-builtimage
That page also describes how you build such image from sources (but as said above this is not necessary), we suggest to use the prebuiltimage to save time
To get your hands on other Video Accelerator HWs and their RDK6.1 SW images, we refer you to RDK-M
Download and install https://www.balena.io/etcher/ tool
...
...
We provide the instructions for Amazon Elastic Container Registry. The private container registry setup RDK-M DAC team is also such type.
You need to have the following util programs installed: aws cli tools and skopeo.
...