Versions Compared

Key

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

...

draw.io Diagram
bordertrue
diagramNameRDK-B OEM Porting of RDK
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth803
revision1


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

Refer to this page to 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, Vendor-Specific Information, NVRAM files and partition, Provisioning, OEM Specific drivers, Other OEM specific utilities, RDK Device-Specific Patches, Image Generation Utilities, 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 the SoC layer is usually done by SoC’s build environment and the new SDK or revision is updated in a 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 to RDK-B Porting Guide for more details

Components of OEM Interface

Include Page
Hardware Abstraction Layer (HAL)
Hardware Abstraction Layer (HAL)

...