Scope of this release is for RDK-B community.This is our first official release of Banana Pi R4
NAND Build
repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -b rdkb-2025q2-kirkstone -m rdkb-bpi-extsrc.xml repo sync -j`nproc` --no-clone-bundle MACHINE=bananapi4-rdk-broadband BPI_IMG_TYPE=nand source meta-cmf-bananapi/setup-environment-refboard-rdkb bitbake rdk-generic-broadband-image |
SD Build
repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -b rdkb-2025q2-kirkstone -m rdkb-bpi-extsrc.xml repo sync -j`nproc` --no-clone-bundle MACHINE=bananapi4-rdk-broadband source meta-cmf-bananapi/setup-environment-refboard-rdkb bitbake rdk-generic-broadband-image |
NOTE: Prerequisite for SDCard build
Pre-requirements: Install tftp server in you local machine and copy the image to tftp server location
| Step 1: Power on the BPi board Step 2:You will see U-Boot Boot Menu procedure (ie, startup system, upgrade firmware, ...) Step 3:Select the second option upgrade firmware -> Run image after upgrading? (Y/n): Y Step 4:Next on Available load methods select 0 which is TFTP client. Step 5:Setup device network Input U-Boot's IP address: (same network as tftp server, eg:192.168.2.1) Input TFTP server's IP address: (tftp server IP address) Input IP netmask: 255.255.255.0 Input file name: rdk-generic-broadband-image-bananapi4-rdk-broadband-sysupgrade.bin (BPI image in bin format) Step 6:Then enter, image will be downloaded from tftp server to BPI and will start flashing the image to BPI device if success. |
|---|
Tested machines - Linux,MacOs
Copy wic.bz2 from build machine MacOs
Linux
|
|---|
| S.No | Sanity Tested on | Status |
|---|---|---|
| 1 | erouter0 interface got Wan IPv4 and IPv6 | Pass |
| 2 | brlan0 interface got default LAN IP & Ipv6 | Pass |
| 3 | Able to take SSH Connection | Pass |
| 4 | All CCSP process are running | Pass |
| 5 | Able to Ping www.google.com & ping -6 www.google.com in Gateway (i,e erouter0) | Pass |
| 6 | All systemd services are running | Pass |
| 7 | Able to connect LAN client | Pass |
| 8 | LAN client got IP from default pool range for Ipv6 and Ipv4 | 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(i,e 2G,5G,6G) for Ipv4 and Ipv6 | Pass |
| 12 | Wireless client can access the CaptivePortal Page(i,e 2G,5G,6G) | Pass |
| 13 | Internet should work on Connected clients after changing the default credentials | Pass |
| 14 | Using dmcli to check the CCSP TR-181 DataModels | Pass |
| 15 | WebUI page should be loaded on Connected clients after changing the default credentials | Pass |
| 16 | WebUI page should be loaded through erouter0IP via RM | Pass |
| 17 | wifi0, wifi1, wifi2 interfaces should be UP and RUNNING | Pass |
| 18 | All ccsp logs files should be generated in /rdklogs/logs folder | Pass |
| 19 | Factory Reset | Pass |
| 20 | Device stable | Pass |
| S.No | Features tested on | Status |
|---|---|---|
| 1 | WebPa get and set should work, query device. | Pass |
| 2 | LogUpload/Logrotation | Pass |
| 3 | RFC | Pass |
| 4 | Webconfig | Pass |
| 5 | Telemetry 2 | Pass |
| 6 | Usppa get and set are working through DM’s | Pass |
| 7 | Cellular Mode | Pass |
| 8 | Local WebUI | Pass |
| 9 | Firewall | Pass |
| 10 | OneWiFi Triband | Pass |
| 11 | CPU Proc Analyser | Pass |
| 12 | WAN Connectivity (i,e Ipv4) | Pass |
| 13 | WAN Connectivity (i,e Ipv6) | Pass |
| 14 | WiFi Connectivity | Pass |
| 15 | LAN Connectivity | Pass |
| 16 | SNMP | Pass |
| 17 | Bridge Mode | Pass |
| 18 | DAC | Pass |
| 19 | OneWifi with Single WiPhy Design | Pass |
| 20 | TR069 | Pass
|
| 21 | eSDK | Pass |
| 22 | PopulateSDK | Pass |
| 23 | SelfHeal | Pass |
| 24 | Test and Diagnostic | Pass |
| 25 | Crash Upload | Pass |
| 26 | SD card support | Pass |
| 27 | Factory reset | Pass |
| Q4' 2024(Previous prebeta release,Oct 2024) | Q1' 2025 (current beta release,Feb 05 2025 ) | Q12025 official Release | Q2' 2025 | Q3' 2025 | Future |
|---|---|---|---|---|---|
|
| Same features of Beta Release |
|
|
|
For the DAC Usppa use case, DSM does not create a folder automatically when extracting the bundle. The required changes are not present yet in the DSM code. So, need to do it manually like below and host the bundle(new_bundle.tar.gz) in server for testing it.