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
RDK-B iteration rdkb-20180123 is now available. Below are links to the relevant documents for the iteration.
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 | nightly/20180123 | 2018-01-23 baseline. |
Post-baseline updates | ||
TDK | M54 | |
Manifest | rdkb-20180123 |
$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20180123
$ 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-20180123
in the build sequence above specifies the branch to use. If you omit the -b rdkb-20180123
entirely, you will get the master (HEAD) of each component.-b rdkb-20180123
option in the repo init command.$ 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: https://wiki.rdkcentral.com/display/TDK/TDK+Release+M54
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$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-20180123-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
Please see RDK Broadband (RaspberryPi) -Krogoth.
RPI Issues:
Emulator Issues:
Generic TDK Issues:
RDK-V release rdkv-2017q4 is now available.
Baseline | nightly/20171228 | Updates from Comcast 2017-12-28. |
Post-baseline updates | ||
TDK | M53 | https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53 |
Manifest | rdkv-2017q4 |
Details of all RDK-V releases and iterations can be found here
rdk-oe
(Yocto).$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-2017q4-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment
Select option raspberrypi-rdk-hybrid.conf
$ bitbake rdk-generic-hybrid-wpe-image
Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-hybrid
folder
$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-2017q4-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment
Select option raspberrypi-rdk-mc.conf
$ bitbake rdk-generic-mediaclient-wpe-image
Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-mc
folder
Documentation for RDK-V on RaspberryPi is available at:
Media Gateway Hybrid (RaspberryPi)-2.1-krogoth
Media Client (RaspberryPi)-2.1-Krogoth
Some basic sanity tests were performed on the Hybrid and Client images, playing video locally via gst-play and also using WPELauncher.
In addition streaming tests were performed using rmfApp.
TDK M53 or later must be used to test this release as prior versions of TDK Manager are not compatible with the TDK Agent in this release due to a recent change in the TDK JSON RPC version
{"playbackUrl": "http://<hybrid IP>:8080/hnStreamStart?deviceId=<hybrid mac address>&DTCP1HOST=<hybrid IP>&DTCP1PORT=5000"} e.g. {"playbackUrl": "http://192.168.21.234:8080/hnStreamStart?deviceId=08:bb:83:b3:b3:07&DTCP1HOST=192.168.21.234&DTCP1PORT=5000"}
RDK-B release rdkb-2017q4 is now available. Below are links to the relevant documents for the release.
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 | nightly/20171228 | 2017-12-28 baseline. |
Post-baseline updates | revert changes 13738, 13840 | |
TDK | M53 | |
Manifest | rdkb-2017q4 |
$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-2017q4
$ 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-2017q4
in the build sequence above specifies the branch to use. If you omit the -b rdkb-2017q4
entirely, you will get the master (HEAD) of each component.-b rdkb-2017q4
option in the repo init command.$ 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: https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53
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$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-2017q4-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
Please see RDK Broadband (RaspberryPi) -Krogoth.
TDK M53 or later must be used to test this release as prior versions of TDK Manager are not compatible with the TDK Agent in this release due to a recent change in the TDK JSON RPC version
RPI Issues:
Emulator Issues:
Generic TDK Issues:
RDK-B iteration rdkb-20171228 is now available. Below are links to the relevant documents for the iteration.
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 | nightly/20171228 | 2017-12-28 baseline. |
Post-baseline updates | revert changes 13738, 13840 | |
TDK | M53 | |
Manifest | rdkb-20171228 |
$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20171228
$ 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-20171228
in the build sequence above specifies the branch to use. If you omit the -b rdkb-20171228
entirely, you will get the master (HEAD) of each component.-b rdkb-20171228
option in the repo init command.$ 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: https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53
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$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-20171228-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
Please see RDK Broadband (RaspberryPi) -Krogoth.
TDK M53 or later must be used to test this release as prior versions of TDK Manager are not compatible with the TDK Agent in this release due to a recent change in the TDK JSON RPC version
RPI Issues:
Emulator Issues:
Generic TDK Issues:
RDK-V iteration rdkv-20171228 is now available.
Baseline | nightly/20171228 | Updates from Comcast 2017-12-28. |
Post-baseline updates | ||
TDK | M53 | https://wiki.rdkcentral.com/display/TDK/TDK+Release+M53 |
Manifest | rdkv-20171228 |
rdk-oe
(Yocto).build_framework
system is no longer supported.A detailed changelog since the last iteration (rdkv-20171127) can be found here.
Details of all RDK-V releases and iterations can be found here
$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-20171228-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment
Select option raspberrypi-rdk-hybrid.conf
$ bitbake rdk-generic-hybrid-wpe-image
Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-hybrid
folder
$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-20171228-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment
Select option raspberrypi-rdk-mc.conf
$ bitbake rdk-generic-mediaclient-wpe-image
Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-mc
folder
Documentation for RDK-V on RaspberryPi is available at:
Media Gateway Hybrid (RaspberryPi)-2.1-krogoth
Media Client (RaspberryPi)-2.1-Krogoth
Some basic sanity tests were performed on the Hybrid and Client images, playing video locally via gst-play and also using WPELauncher.
In addition streaming tests were performed using rmfApp.
TDK M53 or later must be used to test this release as prior versions of TDK Manager are not compatible with the TDK Agent in this release due to a recent change in the TDK JSON RPC version
{"playbackUrl": "http://<hybrid IP>:8080/hnStreamStart?deviceId=<hybrid mac address>&DTCP1HOST=<hybrid IP>&DTCP1PORT=5000"} e.g. {"playbackUrl": "http://192.168.21.234:8080/hnStreamStart?deviceId=08:bb:83:b3:b3:07&DTCP1HOST=192.168.21.234&DTCP1PORT=5000"}
RDK-B iteration rdkb-20171127 is now available. Below are links to the relevant documents for the iteration.
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 | CMF-20171127 | 2017-11-27 baseline. |
Post-baseline updates | ||
TDK | M52 | |
Manifest | rdkb-20171127 |
$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20171127
$ 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-20171127
in the build sequence above specifies the branch to use. If you omit the -b rdkb-20171127
entirely, you will get the master (HEAD) of each component.-b rdkb-20171127
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
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
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$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-20171127-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
Please see RDK Broadband (RaspberryPi) -Krogoth.
RPI Issues:
Emulator Issues:
Generic TDK Issues:
RDK-B iteration rdkb-20171030 is now available. Below are links to the relevant documents for the iteration.
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 | CMF-20171030 | 2017-10-30 baseline. |
Post-baseline updates | ||
TDK | M52 | |
Manifest | rdkb-20171030 |
$ 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
-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-20171030
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.-b rdkb-20171030
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
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
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$ 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
Please see RDK Broadband (RaspberryPi) -Krogoth.
RPI Issues:
Emulator Issues:
Generic TDK Issues:
RDK-V iteration rdkv-20171030 is now available.
Baseline | CMF-20171030 | Updates from Comcast 2017-10-30. |
Post-baseline updates | tdk: f3d5847b | |
TDK | M52 | https://wiki.rdkcentral.com/display/TDK/TDK+Release+M52 |
Manifest | rdkv-20171030 |
Emulators:
{"playbackUrl": "http://<hybrid IP>:8080/hnStreamStart?deviceId=<hybrid mac address>&DTCP1HOST=<hybrid IP>&DTCP1PORT=5000"} e.g. {"playbackUrl": "http://192.168.21.234:8080/hnStreamStart?deviceId=08:bb:83:b3:b3:07&DTCP1HOST=192.168.21.234&DTCP1PORT=5000"}
Platforms:
rdk-oe
(Yocto).build_framework
system is no longer supported.$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-20171030-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment
Select option raspberrypi-rdk-hybrid.conf
$ bitbake rdk-generic-hybrid-wpe-image
Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-hybrid
folder
$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-20171030-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment
Select option raspberrypi-rdk-mc.conf
$ bitbake rdk-generic-mediaclient-wpe-image
Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-mc
folder
Documentation for RDK-V on RaspberryPi is available at:
Media Gateway Hybrid (RaspberryPi)-2.1-krogoth
Media Client (RaspberryPi)-2.1-Krogoth
Some basic sanity tests were performed on the Hybrid and Client images, playing video locally via gst-play and also using WPELauncher.
In addition streaming tests were performed using rmfApp.
A detailed changelog since the last iteration (rdkv-20170925) can be found here.
Details of all RDK-V releases and iterations can be found here
RDK-B release rdkb-2017q3 is now available. 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-20170929 | 2017-09-29 baseline. |
Post-baseline updates | webui cc93f1d meta-rdk 948ab27 meta-cmf-raspberrypi 68ec285 meta-cmf-raspberryp 0c69589 | |
TDK | M51 | |
Manifest | rdkb-2017q3 |
$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-2017q3
$ 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-2017q3
in the build sequence above specifies the branch to use. If you omit the -b rdkb-2017q3
entirely, you will get the master (HEAD) of each component.-b rdkb-2017q3
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
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+M51
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$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-2017q3-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
Please see RDK Broadband (RaspberryPi) -Krogoth.
General:
RPI Issues:
Emulator Issues:
Generic TDK Issues:
RDK-B iteration rdkb-20170929 is now available. Below are links to the relevant documents for the iteration.
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 | CMF-20170929 | 2017-09-29 baseline. |
Post-baseline updates | webui cc93f1d meta-rdk 948ab27 meta-cmf-raspberrypi 68ec285 meta-cmf-raspberryp 0c69589 | |
TDK | M51 | |
Manifest | rdkb-20170929 |
$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20170929
$ 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-20170929
in the build sequence above specifies the branch to use. If you omit the -b rdkb-20170929
entirely, you will get the master (HEAD) of each component.-b rdkb-20170929
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
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+M51
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$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-20170929-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
Please see RDK Broadband (RaspberryPi) -Krogoth.
General:
RPI Issues:
Emulator Issues:
Generic TDK Issues:
RDK-V iteration rdkv-20170925 is now available.
Baseline | CMF-20170925 | Updates from Comcast 2017-09-25. |
Post-baseline updates |
| |
TDK | M51 | https://wiki.rdkcentral.com/display/TDK/TDK+Release+M51 |
Manifest | rdkv-20170925 |
Emulators:
{"playbackUrl": "http://<hybrid IP>:8080/hnStreamStart?deviceId=<hybrid mac address>&DTCP1HOST=<hybrid IP>&DTCP1PORT=5000"} e.g. {"playbackUrl": "http://192.168.21.234:8080/hnStreamStart?deviceId=08:bb:83:b3:b3:07&DTCP1HOST=192.168.21.234&DTCP1PORT=5000"}
Platforms:
rdk-oe
(Yocto).build_framework
system is no longer supported.$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-20170925-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment
Select option raspberrypi-rdk-hybrid.conf
$ bitbake rdk-generic-hybrid-wpe-image
Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-hybrid
folder
$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkv.xml –b rdkv-20170925-rpi
$ repo sync -j4 --no-clone-bundle
$ source meta-cmf-raspberrypi/setup-environment
Select option raspberrypi-rdk-mc.conf
$ bitbake rdk-generic-mediaclient-wpe-image
Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-mc
folder
Documentation for RDK-V on RaspberryPi is available at:
Media Gateway Hybrid (RaspberryPi)-2.1-krogoth
Media Client (RaspberryPi)-2.1-Krogoth
Some basic sanity tests were performed on the Hybrid and Client images, playing video locally via gst-play and also using WPELauncher.
In addition streaming tests were performed using rmfApp.
A detailed changelog since the last iteration (rdkv-20170830) can be found here.
Details of all RDK-V releases and iterations can be found here
RDK-B iteration rdkb-20170830 is now available. Below are links to the relevant documents for the iteration.
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 | CMF-20170830 | 2017-08-30 baseline. |
Post-baseline updates | ||
TDK | M50 | |
Manifest | rdkb-20170830 |
$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20170830
$ 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-20170830
in the build sequence above specifies the branch to use. If you omit the -b rdkb-20170830
entirely, you will get the master (HEAD) of each component.-b rdkb-20170830
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
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+M50
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$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-20170830-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
General:
RPI Issues:
Emulator issues:
Generic TDK Issues:
RDK-V iteration rdkv-20170830 is now available.
Baseline | CMF-20170830 | Updates from Comcast 2017-08-30. |
Post-baseline updates |
| |
TDK | M50 | https://wiki.rdkcentral.com/display/TDK/TDK+Release+M50 |
Manifest | rdkv-20170830 |
Emulators:
{"playbackUrl": "http://<hybrid IP>:8080/hnStreamStart?deviceId=<hybrid mac address>&DTCP1HOST=<hybrid IP>&DTCP1PORT=5000"} e.g. {"playbackUrl": "http://192.168.21.234:8080/hnStreamStart?deviceId=08:bb:83:b3:b3:07&DTCP1HOST=192.168.21.234&DTCP1PORT=5000"}
Platforms:
rdk-oe
(Yocto).build_framework
system is no longer supported.New components:
devices/intel-x86-pc/rdkemulator/mfrlibs.
A detailed changelog since the last iteration (rdkv-20170724) can be found here.
Details of all RDK-V releases and iterations can be found here
RDK-B iteration rdkb-20170803 is now available. Below are links to the relevant documents for the iteration.
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 | CMF-20170803 | 2017-08-03 baseline. |
Post-baseline updates | ||
TDK | M50 | |
Manifest | rdkb-20170803 |
$ mkdir rdkb
$ cd rdkb
$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkb.xml -b rdkb-20170803
$ 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-20170803
in the build sequence above specifies the branch to use. If you omit the -b rdkb-20170803
entirely, you will get the master (HEAD) of each component.-b rdkb-20170803
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
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+M50
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$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init –u https://code.rdkcentral.com/r/manifests -m rdkb.xml –b rdkb-20170803-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
General:
RPI Issues:
Emulator TDK issues:
Generic TDK Issues:
RDK-V iteration rdkv-20170724 is now available.
Baseline | CMF-20170724 | Updates from Comcast 2017-07-24. |
Post-baseline updates |
| |
TDK | M49 | https://wiki.rdkcentral.com/display/TDK/TDK+Release+M49 |
Manifest | rdkv-20170724 |
Emulator:
{"playbackUrl": "http://<hybrid IP>:8080/hnStreamStart?deviceId=<hybrid mac address>&DTCP1HOST=<hybrid IP>&DTCP1PORT=5000"} e.g. {"playbackUrl": "http://192.168.21.234:8080/hnStreamStart?deviceId=08:bb:83:b3:b3:07&DTCP1HOST=192.168.21.234&DTCP1PORT=5000"}
Platforms:
rdk-oe
(Yocto).build_framework
system is no longer supported.
A detailed changelog since the last iteration (rdkv-20170626) can be found here.
Details of all RDK-V releases and iterations can be found here