RDK-B_20171030

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

Below are links to the relevant documents for the release.

• RDK-B 20171030 Emulator Test Report (Gerrit)
• RDK-B 20171030 RaspberryPi Test Report (Gerrit)
• A detailed changelog since the last iteration (RDK-B-20170929) can be found here (Gerrit).

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 

Highlights since 20170929

• New components: None.
• Components updated:
  • crashupload, rdk_logger, CcspCMAgent, CcspCommonLibrary, CcspHomeSecurity, CcspLMLite, CcspMisc, CcspMoCA, CcspPandM, CcspPsm, CcspSnmpPa, CcspTr069Pa, CcspWecbController, CcspWifiAgent, GwProvApp, GwProvApp-ePON, PowerManager, TestAndDiagnostic, Utopia, Xconf, hal, halinterface, hotspot, sysint, webui, rdkb/devices/raspberrypi/hal, rdkb/devices/rdkbemu/ccsp/rdkb, meta-westeros-raspberrypi.
• Community contributions: 
  • Please refer to the changelog since the last iteration (RDK-B_20170929) here (Gerrit).

Getting the code

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

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