Versions Compared

Key

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

...

2)OCI image generation.
    -OCI image generation is for broadband application developers, in which they will create their aplication irespective of platform. That image will be competable with all the plaforms but only difference is they need to define the arch of the platform like 32 bit and 64 bit or they can use this to develop applcation for 86 arch based also.
    - As mentioned we will be using generic code for the generation of OCI image , so that will be meta-dac-sdk-broadband meta layer .(https://github.com/rdkcentral/meta-dac-sdk-broadband)
    - As this is platform independent, but you can follow mentioned Jira for any query with respect to oci image image generation for BPIR4.

Jira
serverJIRA
serverId11deff04-0380-3a3d-a916-0849d4e573f7
keyRDKBACCL-325

    -Build instructions are mentioned below for oci image generation, as of now we are offering "iperf3 application" in meta-dac-sdk-broadband.

...

Steps to generate OCI Image

...

 

...

               -By default BPIR4 support aarch64.

  • Build instructions


Code Block
#
titleOCI Build instructions for aarch64
#following
#Following repo commands will required meta-layers see manifest of
 
 https://code.rdkcentral.com/r/plugins/gitiles/manifests/+/refs/heads/rdk-next/rdkb-extsrc.xml


1)repo init -u
 
 https://code.rdkcentral.com/r/rdkcmf/manifests
 
 -m rdkb-extsrc.xml -b kirkstone


 

 

#execute the below command to clone the meta-dac-sdk-broadband and bitbake


2)sed -i '/oe-layers.xml/a  \ \ \ \ <project name="rdkcentral/meta-dac-sdk-broadband" remote="github" path="meta-dac-sdk-broadband" revision="main" /> \n\ \ \ \ <project name="yoctoproject/poky" remote="github" path="." revision="1e0d58c53b7d9c3feb631e46666ae7a3e3614253" upstream="kirkstone"/>' .repo/manifests/rdkb-extsrc.xml

 
 
 
repo sync -j `nproc`

 
3)repo sync -j `nproc` --no-clone-bundle --no-tags


 


# cherrypick the below link to overcome the old syntax override issue with bitbake


4)cd bitbake && git fetch
 
 https://code.rdkcentral.com/r/rdk/components/opensource/oe/bitbake
 
 refs/changes/35/85335/3 && git cherry-pick FETCH_HEAD && cd ..


 


5). ./oe-init-build-env


6)cp ../meta-dac-sdk-broadband/manifests/bblayers.conf conf/


7)echo 'MACHINE = "raspberrypi4-64"' >> conf/local.conf

      
# Building Iperf DAC app
bitbake
  # This step is used to defenentaite the arch where BPIR4 supports 64 bit arch by default.
      
# Building Iperf DAC app
bitbake dac-image-


Bundle Creation

  • https://github.com/rdkcentral/BundleGen

    ->New template for BPIR4.
        1)bpir4_reference.json
        2)bpir4_reference_libs.json
         
  • Generate OCI bundle from the OCI image using Bundlegen tool
    • git clone https://github.com/rdkcentral/BundleGen.git  (clone Bundlegen code.)
    • cd BundleGen
    • export PYTHONPATH=/usr/lib/python3.8/site:$PYTHONPATH
    • tar -xvf dac-image-iperf3-raspberrypi4-20240930100642.rootfs-oci.tar
    • bundlegen generate --platform rpi4_reference_bb_kirkstone oci:dac-image-iperf3-raspberrypi4-20240930100642.rootfs-oci.tar ~/iperf332 (creates the iperf332.tar.gz bundle file)
    • follow this  iperf3 application document to test the iperf3 application using dac 

...