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

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-201705082017-05-08 baseline.
Post-baseline updates  
TDKM47

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

Manifestrdkb-20170508 

Highlights since 20170424

  • New components: None
  • Components updated:
    • crashupload, CcspCommonLibrary, CcspLMLite, CcspMoCA, CcspPandM, CcspPsm, CcspSnmpPa, CcspTr069Pa, CcspWifiAgent, TestAndDiagnostic, Utopia, hal, sysint, webui, hal, rdkb, rdkbemu_xb3, rdkb/devices/raspberrypi/hal.
  • Patches updated: None.
  • Community contributions: 
    • Please refer to the changelog since the last iteration (RDK-B_20170424) here (Gerrit).
    • 9002 RPI-3: [RPI][Broadband] Fails to enable the SSH with TR-181 parameter Device.X_CISCO_COM_DeviceControl.SSHEnable

Getting the code

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

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

  • TCL tests not run for RPI or Emulator, TCL scripts and script execution will be resumed once the scripts are stabilized.
  • RDKBEMU-436 - PAM Randomly the advance config scripts is causing the PAM process to crash or go to a deadlock state
    • Some of the advanced config scripts are causing the PAM process to deadlock or crash. A reboot is required to recover, this issue caused a regression in a number of tests.
  • TDK-355 - RDK-B TS_SNMP "no such object at this OID issue" failures due to snmp_subagent.service failing
    • snmp_subagent service is not running. Because of this the communication between ccsp-snmp-subagent and NET SNMP agent is broken and any SNMP scripts queries to the OIDs in range .1.3.6.1.4.1.17270.44.1.2.1 fail
  • RDKBEMU-418: Ping to outside world not working with specific emulator Network configuration.
  • TDKB-29 - TS_SNMP_Get2.4SSIDWithDisabledXfinityWifi is causing the other SNMP scripts to fail. This test case is skipped in Emulator.
  • TDK-341 - RDK-B Emulator TS_PAM_IpIfMaxMTUSize fails on CMF image
    • RDKBEMU-406 raised on emulator
  • TDK-342 - RDK-B Emulator SNMP Tests - No Such Instance currently exists at this OID
    • TS_SNMP_Get2.4SSIDWithDisabledXfinityWifi tests fails in automated run but passes in manual run under investigation
  • TDK-344 - RDK-B Emulator TS_TAD traceroute test failures on CMF image
    • TS_TAD_Traceroute test fail in CMF evironement due to some security restrictions with test setup
  • TDK-348 - TDK-B RPI RDK Logger Tests Failiing
  • RPI-2 - Value of Device.WiFi.Radio.2.AutoChannelEnable is getting changed to "false" when Device.WiFi.Radio.2.X_CISCO_COM_ApplySetting is applie
  • RPI-7 - Randomly observing boot up issue in RaspberryPI broadband
  • RPI-19 - TFTP log transfer is not happening with the erouter0 interface
  • RPI-21 - DNS Client Allows to set value for Device.DNS.Client.Server.1.DNSServer even if the Device.DNS.Client.Server.1.Type is not Static
  • RPI-22 - Setting the security mode as WPAWPA2-PSK (TKIP/AES) is making the WIFI client to connect to the SSID with the Authentication Mode as "WPA-Personal" instead of "WPA2-Personal"
  • No labels