The generic RDK includes source code and links to acquire open source / 3rd party components. It also includes instructions for creating SoC specific RDK and basic validation tools.
This section contains MVPD applications and proprietary software as well as components that are device and SoC independent.
Contains SoC specific changes/optimization and SoC software in addition to items in generic RDK. It also includes instructions for OEM integration and tools for basic validation.
This layer features optimized components for SoC specific RDK provided by the OEM. This includes OEM software for boot-up, image updates, and APIs to handle custom drivers.
The RDK software stack can be visualized in terms of increasing levels of specificity. At the top are the generic layers – Generic RDK and MVPD Platform Components – which vary in level of proprietary components. As you move down to the SoC layer, this stack contains software such as the SDK and SoC-level patches for the generic RDK and MVPD components. Further down the stack, you find OEM-provided firmware that is device-specific. These could be specializations to the generic or SoC components or complementary software components provided by the OEM to create a fully functional set-top device.
The RDK includes over thirty software components that allow for patches for open source and third-party extensions. This package consists of:
Includes source code for all generic RDK components. Restrictions exist for access to RDK components requiring a special license.
List of all RDK components, software versions, and access instructions.
RDK Porting Guide
Provides licensees step-by-step procedures to install, build, and integrate RDK.
Provides the latest information on RDK, release timelines, architecture documentation, tutorials, white papers, etc.
Click here to request a login account for RDK
Click here for licensing information
The generic RDK trunk is accessible via RDK-M CMF Gerrit and reflects the most recent contributions from both Comcast development and the community. On a periodic basis, the trunk is tagged and those tags are made available. The code will be built and tested by RDK-M CMF ahead of tagging and made available for download along with appropriate documentation including a readme, component manifest, user guides and test results. Community members can fetch the tagged code from RDK-M CMF Gerrit and work with it.
Yes. RDK based devices have been deployed on more than five million devices.
To get more information on RDK, please license RDK if you have not already done so. Once you have a license, click here to access the RDK support site.
Once you have been notified that the agreement has been executed by RDK Management, RDK Support will send you a short questionnaire. The questionnaire MUST be completed. Once submitted you will receive your RDK Wiki user account information within 48 hours. RDK Wiki access is limited to authorized staff of licensee companies only.
If you uncover what you believe to be a security gap in the RDK code you can submit a secure message to RDK Management by using the following link: https://rdkcentral.com/security-submissions/
Yes. Our security point of contact is configured to accept PGP encrypted messages for submission of information regarding security vulnerabilities discovered in the RDK platform.
By attaching your Public Key, it will ensure that you receive a secure message confirming receipt of the submission.
Yes, as long as you use your Public Key when submitting the issue.
For a full list of FAQs regarding RDK, please refer to the RDK Wiki by clicking here.