Introduction:

Dac feature is based of 3 stages in BPIR4.
1)Dac functionality in BPIR4.
      -dobby , crun and dsm functionality play a major role from device side, which are used for the running of any dac application in the BPIR4 device .
      -Above mentioned all funtionality has been brought to BPIR4 by including "dac" distro feature, for reference you follow mentioned jira.

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.
    -Build instructions are mentioned below for oci image generation, as of now we are offering "iperf3 application" in meta-dac-sdk-broadband.

#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
 
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  # This step is used to defenentaite the arch where BPIR4 supports 64 bit arch by default.
      
# Building Iperf DAC app
bitbake dac-image-iperf3

3) Bundle Creation
      -After OCI image gets generated we need to generate bundlegen for that generated oci image to make that application platform compatible. (https://github.com/rdkcentral/BundleGen.git)
      - For BPIR4 we are having below mentioned templetes.
            1)bpir4_reference.json
            2)bpir4_reference_libs.json
     -Before generating bundlegen get confirm that your vm has supported packages in local machine(linux machine) for bundlegen support. follow mentioned wiki for bundle gen support.
     Containerization using META DAC SDK in RDK-B RPI#,Install%20Bundlegen%20in%20a%20VM%20or%20any%20host%20machine,-Reference%20%3A%20Containerization

git clone https://github.com/rdkcentral/BundleGen.git  (clone Bundlegen code.)
cd BundleGen
python3 setup.py build 
python3 setup.py install
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 

Generate OCI bundle from the OCI image using Bundlegen tool

CPE code base

• No changes required

Reference ticket

REFPLTB-2924 - Required meta-dac-sdk-broadband kirkstone support for DAC In Progress