<Work in progress. only the skeleton added>

This page provides the step by step procedures for OEMs to adopt RDK-B. OEM layer sits on top of SoC layer and later adds support for software for boot-up, image updates, and APIs to handle custom drivers. 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.

Before You Begin

RDK License

OEMs are advised to get into an agreement with RDK Management LLC to obtain the free license so as to use the complete RDK Code base in their platform. More details about license is available at https://rdkcentral.com/licenses/ . Please email info@rdkcentral.com if you have additional questions about licenses or membership

Bringing up RDK by OEM- Approach

Product Specifications

RDKM On-boarding

Roles & Responsibilities

A table explaining the roles & responsibilities of OEM & RDKM

Product Engineering

Sample Reference Flash Layout (Optional) :

Device Firmware

SoC/OEM meta-layer creation

TDK and RDK Certification Suite Package

SDK Releases

HAL + SDK binary

Complete source code

Collaboration with SoC

Procedure for OEM porting of RDK

Components of OEM Interface