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

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-2024q3-kirkstone can be found here


Baseline

Baseline Branchnightly/20241203-kirkstone
Post-baseline updates


TDKM132
Manifest branch

rdkb-2024q4-kirkstone

Highlights

Components updated since rdkb-2024q4-kirkstone


CcspAdvSecurityjstrdkcentral/meta-rdk-wan
CcspCMAgentlibSyscallWrapperrdkcentral/rdkb-halif-platform
CcspCommonLibraryMeshAgentRdkInterDeviceManager
CcspDmClimeta-cmfRdkTelcoVoiceManager
CcspEthAgentmeta-cmf-broadbandrfc
CcspLMLitemeta-cmf-meshsysint
CcspMiscmeta-cmf-raspberrypitelemetry
CcspMtaAgentmeta-rdkTestAndDiagnostic
CcspPandMmeta-rdk-broadbandUtopia
CcspPsmmeta-rdk-extwebui
CcspTr069PaOneWifiwebui-bwg
CcspWifiAgentPlatformManagerXconf
CcspXDNSrdk_loggerxupnp
CoreNetLibrdk-wifi-hal
crashuploadrdk/tools/tdk
DhcpManagerrdkb/components/generic/json-rpc
GwProvApprdkb/components/generic/notify_comp
GwProvApp-EthWanrdkb/components/generic/startParodus
halinterfacerdkb/tools/tdkb
hotspotRdkCellularManager

Community contributions

A detailed changelog since the last release rdkb-2024q3-kirkstone 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-2024q4-kirkstone branch 
mkdir <workspace dir> 
cd <workspace dir>

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -m rdkb-extsrc.xml -b rdkb-2024q4-kirkstone  
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-2024q4-kirkstone
  • The -b rdkb-2024q4-kirkstone in the build sequence above specifies the branch to use.
  • If you omit the -b rdkb-2024q4-kirkstone entirely, you will get the HEAD of each component


Building the code

RDKB 2024Q4 Manifests

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-2024q4-kirkstone  
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-2024q4-kirkstone  
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 4B Extender 32 Bit

mkdir <workspace dir> 
cd <workspace dir>

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

cd meta-cmf-broadband
<UPDATE 0001-Update-bhaul-credential.patch with credential and redirector URL>
cd ../

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

Automated RPI Sanity tests include:

  • Services checks (OneWifi, 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.
Test No.TestRPI 4 32 BitRPI 4 64 Bit
1Boot up & SSH access
2Verify SSID name & password
3Captive Portal page
4Check Internet connectivity (Wi-Fi client)
5Check Web UI Launch with local gateway IP and login with admin
6verifying whether it is listing the basic parameters
7Verified the connected devices are listing
8Process Checklist - list of process running and ensure all the CCSP processes are running
9DMCLI Output. Verify it is listing all the parameters

Additional Manual Sanity Tests:

S.No

Sanity Test

Status

32 Bit

Status

64 bit

Jira

1

erouter0 interface got Wan Ipv4 and Ipv6 address

Pass

Pass


2

brlan0 interface got default LAN IP

Pass

Pass


3

Able to take SSH Connection

Pass

Pass


4

All CCSP process are running

Pass

Pass


5

Able to Ping www.google.com and Ping -6 www.google.com

Pass

Pass


6

All systemd services are running

Pass

Pass


7

Able to connect LAN client

Pass

Pass


8

LAN client got IP from default pool range (ipv4 & ipv6)

Pass

Pass


9

LAN client should open with CaptivePortal Page

Pass

Pass


10

Able to connect wireless client

Pass

Pass


11

Wireless client got IP from default pool range (ipv4 & ipv6)

Pass

Pass


12

Wireless client can access the CaptivePortal Page

Pass

Pass


13

Internet should work on Connected clients after changing the default credentials

Pass

Pass


14

Using dmcli to check the  CCSP TR-181 DataModels 

Pass

Pass


15

WebUI page should be loaded on Connected clients after changing the default credentials

Pass

Pass


16

WebUI page should be loaded through erouter0IP via RM

Pass

Pass


17

wlan0 and wlan1 interfaces should be UP and RUNNING

Pass

Pass


18

All ccsp logs files should be generated in /rdklogs/logs folder

Pass

Pass


19

Bridge Mode

Pass

Pass


20

Clients are able to get internet after reboot

Pass

Pass


21

Wifi data persistence after reboot

Pass

Pass


22

Factory Reset

Partial Pass

Partial Pass

TDK & Automatics Testing

  • No labels