How to integrate opensync onto a RDK-B platform.

HI SHAMANTHA KUMAR,

Could you please let us know the target device in which you wanted to intergrate the opensync? and which release code base you are referring too?

Thanks and Regards
Srinivas

Hi SHAMANTHA KUMAR,

Please find the below links on the procedure on how to intergrate opensync and building opensync with rdkb,
https://static1.squarespace.com/static/5bbce542d7819e023f203f03/t/5e8dd17c486ea838cc40597d/1586352728434/04_08_019-1129-20_RDK-B_OpenSync_Integration.pdf

https://static1.squarespace.com/static/5bbce542d7819e023f203f03/t/5e68fbee9d45511c3bb45d98/1583939381895/019-1129-21-200309_Building_OpenSync_with_RDK-B.pdf

Thanks and Regards

Srinivas

Hi SHAMANTHA KUMAR,

For opensync support, You need to have a vendor layer and HAL API implementations 

sample vendorlayer for rdk :

https://github.com/plume-design/opensync-vendor-rdk-template

Opensync is integrated in turris omnia,
vendorlayer:
https://github.com/rdkcentral/opensync-vendor-rdk-turris 

you need a Wifi hal implementation. This is up to each wifi chip vendor to add implementation for RDKB, there is cfg80211 based wifi hal implementation that is prepared for turris omnia. if vendor do not have own and support cfg80211 then can reuse that hal.

wifi hal apis:
https://github.com/rdkcentral/rdkb-turris-hal/

Thanks and Regards

Srinivas

Hi Srinivas,

Is it possible to create a RDK-B image with .img format?

by default only .bin and ext4 format images are created.

Thanks & Regards,

Shamantha Kumar.

Hi Srinivas,

Thank you for sharing the information.

Actually we are trying to create a image for arm architecture based boards, when we execute the source meta-cmf-bsp-emulator/setup-environment, list of profiles will be displayed. which profile do we hav to select inorder to flash onto a arm boards

source meta-cmf-bsp-emulator/setup-environment
1) meta-cmf-bsp-emulator/conf/machine/qemux86broadbanddev.conf
2) meta-cmf-bsp-emulator/conf/machine/qemux86hybdev.conf
3) meta-cmf-bsp-emulator/conf/machine/qemux86mcdev.conf
4) meta-cmf-raspberrypi/conf/machine/raspberrypi3-64-rdk-broadband.conf
5) meta-cmf-raspberrypi/conf/machine/raspberrypi3-64-rdk-broadband-musl.conf
6) meta-cmf-raspberrypi/conf/machine/raspberrypi-rdk-broadband.conf
7) meta-cmf-raspberrypi/conf/machine/raspberrypi-rdk-broadband-musl.conf
8) meta-cmf-raspberrypi/conf/machine/raspberrypi-rdk-hybrid.conf
9) meta-cmf-raspberrypi/conf/machine/raspberrypi-rdk-hybrid-westeros.conf
10) meta-cmf-raspberrypi/conf/machine/raspberrypi-rdk-mc.conf
11) meta-cmf-raspberrypi/conf/machine/raspberrypi-rdk-mc-westeros.conf
12) meta-raspberrypi/conf/machine/raspberrypi0.conf
13) meta-raspberrypi/conf/machine/raspberrypi2.conf
14) meta-raspberrypi/conf/machine/raspberrypi3.conf
15) meta-raspberrypi/conf/machine/raspberrypi-cm3.conf
16) meta-raspberrypi/conf/machine/raspberrypi-cm.conf
17) meta-raspberrypi/conf/machine/raspberrypi.conf
18) meta-raspberrypi/conf/machine/raspberrypi-rdk-mc.conf
19) meta-rdk-bsp-emulator/conf/machine/qemuarmbroadband.conf
20) meta-rdk-bsp-emulator/conf/machine/qemux86broadband.conf
21) meta-rdk-bsp-emulator/conf/machine/qemux86broadband-dev.conf
22) meta-rdk-bsp-emulator/conf/machine/qemux86broadband-morty.conf
23) meta-rdk-bsp-emulator/conf/machine/qemux86broadband-musl.conf
24) meta-rdk-bsp-emulator/conf/machine/qemux86hyb.conf
25) meta-rdk-bsp-emulator/conf/machine/qemux86hyb-dev.conf
26) meta-rdk-bsp-emulator/conf/machine/qemux86hyb-morty.conf
27) meta-rdk-bsp-emulator/conf/machine/qemux86mc.conf
28) meta-rdk-bsp-emulator/conf/machine/qemux86mc-dev.conf
29) meta-rdk-bsp-emulator/conf/machine/qemux86mc-morty.conf
30) openembedded-core/meta/conf/machine/qemuarm.conf
31) openembedded-core/meta/conf/machine/qemux86-64.conf
32) openembedded-core/meta/conf/machine/qemux86.conf

Thanks & Regards,

Shamantha Kumar.

Hi Unknown User (cpokuru)

can you share us any documents about how to integrate opensync with Turris omnia on RDK-B stack

previously we referred this doc https://www.opensync.io/s/019-1129-21_Building_OpenSync_with_RDK-B.pdf , and on page 6 it was mentioned like The vendor is expected to implement the missing functionality. so, my question is do all the missing functions mentioned in the above thread should be implemented in the respective map.c, radio.c, target.c files? and also how come we can able to know the description of those API's. 

Hi Unknown User (srinivas.k)

can you tell us how to compile the ccsp framework, whenever we are trying to do bitbake ccsp components in the build directory we are getting an error called nothing PROVIDES <component name>

Hi Unknown User (srinivas.k)

for getting USB support do we need to enable any option in rdkb? which actually means due to memory constraints we want to boot from USB for that is there any options to be enabled or packages to be installed in rdkb?

I've been trying to bring up a Turris based router/extender pair but am failing badly with the extender.

I tried to follow: https://wiki.rdkcentral.com/courses/playcourse.action?course=87986923 but that has now become blocked to me.

The steps to build the extender were:

repo init -u https://code.rdkcentral.com/r/manifests -m rdkb-turris-pod-extsrc.xml -b rdk-next
repo sync -j 4 --no-tags --no-clone-bundle

Then in a docker container:

MACHINE=turris-extender source ./meta-turris/setup-environment
bitbake rdk-generic-extender-image

I then flashed the device-tree and zImage onto /dev/mmcblk0p3 and extracted the rootfs to /dev/mmcblk0p5, set the boot parameters accordingly and rebooted. The box comes up with no physical interfaces, just lo.

ps -ef shows some Kernel processes and:

root      1502     1  0 14:09 ?        00:00:00 /lib/systemd/systemd-journald
root      1519     1  0 14:09 ?        00:00:00 /lib/systemd/systemd-udevd
root      2615     1  0 14:09 ?        00:00:00 /sbin/klogd -n
root      2616     1  0 14:09 ?        00:00:00 /usr/sbin/wpa_supplicant -g/va
message+  2617     1  0 14:09 ?        00:00:00 /usr/bin/dbus-daemon --system
root      2628     1  0 14:09 ?        00:00:00 /sbin/syslogd -n -C
root      2629     1  0 14:09 ?        00:00:00 /lib/systemd/systemd-logind
root      2630     1  0 14:09 ttyS0    00:00:00 /bin/login -f
root      2631     1  0 14:09 tty1     00:00:00 /sbin/agetty --noclear tty1 li
root      2724     1  0 14:09 ?        00:00:00 /usr/sbin/hostapd -g /var/run/

systemctl status shows

 turris-extender
    State: degraded
     Jobs: 0 queued
   Failed: 2 units
    Since: Tue 2020-09-29 14:09:38 UTC; 25min ago
   CGroup: /
           ├─init.scope
           │ └─1 /sbin/init
           └─system.slice
             ├─hostapd.service
             │ └─2724 /usr/sbin/hostapd -g /var/run/hostapd/global -B -P /var/run/hostapd-global.pid
             ├─dbus.service
             │ └─2617 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
             ├─system-serial\x2dgetty.slice
             │ └─serial-getty@ttyS0.service
             │   ├─2630 /bin/login -f
             │   ├─2727 -sh
             │   ├─2740 systemctl status
             │   └─2741 /bin/cat
             ├─system-getty.slice
             │ └─getty@tty1.service
             │   └─2631 /sbin/agetty --noclear tty1 linux
             ├─systemd-logind.service
             │ └─2629 /lib/systemd/systemd-logind
             ├─systemd-udevd.service
             │ └─1519 /lib/systemd/systemd-udevd
             ├─busybox-syslog.service
             │ └─2628 /sbin/syslogd -n -C
             ├─systemd-journald.service
             │ └─1502 /lib/systemd/systemd-journald
             ├─busybox-klogd.service
             │ └─2615 /sbin/klogd -n
             └─wpa_supplicant-global.service
               └─2616 /usr/sbin/wpa_supplicant -g/var/run/wpa_supplicant-global -P /var/run/wpa_supplicant-global.pid

and systemctl list-units --failed shows

  UNIT                        LOAD   ACTIVE SUB    DESCRIPTION
● dnsmasq.service             loaded failed failed DNS forwarder and DHCP serv
● systemd-update-utmp.service loaded failed failed Update UTMP about System Bo

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

I've skipped show all the units

Any idea of where to go next? It strikes me this should do something more than start only a few services and have 0 wifi interfaces.

Hello Unknown User (hteece) ,

"ifconfig -a" would show up all wifi interface along with other interfaces.

All interfaces are not "Up" and "Running" state.

Dnsmasq service are not required to be running on extender device.

We have eliminated the need to run script for starting OpenSync on RDKB Gateway. But on extender device, systemd service for starting OpenSync is not yet merged. Meanwhile will find and share the script for running OpenSync on extender device.

Will be updating you shortly.