This is the summary page that describes CMF quarterly release rdkb-2022q3-dunfell, based on the new branch rdk-next and dunfell oe layers. Below are links to the relevant documents.

Note: The master branch has been deprecated in select community repositories and rdk-next is now the lead development branch.

Note: The latest rdkb quarterly release 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 release rdkb-2022q2-dunfell can be found here.

Baseline

Baseline Branchnightly/20220908-dunfell
Post-baseline updatesNA
TDKM104
Manifest branch

rdkb-2022q3-dunfell

Highlights

Components updated since rdkb-2022q2-dunfell 


rbusCcspMisc
rbuscoreCcspMtaAgent
OvsAgentCcspPandM
crashuploadCcspPsm
dcaCcspSnmpPa
jstCcspWifiAgent
lxc-container-generatorCcspXDNS
rdk_loggerGwProvApp
rdmGwProvApp-EthWan
rfcMeshAgent
telemetryPowerManager
xupnpRdkGponManager
rdk/components/opensource/rtmessageRdkTelcoVoiceManager
rdkb/components/generic/CcspLogAgentRdkWanManager
rdkb/components/generic/harvesterRdkXdslManager
rdkb/components/generic/notify_compTestAndDiagnostic
rdkb/components/generic/startParodusUtopia
CcspAdvSecurityXconf
CcspCMAgenthalinterface
CcspCommonLibraryhotspot
CcspDmClisysint
CcspEthAgentwebui
CcspHomeSecuritywebui-bwg
CcspLMLite

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 release rdkb-2022q2-dunfell can be found here.

Getting the code

mkdir <workspace dir>
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m <manifest.xml> -b rdkb-2022q3-dunfell  
repo sync -j `nproc` --no-clone-bundle --no-tags  
  • The -m <manifest.xml> in the sequence above is important. If this is not specified, you will get an RDK-V tree by default.
    • For RPI builds use manifest: rdkb.xml

      repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-extsrc.xml -b rdkb-2022q3-dunfell
    • For Turris  builds use manifest: rdkb-turris-extsrc.xml

      repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-turris-extsrc.xml -b rdkb-2022q3-dunfell
  • The -b rdkb-2022q3-dunfell in the build sequence above specifies the branch to use.
  • If you omit the -b rdkb-2022q3-dunfell entirely, you will get the HEAD of each component

Building the code

Building for RaspberryPi 3

mkdir <workspace dir> 
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-extsrc.xml -b rdkb-2022q3-dunfell  
repo sync -j `nproc` --no-clone-bundle --no-tags 

MACHINE=raspberrypi-rdk-broadband source meta-cmf-raspberrypi/setup-environment

bitbake rdk-generic-broadband-image

# To build TDK image
bitbake rdk-generic-broadband-tdk-image
  • Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi-rdk-broadband folder


Building for RaspberryPi 4B 32 Bit

mkdir <workspace dir> 
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-extsrc.xml -b rdkb-2022q3-dunfell  
repo sync -j `nproc` --no-clone-bundle --no-tags 

MACHINE=raspberrypi4-rdk-broadband source meta-cmf-raspberrypi/setup-environment

bitbake rdk-generic-broadband-image

# To build TDK image
bitbake rdk-generic-broadband-tdk-image
  • Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi4-rdk-broadband folder

Building for RaspberryPi 4B 64 Bit

mkdir <workspace dir> 
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-extsrc.xml -b rdkb-2022q3-dunfell  
repo sync -j `nproc` --no-clone-bundle --no-tags 

MACHINE=raspberrypi4-64-rdk-broadband source meta-cmf-raspberrypi/setup-environment

bitbake rdk-generic-broadband-image

# To build TDK image
bitbake rdk-generic-broadband-tdk-image
  • Note. The kernel Image and root filesystem will be created under the ./tmp/deploy/images/raspberrypi4-64-rdk-broadband folder

Building for Turris GW

mkdir <workspace dir> 
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-turris-extsrc.xml -b rdkb-2022q3-dunfell  
repo sync -j `nproc` --no-clone-bundle --no-tags 

MACHINE=turris source meta-turris/setup-environment

bitbake rdk-generic-broadband-image

# To build TDK image
bitbake rdk-generic-broadband-tdk-image

Building for Turris Extender

mkdir <workspace dir> 
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-turris-pod-extsrc.xml -b rdkb-2022q3-dunfell  
repo sync -j `nproc` --no-clone-bundle --no-tags    

MACHINE=turris-extender source meta-turris/setup-environment  

bitbake rdk-generic-extender-image

Building for RPI4 Extender

mkdir <workspace dir> 
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-pod-extsrc.xml -b rdkb-2022q3-dunfell  
repo sync -j `nproc` --no-clone-bundle --no-tags 

MACHINE=raspberrypi4-rdk-extender source meta-cmf-raspberrypi/setup-environment

bitbake rdk-generic-extender-image

Documentation 

Documentation on the RDK-B reference platforms including host requirement setup and flashing instructions are available from the following links:

RDK Reference Platforms

RDK-B (RaspberryPi)

RDK-B R-Pi Yocto 3.1 - Dunfell

RDK-B (Raspberry Pi) Build and Setup Manual - Router Profile

RDK-B Turris

For all other RDK documentation please refer to the RDK wiki at https://wiki.rdkcentral.com/ 

Testing

Sanity Testing

RPI Sanity tests include:

  • Services checks (wifiagent, hostapd, ccsp processes)
  • Network (WAN) connectivity 
  • LAN client
  • Wifi 2.4Ghz and 5Ghz hotspot testing.
  • Login, menu navigation, parameter modification, e.g. Wifi SSID/password change and re-connection, changing admin password.
  • NOTE you need to reboot after flashing the device to get erouter0 IP see:  REFPLTB-1775 - Getting issue details... STATUS

Turris Sanity test include:

  • Services checks (wifiagent, hostapd, ccsp processes)
  • Network (WAN) connectivity 
  • Wifi 2.4Ghz and 5Ghz hotspot testing.
  • LAN client 
  • Ping and traceroute via WEB UI
  • Admin WEBUI works over <erouter IP>:8080 and WiFi
  • Extender Plume NOC Connectivity with Turris Extender and RPI 4 Extender
    • RPI 4 Extender is not working see REFPLTB-1508 - Getting issue details... STATUS
    • Turris Extender Access Points are not working REFPLTB-1836 - Getting issue details... STATUS

TDK Testing

  • No labels