This page will guide you through publishing your DAC app to the RDK ASMS cloud as an AppDeveloper, then installing and running it on a Raspberry Pi (RPI). More detailed documentation of all the components used is available on their respective pages.explains how you as AppDeveloper can create/compile your native (c/c++) application using DAC SDK and how to publish it to RDK-M DAC-cloud staging area. 

If your application meets the DAC contract for binary compatibility, this will allows you as AppDeveloper 

• to download, run and test that same native application on all RDK6.1 Video Accelerators without any additional integration steps
• to exchange your Application binary with real RDK operators, technically allowing them to test/run your application on their boxes. 

// TO REMOVE This page will guide you through publishing your DAC app to the RDK ASMS cloud as an AppDeveloper, then installing and running it on a Raspberry Pi (RPI). More detailed documentation of all the components used is available on their respective pages.

You will need

What do you need

• Video Accelerator with final RDK6.1 image on it. This can be Raspberry Pi 4 (RPI4) on which you can flash RDK6.1 final release image.   Note Raspberry Pi 4 (RPI4) and final RDK6.1 image.  Note that RPIv3B/3B+ is deprecated, not supported by RDK-M anymore. tool Tool to flash RDK6.1 rpi image to SD card, example is provided with https://www.balena.io/etcher/ toolYour 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.. Contact RDK-M if you want to test it on more carrier grade Video Accelerator (with amlogic, broadcom or realtek SoC) with RDK6.1 image
• Your application source code with bitbake recipe 
• DAC SDK https://github.com/rdkcentral/meta-dac-sdk to cross compile your application, auto add dependent libraries and automatically package/output your application as oci compliant dac container image.
• As App developer company/entity you will need to request to RDK-M DAC support team via support@rdkcentral.com  :
  
  • login/pswd to register your app and its metadata in RDK-M ASMS instance (ASMS is AppStore Metdata µService and part of DAC cloud setup of RDK-M)
  • an associated "Maintainer" identifier (string) to be able to upload/register your app. 
  • credentials for uploading your OCI image to the private RDK OCI container registry. Is not required if you choose to upload it to a public accessible OCI container registry or ask support team to upload it for you.

Above is one time request per App developer entity. Once you have above credentials, you can reuse them for publishing other apps under your entity. At this moment requesting these credentials is still manual process, a point to improve in future 

Flash prebuilt RDK6.1 SW image on your RPI4

...