RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
The aim of this document is to explain the procedure for OEM porting of RDK.
draw.io Diagram | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 .
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 )
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
Background Color | ||
---|---|---|
| ||
Components of OEM Interface |
Bluetooth Manager implements the Bluetooth HAL i.e. Bluetooth Core (BTRCore) API. Bluetooth HAL interface provides a software abstraction layer that interfaces with the actual Bluetooth implementation and/or drivers. RDK Bluetooth HAL layer enables projects to pick any Bluetooth profiles as per their requirements. Bluetooth HAL uses BlueZ5.42 stack which is a quite popular Linux Bluetooth library.
Table of Contents |
---|
The OEM 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.
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.
Below is the list of component having an OEM interface i.e. either they have a device specific part of the code or add OEM specific improvement to the component.
...
Uploads core dumps to
...
a FTP server if there are any
...
This interface is optional, OEM may implement a customized script for uploading the crash dump files to a server using specific certificate files
...
...
...
...
...
...
...
...
Provides platform specific configuration options for Hardware test. Which will run periodically in background to check attached hardware health.
...
LED Manager is used to control the LED patterns during different system events.
...
This handles the HDCP service operations such as enable or disable the HDCP.
...
...
Info |
---|
For details on the Wi-Fi HAL Public APIs and Data Types, please refer: https://wiki.rdkcentral.com/doxygen/rdkv-opensourced/df/dce/group___w_i_f_i___h_a_l.html |
Show If | ||
---|---|---|
|
...
Manufacturer LibraryThe Manufacturer Library implements a set of interfaces that enable configuration and usage of vendor specific components in the STB. InterfacesMFR API:The APIs comprise of functions that allow to -
eCM API:The eCM API is intended to be used by DSGCC. It allows to -
FPD API:The API controls front panel’s indicators and allows to register key stroke callbacks -
Storage ManagerProvides following functionalities in handling of storage devices such as SD card and so on.
[SDCARD_CONFIG] SYSINTA collection of system integration shell scripts and configuration files that handles many of the initialization and routine job such as bringing up applications or rotating log etc. OEM can define following parts of sysint code.
|