CMF

RDK Releases

Documentation

CMF Videos

Support
Support for CMF is provided by the RDK Support group.

To contact RDK Support:
Enter a ticket: https://jira.rdkcentral.com/
or
E-mail: support@rdkcentral.com

Child pages
  • RDK-B_20180426
Skip to end of metadata
Go to start of metadata

This is the summary page that describes the CMF iteration rdkb-20180426. Below are links to the relevant documents for the release.

Note: The latest rdkb iteration addresses licensing issues so users are advised to move to the latest iteration.

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

A detailed changelog since the last iteration RDK-B_20180325 can be found here.


Baseline

Baselinenightly/2018042620180426 baseline.
Post-baseline updates  
TDKM57https://wiki.rdkcentral.com/display/TDK/TDK-B+Release+M57
Manifestrdkb-20180426 


Highlights since RDK-B_20180325

  • Components updated:

    • crashupload, rdk_logger, rdm, CcspCommonLibrary, CcspHomeSecurity, CcspLMLite, CcspMoCA, CcspPandM, CcspPsm, CcspSnmpPa, CcspTr069Pa, CcspWifiAgent, GwProvApp, GwProvApp-ePON, TestAndDiagnostic, Utopia, Xconf, hal, halinterface, hotspot, sysint, webui, rdkb/devices/intel-x86-pc/emulator/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, 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:

    • A detailed changelog since the last iteration RDK-B_20180325 can be found here.


Getting the code

Note: The manifests repository is only available to RDK licensees.

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


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: release M57


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


Running on the RaspberryPi

Please see RDK Broadband (RaspberryPi)


Documentation for RDK-B on RaspberryPi

RDK Broadband (RaspberryPi)


RaspberryPi Sanity Testing

Sanity tests include:

  • Wifi 2.4Ghz and 5Ghz hotspot testing.
  • Login, menu navigation, parameter modification, e.g. Wifi SSID/password change and re-connection, changing admin password.


Known Issues

Known issues are detailed here.

  • No labels