RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
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 driver porting / integration
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.
The Manufacturer Library implements a set of interfaces that enable configuration and usage of vendor specific components in the STB.
Interfaces
The APIs comprise of functions that allow to:
The eCM API is intended to be used by DSGCC. It allows to:
3. FPD API
The FPD interface specification is defined and provided by Comcast.
The API controls front panel’s indicators and allows to register key stroke callbacks:
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.
Provides the SNMP agent process which:
Respond to Get requests from SNMP Management System.
Provides following functionalities in handling of storage devices such as SD card etc.
[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>
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.
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
Can partially or entirely address various use cases.
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) |