Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Procedure for OEM porting of RDK

The aim of this document is to explain the procedure for OEM porting of RDK.

...

Include Page
RDK-B 4.0 -OEM Porting Guide
RDK-B 4.0 -OEM Porting Guide

...

Step 1 : Selection of SoC board with RDK ported on it

Refer this page SoC Platform Firmware to know the details about Yocto manifests, SoC meta-layer creation includes adding the Machine Configuration File for the new SoC .

Step 2 : Add OEM components

OEM needs to add OEM specific components like Firmware Upgrade, Secure Boot Loader, MFR libraries, Vendor Specific Information, NVRAM files and partition, Provisioning, OEM Specific drivers, STB Utilities, RDK Device-Specific Patches, Image Generation Utiities etc. as well as interfacing layers to the generic RDK for relevant OEM code modules ( see below )

Step 3 : Upgrade RDK/SoC components for OEM changes

Any Revision change in SoC layer is usually done by SoC’s build environment and the new SDK or revision is updated in recipe. If a new recipe is added for any update in SoC software, then can be handled using PREFERRED_VERSION Yocto flag in meta layer

Refer RDK-B Porting Guide for more details

Components of OEM Interface

For components of OEM interface Please refer Hardware Abstraction Layer (HAL).