• Created by Unknown User (sbarrett), last modified on Jun 29, 2017

This is the summary page that describes the CMF RDK-B iteration rdkb-20170626.

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

 

BaselineCMF-201706262017-06-26 baseline.
Post-baseline updates  
TDKM48

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

Manifestrdkb-20170626 

Highlights since 20170523

  • New components: rdkb/components/opensource/ccsp/CcspXDNS, rdkb/components/opensource/ccsp/webpa-broadband.
  • Components updated:
    • CcspCommonLibrary, CcspCr, CcspLMLite, CcspMisc, CcspMoCA, CcspPandM, CcspPsm, CcspSnmpPa, CcspTr069Pa, CcspWifiAgent, TestAndDiagnostic, Utopia, Xconf, hal, halinterface, sysint, webui, rdkb/devices/raspberrypi/hal, rdkb.
  • Patches updated:
    • patches/rdk-oe
  • Community contributions: 

Getting the code

$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20170626
$ 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-20170626 in the build sequence above specifies the branch to use. If you omit the -b rdkb-20170626 entirely, you will get the master (HEAD) of each component.
  • At any time, the community can build latest master by dropping the -b rdkb-20170626 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 the emulator

$ source meta-cmf-rdkb-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 for RDK-B documentation is available: https://wiki.rdkcentral.com//display/TDK/TDK+Release+M48

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-20170626-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://rdkwiki.com/rdk/display/DEVTOOLS/RDK+Broadband+%28RaspberryPi%29+-Krogoth

Running on the RaspberryPi

Known Issues

General:

  • TCL tests not run for RPI or Emulator, TCL scripts and script execution will be resumed once the scripts are stabilized
  • Some of the TDK advanced config scripts are causing the PAM process to deadlock or crash on the RDKB Emulator
    • Several issues are raised on RDBK Emulator (RDKBEMU-436, RDKBEMU-458, RDKBEMU-477)
  • Some TDK TS_TAD emulator tests fail in CMF test setup due to security restrictions with test setup

TDK Issues:

  • TDK-362 RDKB EMU TS_WIFIAGENT_EnableAccessPoint kills hostapd.service
    • RDKBEMU-475 raised, setting Device.WiFi.SSID.1.Enable/Device.WiFi.SSID.2.Enable to true kills hostapd, reboot resolves
  • TDK-364 RDKB-RPI TDK TS_WIFIAGENT_AccessPointRetryLimit Fail
  • TDK-366 RDKB-EMU Setting Device.WiFi.Radio.1.X_CISCO_COM_ApplySetting kills hostapd.service
    • RDKBEMU-481 raised
  • TDK-367 RDKB-EMU TS_SNMP_SetSSIDEnable tests kill hostapd service
    • RDKBEMU-483 raised
  • TDK-368 RDKB-EMU Intermittent Segfault in CcspWiFiAgent.service
    • observed intermittent segfault when running TS_WIFIAGENT_FactoryReset test on emulator, reboot resolves

RPI Issues:

  • RPI-7 Randomly observing boot up issue in RaspberryPI broadband
  • RPI-29 SSID Name of WIFI 2.4 and 5GHZ not getting reverted to default SSID Name after doing WIFI factory reset
    • TS_WIFIAGENT_FactoryReset failure
  • RPI-30 KeyPassPhrase of WIFI 2.4 and 5GHZ not getting reverted to default password after doing WIFI factory reset
    • TS_WIFIAGENT_5GHZ_PassphraseAfterReset failure
  • No labels