You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 35
Next »
Scope:
This guide will help RDK-B community to port OneWifi on their platforms
Prerequisites:
TBD
- Raspberry Pi4 64 bit
- Raspberry Pi4 32 bit
Supported yocto version:
- Dunfell
- Kirkstone(supported in rdkb2023q3 kirkstone beta release and planned for rdkb2023q4 official release)
Epic details:
Approach followed:
- Full Management frame approach(Highly recommended for SoC vendors,OEM's and Operators)
- Event based approach(Only for Raspberry Pi4,Since there is no much support for full management from broadcom driver side we opted this approach.To continue using this approach,this should be discussed with Operators and RDK-B Architecture Review Board)
Step by step procedure:
Include rdkb2023q2 release on top of SoC SDK.this is the recommended rdkb stable release for OneWifi (rdkb-2023q2-dunfell)
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkNoYW5kcmFrYW50aCBQb2t1cnUiLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiQ2hhbmRyYWthbnRoIFBva3VydSIsImxhbmd1YWdlIjoiZW4iLCJ1aUNvbmZpZyI6Int9IiwiZGlhZ3JhbURpc3BsYXlOYW1lIjoiIiwic0ZpbGVJZCI6IiIsImF0dElkIjoiMjg4MDAzODY5IiwiZGlhZ3JhbU5hbWUiOiJSREstQnJlbGVhc2UiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiUG9ydGluZyBHdWlkZSAtIE9uZVdpZmkiLCJ0YnN0eWxlIjoidG9wIiwiY2FuQ29tbWVudCI6ZmFsc2UsImRpYWdyYW1VcmwiOiIiLCJjc3ZGaWxlVXJsIjoiIiwiYm9yZGVyIjp0cnVlLCJtYXhTY2FsZSI6IjEiLCJvd25pbmdQYWdlSWQiOjI4ODAwMzc2OSwiZWRpdGFibGUiOmZhbHNlLCJjZW9JZCI6MjkxMjc1MDgwLCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjoyLCJtYWNyb0lkIjoiMjU5NjE5NjEtNjdkMy00Y2Y5LTgxZWMtMGMzM2UwMWU3ODk2IiwicHJldmlld05hbWUiOiJSREstQnJlbGVhc2UucG5nIiwibGljZW5zZVN0YXR1cyI6Ik9LIiwic2VydmljZSI6IiIsImlzVGVtcGxhdGUiOiIiLCJ3aWR0aCI6IjU0MSIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6MTY5ODY5OTMxNzAwMCwiZXhjZWVkUGFnZVdpZHRoIjpmYWxzZSwib0NsaWVudElkIjoiIn0=
Dependencies to build OneWifi
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkNoYW5kcmFrYW50aCBQb2t1cnUiLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiQ2hhbmRyYWthbnRoIFBva3VydSIsImxhbmd1YWdlIjoiZW4iLCJ1aUNvbmZpZyI6Int9IiwiZGlhZ3JhbURpc3BsYXlOYW1lIjoiIiwic0ZpbGVJZCI6IiIsImF0dElkIjoiMjg4MDAzODc4IiwiZGlhZ3JhbU5hbWUiOiJvbmV3aWZpZGVwZW5kZW5jeSIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJQb3J0aW5nIEd1aWRlIC0gT25lV2lmaSIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6Mjg4MDAzNzY5LCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjoyOTEyNzUwODAsInBhZ2VJZCI6IiIsImxib3giOnRydWUsInNlcnZlckNvbmZpZyI6eyJlbWFpbHByZXZpZXciOiIxIn0sIm9kcml2ZUlkIjoiIiwicmV2aXNpb24iOjE0LCJtYWNyb0lkIjoiYjAwNGY4NmMtYjFkZC00OTBiLWEyM2EtYTQ3MWIyNjNkMmY4IiwicHJldmlld05hbWUiOiJvbmV3aWZpZGVwZW5kZW5jeS5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiMTU1MSIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6MTY5ODcwNTU1NDAwMCwiZXhjZWVkUGFnZVdpZHRoIjpmYWxzZSwib0NsaWVudElkIjoiIn0=
Systemd Service file:
Manifest entries:
- Onewifi component entry in manifest file (OneWifi) and rdk-wifi-hal component entry in manifest (rdk-wifi-hal)
Layers to consider:
1.meta-raspberrypi ( Or )meta-cmf-soc-<soc name> ------- Firmware/drivers/kernel to be available
- For proposing a new component,please create a bb file here
2.meta-cmf-raspberrypi (Or) meta-cmf-<platformname> --------- RDK-B changes to specific to SOC platform
- All changes that need to be done for the primary recipe are handled in the form of bbappend
- Patches: Patches are recommended if the changes are very specific and tied with SOC platform code.
3.meta-cmf-broadband ----------- RDK-B changes which are common for all RDK-B community members
- All changes that need to be done for the primary recipe are handled in the form of bbappend
- Patches: Patches are recommended if the changes are very specific and tied with SOC platform code.
Bug fixing or feature enhancement:
- Bug fixing or feature enhancement done as part of OneWifi which are generic enough should come to OneWifi generic repo
Flags defined in Onewifi:
- Raspberry Pi has certain limitations on the driver side to support end to end use case of OneWifi and Build dependencies which are specific to comcast.to avoid such issues we have introduced a flag (_PLATFORM_RASPBERRYPI_) to keep it under conditional compilation.for Real targets we dont really need this flags
Bulk atomic HAL apis for common configuration
wifi_hal_sendDataFrame |
wifi_hal_newApAssociatedDevice_callback_register |
wifi_hal_apDeAuthEvent_callback_register |
wifi_hal_apDisassociatedDevice_callback_register |
wifi_hal_register_frame_hook |
wifi_hal_disassoc |
wifi_hal_send_mgmt_frame_response |
wifi_hal_init |
wifi_hal_getHalCapability |
wifi_hal_setRadioOperatingParameters |
wifi_hal_createVAP |
wifi_hal_startScan |
wifi_hal_connect |
wifi_hal_get_default_country_code |
wifi_hal_get_default_ssid |
wifi_hal_get_default_keypassphrase |
wifi_hal_get_default_wps_pin |
wifi_hal_get_default_ssid |
wifi_hal_get_default_radius_key |
wifi_hal_setRadioOperatingParameters |
wifi_hal_staConnectionStatus_callback_register |
wifi_hal_scanResults_callback_register |
wifi_hal_mgmt_frame_callbacks_register |
wifi_hal_getRadioVapInfoMap |
wifi_hal_delApAclDevice |
wifi_hal_addApAclDevice |
wifi_hal_kickAssociatedDevice |
wifi_hal_setApWpsButtonPush |
wifi_hal_setApWpsPin |
wifi_hal_disconnect |
wifi_hal_getRadioOperatingParameters |
wifi_hal_getScanResults |
Stats implementation:
- This is vendor specific.we can use vendor based implementation from device specific HAL.pls refer this ticket for reference(
REFPLTB-2510
-
Getting issue details...
STATUS
)
wifi database:
64 bit build support:
- Comcast doesnt have 64 bit support in the current platforms.from RDK team side we have Raspberrypi 4 platform which support 64bit.we have supported Onewifi as part of this platform and fixed lot of alignment issues and warning treated as errors