Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

This Page is under Development

Introduction

Briefly describe in general terms the system/application and the purpose for which it is intended, written in non-technical terminology. Consider including a high-level architecture diagram for the system. The description should include, but is not limited to, the following:

  • Key features or major functions/use cases performed by the system/application
  • Architecture of the system in non-technical terms (e.g., client server, Web-based, etc.)
  • System environment or special conditions

Environment Setup

  • Set-up Considerations

<Briefly describe and graphically depict as appropriate the equipment, communications, and network configuration of the system in a way that a non-technical user can understand>

  • User Access Considerations

<Briefly describe and graphically depict as appropriate the equipment, communications, and network configuration of the system in a way that a non-technical user can understand>

  • Accessing the System

<Provide detailed information and describe the procedures necessary to access the system. If applicable, include how to get a user ID and log on to the system, as well as the actions a user must take to change and/or reset a password.>

  • System Work Flow

<Describe how system flow is happening mentioning checkpoints which can be verified during flow to ensure system is working as expected>

  • Exiting the System

<Mention the validation artifacts that are essential to ensure the functionality is working as expected. Also any limitation while closing the validation process>

Executing System

Describe the specific system function or feature in detail and depict graphically by including screen prints and descriptive narrative as appropriate. Ensure each screen print is captioned and has an associated tag providing appropriate alternative text

Follow the above for sub feature / use cases

Troubleshooting

  • Error Messages

<Identify the error messages that a user may receive and the likely cause(s) and/or possible corrective actions for the error>

  • Special Considerations

<If applicable, describe any special circumstances, actions, exceptions, etc., that should be considered for troubleshooting.>

This document describes the Wifi Establishment  in thunder images.This can be achieved by using NetworkControl plugin and Netsrvmgr component.Here Networkcontrol plugin is used for IP configurations as part of the WPEFramwork infrastructure and  Netsrvmgr component is used for Managing the Wi-Fi network by connecting to AP (Access Point) and provide the notification to the application. Generally it is called as Wi-Fi Network Manager.

Building Procedure

$ repo init -u https://code.rdkcentral.com/r/manifests -m rdkv-asp-nosrc.xml -b thunder

$ repo sync -j4 --no-clone-bundle

$ source meta-cmf-raspberrypi/setup-environment

select meta-cmf-raspberrypi/conf/machine/raspberrypi-rdk-hybrid-thunder.conf

$ bitbake rdk-generic-hybrid-thunder-image


Block diagram explanation

    For establishing the wifi  in thunder image we need   two things one is Networkcontrol  plugin and other is Netsrvmgr. The Network Control plugin provides functionality for network interface management. Networkcontrol has mainly two properties which are Network and up. Network  is used for Provides access to the current network information and up is used for Provides access to the interface up status.This plugin is designed to be loaded and executed within the Thunder framework.And Netsrvmgr has 3 major functionalities like wifi,moca,route.Here we will discuss about wifi .This will takes some responsibilities likedetect the Network interfaces dynamically , send notifications to subscribers and Setup and update the network routes based on priorities, wifi connection status, availability, etc.we can provide ssid and password details in /opt/wifi/wpa_supplicant.conf.After reboot the box we can see the wifi connection in raspberry pi .we can verify this by using the netsrvmgr.service

Debug Logs

  • For confirming  IP configuration in wpeframework we can verify it on wpeframework  service.

          Example:
           journalctl -x -u wpeframework

  • We can verify wifi-hal logs like connecting to particular ssid or not,wifi initialization and all  it on netsrvmgr service. 
    Example:  journalctl -x -u netsrvmgr

Referrence

netsrvmgr

https://github.com/WebPlatformForEmbedded/ThunderNanoServices/blob/master/NetworkControl/doc/NetworkControlPlugin.md#ref.Thunder

...


Contact

Organization

Phone

Email

Role

<Contact Name>

<Organization>

<Phone>

<Email>

<Role>