RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
The first step to get a fully functional product is the define the product features and see if they meet the standard requirements. A list of expected features from an IP based RDK-V Accelerator are listed at Product Specifications. SoC can use this as a guide while engineering the RDK SoC platform.
This should be used only as a reference and not a final set of features.
RDKM offers collaboration space for SoCs which would help SoCs to collaborate with OEM and RDK teams (as well as any 3rd party). RDKM collaboration zone includes features like (but not limited to) CMF facility to maintain build manifests as well as SoC/OEM specific code, SoC SDK artifact storage facility, JIRA & RDK Wiki spaces, integration with Test & Certification suites, monthly & release tagging and so on.
Once the product features are decided, the device engineering can be started. SoC needs to decide on the hardware layout that incorporates components to the target board. A sample expected hardware specification list as well as a sample flash layout is available at Product Engineering.
SoC can make use of the details available at SoC Platform Firmware to start developing a Yocto build to engineer the device firmware builds based on RDK Yocto build setup.
RDKM offers an in-house Test & certification suite that facilitates SoCs to get their video certified as RDK Compliant device. Certification program includes testing which validates the RDK stack on the device with defined test suite called as RDK Certification Test Suite.
For more details on the RDK Certification please refer: RDK Video Accelerator Certification
Step 1 : Get a board with Linux + drivers
RDK is based on yocto based linux distribution so SoC vendors has to get a board that is running on linux which is a SoC version of linux with the required drivers that are needed to run all the hardware that are associated in the board like Wifi.
Linux version that is having can be optimzed and hardened by linux kernal can be hardened by SoC vendor itself because RDK is not dealing with hardening Linux in the SOC port so whatever is required is the job of SoC how to hardening how to make it secure those things it is responsibility of SoC vendor.
Mostly they will be having linux for on their board with required drivers
Step 2 : Move the build to Yocto, compare it to supported Yocto version of RDK
RDK is based on yocto build setup so if their is not based on yocto so they need to migrate to yocto format so that they can easily adopt on top of it. In case they are not doing it will be little difficult for them to first port the complete RDK and later keep the patches. So ,it is always recommended to port yocto on top of , recommended to convert their linux distribution to a yocto based build
Step 3 : Compare and verify the compiler flags used in RDK and in platform to avoid issues
for eg: RDK considers hardware floating point in platform where as some platforms are on software based floating point
Step 4 : Compare the open source versions used in platform as different versions will cause problems
Step 5 : Move the RDK recipes to platform yocto build
Step 6 : Get a successful build etc
ToDO
Add a section here, with diagram, on the (like get a board with Linux + drivers, move the build to Yocto, compare it to supported Yocto version of RDK, compare and verify the compiler flags used in RDK and in platform to avoid issues ( for eg: RDK considers hardware floating point in platform where as some platforms are on software based floating point ), compare the open source versions used in platform as different versions will cause problems ), move the rdk recipes to platform yocto build, get a successful build etc.
Device settings component is having a HAL interface to control device specific peripherals such as video port, audio port and display and front panel.
More details on HAL interface can be found here: Device Settings HAL Types & Public API DTCP HAL Interfaces.
Integrates the SoC provided DTCP library with DTCP/IP manager Interface implementation which manages source/sink DTCP/IP sessions and performs the encryption/decryption.
Hal Interface specification: DTCP HAL Interfaces
Contains SoC specific MOCA libraries, headers and MOCA profile codes.
API Details: TR69 Host Interface Handler
For more details on tr69hostif, please refer: tr69hostif
qamtunersrc is a push based gstreamer source plugin which tunes to the given service and provides the SPTS data.
Depends on platform specific libraries for tune, filtering, and pod functionalities.
Playersinkbin is a gstreamer bin element consisting of demux, decoder and sink elements. A template file gstplayersinkbin.c.template and gstplayersinkbin.h.template are provided as a reference for SoC implementation. SoC has to add details of platform specific plugins and implement the required properties expected out of them.
SDK Vendors should implement CEC driver interface API as specified in hdmi_cec_driver.h
HAL Interface Specificcation: HDMI-CEC HAL API's specification
Power, IR and DeepSleep modules are having SoC dependency. API's are specified in plat_power.h, plat_ir.h and deepSleepMgr.h
More details about api's can be found here
Contains functions for creating and handling native eglwindow. Hal api's are specified in westeros-gl.h
Wi-Fi Client HAL provides an interface (data structures and API) to interact with underlying Wi-Fi driver and enabling the client to be connected with an Access Point.
Hal API's are specified in wifi_client_hal.h. Doxygen Link: Wifi HAL API Specification
Set of Cryptographic API's Implementation, can be used to achieve all type of Cryptographic requirements from Premium App.
Media Pipeline Backend layer is a module in device layer which glues the media pipeline capabilities of the device to that of the IgnitionX.
As part of integrating Premium Apps as a native application on the RDK stack, the Premium Apps Video Porting (PVP) Layer needs to be implemented. The PVP Layer consists of the following modules:
Abstraction layer for third-party applications to get specific GStreamer values from the SoC pipeline.
Amazon assets are encrypted using Microsoft PlayReady. A robust implementation of the PlayReady must be provided for porting kit to decrypt assets.
Text-to-speech converts text into spoken voice output to help customers navigate the Prime Video application without seeing the screen. Text-to-speech is mandatory for the US region and optional in other regions.