Getting Started

Product Specifications

The first step to get a fully functional product is the define the product features and see if they meet the standard requirements. A list of expected features from an IP based RDK-V Accelerator are listed at Product Specifications. OEM can cross check the expected features/specifications with the capabilities of the SoC platform being used and can finalize the features supported by the product.

...

Certification program includes testing which validates the RDK stack on the device with defined test suite called as RDK Certification Test Suite. It is mandatory to go through this program in order to brand user's platform as RDK compliant product.

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.

...

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 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

Device Settings

• OEM implementation includes device specific configuration parameters & customizing data structures for front panel setting and so on

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
• Provides 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 and so on

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 and so on

Wi-Fi

• OEM specific Wi-Fi driver configuration files and utility library can be added optionally

...

Licensed

Manufacturer Library

The Manufacturer Library implements a set of interfaces that enable configuration and usage of vendor specific components in the STB.

Interfaces

MFR API: The APIs comprise of functions that allow to -

...

• Set LED color
• Get/Set LED brightness
• Set LED blink
• Get/Set text
• Register/Unregister key callback

Storage Manager

Provides following functionalities in handling of storage devices such as SD card and so on.

...

[SDCARD_CONFIG]
MMC_DEV_NODE=/device/node/name/of/mmcblock
MMC_SRC_DEV_NODE=/dev/mmcblk<NodeName>
MOUNT_PATH=/tmp/data
FRAME_RATE_MBPS=<Max-FrameRate-Numeric>
IsTSBEnableOverride=<true/false>
filesystemtype=<vfat/ext3 ...>
DEFAULT_TSB_MAX_MINUTE=<TIME-DURATION-IN-MINUTE>
DISK_CHECK_SCR_PATH=/lib/rdk/disk_check
TSB_VALIDATION_FLAG=<true/false>

SYSINT

A 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. 

...