Mask the recipe in platform specific MACHINE conf file and run the source command again to build.

For example, to MASK ccsp-gwprovapp-ethwan in Rpi build, add below line in Rpi specific Machine conf file. Add below line in file

“meta-cmf-raspberrypi/conf/machine/raspberrypi-rdk-broadband.conf ”

BBMASK .= "|.meta-rdk-broadband/recipes-ccsp/ccsp/ccsp-gwprovapp-ethwan.bb"

Run the source command again to build

source meta-cmf-raspberrypi/setup-environment  ->  select respective conf file

If you encounter below error,

repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.
Downloading Repo source from https://gerrit.googlesource.com/git-repo
remote: Counting objects: 1, done
remote: Finding sources: 100% (41/41)
remote: Total 41 (delta 14), reused 41 (delta 14)
Unpacking objects: 100% (41/41), done.
Traceback (most recent call last):
File "<File Path>", line 56, in <module>
from subcmds.version import Version
File "<File Path>", line 38, in <module>
['%s' % name])
File "<File Path>", line 27, in <module>
from hooks import RepoHook
File "<File Path>", line 472
file=sys.stderr)
^
SyntaxError: invalid syntax

Upgrade the repo using below command to use with python3.

curl https://storage.googleapis.com/git-repo-downloads/repo-1 > ~/bin/repochmod a+x ~/bin/repopython3 ~/bin/repo init -u <repo URL>python3 ~/bin/repo sync

Make sure that the build machine is having required packages installed for specific Yocto flavor.
Eg: https://docs.yoctoproject.org/3.2.3/ref-manual/ref-system-requirements.html

Metadata represents the versions of the various components in a distribution, such as the particular versions of the Linux kernel or libraries. The project supplies an example set of metadata that can generate several example distributions. The actual metadata used for the construction of a custom distribution may be supplied by a commercial vendor or created by an embedded developer. The root filesystem is defined in the metadata for a given build of a distribution.

There are tools within BitBake that enable this level of details.

• “bitbake -g targetname” creates depends.dot and task-depends.dot files in the current directory. These files show which packages and tasks depend on which other packages and tasks and are useful for debugging purposes.
• "bitbake -g -u depexp targetname" shows results in a more human-readable, GUI style. A simple mount of the resulting root image will show how much storage space is being used.

In addition, the toaster is a new graphical user interface for BitBake that makes these tools much easier to use.

As with any complex system, the real answer is it depends, but of course that is not very helpful. The simplest method for adding a single package to your build is to add 

the below line to conf/local.conf:

• IMAGE_INSTALL_append = " package"

Use your own package name in place of package. Note the leading space before the package name. If you want to add multiple packages, you can use multiple lines like the above, or list all packages on a single line with:

• IMAGE_INSTALL_append = " package1 package2 package3"

Although If you add in local.conf , that is not permanent change. For permanent addition of that package in final rootfs, you need to be added in image recipe or any package group which is included in the image recipe.

Prebuilds are handled internally by Yocto by using sstate-cache. If a prebuilt from a known good build is available, the build can point to that folder via the conf file inside the ./build<buildtype>/conf/ folder so that the prebuilts are picked up from the location

This depend entirely on multiple factors like capacity of build machine, first time build or repeated build in the same work space as well as changes in components on which the component in question depends on( if there is a change, the depending component is first built and then the dependent component ) and hence cannot be answered directly.

When you checkout sandbox every component is independently buildable, and bitbake ( OE's build engine) is responsible to identify and sort the component dependency chain and ensure its built along. if you were to build a single component the commands are

bitbake <component>

where component is in one to one relation with .bb ( recipe ) file that can be found in the Yocto/OE metadata ( meta-rdk* layers ) e.g. if you were to build rdkbrowser then you would see that its recipe is housed in generic layer called meta-rdk-cmf and recipe is called rdkbrowser.bb so the command would be

bitbake rdkbrowser

However this will only generate CMF component and for packaging it up into final image you still have to build the image component to repackage rdkbrowser

bitbake rdk-generic-hybrid-wpe-image

would generate the CMF generic image for hybrid devices. it will only rebuild the affected components when building the image if nothing has changed it will not recreate the image.

bitbake has division of work into individual tasks for a component. Secondly, the recipes are wired to notice changes in upstream repository as well when you do repo sync. You can use below command to see what all individual tasks are available.

bitbake -c listtasks <component>

It will show an output like

do_build                       Default task for a recipe - depends on all other normal tasks required to 'build' a recipe

do_bundle_initramfs            Combines an initial ramdisk image and kernel together to form a single image

do_checkuri                    Validates the SRC_URI value

do_checkuriall                 Validates the SRC_URI value for all recipes required to build a target

do_clean                       Removes all output files for a target

do_cleanall                    Removes all output files, shared state cache, and downloaded source files for a target

do_cleansstate                 Removes all output files and shared state cache for a target

do_compile                     Compiles the source in the compilation directory

You can rerun any of the above tasks

bitbake -C compile rdkbrowser

would force recompile of servicemanager, if you wish to perform all the build steps for a component you can do that too by

bitbake -c cleansstate rdkbrowser; bitbake rdkbrowser

Similarly, in general you can have:

bitbake <target> -c<task_to_be_executed>

This will ensure do_<task_to_be_executed>() will be called.

task_to_be_executed can  fetch, unpack, configure, compile, install, package etc

If we were to draw parallels

--rebuild = bitbake -c cleansstate <component> ; bitbake <component>

--build-only = bitbake <component>

--skip-package is delegated to shared state mechanism to figure out at present.

Unless you do 'repo sync' sources will not be updated

'repo sync' can cover only components with external src support, it means that in cases when SRCREV is set to AUTOREV and component doesn't support external src, then bitbake will try to update sources from a remote repository during build time.

There is no documentation for AUTOREV, but it's doing only one function - check remote repository for any new sources updates.

You can prevent this behaviour by changing BB_SRCREV_POLICY variable in you local <sandbox>/conf/local.conf

These are OE metadata variables, bitbake has preprocessing options where it expands all the local bitbake variables so you could take advantage of that option to figure it out

bitbake -e rf4ce | grep "^S ="

bitbake -e rf4ce | grep "^WORKDIR ="

It can be used to check for any bitbake variable, alternatively you can pipe the whole bitbake -e output to a file and inspect the file in your favourite editor

• You can find log files for each task in the recipe's temp directory. Log files are named log.taskname-Eg:compile logs are present in the file log.do_compile. Bitbake maintains logs separately for each of the tasks that run while building the component. These tasks are typically the fetch task, the compile task, install task and so on.
• Eg: For a RPI device, typically logs are present under the build-raspberrypi-rdk-hybrid//tmp/work/<*-rdk-linux> and under the component directory. Other devices would have logs present under similar folders. For instance, logs are present under build-raspberrypi-rdk-hybrid/tmp/work/<*-rdk-linux>/rdkbrowser/1.99+gitAUTOINC+8c3f17fdc6_fa6c8b4334_dc33f7d6bc_4bc1f2f4c9-r0/temp

The warnings like -Werror -Wall -Wextra are turned on for compiler for most of the Ccsp components .All these warnings must be fixed for successful compilation as all warnings are treated as errors.

Werrors due to unused parameters in code can be fixed by using:

UNREFERENCED_PARAMETER(user_data); ,if user_data variable is not used in the scope of definition of the function .

* satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-...:

*             net-snmp *

* opkg_install_cmd: Cannot install package packagegroup-....

The above error indicates that :

You asked for adding net-snmp ( the package ) not ( the recipe ) now net-snmp ( the recipe ) may generate a number of ( packages ) so you should add the packages ( runtime items) to the package groups and not the recipes ( build time items). Usually yocto/OE does generate a output package with same name as input recipe so for net-snmp.bb there will be a net-snmp ipk but thats just a common case not a hard and fast rule.

Now in this particular case when a package has nothing to emit into the ${PN} package the package is left empty and hence not emitted. If you want to emit the package regardless you have to add

ALLOW_EMPTY_<package> = "1" in the recipe,but this is less of a usecase to demand empty packages. If you expressed the packagegroup RDEPENDS correctly you would not need it.

sstate-cache is always adding new versions and hence is growing in size always, thankfully we have a tool in Yocto to manage it, here is a sample on how to do it for raspberrypi you can set WORKSPACE and MACH variables to point to the values for machine
sstate-manage.sh

 To enable kernel/busybox features you can append metadata to the recipes (i.e. .bb files) by simply creating an append file (i.e. .bbappend files) and including metadata in it. If the features needs to be enabled across all the platforms then add in meta-rdk-rpi meta or if it's specific to a platform then append to the recipes available in OEM layer specific to the platform.

Below example shows how to enable IPSec on Yocto builds:  

• Create a stblinux_%.bbappend
• Create a file called enable_netkey.cfg with following content 
     CONFIG_NET_KEY=y
• Add SRC_URI_append = “file://enable_netkey.cfg "

Make sure .bbappend has the same root name as their corresponding .bb recipes.

• Sometimes when you have a working branch which is not checked out or has uncommitted changes then repo will fail when you try to sync to the latest code base.

• Sample failure logs:

error: generic/devicesettings/generic/: contains uncommitted changes

error: generic/rdkbrowser/: branch master is published (but not merged) and is now 11 commits behind

error: meta-rdk-oem-X/: contains uncommitted changes

• To resolve this you need to checkout the branch and rebase it to the master using below commands.

git rebase —abort

git rebase rdkgerrit/master ( or rdkgerrit/stable2)

• During the process git might throw conflict errors if it cannot merge files automatically. Then you need to merge manually using Vim or any other text editors. But it can be simple if you know exactly what changes needs to be saved / removed.
• For example you can use below command to keep your changes

git checkout --ours FILE

• If you want to run on multiple files then use below command.

grep -lr ‘<<<<<<<<’.  |  xargs git checkout --ours

• Similarly,  you can use below commands if you want to keep other changes.

git checkout --yours FILE

grep -lr ‘<<<<<<<<’.  |  xargs git checkout –theirs

• Verify the files from which recipe they are being generated under build-<platform>/buildhistory/packages/mips32el-rdk-linux folder
• Add the below line format under that particular recipe.

FILES_${PN}-dev += " file1 file2 etc"

• Verify that cat <package>-dev/latest  should contain these files under FILELIST. 

Yocto project build system has a utility which can provide information about which package (ipk or rpm) is providing a given file, this helps in finding further information on packaging e.g. if you want to do more finer packaging, run the following command in your build environment

oe-pkgdata-util find-path /lib/libc.so.6
glibc: /lib/libc.so.6

Common build failures are reported in Yocto builds. Some build failures are hard to analyze with logs, unless we get access to the failure workspace. In most cases they are hard to reproduce on local workspace. We go through multiple iteration of builds, lock down the node and then debug. To debug these failures use Packages file found under tmp/deploy/ipk directory on you local workspace .

The signal core dump that are generated under /tmp can be decoded using gdb
Procedure :

1. In <image>.bbappend file
   IMAGE_INSTALL_append = " gdb"
2. In local.conf
   INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3.0"
   INCOMPATIBLE_LICENSE_pn-gdb = ""
   EXTRA_IMAGE_FEATURES += "tools-debug"
   EXTRA_IMAGE_FEATURES += "dbg-pkgs"
3. In <component>.bbappend
   CFLAGS += " -D_DEBUG -g "
4. Compile and flash the binary to device
5. Run gdb -c <path to signal dump> <binary>

This should be because of architecture bit mismatch . To overcome this should either choose the right target platform or put the executable file as a tar file in bb file.

Issue:

While building the stack, the bitbake process will be aborted if the disk space runs low beyond the minimum requirement.

Example console log:

WARNING: The free space of /mnt/home/gpsahu01/cmf/test/build-qemux86hyb/tmp (/dev/vdb) is running low (0.999GB left)

ERROR: No new tasks can be executed since the disk space monitor action is "STOPTASKS"!

WARNING: The free space of /mnt/home/gpsahu01/cmf/test/downloads (/dev/vdb) is running low (0.095GB left)

ERROR: Immediately abort since the disk space monitor action is "ABORT"!

NOTE: Sending SIGTERM to remaining 1 tasks

Possible solution:

Yocto stack requires more than 30 GB of free disk space for build to complete, so it is required to keep sufficient disk space available before starting the build process.

Issue:

Bitbake complains about a missing “sys/cdefs.h” and the error can be encountered in random recipes when we move from one build host to other.

Example console log:

compilation terminated.
| In file included from /usr/include/stdio.h:27:0,
|                  from ./src/kern_head.c:13:
| /usr/include/features.h:374:25: fatal error: sys/cdefs.h: No such file or directory
|  #  include <sys/cdefs.h>
|                          ^
| compilation terminated.
| In file included from /usr/include/stdio.h:27:0,
|                  from ./src/sstrip.c:9:
| /usr/include/features.h:374:25: fatal error: sys/cdefs.h: No such file or directory
|  #  include <sys/cdefs.h>
|                          ^
| compilation terminated.
| make: *** [encode] Error 1
| make: *** Waiting for unfinished jobs....
| make: *** [kern_head] Error 1
| make: *** [sstrip] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command

Possible Solution:

This issue may be caused by a missing “g++-multilib” package in the build host (observed in Ubuntu 14.4). Installing the package with “sudo apt-get install g++-multilib” should resolve this issue. Also the build machines should be configured following the procedure as per Setup guide to avoid similar issues.

Issue:

The bitbake process terminates after complaining about a non-existent path or environment variable.

Example console log #1:

ERROR: Function failed: iarmbus: LIC_FILES_CHKSUM points to an invalid file: ${RDK_ROOT_PATH}/components/generic/iarmbus/core/include/libIARM.h

Example console log #2:

ERROR: ParseError at /mnt/home/gpsahu01/cmf/test/meta-virtualization/recipes-extended/images/cloud-image-controller.bb:29: Could not inherit file classes/image-vm.bbclass

Possible solution:

This may be due to a wrongly setup environment e.g. we have executed “meta-rdk/setup-environment” instead of sourcing “meta-cmf/setup-environment”

Issue:

The issue is observed during setup and machine selection stage, setup-environment script will throw unexpected error about non-existing layer paths.

Example console log:

gpsahu01@dvm-wcdcc-tata-001:~/cmf/emulator-2.1-20160919$ source meta-cmf/setup-environment

1) meta-raspberrypi/conf/machine/raspberrypi0.conf             7) meta-rdk-bsp-emulator/conf/machine/qemux86hyb.conf

2) meta-raspberrypi/conf/machine/raspberrypi2.conf             8) meta-rdk-bsp-emulator/conf/machine/qemux86mc.conf

[…]

Please enter your choice of machine [1..11]: 7

### Shell environment set up for builds. ###

Writing auto.conf ...

Writing versions.txt ...

-bash: cd: ../meta-browser//: No such file or directory

fatal: Not a git repository (or any parent up to mount point /mnt)

Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

-bash: ../patches/rdk-oe/meta-linaro//*.patch: No such file or directory

-bash: cd: ../meta-openembedded//: No such file or directory

fatal: Not a git repository (or any parent up to mount point /mnt)

Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Possible solution:

If the host PC has set colored terminal output for commands then it may cause unexpected errors being shown during execution of meta-cmf/setup-environment script. To fix the problem we can run following command:

gpsahu01@dvm-wcdcc-tata-001:~/cmf/emulator-2.1-20160919$ alias ls='ls --color=no'

Looks like memory issue hence changing Ubuntu to 64 bit version should resolve the issue. The below are the Ubuntu configurations,

• Ubuntu 16.04 - 64 bit
• 6GB RAM

16GB Swap

To include a specific feature that is not available in base build, enable the feature specific DISTRO flag in platform specific config file. For example to include USPA feature in Rpi build,

Add the DISTRO specific flag in Rpi platform specific conf file

In File meta-cmf-raspberrypi/conf/distro/include/rdk-rpi.inc

Add DISTRO_FEATURES_append = " usppa" (to include the feature if not there)

DISTRO_FEATURES_remove = " usppa" (to remove the feature)

Make sure the recipe is part of the package build

In File meta-rdk/recipes-core/packagegroups/packagegroup-rdk-ccsp-broadband.bb must be included as a DISTRO protected feature RDEPENDS_packagegroup-rdk-ccsp-broadband += " \ ${@bb.utils.contains('DISTRO_FEATURES', 'usppa', "usp-pa", "", d)}"

ERROR: ParseError at /home/a1602446/build-raspberrypi-rdk-broadband/conf/local.conf:247: Could not include required file conf/distro/include/##RDK_FLAVOR##.inc

Above error occurs intermittently, which can be fixed by retrying the source command for setup_environment file.

In case of Rpi, it is 

• source meta-cmf-raspberrypi/setup-environment

Please refer Compile-time Build Variants Flags

Issue:

Bitbake fails on populate sysroot state when building with an un-clean stack.

Example console log:

ERROR: Function failed: llvm_sysroot_preprocess (log file is located at /mnt/home/gpsahu01/cmf/test/build-qemux86hyb/tmp/work/i586-rdk-linux/llvm3.3/3.3-r0/temp/log.do_populate_sysroot.9648)

Possible solution:

This may happen when a previous build process was unexpectedly terminated or aborted. Re-build after cleaning the problematic recipe or image (bitbake <recipe> -c cleanall) would fix the issue.

Issue:

Bitbake terminates the compilation process on ‘do_patch’ task. This may happen in following cases:

-          When using an old recipe file where the SRC_URI link has updated its folder structure.

-          Wrongly formatted patch file (run dos2unix for conversion)

-           Incorrect patch level (p0, p1, etc.)

Example console log:

ERROR: Command Error: exit status: 1 Output:
Applying patch 0001-src-Makefile.am-Dont-check-if-we-are-cross-compiling.patch
can't find file to patch at input line 18
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------

Possible Solution:

From the above output it seems that the file to which patch will be applied is not found, possible reason may be the source folder structure doesn’t match with the destination folder structure. E.g. the source directory or ${S} starts from the relative path ‘src’ folder and we are trying to patch outside of it.

By default bitbake patches the files with patch level ‘p1’ so creating a patch file which matches destination folder structure would solve this issue. Another option is to alter the patch level. E.g.

SRC_URI += file://docsis_3383.patch;striplevel=0

Issue:

Bitbake complains about md5sum mismatch when a recipe has retained old md5sum value while the source file is updated.

Example console log:

ERROR: gst-plugins-playersinkbin-noop: md5 data is not matching for file://gstplayersinkbin.c;md5=0f518921aef846c156f91ce4dd6b7c76
ERROR: gst-plugins-playersinkbin-noop: The new md5 checksum is 958142c8f2783c6c4f357f561585b4da

Possible solution:

Update the new md5sum value of the file in recipe. This can be done using following steps:

:…/meta-rdk/recipes-extended/gst-plugins-playersinkbin/files$ md5sum -t gstplayersinkbin.c
958142c8f2783c6c4f357f561585b4da gstplayersinkbin.c

Now change the above value in recipe:

LIC_FILES_CHKSUM = "file://gstplayersinkbin.c;md5=958142c8f2783c6c4f357f561585b4da \”

Example Console Log :

repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.
Downloading Repo source from https://gerrit.googlesource.com/git-repo
remote: Finding sources: 100% (32/32)
remote: Total 32 (delta 14), reused 32 (delta 14)
Unpacking objects: 100% (32/32), done.
File "/mnt/home /cmf/.repo/repo/main.py", line 79
file=sys.stderr)
^
SyntaxError: invalid syntax

If you're using an older system without Python 3.6+, try downloading an older version of the Repo Launcher that still supports Python 2.7.

Possible Solution :

# create a bin directory

mkdir ~/bin

export PATH=~/bin:$PATH

curl https://storage.googleapis.com/git-repo-downloads/repo-1 > ~/bin/repo

chmod a+x ~/bin/repo

ERROR: trower-base64-git+AUTOINC+fbb9440ae2-r0 do_fetch: Fetcher failure: Unable to find revision fbb9440ae2bc1118866baefcea7ff814f16613dd in branch master even from upstream

ERROR: trower-base64-git+AUTOINC+fbb9440ae2-r0 do_fetch: Fetcher failure for URL: 'git://github.com/Comcast/trower-base64.git'. Unable to fetch URL from any source.

ERROR: trower-base64-git+AUTOINC+fbb9440ae2-r0 do_fetch: Function failed: base_do_fetch

ERROR: Logfile of failure stored in: /builds/__repo/build-brcm968360GW/tmp/work/cortexa7t2-vfp-rdk-linux-gnueabi/trower-base64/git+AUTOINC+fbb9440ae2-r0/temp/log.do_fetch.18310

ERROR: Task (/builds/__repo/meta-rdk-ext/recipes-support/trower-base64/trower-base64_1.0.bb:do_fetch) failed with exit code '1

Few points to check here,

• First check if the SRC_URL can be accessed manually in browser

• Check the path of the URL is proper and check the branch detail as well

For example, above error can be fixed by appending branch=main in the SRC_URL path

• The rootfs doesn't contain libpcap.so, as tcpdump utility is not appended in the packagegroup-rdk-oss-broadband.bbappend file in the Raspberry-pi build whereas you can find the tcpdump utility appended for the corresponding file for Emulator build.
• So, if we include tcpdump utility in the above mentioned file, libpcap. So file will be present in the rootfs of the raspberry-pi build.
• See below output from the raspberry-pi device after adding tcpdump -

root@RaspberryPi-Gateway:/# find . -iname libpcap* ./usr/lib/libpcap.so.1.7.4 ./usr/lib/libpcap.so.1

Currently no such pre-built images are available for download. You can follow the simple build instructions to generate your own build.

Eg:

• RDK-B Raspberrypi - Host SetUp and Build Instructions
• RDK-B Emulator Build Instructions

The eRT (embedded router) subsystem is generally used to perform dmcli operations on Raspberry pi which can function as a basic router. To perform dmcli operations in emulator we use simu.

We're simply building the application using go build (without any Yocto recipes) as shown below -

env CC=arm-linux-gnueabihf-gcc LD=arm-linux-gnueabihf-ld GOOS=linux GOARCH=arm GOARM=7 CGO_ENABLED=1 go build

• RDK officially doesn't support GO language compatibility. But you may always try GO binaries as most RDKM code bases are based on Yocto open-embedded builds and the binaries work out of the box.
• You can simply build the application using go build (without any Yocto recipes) as shown below -
  • env CC=arm-linux-gnueabihf-gcc LD=arm-linux-gnueabihf-ld GOOS=linux GOARCH=arm GOARM=7 CGO_ENABLED=1 go build

• Each component has its own XML file , which will be available under /usr/ccsp/<component>
• Here for Device.WiFi. , the XML file (TR181-WiFi-USGv2.XML) is available under /usr/ccsp/wifi. This file provides details regarding the data models available under Device.WiFi.

Please refer https://wiki.rdkcentral.com/display/RDK/RDKB+Containerization+in+RPI+-+User+Manual+-+2019+M3 .

Below are the two ways to enable debug logs for component

1. adding prints in the respective place of code
2. using rdkb logger(LogAgent) .
   LoggerEnable - to enable/disable logs for particular component. If it is TRUE logs are enabled otherwise logs are disabled.
   LogLevels - To set different log levels for each component. By default all modules log level is 4 (RDK_LOG_INFO).

The steps are –

• Port valgrind to the platform (if not already available)
• Compile the component with debug symbols enabled (i.e, avoid stripping the component executable/library. alternatively, you may replace the stripped binary with unstripped binary if it is not a read-only image)
• Stop the service and start the binary as part of valgrind (just like we load any normal binary using valgrind)
• Once you have enough data collected (or observed the issue you were trying to debug), you may stop it and examine the xml file for details.

For reference please look into this attachment :

• ipset is available in real RDK-B devices( like the XB6 devices for example). To enable ipset for RDKB emulator, you can do that as the yocto recipes for ipset are already available at /meta-openembedded/meta-networking/recipes-extended/ipset/38.bb
• You need to add the recipe to the package group for emulator to use it up during build time (you may add them in ./meta-rdk-bsp-emulator/recipes-core/packagegroups/packagegroup-rdk-ccsp-broadband.bbappend)

Follow the below steps to customize kernel –

• Need to Create config file within linux bb/bbappend file available directory
  Path: meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi
  ( XXX.cfg ) - Example:camera.cfg
• Configuration parameter addition: Add config data to created config file so as to enable it. For example, add the below line to our camera.cfg file
  CONFIG_VIDEO_BCM2835=y
• Need to add created config file under SRC_URI of linux bb/bbappend file mentioned in step 1
  SRC_URI = "file://camera.cfg"
• Do compilation and Installation
  bitbake "component-name" -c compile -f
  bitbake "component-name" –f

Yes, igmp_snooper program is present in RDK-B .

• There is a shell script named "service_mcastsnooper.sh" under /etc/utopia/service.d directory, and in the script, it will execute "igmp_snooper $sw_opt $if_opt $querier_opt 

The data model can be managed via TR-069 , TR-181, management protocols like SNMP, WebUI, WEBPA .

• The eCM and eRT subsystems will always coexists in a DOCSIS based WAN frontend gateway devices. Any request for eCM parameters will be routed to eCM Message Bus Adapter component which uses SNMP or other protocols to talk to the cable modem firmware in the backend.
• In Rpi, we have only eRT and in emulator we have simu.
• eCM is applicable only to DOCSIS based devices , which uses SNMP based OIDs.

Use NTP sync to run in the background to sync time with NTP servers.Update the NTP servers in ntp conf file if needed.

Minimum Hardware requirement :

• A Raspberry Pi 3B with the below configuration can be an ideal minimum requirement to support most of the functionalities for RDK-B.
• The configuration of RPi 3B is CPU: Quadcore 1.2 GHz Broadcom BCM2837 64bit with 1GB RAM.
• R-Pi 3B would be sufficient for the basic wireless functionality using 2.4GHz. In case of 5 GHz band support R-Pi 3B+ would be good (Note : R-Pi 3B+ doesn’t support simultaneous dual band operations).
• Flash: The minimum size is around 285 MB. Anything above this should work just fine for loading/storing the build.
• RAM: As far as the logs/database is concerned, anything around 16 MB should be sufficient.

The above requirement supports all the basic functionalities  of RDK-B.

• RPC download is not supported in RDK-B.
• RDK-B never had "cisco.spvtg.ccsp.fu.Configuration". This part of the code has come through initial code drop and is deprecated.

Yes. RDKB has the below options to modify SSID name, password, security protocol etc.

• A WebUI, where you can modify these items just like the UI for most normal routers.
• 'dmcli' command line utility which will execute TR69 commands to modify the mentioned items.            

Yes. You can invoke the data models via dmcli commands from your service or via Cdm_GetParam set of APIs from your code. The TR-181 data model specifications that are available in the TR-181 data model XML for each component can be referred.

The CA certificate file and device certificate/private key can be configured in ccsp_tr069_pa_cfg.xml for https support.

There are already reserve SSID for Guest WiFi network. Just enable the SSID using the respective DM to get the features in place.

Duktape is a lightweight javascript engine (https://duktape.org/). Alone it does not provide a web development engine like php or node.js. Therefore,on top of duktape there is a templating engine(called jst) and web server api. To make migration as easy as possible the style of templating and api signiture will match php as closely as possible. Many php functions and variables will be rewritten in javascript, so that changes to the exist code is minimized.

It actually defines what kind of Internet traffic is allowed or blocked. For more details, Please Refer : Firewall - Rule persistence

Please refer Integration Guide for third-party applications into RDK-B stack .

Use journalctl -xu parodus or can look for parodus.log in the log folder i.e. /rdklogs/logs/.

In <image>.bbappend file , upgrade python version using ROOTFS_POSTPROCESS_COMMAND
Code :

#python upgrade
IMAGE_INSTALL_append = " python3 "
ROOTFS_POSTPROCESS_COMMAND += "enable_python3; "
enable_python3() {
ln -sf /usr/bin/python3 ${IMAGE_ROOTFS}${bindir}/python
}

On compiling the code and flashing the image , python3 will be available in your board . Check with below command.

root@RaspberryPi-Gateway:~# python --version
Python 3.5.2

Checksum mismatch error is related to Fetcher failure for URL . The ways to fix this error are as follows

1. the url might be deprecated . Hence should use the right URL with right path
2. md5 checksum must be pointing to older one , which should be replaced with the latest checksum
3. if the component is not required ( or not maintained ) , then they can be masked from inc file

• For this you need to convert all C/C++ logging statements(like printf) to use standard logging functions CcspTraceInfo, CcspTraceWarning,CcspTraceError etc. CcspTraceXxxx functions are based on open-source 'log4c'.
• By using the above apis the logs are automatically written to logfiles.
• After conversion to standard logging functions ,you can verify the logs under /rdklogs/logs/.

The roadmap is always available to the Preferred and Preferred Plus members of RDK at https://wiki.rdkcentral.com/display/ASP/Roadmap . To become a preferred member as well as to know the benefits, please visit https://rdkcentral.com/memberships/  . For the non preferred members, you can get answers to specific queries on Roadmap items by contacting support@rdkcentral.com or asking at https://wiki.rdkcentral.com/display/FORUMS/FORUMS+Home .

Please refer Breakpad steps

On 15 August 2013 Comcast Cable and Time Warner Cable jointly announced the formation of RDK Management, LLC to fulfill the role of the "RDK Entity".

We will maintain compatibility with the previous RDK version as described by the guidelines in the agreement. Additional details will be posted on the RDK Wiki as they become available.

Licensee are not required to take a new baseline.

RDKM does not assess run-time royalties for the Generic RDK.

The infrastructure to support DVB exists today; but additional components may need to be developed to support the particular network type. Typical enhancements include converting a URI to a network-specific identifier in the SI handling, and enhancing the security processor to implement CA that doesn't use the cable card.

RDK supports CEA-708 and EIA-608.

The font-type used for Closed Captioning belongs to an opensource family called Droid with specific glyphs for closed captions. Incase operators are using licensed fonts they have to meet the exclusive license requirements for those fonts.

OEM vendors will need to work with font vendors to provide fonts that comply with FCC standards. RDK Support is looking into whether FCC-compliant open-source fonts are available, and will provide that information in a future update.

To add VOD support for a different system, the VOD client would be rewritten to talk to the appropriate backend to provide content. This is an independent implementation and not coupled to any specific MSO configuration. The client is responsible for tuning to the content, connecting it to a sink, and starting streaming. It comes into play only after a VOD request is received by the receiver, the purchase is completed, and the connection is created (i.e., broadcast has started from servers side). Because time shift buffers are not allowed for VOD content, trickplay commands are merely forwarded to the content source, which is responsible for taking the appropriate actions.

Yes, RDK supports these tags in the current version.

Device Settings is integrated with IARM, which invokes the HAL API to effect changes requested by the application. Interface specifications are available for application developers.

The IP client provided by RDK works with the RDK Server, not the general DMS. This is the direction for now. CVP-1 and CVP-2 certification are planned for RDK Servers.

Separate RDK release packages will be available for IP and Hybrid versions. The requirements will draw a clear distinction between IP and Hybrid components

Control of front-panel brightness and other front-panel controls such as LED displays, power-button and similar controls will be specified as part of the Comcast Manufacturer Interface Specification.

The answer can be "extsrc is used to faciliate easy development work. If it is preferred otherwise, there is a XXX-nosrc.xml manifest file which will be retained after the first build and hence saving time 

Many developments  & improvements happening in RDK .Few are listed below.

• Doxygen : Video & Broadband documentations are available in the following locations.
  • For Broadband: https://wiki.rdkcentral.com/doxygen/rdkb/index.html
  • For Video: https://wiki.rdkcentral.com/doxygen/rdkv-opensourced/index.html
• Github : https://github.com/rdkcentral/
• Systemd

For latest updates see Announcements at https://wiki.rdkcentral.com/ page and  " What is the Roadmap for the RDK?" question in this page to know about the Roadmap of RDK.

1. git commit your changes in both the local repos
2. Create a branch and check it out in both repos make sure it has the SAME NAME (i.e. git checkout -b my_special_changes)
3. Then finally do a git review in both repos (or more specifically git review master or git review stable2)

What this does:

In gerrit the changes will be put up for review in the branch you specified in your git review command (master or stable2). At the same time it will set the Topic field to the name of your local branch (i.e. my_special_changes). When gerrit sees topic fields with identical names it binds them together. So it forces project maintainers to press the "Submit Together" button so they go in at the same time once given +2.

Install SDK if it is not already installed by following the steps under the previous heading. Install Groovy version 2.0.7 / 2.0.6 (until M75)using the below command 

• sdk install groovy 2.0.6

Check groovy version :

• groovy -version

From M76 release onwards, the supported groovy version is groovy 2.3.0. Install SDK if it is not already installed by following the steps under the previous heading. Install Groovy version 2.3.0 using the below command –

• sdk install groovy 2.3.0

Check groovy version :

• groovy –version

Follow are the commands to install MySQL

• sudo apt-get install mysql-server      

mysql installation will ask for the password during installation. (give the root password)

If validate_password plugin is present for Mysql, set the password policy as LOW using the below command

• set GLOBAL validate_password_policy=LOW; flush privileges";

Login to mysql prompt

• sudo mysql -u root -p

It will ask for password, give the root password given during installation.

There is no size restrictions imposed by RDK as such, the limits depends on SoC and OEM factors including Flash size. The firmware image will be compressed using SquashFS with LZMA compression.

No advanced options are currently supported by the IARM.  It is mainly an event bus with a pub/sub metaphor.  A lot of what is available is driven by the need.  If some of the features are needed we should see a feature request.  We are open to discussion of improvement as long as there is a case for it. No metrics have been captured at this time outside of the overall cloud metrics where IARM is part of the overall latency.

The various components in RDK have dependencies on other components, and some of these have similar functions. As long as the claims on memory and other system resources is small (e.g., Mongoose is a single file) it may be expedient to retain these redundant components.

It is optional and some devices is known to have HDMI 2.0 such as accelerator.

 Checkout relevant code repos based on your requirements from https://code.rdkcentral.com/r/admin/repos

1. For Open sourced components, search for required component in the filter option to get the relevant code repo.
2. For Licensed components, sign in to https://code.rdkcentral.com/r/admin/repos using username and password,and search for required component in the filter option to get the relevant code repo.