Page History

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 -

• Perform vendor-specific initialization
• Read/Write serialized data
• Validate and write the image into flash
• Prepare for reboot STB (legacy)
• Set cable card type
• Get filesystem path configuration (legacy)
• Generate DES session key using DFAST2 algorithm

eCM API:  The eCM API is intended to be used by DSGCC. It allows to -

• Trigger the eCM initialization after the eCM booting is completed
• Check if the image should be downloaded in case of CDL

FPD API: The API controls front panel’s indicators and allows to register key stroke callbacks -

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

• Scans and mounts MMC devices
• Manages SD card file properties
• reads TSB health
• OEM has to provide the following device specific configuration

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

• Customize "/etc/common.properties" and "/etc/device.properties" files which defines environment variables for the following:
  

  • Model name of the STB

  • Build type ( dev or prod)

  • Type of the device i.e. mediaclient or hybrid etc.

  • Default interface

  • OEM Manufacturer name e.g. Pace, Cisco, Arris etc.

  • SoC provider name. e.g. BRCM

• Customize the utility scripts in lib/rdk which provides Shell functions for the following features and to the application layers.
  • To Access device specific information
  • Factory reset operation
  • Monitoring peripherals & hardware specific to the OEM device

Conclusion

The Reference Design Kit (RDK) is a solution for wide range of OEM and SoC manufacturers is gaining considerable market and attracting attention from a wide range of community users. As RDK is evolving as the preferred open-source set-top middleware stack, it requires proper guideline and manual in place. This document will prove as a useful handbook for beginners as well as those who want to switch their services to RDK based platform. It will help them to remove the ambiguity in different levels of porting and help them achieve the result in short period. Moving forward, this can also evolve to accommodate more nitty-gritty’s of porting and resolving related issues.

Reference Links