RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
https://docs.yoctoproject.org/migration-guides/release-notes-4.0.html#security-fixes-in-4-0
https://docs.yoctoproject.org/migration-guides/release-notes-4.0.html#recipe-upgrades-in-4-0
The following commands fetches the source code of Rpi4-32 using repo tool
repo init -u https://code.rdkcentral.com/r/manifests -b feature-kirkstone -m rdkb-extsrc.xml repo sync --no-tag MACHINE=raspberrypi4-rdk-broadband source meta-cmf-raspberrypi/setup-environment bitbake rdkb-generic-broadband-image
The following commands fetches the source code of Rpi4-64 using repo tool
repo init -u https://code.rdkcentral.com/r/manifests -b feature-kirkstone -m rdkb-extsrc.xml repo sync --no-tag MACHINE=raspberrypi4-64-rdk-broadband source meta-cmf-raspberrypi/setup-environment bitbake rdkb-generic-broadband-image
RDK-B RPI4 64 bit:
US Number | title |
---|---|
REFPLTB-1805 - Getting issue details... STATUS |
Migrate RPI4 64 bit to Yocto 4.0 |
REFPLTB-1883 - Getting issue details... STATUS | Manifest changes to support kirkstone |
REFPLTB-1902 - Getting issue details... STATUS | Build Yocto 4 core-image-minimal for RPI 64bit target |
REFPLTB-1977 - Getting issue details... STATUS | Build Yocto 4 rdk-generic-broadband-image for RPI 64bit target |
RDK-B RPI4 32 bit:
US Number | title |
---|---|
REFPLTB-1806 - Getting issue details... STATUS | Migrate RPI4 32 bit to Yocto 4.0 |
Kirkstone (Yocto 4.0) can be built using Ubuntu 18.04, 20.04 or 22.04 VMs. All these variants need additional packages to be installed over the vanilla version.
To tackle the build issues from moving one version to another, we have decided to split the problem into different subtasks. So instead of building a complete image at one go, we have planned for the generation of the following images:
These images need to be tested in cmf, to ensure that nothing has broken the existing system.
In order to provide a smooth transition without disturbing the existing branch, we have created a branch called `feature-kirkstone` for non-OE layers and another branch called `rdk/kirkstone` for OE layers and bitbake.
The machine configuration shall have a distro defined “Kirkstone”
Note: A detailed migration steps will be update before March 02,2023
Docker file for ubuntu 20.04
Test Summary
S.No | Sanity tested on | Status |
1 | erouter0 interface got Wan IP | Pass |
2 | brlan0 interface got default LAN IP | Pass |
3 | Able to take SSH Connection | Pass |
4 | All CCSP process are running | Pass |
5 | Able to Ping www.google.com | Pass |
6 | All systemd services are running | Pass |
7 | Able to connect LAN client | Pass |
8 | LAN client got IP from default pool range | Pass |
9 | LAN client should open with CaptivePortal Page | Pass |
10 | Able to connect wireless client | Pass |
11 | Wireless client got IP from default pool range | Pass |
12 | Wireless client can access the CaptivePortal Page | Pass |
13 | Internet should work on Connected clients after changing the default credentials | Pass |
14 | RdkWanManager systemd service should be in running state | Pass |
15 | Using dmcli to check the CCSP TR-181 DataModels | Pass |
16 | WebUI page should be loaded on Connected clients after changing the default credentials | Pass |
17 | WebUI page should be loaded through erouter0IP via RM | Pass |
18 | hostapd systemd service should be in running | Pass |
19 | wlan0 and wlan1 interfaces should be UP and RUNNING | Pass |
20 | All ccsp logs files should be generated in /rdklogs/logs folder | Pass |
support@rdkcentral.com