TDA4VM: Need to run EWAOL on TDA4VM

Hi Jared,

Thanks for your reply!

I am trying to add the meta-ewaol layer to my yocto build.

Can you please tell me where do I find the "IMAGE_INSTALL" variable to add the necessary packages?

Hi Progna,

You can set the variable within your local.conf or write a custom recipe.

You can read the Yocto documentation about it here: docs.yoctoproject.org/.../customizing-images.html

Best,
Jared

Hi Jared.

We tried to add layers for meta-ewaol along with base yocto build, we have used the below steps :

1. Clone the meta-ewaol repository:
Run this in your top-level Yocto build directory (~/yocto-build):
cd ~/yocto-build
git clone https://gitlab.com/soafee/ewaol/meta-ewaol.git -b kirkstone-dev

2. Add the meta-ewaol layers:
Use bitbake-layers to add the required layers to your existing build:
cd ~/yocto-build/build
bitbake-layers add-layer ../meta-ewaol/meta-ewaol-distro
bitbake-layers add-layer ../meta-ewaol/meta-ewaol-bsp
bitbake-layers add-layer ../meta-ewaol/meta-ewaol-tests

Check added layers:
bitbake-layers show-layers
You should now see meta-ewaol-distro, meta-ewaol-bsp, meta-ewaol-tests.

 3. Update your local.conf:
Edit your local.conf (located in ~/yocto-build/build/conf/local.conf) and add these variables to enable the EWAOL features:

 # Set the MACHINE for your TI J721E EVM board
MACHINE = "j721e-evm"

# Enable Docker, virtualization (Xen), and K3s (Kubernetes) in the image
DISTRO_FEATURES:append = " virtualization k3s docker ewaol-virtualization"

# Optional: set EWAOL as your distro if you want EWAOL defaults.
# DISTRO = "ewaol"

 4. Add EWAOL components into existing tisdk-adas-image:
Edit the existing recipe (tisdk-adas-image.bb) to include EWAOL packages (Docker, Xen, Kubernetes):
vim ~/yocto-build/meta-arago-distro/recipes-core/images/tisdk-adas-image.bb
Added this line (or similar) to include EWAOL components explicitly:
IMAGE_INSTALL:append = " \
    docker \
    xen \
    k3s \
"

 5. Build your unified image:
Rebuild the existing TI SDK image (tisdk-adas-image):
cd ~/yocto-build/build
bitbake -k tisdk-adas-image
This will generate a unified .wic image that includes both the original TI SDK components and the additional EWAOL functionality.

 6. Flash and run on TI J721E EVM:
Locate the .wic image in:
~/yocto-build/build/tmp/deploy/images/j721e-evm/tisdk-adas-image-j721e-evm.wic
Flash the image to an SD card using:
sudo dd if=tisdk-adas-image-j721e-evm.wic of=/dev/sdX bs=4M status=progress conv=fsync
(Replace /dev/sdX with your actual SD card device.)
Insert the SD card into your TI J721E EVM, boot it up, and you now have your existing TI environment plus EWAOL support.

 7. Verify Docker, Xen, and Kubernetes (k3s):
Once booted, run the following tests:
Docker Test:
docker run hello-world
Xen Check:
xl info
k3s Kubernetes Check:
kubectl get nodes

Even after this, the ewaol is not showing up in the target, we tried with the below command to verify:

systemctl status --no-pager --lines=0 docker.service k3s.service xendomains.service

We did not get any output.

Any help is appreciated!

Hi Progna,

Progna Chowdhury said:

Once booted, run the following tests:
Docker Test:
docker run hello-world
Xen Check:
xl info
k3s Kubernetes Check:
kubectl get nodes

So are docker, xen, and k3s running properly?

Progna Chowdhury said:

Even after this, the ewaol is not showing up in the target, we tried with the below command to verify:

systemctl status --no-pager --lines=0 docker.service k3s.service xendomains.service

I'm not familiar with EWAOL, is there a specific package that needs to be included in the Yocto image's recipe?

I additionally found this link: https://meta-ewaol.docs.soafee.io/en/latest/user_guide/extend.html#porting-ewaol-to-a-custom-or-unsupported-target-platform-via-kas 

Best,
Jared