How to generate rootfs image along with opensync package ? 

  • No labels

15 Comments

  1. Hi Deepika Ganapathi Bhat ,

    Thanks for reply. I could build the opensync source code using 'bitbake opensync' after that trying to generate image along with opensync package using 'bitbake rdk-generic-broadband-image'. But the build failed with below error. can you throw some input on this error. 

    ERROR: rdk-generic-broadband-image-1.0-r0 do_rootfs: Unable to install packages. Command '/home/munees/build/build-brcm/tmp/work/brcm-rdk-linux-gnueabi/rdk-generic-broadband-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/munees/build/build-brcm/tmp/work/brcm-rdk-linux-gnueabi/rdk-generic-broadband-image/1.0-r0/opkg.conf -t /home/munees/build/build-brcm/tmp/work/brcm-rdk-linux-gnueabi/rdk-generic-broadband-image/1.0-r0/temp/ipktemp/ -o /home/munees/build/build-brcm/tmp/work/brcm-rdk-linux-gnueabi/rdk-generic-broadband-image/1.0-r0/rootfs  --force_postinstall --prefer-arch-to-version   --add-ignore-recommends qtbase-fonts-pfa --add-ignore-recommends qtbase-fonts-qpf --add-ignore-recommends qtbase-fonts-ttf-vera --add-ignore-recommends udev-hwdb install opensync packagegroup-base-extended packagegroup-core-boot packagegroup-rdk-ccsp-broadband packagegroup-rdk-oss-broadband rdk-logger run-postinsts' returned 255:
    Disfavor package: udev-hwdb
    Installing run-postinsts (1.0) on root
    Downloading file:/home/munees/build/build-brcm/tmp/work/brcm-rdk-linux-gnueabi/rdk-generic-broadband-image/1.0-r0/oe-rootfs-repo/all/run-postinsts_1.0-r10_all.ipk.
    Installing libc6 (2.31+git0+df31c7ca92) on root
    Downloading file:/home/munees/build/build-brcm/tmp/work/brcm-rdk-linux-gnueabi/rdk-generic-broadband-image/1.0-r0/oe-rootfs-repo/cortexa15hf-neon-vfpv4/libc6_2.31+git0+df31c7ca92-r0_cortexa15hf-neon-vfpv4.ipk

    Thanks,

    Munees


  2. Hi Z-Muneeswaran R 

    In order to add OpenSync to the image, append the following line to image’s recipe:
    (File: <image>.bbappend file )

    IMAGE_INSTALL += "opensync"
    Then rebuild the image using bitbake <image>

  3. Hi Deepika Ganapathi Bhat

    I append IMAGE_INSTALL += "opensync" into <image>.bbappend. But still the getting same error as mentioned before. Any other steps missing to install opensync in the image receipe ? .Because I could build the image without opensync 'bitbake <image>'


    1. Hi Z-Muneeswaran R 

      As in the error mentioned in above comment , i could see this line Disfavor package: udev-hwdb
      so,Could you please add the below line in local.conf and verify the build.
      BAD_RECOMMENDATIONS += "udev-hwdb"

      Regards,

      Deepika Bhat

  4. Hi Deepika Ganapathi Bhat ,

    Thanks for your input. I added BAD_RECOMMENDATIONS += "udev-hwdb"  into 'conf/local.conf' file. but there was no impact on this change. I could see the same error even after clean build as well.

    I attached the complete for your reference. Please let me know if some thing else was missing.

    Thanks,

    Munees

  5. Hi Z-Muneeswaran R 

    From the logs attached, we can see

    there is a conflict between procps vmstat and broadcom-wifi vmstat . both trying to install same file. Please try to remove file install from one path and try for build.


    Regards,

    Deepika Bhat.

  6. Hi Deepika Ganapathi Bhat 

    Thanks for your valuable support. Now I could build the opensync with rootfs image. The opensync binaries and libraries are copied into the rootfs image folder. Let me verify on the target system.

    Also if you have any notes or details to verify the opensync with rdk based platform on plume cloud.

    Regards,

    Munees

    1. Hi Z-Muneeswaran R 

      Need a account to be created in plume NOC.

      for now opensync is supported in rpi4 extender and turris-omnia GW . you can refer below link

      https://wiki.rdkcentral.com/display/RDK/WiFi+Extender+with+Turris+Omnia+Reference+Platform+-+Cloud+Access+Guide

  7. Hi Deepika Ganapathi Bhat

    Thanks for sharing details. I have requested access to the link. can you grant permission to access.

    Thanks,

    Munees

    1. Hi Z-Muneeswaran R 

      You can query here.
      Plume's point of contact
      Mail id: integration@opensync.io
      1. Hi Deepika Ganapathi Bhat 

        Access to the link was not given to me. Could you please share the PDF doc of the cloud access guide here. I query to plume as well but no response yet.

        https://wiki.rdkcentral.com/display/RDK/WiFi+Extender+with+Turris+Omnia+Reference+Platform+-+Cloud+Access+Guide

        1. Hi Z-Muneeswaran R 

          Please check now,  access is  provided for the above wiki page.

          1. Hi Deepika Ganapathi Bhat 

            Thanks for giving access. I can access now.

  8. Hi Deepika Ganapathi Bhat

    The manager script used to spawn the ovs-server and opensync managers. I could see ovsdb and openvswitch deamon was running on my target when start the manager init.

    But opensync managers are not running on the device.(checked using command 'ps -w')

    The dm manager was not running even after script starting the manager 'start-stop-daemon -b -o -c  root -S -x /usr/opensync/bin/dm' manager.

    Please help to check what is missing to start the manager ?

    Please refer to console logs after starting the manager init script

    root@Docsis-Gateway:~# /usr/opensync/scripts/managers.init start
    CONFIG_TARGET_PATH_BIN : /usr/opensync/bin
    OPENSYNC_TOOLS_DIR=/usr/opensync/tools
    LAN_IPADDR=10.0.0.1
    LAN_NETMASK=255.255.255.0
    LAN_DHCP_START= 10.0.0.2
    LAN_DHCP_END= 10.0.0.253
    LAN_BRIDGE: br-home
    Starting OpenSync OVSDB management
    /usr/sbin/ovsdb-server is already running
    Starting OVS Switch Daemon
    Error: syntax error
    Details: Parsing ovsdb operation 1 of 1 failed: No table named Wifi_Inet_Config.
    Syntax: {"op":"update","row":{"dhcpd":["map",[["start","10.0.0.2"],["stop","10.0.0.253"]]],"inet_addr":"10.0.0.1","netmask":"255.255.255.0"},"table":"Wifi_Inet_Config","where":[["if_name","==","br-home"}
    /usr/opensync/scripts/managers.init: line 162: platform_start: command not found
    platform_start
    Starting OpenSync Logger to RDK Logger Daemon
    Starting OpenSync managers
    root@Docsis-Gateway:~#