RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Page History
...
RDK-C rdk-next Yocto 3.1 dunfell build for Raspberrypi
server and client connectivity diagram
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
openwebrtc Compilation Procedure For X86
...
Below command is cloning the openwebrtc source into current PC.
git clone https://github.com/rdkcteam/openwebrtcnative-m72webrtc.git
| Console output |
|---|
user@BLTSLRM110: |
~$ git clone https://github.com/rdkcteam/ |
webrtc.git |
native- |
webrtc'... |
49, done. |
41/ |
41), done. |
20/20), done. |
49 (delta |
11), reused |
41 (delta |
11), pack-reused |
8 |
Unpacking objects: 100% ( |
49/ |
49), |
41.97 KiB | 511.00 KiB/s, done. |
STEP 2:
Goto openwebrtc-m72 native-webrtc/PC_Streamer folder and give below export command.export PATH=$PATH:/home/user/Desktop/openwebrtc-m72/buildtools/linux64/commands.
sudo chmod 777 webrtc_browser.sh
./webrtc_browser.sh
| Console output |
|---|
user@BLTSLRM110: |
~$ cd |
native-webrtc/PC_Streamer/ user@BLTSLRM110:~/ |
STEP 3:
Run the below command.
gn gen out/Default --args='rtc_use_h264=true is_component_ffmpeg=true rtc_libvpx_build_vp9=false rtc_use_gtk=false rtc_include_tests=false'
native-webrtc/PC_Streamer$ sudo chmod 777 webrtc_browser.sh |
|
Done. Made 651 targets from 185 files in 322ms
STEP 4:
Run the below command.
ninja -C out/Default
native-webrtc/PC_Streamer$ ./webrtc_browser.sh |
STEP 3:
Completion of step2 the binaries are generated into native-webrtc/PC_Streamer/webrtc-checkout/Completion of above command all the binaries are generated into out/Default folder inside.
Validation Procedure of Webrtc
...
Run the peerconnection_server binary located at (openwebrtcnative-m72webrtc/out/DefaultPC_Streamer/webrtc-checkout).
./peerconnection_server
| Console output |
|---|
user@BLTSLRM110:~/Desktop/openwebrtc-m72/out/Default$ ./peerconnection_server Server listening on port 8888 |
STEP 2:
Open new terminal Goto openwebrtc-m72/out/Defaultpathand path, run the below two commands one by one.
...
Refer the below peerconnection_client GTK window.
STEP 3:
Provide IP address of server pc and press connect button.
...
Refer the below peerconnection_client GTK window.
STEP 4:
Stop below service before runing the peerconnection_client binary.
stop pipewiresystemctl stop rms-launcher
systemctl stop mst-launcher.service
Run the peerconnection_client binary into RPI board side and Enter server PC IP address, port numner.
peerconnection_client
| Console output |
|---|
| root@raspberrypi3-rdk-camera:~# peerconnection_client Inside constructor CustomSocketServer()..... Initialized thread... "Registering PeerConnectionClient::RegisterObserver()" Enter server IP Address 192.168.0.126 Enter port number 8888 |
STEP 5:
Need to Check whether the peerconnection_server side both clients are connected are not.
| Console output |
|---|
user@BLTSLRM110:~/Desktop/openwebrtc-m72/out/Default$ ./peerconnection_server Server listening on port 8888 New connection... New member added (total=1): zaid@zaid-ahmad Disconnecting socket Total connected: 1 New connection... New connection... New member added (total=2): user@raspberrypi3-rdk-camera Disconnecting socket Total connected: 2 New connection... Disconnecting socket Total connected: 2 New connection... |
STEP 6:
PC side peerconnection_client GTK window shows the number of peers client devices areconnected list.
STEP 7:
Double click user@rasspberrypi3-rdk-camerafrom the listed peer connected devices.
Overview
Community Forums
Content Tools
Tasks