You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »


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.

Bluetooth

Bluetooth driver integration

Crash Upload

  • Uploads core dumps to an 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.

Device Settings

  • OEM implementation includes device specific configuration parameters & customizing data structures for front panel setting etc.

DTCP

  • Integrates the SoC provided dtcp library with DTCP/IP manager Interface implementation which Manages source/sink DTCP/IP sessions and performs the encryption/decryption.
  • Should Provide setup scripts to initialize the default dtcp data to device specific persistent partition. 

hwselftest

Provides platform specific configuration options for Hardware test. Which will run periodically in background to check attached hardware health.

  • OEM dependency is limited to providing a configuration file hwselftest.conf which defines the hardware interfaces that should be tested e.g. partition name, HDMI, IR, MOCA etc.

LED Manager

LED Manager is used to control the LED patterns during different system events.

  • OEM should implement the template code to ensure that it matches with their LED coloring scheme and other configuration parameters such as brightness level and number of LED types, multi-color or single color LEDs.

tenableHDCP

This handles the HDCP service operations such as enable or disable the HDCP.

  • OEM interface includes implementing manufacturer specific calls to read the keys etc.

wifi

  • OEM specific wifi driver configuration files and utility library can be added optionally.




  • No labels

DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.