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

• RPI profile has enabled DISTRO OneWifi.
• For RPI 4 Extender see RPI4 Extender - reference implementation
  
• TDK Testing was performed on the rdkb-2024q1-kirkstone release, please refer to this release for test results
• Turris GW is no longer supported for community releases.

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

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-2023q4-dunfell can be found here. 

Baseline

Highlights

Components updated since rdkb-2023q4-dunfell

Community contributions

A detailed changelog since the last release rdkb-2023q4-dunfell can be found here. 

Getting the code

Note:

• The manifests repository is only available to RDK licensees.
• Opensource versions of the RDKB manifests are available from the rdkcmf/manifests repository rdkb-2024q1-dunfell branch 

mkdir <workspace dir>
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m <manifest.xml> -b rdkb-2024q1-dunfell  
repo sync --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-2024q1-dunfell

• The -b rdkb-2024q1-dunfell in the build sequence above specifies the branch to use.
• If you omit the -b rdkb-2024q1-dunfell entirely, you will get the HEAD of each component

Building the code

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-2024q1-dunfell  
repo sync --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-2024q1-dunfell  
repo sync --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 RaspberryPi 4 Extender

mkdir <workspace dir> 
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/manifests -m rdkb-pod-extsrc.xml -b rdkb-2024q1-dunfell
repo sync --no-clone-bundle --no-tags 

<UPDATE 0001-Update-bhaul-credential.patch in meta-cmf-broadband layer> 

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

Kirkstone (Yocto 4.0) Migration - RDK-B

RPI4 Extender - reference implementation

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.

TDK Testing

• TDK component tests were not run against the release