Tool/software:
If I build the configs/processor-sdk/processor-sdk-scarthgap-10.01.10.04-config.txt, the tisdk-default image fails to launch the ti-apps-launcher with the following error:
Cannot find /opt/edgeai-gst-apps/init_script.sh
And indeed that folder location doesn't exist.
This can be tracked back to the following service file:
meta-tisdk/recipes-demos/ti-apps-launcher/ti-apps-launcher/ti-apps-launcher-analytics.service 1:# This is a system unit for launching ti-apps-launcher with auto-login as the 5:Description=ti-apps-launcher service 18:ExecStart=/bin/sh -c '. /opt/edgeai-gst-apps/init_script.sh ; /usr/bin/ti-apps-launcher'
This service file is selected because of a commit 3 months ago:
commit 8b0a37e3677376e73419140acc1e04af31048c3d
Author: Chirag Shilwant <c-shilwant@ti.com>
Date: Sat Nov 16 21:16:43 2024 +0530
recipes-demos: ti-demo: wait for dev-dri-card1 before starting on eglfs
- On eglfs based systems, the ti-demo is starting before the
display and gpu cards are enumerated resulting in kernel crashes.
So add the udev rule for /dev/dri/card1 in display cluster
filesystem and wait for it before starting apps on eglfs.
- Switch to using analytics service for AM62x & AM62P as meta-edgeai
is now stable
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
This adds a dependency on the meta-edgeai layer that isn't properly checked for. This commit should have added a RDEPENDS on the recipe which installs the init_script.sh file. Then the build would have failed and this issue would have been found earlier.
configs/processor-sdk/processor-sdk-scarthgap-10.01.10.04-config.txt is missing the meta-edgeai layer.
jcormier@jcormier-MS-7A93:/export/space/jcormier/yocto/yocto_scarthgap/oe-layersetup$ diff -u configs/processor-sdk/processor-sdk-scarthgap-10.01.10.04-config.txt configs/processor-sdk/processor-sdk-scarthgap-chromium-10.01.10.04-config.txt --- configs/processor-sdk/processor-sdk-scarthgap-10.01.10.04-config.txt 2025-01-16 15:37:17.628889152 -0500 +++ configs/processor-sdk/processor-sdk-scarthgap-chromium-10.01.10.04-config.txt 2025-01-16 15:37:17.628889152 -0500 @@ -4,6 +4,7 @@ bitbake,https://git.openembedded.org/bitbake,2.8,6c2641f7a9e92c1b82e306f59ddd3c1249c52cbf meta-tisdk,https://github.com/TexasInstruments/meta-tisdk.git,scarthgap,10.01.10.04,layers= meta-arago,https://git.yoctoproject.org/meta-arago,scarthgap,10.01.10,layers=meta-arago-distro:meta-arago-extras:meta-arago-demos:meta-arago-test +meta-browser,https://github.com/OSSystems/meta-browser.git,master,1ed2254d72a4c25879014c98be287a7e3e22904c,layers=meta-chromium meta-qt5,https://github.com/meta-qt5/meta-qt5.git,scarthgap,eb828418264a49b8d00035cb3d7b12fcea3be801,layers= meta-virtualization,https://git.yoctoproject.org/meta-virtualization,scarthgap,450941a1b6df96285691e8c23d4f332d3c88a994,layers= meta-openembedded,https://git.openembedded.org/meta-openembedded,scarthgap,b8d1a14f7f3b76457c36752202ea7ae5881b6654,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems:meta-multimedia @@ -11,6 +12,7 @@ meta-arm,https://git.yoctoproject.org/meta-arm,scarthgap,7088279c0ab00c7dabefdd4544951b4746b48476,layers=meta-arm:meta-arm-toolchain meta-clang,https://github.com/kraj/meta-clang,scarthgap,9fbfa9db33131abdf3870a94f00199eb53e276e5,layers= oe-core,https://git.openembedded.org/openembedded-core,scarthgap,dac630ab5ee7aa6c5c7c294093adbd11b116c765,layers=meta +meta-edgeai,https://git.ti.com/git/edgeai/meta-edgeai.git,scarthgap,10.01.10.04,layers= OECORELAYERCONF=./sample-files/bblayers.conf.sample OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
I'm pretty sure the only difference expected between the non-chromium and chromium configs is meta-browser.
