Blog from January, 2018

RDK-V Release rdkv-2017q4 available
Stephen Barrett posted on Jan 12, 2018

RDK-V release rdkv-2017q4 is now available.

Baselinenightly/20171228Updates from Comcast 2017-12-28.
Post-baseline updates



TDKM53https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53
Manifestrdkv-2017q4

Highlights

  • This is the first RDK-V quarterly release.
  • This release is equivalent to the rdkv-20171228 iteration.

Details of all RDK-V releases and iterations can be found here

Build System

  • Reference platform builds still have a dependency on podManager.
  • All builds use rdk-oe (Yocto).
  • rdk/components/generic/injectedbundle cannot be built by the community because of a dependency on AVE.
  • Root Filesystem uncompressed image sizes:
    • XG1v3 208676 (KiB)
    • XI3v2 197288 (KiB)

Building for RaspberryPi Hybrid

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-2017q4-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment

Select option raspberrypi-rdk-hybrid.conf

$ bitbake rdk-generic-hybrid-wpe-image

Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-hybrid folder

Building for RaspberryPi Mediaclient

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-2017q4-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment

Select option raspberrypi-rdk-mc.conf

$ bitbake rdk-generic-mediaclient-wpe-image

Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-mc folder


Documentation for RDK-V on RaspberryPi is available at: 

Media Gateway Hybrid (RaspberryPi)-2.1-krogoth

Media Client (RaspberryPi)-2.1-Krogoth

RaspberryPi Sanity Testing

Some basic sanity tests were performed on the Hybrid and Client images, playing video locally via gst-play and also using WPELauncher.

In addition streaming tests were performed using rmfApp.

Known Issues

TDK M53 or later must be used to test this release as prior versions of TDK Manager are not compatible with the TDK Agent in this release due to a recent change in the TDK JSON RPC version

  • Emulators:
    • TDK-346 RDK-V CMF Emulators xcal-device service and xdiscovery not running
      • Causes most XUPNP tests to fail, issue (which is a work around procedure) is marked as resolved but the underlying issue won't be addressed until dependency on POD manager issue is removed
      • The output.json file created by this service is required for a number of the E2E tests, we have worked around this by creating the /opt/output.json file on hybrid and media client as follows:
        {"playbackUrl": "http://<hybrid IP>:8080/hnStreamStart?deviceId=<hybrid mac address>&DTCP1HOST=<hybrid IP>&DTCP1PORT=5000"}
e.g. {"playbackUrl": "http://192.168.21.234:8080/hnStreamStart?deviceId=08:bb:83:b3:b3:07&DTCP1HOST=192.168.21.234&DTCP1PORT=5000"}
    • TDK-354 RDKV Emulator Testing Script Time Outs
      • We are observing inconsistency in some of the E2E tests results, i.e. tests may sometimes pass and sometimes fail with a SCRIPT TIMEOUT error
    • TDK-292 RDKV Emulator-HYB recorder failures
      • requires DVR Simulator (refer to TDK-277)
    • TDK-380 RDKV Emulator "No such file or directory:" retrieving recordDetails.txt
    • TDK-381 RDKV Emulator RMF_HNSrc_MPSink GetMediaTime() Failures
    • TDK-436 RDKV EMU E2E and RMF Regressions Post JSON RPC Updates
  • RPI:
    • RPI-125 RDKV Hybrid: ssh services not working on bring up
    • RPI-160 RDKV Mediaclient:ssh services not working
  • Platforms:
    • RDK-283 Absence of POD in CMF image blocks RMF system level functionality
      • xcal device service doesn't start, so /opt/output.json file required by E2E tests not created we have worked around this by creating the tmp/ip_acquired file, with this workaround we can run TDK E2E tests
    • TDK-277 Testing of Recorder component will remain blocked until DVR Simulator code is available
    • TDK-276 Subset of Recorder tests still consistently failing for CMF
    • TDK-387 RDKV Platform XG1V3 XUPNP Event not received by xcal-device process
    • TDK-388 RDKV Platform XG1V3 RMF MPSink Set Volume Errors
    • TDK-389 RDKV Platform E2E Tests Failures "HNSource play failed current state not playing"
RDK-B Release 2017q4 available
Stephen Barrett posted on Jan 12, 2018

RDK-B release rdkb-2017q4 is now available. Below are links to the relevant documents for the release.

Below are links to the relevant documents for the release.

For the Gerrit links, you need to log in before you will be able to see the contents.

The latest RDK-B release addresses licensing issues so users are advised to move to the latest release.

Baseline 

Baselinenightly/201712282017-12-28 baseline.
Post-baseline updatesrevert changes 13738, 13840
TDKM53

https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53

Manifestrdkb-2017q4

Highlights since 2017q3

  • This release is equivalent to the rdkb-20171228 iteration.
  • Components updated:
    • meta-rdk-asp, meta-rdk-bsp-emulator, meta-cmf, meta-cmf-broadband, meta-cmf-raspberrypi, meta-rdk, meta-rdk-broadband, devices/intel-x86-pc/rdkbemulator/tdkb, tdk, tdk-advanced, tdkb.
    • crashupload, rdk_logger, sys_resource, CcspCMAgent, CcspCommonLibrary, CcspDmCli, CcspHomeSecurity, CcspLMLite, CcspMisc, CcspMoCA, CcspPandM, CcspPsm, CcspSnmpPa, CcspTr069Pa, CcspWifiAgent, GwProvApp, GwProvApp-ePON, PowerManager, TestAndDiagnostic, Utopia, Xconf, hal, halinterface, hotspot, sysint, webui, sysint, rdkb/devices/raspberrypi/hal, rdkb/devices/rdkbemu/ccsp/rdkb.
  • Patches:
    • Separate patch files for the open-source OE layers are no longer maintained. Instead, from this quarterly release, mirrors of the OE layers used by RDK are maintained at CMF, containing rdk branches that contain the patches already applied. The RDK build scripts and recipes now all use these instead of the previous patches.
  • Community contributions: 
    • Please refer to the changelog since the last release (rdkb-2017q3) here (Gerrit).

Getting the code

$ mkdir rdkb
$ cd rdkb 
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-2017q4
$ repo sync -j4 --no-clone-bundle
  • The -m rdkb.xml in the build sequence above is important. If this is not specified, you will get an RDK-V tree by default.
  • The -b rdkb-2017q4 in the build sequence above specifies the branch to use. If you omit the -b rdkb-2017q4 entirely, you will get the master (HEAD) of each component.
  • At any time, the community can build latest master by dropping the -b rdkb-2017q4 option in the repo init command.
  • We have verified that this iteration boots to a login prompt and that you can log in, and that you can connect with a web browser to the web admin page.

Building for the emulator

$ source meta-cmf-bsp-emulator/setup-environment (select qemux86broadband)
$ bitbake rdk-generic-broadband-image

The image path will be: build-qemux86broadband/tmp/deploy/images/qemux86broadband/rdk-generic-broadband-image-qemux86broadband.vmdk

To build TDK, follow the steps as for a normal build, above, but use the following bitbake command:

$ bitbake rdk-generic-broadband-tdk-image

The image path will be: build-qemux86broadband/tmp/deploy/images/qemux86broadband/rdk-generic-broadband-tdk-image-qemux86broadband.vmdk

TDK documentation is available here: https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53

Running the emulator

  1. Start VirtualBox.
  2. Click New -> Enter name -> Select type Linux -> Select version Other Linux (32 bit) -> Click Next
  3. Select Memory size - 512MB -> Click Next
  4. Select option Use an existing virtual hard drive -> Select the built image above -> Click Create
  5. Once the VM has been created, select the new image and click Settings -> Network -> Select Attached to: 'Bridged Adapter' -> Click Ok
  6. Click Start. This will bring up the emulator with the initial splash screen

Building for RaspberryPi

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-2017q4-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment

Select option raspberrypi-rdk-broadband.conf

$ bitbake rdk-generic-broadband-image

Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-broadband folder

Documentation for RDK-B for RaspberryPi is available here: https://wiki.rdkcentral.com/display/DEVTOOLS/RDK+Broadband+(RaspberryPi)+-Krogoth

Running on the RaspberryPi

Please see RDK Broadband (RaspberryPi) -Krogoth.

Known Issues

TDK M53 or later must be used to test this release as prior versions of TDK Manager are not compatible with the TDK Agent in this release due to a recent change in the TDK JSON RPC version

RPI Issues:

  • TDK-409 RDKB RPI TS_WIFIHAL_5GHzGetRadioStandard Failure
  • TDK-434 RDKB RPI WIFIAGENT 2.4 and 5 IsSSIDDown Failures
  • RPI-41 TDK SelfHeal lighttpd process is not getting restarted automatically once the process is crashed/killed
  • RPI-61 port triggering is not working for RaspberryPi device
  • RPI-63 LMLIte Connected devices are not displayed on management portal under connected device list
  • RPI-85 TDK WIFI Not able to change the operating standard value of 2.4GHZ
  • RPI-86 TDK WIFI Not able to change the operating standard value of 5GHZ
  • RPI-131 Cannot get admin password from backend.
  • RPI-138 RDKB WiFi Get Extension channel not returning desired outputs
  • RPI-146 TDK WIFI HAL wifi_getRadioExtChannel returns an empty string for 2.4Ghz
  • RPI-147 WiFi HAL api wifi_getRadioSupportedFrequencyBands() returning a null string
  • RPI-148 TAD LMLite Device.Hosts.HostNumberOfEntries is not zero in Bridge mode
  • RPI-149 TDK WIFIHAL mismatch between the values returned by wifi_getRadioStandard() and wifi_getRadioSupportedStandards() for radioIndex 0
  • RPI-150 TDK WIFI AutoChannelEnable is not disabling when radio channel is changed for 5GHz
  • RPI-151 TDK WIFI AutoChannelEnable is not disabling when radio channel is changed for 2.4GHz

Emulator Issues:

  • TDK-368 RDKB-EMU Intermittent Segfault in CcspWiFiAgent.service
  • TDK-375 RDKB EMU TS_TAD UDPEcho Test Failures
  • TDK-424 RDKB EMU TS_WIFIHAL Failures
  • TDK-425 RDKB EMU failure setting Device.X_RDKCENTRAL-COM_Report.NetworkDevicesStatus.ReportingPeriod
  • TDK-432 RDKB EMU WIFIHAL GetSSIDStatus Failures
  • TDK-444 RDKB EMU TS_SNMP_SetSSIDEnableWithRadioDisabled Failure
  • TDK-445 RDKB EMU TS_SNMP_Get2.4SSIDWithDisabledXfinityWifi Failure
  • RDKBEMU-380 TDK SNMP SNMP Query to get the System Description details is not returning the mandatory fields like HW_REV,SW_REV
  • RDKBEMU-502 Parameters like BytesReceived, PacketsReceived are not getting populated after a successful UDP echo command executed
  • RDKBEMU-569 TDK WIFI HAL wifi_getRadioExtChannel returns an empty string for 2.4Ghz
  • RDKBEMU-570 TDK WIFI HAL Enabling or disabling wifi radio and ssid through hal api is not reflecting in emulator
  • RDKBEMU-582 WIFI wlan0_0 missing following integration of NetworkManager
    • note network manager reverted from this release due to this issue
  • RDKBEMU-585 TDK UserInterface] Device.UserInterface.X_CISCO_COM_RemoteAccess.Enable shows a different value when queried with Device.UserInterface.X_CISCO_COM_RemoteAccess
  • RDKBEMU-586 TDK UserInterface Device.UserInterface.X_CISCO_COM_RemoteAccess.FromAnyIP shows a different value when queried with Device.UserInterface.X_CISCO_COM_RemoteAccess
  • RDKBEMU-589 TDK WIFI HALwifi_getRadioMaxBitRate returns NULL for 2.4GHz and 5GHz
  • RDKBEMU-594 TDK WiFi Set operation with HAL api wifi_setApEnable() is failing for 2.4GHz
  • RDKBEMU-595 TDK WiFi Set operation with HAL api wifi_setApEnable() is failing for 5GHz
  • RDKBEMU-596 TDK WiFi The HAL api wifi_getBaseBSSID() is returning junk value for 2.4GHz
  • RDKBEMU-597 TDK WiFi HAL api wifi_getRadioIfName() not returning expected value for 2.4GHz
  • RDKBEMU-598 TDK WiFi HAL api wifi_getRadioIfName() not returning expected value for 5GHz

Generic TDK Issues:

  • RDKB-9915 TDK Port Triggering Master CcspPandMSsp process crashes when trying to enable a rule added for port triggering
  • RDKB-10750 TDK PAM Master Fails to set the value as "Requested" for Device.IP.Diagnostics.DownloadDiagnostics.DiagnosticsState
  • RDKB-14126 TDK Getting invalid parameter error on setting parameter values for a new PortMapping rule


RDK-B Iteration 20171228 available
Stephen Barrett posted on Jan 10, 2018

RDK-B iteration rdkb-20171228 is now available. Below are links to the relevant documents for the iteration.

For the Gerrit links, you need to log in before you will be able to see the contents.

The latest RDK-B iteration addresses licensing issues so users are advised to move to the latest iteration.

Baseline 

Baselinenightly/201712282017-12-28 baseline.
Post-baseline updatesrevert changes 13738, 13840
TDKM53

https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53

Manifestrdkb-20171228

Highlights since 20171127

  • Components updated:
    • meta-cmf-bsp-emulator, meta-rdk-bsp-emulator, meta-cmf, meta-cmf-broadband, meta-cmf-raspberrypi, meta-rdk, meta-rdk-broadband, tdk, tdk-advanced, tdkb.
    • crashupload, rdk_logger, CcspCMAgent, CcspCommonLibrary, CcspLMLite, CcspMisc, CcspMoCA, CcspPandM, CcspPsm, CcspSnmpPa, CcspTr069Pa, CcspWifiAgent, GwProvApp, TestAndDiagnostic, Utopia, Xconf, hal, sysint, webui, rdkb/devices/raspberrypi/hal, rdkb/devices/rdkbemu/ccsp/rdkb.
  • Patches:
    • Separate patch files for the open-source OE layers are no longer maintained. Instead, from this iteration, mirrors of the OE layers used by RDK are maintained at CMF, containing rdk branches that contain the patches already applied. The RDK build scripts and recipes now all use these instead of the previous patches.
  • Community contributions: 
    • Please refer to the changelog since the last iteration (rdkb-20171127) here (Gerrit).

Getting the code

$ mkdir rdkb
$ cd rdkb 
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20171228
$ repo sync -j4 --no-clone-bundle 
  • The -m rdkb.xml in the build sequence above is important. If this is not specified, you will get an RDK-V tree by default.
  • The -b rdkb-20171228 in the build sequence above specifies the branch to use. If you omit the -b rdkb-20171228 entirely, you will get the master (HEAD) of each component.
  • At any time, the community can build latest master by dropping the -b rdkb-20171228 option in the repo init command.
  • We have verified that this iteration boots to a login prompt and that you can log in, and that you can connect with a web browser to the web admin page.

Building for the emulator

$ source meta-cmf-bsp-emulator/setup-environment (select qemux86broadband)
$ bitbake rdk-generic-broadband-image

The image path will be: build-qemux86broadband/tmp/deploy/images/qemux86broadband/rdk-generic-broadband-image-qemux86broadband.vmdk

To build TDK, follow the steps as for a normal build, above, but use the following bitbake command:

$ bitbake rdk-generic-broadband-tdk-image

The image path will be: build-qemux86broadband/tmp/deploy/images/qemux86broadband/rdk-generic-broadband-tdk-image-qemux86broadband.vmdk

TDK documentation is available here: https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53

Running the emulator

  1. Start VirtualBox.
  2. Click New -> Enter name -> Select type Linux -> Select version Other Linux (32 bit) -> Click Next
  3. Select Memory size - 512MB -> Click Next
  4. Select option Use an existing virtual hard drive -> Select the built image above -> Click Create
  5. Once the VM has been created, select the new image and click Settings -> Network -> Select Attached to: 'Bridged Adapter' -> Click Ok
  6. Click Start. This will bring up the emulator with the initial splash screen

Building for RaspberryPi

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-20171228-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment

Select option raspberrypi-rdk-broadband.conf

$ bitbake rdk-generic-broadband-image

Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-broadband folder

Documentation for RDK-B for RaspberryPi is available here: https://wiki.rdkcentral.com/display/DEVTOOLS/RDK+Broadband+(RaspberryPi)+-Krogoth

Running on the RaspberryPi


Please see RDK Broadband (RaspberryPi) -Krogoth.

Known Issues

TDK M53 or later must be used to test this release as prior versions of TDK Manager are not compatible with the TDK Agent in this release due to a recent change in the TDK JSON RPC version

RPI Issues:

  • TDK-409 RDKB RPI TS_WIFIHAL_5GHzGetRadioStandard Failure
  • TDK-434 RDKB RPI WIFIAGENT 2.4 and 5 IsSSIDDown Failures
  • RPI-41 TDK SelfHeal lighttpd process is not getting restarted automatically once the process is crashed/killed
  • RPI-61 port triggering is not working for RaspberryPi device
  • RPI-63 LMLIte Connected devices are not displayed on management portal under connected device list
  • RPI-85 TDK WIFI Not able to change the operating standard value of 2.4GHZ
  • RPI-86 TDK WIFI Not able to change the operating standard value of 5GHZ
  • RPI-131 Cannot get admin password from backend.
  • RPI-138 RDKB WiFi Get Extension channel not returning desired outputs
  • RPI-146 TDK WIFI HAL wifi_getRadioExtChannel returns an empty string for 2.4Ghz
  • RPI-147 WiFi HAL api wifi_getRadioSupportedFrequencyBands() returning a null string
  • RPI-148 TAD LMLite Device.Hosts.HostNumberOfEntries is not zero in Bridge mode
  • RPI-149 TDK WIFIHAL mismatch between the values returned by wifi_getRadioStandard() and wifi_getRadioSupportedStandards() for radioIndex 0
  • RPI-150 TDK WIFI AutoChannelEnable is not disabling when radio channel is changed for 5GHz
  • RPI-151 TDK WIFI AutoChannelEnable is not disabling when radio channel is changed for 2.4GHz

Emulator Issues:

  • TDK-368 RDKB-EMU Intermittent Segfault in CcspWiFiAgent.service
  • TDK-375 RDKB EMU TS_TAD UDPEcho Test Failures
  • TDK-424 RDKB EMU TS_WIFIHAL Failures
  • TDK-425 RDKB EMU failure setting Device.X_RDKCENTRAL-COM_Report.NetworkDevicesStatus.ReportingPeriod
  • TDK-432 RDKB EMU WIFIHAL GetSSIDStatus Failures
  • TDK-444 RDKB EMU TS_SNMP_SetSSIDEnableWithRadioDisabled Failure
  • TDK-445 RDKB EMU TS_SNMP_Get2.4SSIDWithDisabledXfinityWifi Failure
  • RDKBEMU-380 TDK SNMP SNMP Query to get the System Description details is not returning the mandatory fields like HW_REV,SW_REV
  • RDKBEMU-502 Parameters like BytesReceived, PacketsReceived are not getting populated after a successful UDP echo command executed
  • RDKBEMU-569 TDK WIFI HAL wifi_getRadioExtChannel returns an empty string for 2.4Ghz
  • RDKBEMU-570 TDK WIFI HAL Enabling or disabling wifi radio and ssid through hal api is not reflecting in emulator
  • RDKBEMU-582 WIFI wlan0_0 missing following integration of NetworkManager
    • note network manager reverted from this release due to this issue
  • RDKBEMU-585 TDK UserInterface] Device.UserInterface.X_CISCO_COM_RemoteAccess.Enable shows a different value when queried with Device.UserInterface.X_CISCO_COM_RemoteAccess
  • RDKBEMU-586 TDK UserInterface Device.UserInterface.X_CISCO_COM_RemoteAccess.FromAnyIP shows a different value when queried with Device.UserInterface.X_CISCO_COM_RemoteAccess
  • RDKBEMU-589 TDK WIFI HALwifi_getRadioMaxBitRate returns NULL for 2.4GHz and 5GHz
  • RDKBEMU-594 TDK WiFi Set operation with HAL api wifi_setApEnable() is failing for 2.4GHz
  • RDKBEMU-595 TDK WiFi Set operation with HAL api wifi_setApEnable() is failing for 5GHz
  • RDKBEMU-596 TDK WiFi The HAL api wifi_getBaseBSSID() is returning junk value for 2.4GHz
  • RDKBEMU-597 TDK WiFi HAL api wifi_getRadioIfName() not returning expected value for 2.4GHz
  • RDKBEMU-598 TDK WiFi HAL api wifi_getRadioIfName() not returning expected value for 5GHz

Generic TDK Issues:

  • RDKB-9915 TDK Port Triggering Master CcspPandMSsp process crashes when trying to enable a rule added for port triggering
  • RDKB-10750 TDK PAM Master Fails to set the value as "Requested" for Device.IP.Diagnostics.DownloadDiagnostics.DiagnosticsState
  • RDKB-14126 TDK Getting invalid parameter error on setting parameter values for a new PortMapping rule
RDK-V Iteration rdkv-20171228 available
Stephen Barrett posted on Jan 10, 2018

RDK-V iteration rdkv-20171228 is now available.

Baselinenightly/20171228Updates from Comcast 2017-12-28.
Post-baseline updates



TDKM53https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53
Manifestrdkv-20171228

Build System

  • Reference platform builds still have a dependency on podManager.
  • All builds (emulator and reference platforms) now use rdk-oe (Yocto).
  • The old build_framework system is no longer supported.
  • rdk/components/generic/injectedbundle cannot be built by the community because of a dependency on AVE.
  • Root Filesystem uncompressed image sizes:
    • XG1v3 208672 (KiB)
    • XI3v2 197292 (KiB)

Highlights since 20171127

  • Opensourced components:
    • rdk/components/generic/bluetooth, rdk/components/generic/bluetooth_mgr, rdk/components/generic/breakpad_wrapper.
  • Components updated:
    • meta-cmf-bsp-emulator, meta-rdk-bsp-emulator, gst-plugins-rdk-dvr, mediaframework, meta-cmf, meta-cmf-raspberrypi, meta-cmf-video, meta-rdk, meta-rdk-containers, meta-rdk-video, recorder, tr69, westeros, podManager, meta-cmf-restricted, meta-rdk-restricted, audiocapturemgr, bluetooth, bluetooth_mgr, crashupload, dca, devicesettings, hwselftest, iarmmgrs, mocahal, netsrvmgr, rdk_logger, rdkbrowser2, tenableHDCP, servicemanager, storagemanager, mfr_data, mfr_utils,sysint, tr69hostif, xupnp, tdk, tdk-advanced.
  • Patches:
    • Separate patch files for the open-source OE layers are no longer maintained. Instead, from this iteration, mirrors of the OE layers used by RDK are maintained at CMF, containing rdk branches that contain the patches already applied. The RDK build scripts and recipes now all use these instead of the previous patches.
  • Community contributions:
    • 13967 lsof_4.89: drop obsolete .bbappend
    • 13965 Remove perl native overrides in openssl recipe append
    • 13960 (RPI-156) Fix for libWPEBackend-default.so file should be common to all
    • 13944 Remove find.pl override in openssl recipe append
    • 13942 Re-enable md4 in openssl
    • 13941 Re-enable md4 in openssl
    • 13919 Enable breakpad to build in runpod
    • 13899 cryptsetup: drop obsolete .bbappend
    • 13898 pigz: drop obsolete .bbappend
    • 13897 openssl: remove obsolete duplicate copy of find.pl
    • 13895 Remove unneeded code causing seek issue
    • 13860 (RDKCMF-5857) Build support for new/moved components
    • 13578 systemd: Move OE version specific overrides to appropriate bbappend
    • 13830 dnsmasq: remove temp workaround for dnsmasq 2.75
    • 13826 Don't send buffer release until buffer is actually no longer being used
    • 13814 Fix flickering at high framerates on rpi
    • 13805 Revert adding podmgr overrides and removals of podmgr private dependencies
    • 13804 Revert "Add removal of snmpmanager private dependency"
    • 13803 Revert "Add removal of mfr-data dependency"
    • 13784 rdk-rpi.inc: drop PREFERRED_VERSION_systemd
    • 13777 Remove hwselftest from Emulators
    • 13655 (RDKCMF-7939) DVB-SI changes
    • 13623 (RDKCMF-7937) Modify include directory
    • 13622 (RDKCMF-7936) Add RMFQAMSRCPRIV_H_ guards
    • 13609 (RDKCMF-7934) rmfApp: add tune:// as QAM_SOURCE
    • 13621 (RDKCMF-7935) Add option to define "symbol_rate" in sidb.xml
    • 13436 (RDKCMF-7919) Support for coverity in RDK-V components.
    • 13435 (RDKCMF-7918) Support for coverity in emulator components.
    • 13423 (RDKCMF-7914) : Support for static analysis on tr69agent
    • 13420 (RDKCMF-7913) : Support for static analysis on audiocapturemgr
    • 13417 (RDKCMF-7912) : Support for static analysis on westeros
    • 13412 (RDKCMF-7910) : Support for static analysis on bluetooth
    • 13677 (RDKCMF-7942) RMF streamer build failure due to recorder ipdvr
    • 13703 Add optional fps output logs for gl render module
    • 13702 Add external source support for gst-plugins-playersinkbin-rpi build
    • 13701 Update tdk override to fix podmgr dependency
    • 13528 Modifying code to support 64 bit platforms for accessing decoderHandle
    • 13676 Update tdk override to fix podmgr dependency
    • 13434 (RPI-130) COSA_INTEL_USG_ATOM flag not required for RPi
    • 13654 Add removal of mfr-data dependency
    • 13653 Add removal of snmpmanager private dependency
    • 13652 Add podmgr overrides and removals of podmgr private dependencies
    • 13649 Add RDK-M header
    • 13650 Add RDK-M header
    • 13595 raspberrypi3-64-rdk-broadband-musl.conf: add machine config for musl testing
    • 13570BD-323 remove jsonrpc recipe append.
    • 13521 Fix fullscreen playback at various output resolutions
    • 13265 (RPI-136) : (Morty)systemd build failure for RDKV Hybrid
    • 13490 More resolution change fixes and misc cleanup
    • 13474 BLDK-512, BLDK-517 Update getProcInfo and getResidentMemory
    • 13473 (RDKCMF-7753) Revert " Remove obsolete file."
    • 13470 Remove leading spaces in dnsmasq_2.75.bbappend
    • 13469 Update utopia 0001-fix-lan-handler-for-rpi.patch


A detailed changelog since the last iteration (rdkv-20171127) can be found here.

Details of all RDK-V releases and iterations can be found here

Building for RaspberryPi Hybrid

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-20171228-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment

Select option raspberrypi-rdk-hybrid.conf

$ bitbake rdk-generic-hybrid-wpe-image

Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-hybrid folder

Building for RaspberryPi Mediaclient

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-20171228-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment

Select option raspberrypi-rdk-mc.conf

$ bitbake rdk-generic-mediaclient-wpe-image

Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-mc folder


Documentation for RDK-V on RaspberryPi is available at: 

Media Gateway Hybrid (RaspberryPi)-2.1-krogoth

Media Client (RaspberryPi)-2.1-Krogoth

RaspberryPi Sanity Testing

Some basic sanity tests were performed on the Hybrid and Client images, playing video locally via gst-play and also using WPELauncher.

In addition streaming tests were performed using rmfApp.

Known Issues

TDK M53 or later must be used to test this release as prior versions of TDK Manager are not compatible with the TDK Agent in this release due to a recent change in the TDK JSON RPC version

  • Emulators:
    • TDK-346 RDK-V CMF Emulators xcal-device service and xdiscovery not running
      • Causes most XUPNP tests to fail, issue (which is a work around procedure) is marked as resolved but the underlying issue won't be addressed until dependency on POD manager issue is removed
      • The output.json file created by this service is required for a number of the E2E tests, we have worked around this by creating the /opt/output.json file on hybrid and media client as follows:
        {"playbackUrl": "http://<hybrid IP>:8080/hnStreamStart?deviceId=<hybrid mac address>&DTCP1HOST=<hybrid IP>&DTCP1PORT=5000"}
e.g. {"playbackUrl": "http://192.168.21.234:8080/hnStreamStart?deviceId=08:bb:83:b3:b3:07&DTCP1HOST=192.168.21.234&DTCP1PORT=5000"}
    • TDK-354 RDKV Emulator Testing Script Time Outs
      • We are observing inconsistency in some of the E2E tests results, i.e. tests may sometimes pass and sometimes fail with a SCRIPT TIMEOUT error
    • TDK-292 RDKV Emulator-HYB recorder failures
      • requires DVR Simulator (refer to TDK-277)
    • TDK-380 RDKV Emulator "No such file or directory:" retrieving recordDetails.txt
    • TDK-381 RDKV Emulator RMF_HNSrc_MPSink GetMediaTime() Failures
    • TDK-436 RDKV EMU E2E and RMF Regressions Post JSON RPC Updates
  • RPI:
    • RPI-125 RDKV Hybrid: ssh services not working on bring up
    • RPI-160 RDKV Mediaclient:ssh services not working
  • Platforms:
    • RDK-283 Absence of POD in CMF image blocks RMF system level functionality
      • xcal device service doesn't start, so /opt/output.json file required by E2E tests not created we have worked around this by creating the tmp/ip_acquired file, with this workaround we can run TDK E2E tests
    • TDK-277 Testing of Recorder component will remain blocked until DVR Simulator code is available
    • TDK-276 Subset of Recorder tests still consistently failing for CMF
    • TDK-387 RDKV Platform XG1V3 XUPNP Event not received by xcal-device process
    • TDK-388 RDKV Platform XG1V3 RMF MPSink Set Volume Errors
    • TDK-389 RDKV Platform E2E Tests Failures "HNSource play failed current state not playing"