Page History

Scope

Goal of this document helps RDK-B community to Port Unified-easy-mesh on to their Gateway/Extender platforms

Assumption

• We assume that the development done on raspbian OS have enabled all the compiler options - Platform Agnostic C++ Coding for RDK-B

Test EM on Raspbian OS

• unified-wifi-mesh on RDK-B

Use

...

R5 Specification

...

R6 specification with Wi-Fi 7

Use case diagram

• draw.io Diagram
  border true diagramName usecasediagram-wifiusdwm simpleViewer false width links auto tbstyle top lbox true diagramWidth 971 height 681 revision 7

Generic Porting stages

• Yocto support
  • Done for all recipes
    • mysqlconnector-cpp (mysql-connector-cpp_1.1.19 New recipe)
    • MariadDB (From openembedded)
    • unified-wifi-mesh(unified-wifi-mesh.bb)

    • ccsp-one-wifi-libhebus.bb(New recipe)

• New cli migration
• Golang support
• Segmentation faults fixing

Current state

Done

...

• 1090 height 754 revision 1

...

<<OneWifiMeshCli>>: reset erouter0 bananapi encode_config_reset:354: {

...

(gdb) bt #0  0x0000000000417fb8 in em_cmd_t::init (this=this@entry=0x7f8b4b7010, dm=dm@entry=0x7f8b7fe690)     at ../../../git/src/ctrl/../../src/cmd/em_cmd.cpp:127 #1  0x0000000000418764 in em_cmd_t::em_cmd_t (this=0x7f8b4b7010, type=em_cmd_type_reset,     param=<error reading variable: Cannot access memory at address 0x7ffc9a6470>, dm=...)     at ../../../git/src/ctrl/../../src/cmd/em_cmd.cpp:703 Backtrace stopped: Cannot access memory at address 0x7ffc9a63f8

...

Ongoing

• Golang support in RDK-B added
• ongoing with latest cli in progress
  • Creating yocto recipe to compile cli go code from yocto
  • Will retest the crashes and update 

Next phase

• Optimizing mariaDB - Target to keep size < 10 MB
• Package Manager
• Stripped onewifi for AP extender

Gateway specific steps

• EasyMesh controller integration - On Going
• Test with BPI R4 controller & RPI4 Agent - TBD
• Test with with BPI R4 controller & BPI R4 agent - TBD

Extender specific steps

• OSS image with SoC specific changes done
• Integration of OneWifi on going
• EasyMesh Agent - To start after Onewifi integration
• Testing with RPI4 controller and BPI R4 Extender

Platform agnostic c++ coding

• Platform Agnostic C++ Coding for RDK-B

State machine

• RDK-B EasyMesh StateMachine
  • RDK-B EasyMesh StateMachine

GoLang support for EM CLI

• Go Language support in RDK-B

BPI-R4 build instruction 

...

repo init -u https://code.rdkcentral.com/r/manifests -b kirkstone -m rdkb-bpi-extsrc.xml
repo sync -j`nproc` --no-clone-bundle
 
Please pick the below machine command based on your requirement
# toDefault build the image with AL_SAP
MACHINE=bananapi4-rdk-broadband FEATURE_TYPE=EasyMesh  source meta-cmf-bananapi/setup-environment-refboard-rdkb
# to build the image without AL_SAP
MACHINE=bananapi4-rdk-broadband FEATURE_TYPE=EasyMesh WITHOUT_ALSAP=yes source meta-cmf-bananapi/setup-environment-refboard-rdkb
 
#to CP the below change for fynecli access for utopia component
https://github.com/rdkcentral/utopia/pull/47
 
bitbake rdk-generic-broadband-image

...

repo init -u https://code.rdkcentral.com/r/manifests -b kirkstone -m rdkb-bpi-ap-extsrc.xml
repo sync -j4 --no-clone-bundle
 
Please pick the below machine command based on your requirement,
#to build the image#Default build with AL_SAP
MACHINE=bananapi4-rdk-broadband-ap-extender  source meta-cmf-bananapi/setup-environment-refboard-rdkb
#to build the image without AL_SAP
MACHINE=bananapi4-rdk-broadband-ap-extender FEATURE_TYPE=EasyMesh WITHOUT_ALSAP=yes source meta-cmf-bananapi/setup-environment-refboard-rdkb
 
bitbake rdk-generic-ap-extender-image

...

cd /usr/ccsp/EasyMesh
onewifi_em_cli bpi

Observation in EM-Contrller Controller device side:  

• All configured VAPs should be UP and Running
• VAPs should be broadcasting EasyMesh default SSIDs(eg, private_ssid, mesh_backhaul)
• Logs files are generated under /tmp folder

Extender 1 + STAR Topology

1.Please ensure below processes are running in Ext1

...

5. Test the connectivity to EM-Controller through backhaul

Test the connectivity with wireless clients.

Extender2 (For Daisy-Chain )

...

6. Wait for few minutes( for Agent to propagate SSID information from Controller to OneWifi in Extender2) and then check

• Check all configured VAPs should be up and running with "iw dev" command
• VAPs should be broadcasting default EasyMesh SSIDS (ie private_ssid, mesh_backhaul)

7. Test the connectivity to EM-Controller through backhaul

Test the connectivity with wireless clients.

Sample logs

EM-Controller and EM-Agent success logs

...

• RDK-B EasyMesh Agent only Reference Platform -Banana Pi R4

Next phase

• Optimizing mariaDB - Target to keep size < 10 MB

Platform agnostic c++ coding

• Platform Agnostic C++ Coding for RDK-B

State machine(WIP)

• RDK-B EasyMesh StateMachine
  • RDK-B EasyMesh StateMachine

Child pages

• RDK-B EasyMesh

  Verification Tech summit 2025

  Verification 

  • RDK-B EasyMesh Verification stages
• RDK-B kirkstone branch 

...