For more information, including FAQs and resources, please visit the link below:
RDKM-SSO
Any questions or comments please feel free to contact RDK Support team support@rdkcentral.com . Thank you. ***
This is the summary page that describes the CMF RDK-B release 2.1-20161010.
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 | CMF-20161010 | 2016-10-10 baseline. |
Post-baseline updates | ||
TDK | M40 | |
Manifest | rdkb-2.1-20161010 |
$ mkdir rdkb $ cd rdkb $ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-2.1-20161010 $ repo sync -j4 --no-clone-bundle
-m rdkb.xml
in the build sequence above is important. If this is not specified, you will get an RDK-V tree by default.-b rdkb-2.1-20161010
in the build sequence above specifies the branch to use. If you omit the -b rdkb-2.1-20161010
entirely, you will get the master (HEAD) of each component.-b rdkb-2.1-20161010
option in the repo init command.$ 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
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://rdkwiki.com/rdk/display/TDK/TDK-B+Release+01
New
-> Enter name -> Select type Linux
-> Select version Other Linux (32 bit)
-> Click Next
Memory size - 512MB
-> Click Next
Use an existing virtual hard drive
-> Select the built image above -> Click Create
Settings
-> Network
-> Select Attached to: 'Bridged Adapter'
-> Click Ok
Start
.This will bring up the emulator with the initial splash screen