...

You will need

• Raspberry Pi 4 (RPIRPI4) 3B  (RPIv3B/3B+ or RPI 4is deprecated)
• Balena Etcher to write the Raspberry Pi SD card: https://www.balena.io/etcher/
• get and load (lib32-)rdk-generic-mediaclient-wpe-image built for you RPIimage software image (aka firmware image) on your RPI4
• Your own built DAC app: you only need the OCI image (.tar) and not a generated bundle (.tar.gz). See this wiki page. Not needed if you only want to install and run other people's published DAC apps.

...

load rdk mediaclient SW image on RPI4

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) and are advised , 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 for making to make available such pre-build rpi rdk6.1 software images lib32-rdk-generic-mediaclient-wpe-image  software image for rpi so that you can just use load these images on you 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 today 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 to instructions on how to build such firmware image.

...

Publish your DAC app to RDK-M DAC cloud

If you don't want to test or publish your own DAC app then you can skip this step and try the already published demo apps in the next section. There are two ways to publish an There are two ways to publish an new app in ASMS:

1. use the official ASMS REST API to publish the app (openAPI swagger REST api)
2. using the dactest.py test tool

But before publishing the app into ASMS you first need to publish your DAC app's OCI image into a container registry that supports OCI compliant format.

Note If you don't want to test or publish your own new DAC app then you can skip this step and try the already published demo apps in the next section.

Publish the OCI image in OCI registry

...