RDK-V 4.0 - OEM Porting Guide

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.

xupnp

Can partially or entirely address various use cases.

1. 1. Provide configuration parameters to client devices.
   2. Discover gateways present in a home network.
   3. Gateway gathers information about the devices on a home network for diagnostics purposes.

OEM specific implementation includes providing following configuration files.

• • xdiscovery.conf (Provides configuration parameter for the xdiscovery service)

    Parameter	Description
    discIf	Interface name to be used for device discovery

  • xdevice.conf (Provides configuration for the xcal-device service)

    Parameter	Description
    BCastIf	Name of Broadcast Interface
    BCastPort	Broadcast Port Value
    StreamIf	Name of Streaming Interface
    GwIf	Gateway Interface

    Paths and names of all input data files

    Parameter	Description
    OemFile	Path to vendor specific dhcp script
    DnsFile	Path to DNS resolve configuration
    DiagFile	Path to Diagnostics JSON
    HostFile	//etc//hosts
    DevXmlPath	Base directory for Device XML
    DevXmlFile	BasicDevice.xml
    LogFile	//opt//logs/xdevice.log
    DevPropertyFile	//etc/device.prpperties (Contains device specific env)