TDA4VH-Q1: yocto-build issue for Ti SDK-10 and TI-SDK-11

Part Number: TDA4VH-Q1

I am facing issue of do_package in yocto build of custom-image and linux-ti-staging.

Attaching file for your reference.  Please provide solution for these task. 

linux-libc-headers  nativesdk-linux-libc-headers  base-files  ca-certificates iso-codes
nativesdk-gnu-config alsa-topology-conf  alsa-ucm-conf  update-rc.d  volatile-binds 
os-release  shadow-securetty  liberation-fonts  netbase  run-postinsts
wayland-protocols qemuwrapper-cross nativesdk-qemuwrapper-cross  ti-img-rogue-umlibs
linux-ti-staging.
All ended up in do_package failure for total  20 package.

Option Tried: 1. Cleanall pacakage build.

2. removed tmp folder and build

3. done setup in different PC and build.

Can you please provide solution or support on build issue

log-fail-kernel.txt 

 

 

  • Hi ,

    What version of the SDK is this?

    What commands have you executed?

    Have you looked at this FAQ:  [FAQ] PROCESSOR-SDK-J784S4: How Do I Build Yocto Images and Packages for J7 Devices?  

    Best,
    Jared

  • Hi Jared,
    I am running build for SDK-11.(11.02.00) I am giving custom build recipes command as per my distro file. distro is based on arago distro only. 

    Attaching Distro(aptiv-ospas120) and bblayer and loca.conf for your reference

    # This template file was created by taking the oe-core/meta/conf/bblayers.conf
    # file and removing the BBLAYERS section at the end.
    
    # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
    # changes incompatibly
    LCONF_VERSION = "7"
    
    BBPATH = "${TOPDIR}"
    BBFILES ?= ""
    
    YOCTOROOT = "${@os.path.abspath(os.path.join("${TOPDIR}", os.pardir))}"
    
    # Layers configured by oe-core-setup script
    BBLAYERS += " \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-arago/meta-arago-distro \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-arago/meta-arago-extras \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-arago/meta-arago-test \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-qt5 \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-virtualization \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-openembedded/meta-networking \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-openembedded/meta-python \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-openembedded/meta-oe \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-openembedded/meta-gnome \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-openembedded/meta-filesystems \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-openembedded/meta-multimedia \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-lts-mixins \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-ti/meta-ti-extras \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-ti/meta-beagle \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-ti/meta-ti-bsp \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-arm/meta-arm \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-arm/meta-arm-toolchain \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-clang \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/oe-core/meta \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-tisdk/meta-ti-foundational \
    	/projects/ceer/ospas120/yocto-sdk-11/degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/sources/meta-edgeai \
    "
    BBLAYERS += " \
            ${YOCTOROOT}/sources/meta-aptiv-ospas120 \
    "
    BBLAYERS += " \
            ${YOCTOROOT}/sources/meta-aptiv-coreio \
    "
    
    
    # Name and version of the distribution
    DISTRO_NAME = "OSPAS120"
    DISTRO_VERSION = "2023.10"
    DISTRO_FEED_URI ?= "http://lcpd.itg.ti.com"
    BUILD_VARIANT = "${@['prod','rt','systest'][int(d.getVar('ARAGO_RT_ENABLE'))+int(d.getVar('ARAGO_SYSTEST_ENABLE'))*2]}"
    TISDK_VERSION ?= "live"
    FEEDURIPREFIX ?= "builds/${DISTRO}-kirkstone/${BUILD_VARIANT}/${MACHINE}/latest/packages/"
    
    OPKG_ARGS:remove = "--prefer-arch-to-version"
    
    TI_MIRROR = "http://software-dl.ti.com/processor-sdk-mirror/sources/"
    MIRRORS += " \
    bzr://.*/.*      ${TI_MIRROR} \n \
    cvs://.*/.*      ${TI_MIRROR} \n \
    git://.*/.*      ${TI_MIRROR} \n \
    gitsm://.*/.*    ${TI_MIRROR} \n \
    hg://.*/.*       ${TI_MIRROR} \n \
    osc://.*/.*      ${TI_MIRROR} \n \
    p4://.*/.*       ${TI_MIRROR} \n \
    npm://.*/.*      ${TI_MIRROR} \n \
    ftp://.*/.*      ${TI_MIRROR} \n \
    https?$://.*/.*  ${TI_MIRROR} \n \
    svn://.*/.*      ${TI_MIRROR} \n \
    "
    
    # SDK paths and names
    SDK_NAME_PREFIX = "ospas120"
    SDK_VERSION = "${DISTRO_VERSION}"
    SDK_VENDOR = "-${SDK_NAME_PREFIX}"
    SDK_NAME = "${SDK_NAME_PREFIX}-${SDK_VERSION}"
    SDKPATHINSTALL = "/opt/${SDK_NAME}"
    
    IMAGE_FSTYPES += "tar.xz.md5sum"
    
    # Extra boot files for WIC images
    do_image_wic[depends] += "tisdk-uenv:do_deploy"
    IMAGE_BOOT_FILES += "uEnv.txt"
    
    # Mask any broken recipes (currently none)
    #BBMASK = ""
    
    TCMODEAPPEND ?= "-${TCMODE}"
    TMPDIR .= "${TCMODEAPPEND}"
    
    # Start with default set of distro features
    DISTRO_FEATURES = "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}"
    
    # Add additional distro features
    DISTRO_FEATURES:append = " pam wayland opengl"
    DISTRO_FEATURES:remove = "x11"
    #DISTRO_FEATURES:append = " opencl"
    DISTRO_FEATURES:append = " vulkan"
    DISTRO_FEATURES:append = " opencv"
    DISTRO_FEATURES:append = " openmp"
    
    # Normally target distro features will not be applied to native builds:
    # Native distro features on this list will use the target feature value
    DISTRO_FEATURES_FILTER_NATIVE:append = " opencl opencv openmp"
    DISTRO_FEATURES_FILTER_NATIVESDK:append = " opencl opencv openmp"
    
    # Set global runtime providers for major components
    ARAGO_SYSVINIT ??= "0"
    INIT_MANAGER ?= "${@['systemd','sysvinit'][int(d.getVar('ARAGO_SYSVINIT'))]}"
    
    # Distro-specific package configuration
    PACKAGECONFIG:append:pn-systemd = " coredump networkd resolved serial-getty-generator"
    
    # Configure Qt5 flags (GLES is still required for qtdeclarative and qtwebkit)
    PACKAGECONFIG_GL:pn-qtbase = "gles2 linuxfb"
    PACKAGECONFIG_DISTRO:pn-qtbase = "icu examples accessibility gif gbm kms libinput"
    PACKAGECONFIG_FONTS:pn-qtbase = "fontconfig"
    PACKAGECONFIG:remove:pn-qtwayland = "xcomposite-egl xcomposite-glx"
    
    # Add gstreamer in package configuration to enable video
    PACKAGECONFIG:append:pn-qtmultimedia = " gstreamer"
    
    # Add examples in Qt5 package configurations
    PACKAGECONFIG:append:pn-qtcharts = " examples"
    #PACKAGECONFIG:append:pn-qtdeclarative = " examples"
    PACKAGECONFIG:append:pn-qtlocation = " examples"
    PACKAGECONFIG:append:pn-qtmultimedia = " examples"
    PACKAGECONFIG:append:pn-qtscript = " examples"
    PACKAGECONFIG:append:pn-qtserialport = " examples"
    PACKAGECONFIG:append:pn-qtsvg = " examples"
    PACKAGECONFIG:append:pn-qtwayland = " examples"
    PACKAGECONFIG:append:pn-qtwebengine = " examples"
    
    # Prefer OpenSSL over GnuTLS for curl due to TSU exemptions
    PACKAGECONFIG:pn-curl = "${@bb.utils.contains("DISTRO_FEATURES", "ipv6", "ipv6", "", d)} proxy openssl verbose zlib"
    
    PACKAGECONFIG:pn-glmark2 = "drm-gles2 wayland-gles2"
    
    # Set this to empty string to prevent xwayland config from being added
    PACKAGECONFIG:pn-weston-init = ""
    
    # Enable testing for opencl and vulkan with piglit
    PACKAGECONFIG:append:pn-piglit = " \
        ${@bb.utils.filter("DISTRO_FEATURES", "opencl vulkan", d)} \
        ${@bb.utils.contains("DISTRO_FEATURES", "opengl", "deqp-gles", "", d)} \
        ${@bb.utils.contains("DISTRO_FEATURES", "vulkan", "deqp-vk", "", d)} \
    "
    PACKAGECONFIG:pn-opengl-es-cts = "${@bb.utils.contains("DISTRO_FEATURES", "wayland", "wayland", "surfaceless", d)}"
    PACKAGECONFIG:pn-vulkan-cts = "${@bb.utils.contains("DISTRO_FEATURES", "wayland", "wayland", "surfaceless", d)}"
    
    # Use llvmpipe for better performance with software rendering
    # Only available for armv6+ devices
    #MESA_GALLIUM_LLVM_PACKAGECONFIG = "gallium-llvm"
    #MESA_GALLIUM_LLVM_PACKAGECONFIG:omapl138 = ""
    #PACKAGECONFIG:append:pn-mesa = " ${MESA_GALLIUM_LLVM_PACKAGECONFIG}"
    #PACKAGECONFIG:append:pn-mesa-pvr = " ${MESA_GALLIUM_LLVM_PACKAGECONFIG}"
    
    # Enable encryption support in open62541
    PACKAGECONFIG:append:pn-open62541 = " encrypt"
    
    # Enable netperf intervals/pacing and histogram
    PACKAGECONFIG:append:pn-netperf = " intervals histogram"
    
    # Use OpenGL ES2 for SDL2
    PACKAGECONFIG_GL:pn-libsdl2 = "gles2"
    
    # Add KMS/DRM backend support
    PACKAGECONFIG:append:pn-libsdl2 = " kmsdrm"
    
    # Enable cryptodev/devcrypto engine in OpenSSL 1.1
    PACKAGECONFIG:append:pn-openssl = " cryptodev-linux"
    
    # Enable GST_TRACER logging in gstreamer
    PACKAGECONFIG:append:pn-gstreamer1.0 = " tracer-hooks coretracers"
    
    # Enable kmssink in gstreamer
    PACKAGECONFIG:append:pn-gstreamer1.0-plugins-bad = " kms"
    
    # Enable gstreamer plugin for libcamera
    PACKAGECONFIG:append:pn-libcamera = " gst"
    
    # Disable pulseaudio routing in alsa by default
    PACKAGECONFIG:remove:pn-alsa-plugins = "pulseaudio"
    RDEPENDS:pulseaudio-server:remove = "alsa-plugins-pulseaudio-conf"
    
    # Configure RAMFS for jailhouse linux-demo
    JH_RAMFS_IMAGE = "tisdk-jailhouse-inmate"
    
    # Enable UI and scripting for perf
    PERF_FEATURES_ENABLE ?= "perf-scripting perf-tui"
    
    # Do not warn on meta-gnome w/o x11
    SKIP_META_GNOME_SANITY_CHECK = "1"
    
    ARAGO_KERNEL_SUFFIX ?= ""
    
    # Set real-time kernel suffix
    ARAGO_RT_ENABLE ?= "0"
    ARAGO_KERNEL_SUFFIX:append = "${@oe.utils.conditional("ARAGO_RT_ENABLE", "1", "-rt", "", d)}"
    
    # Set systest kernel suffix
    ARAGO_SYSTEST_ENABLE ?= "0"
    ARAGO_KERNEL_SUFFIX:append = "${@oe.utils.conditional("ARAGO_SYSTEST_ENABLE", "1", "-systest", "", d)}"
    IMAGE_FSTYPES:remove = "${@['','ubi ubifs'][d.getVar('ARAGO_SYSTEST_ENABLE') == '1']}"
    
    # Enable basic stack and buffer overflow protections
    #TARGET_CPPFLAGS += "-fstack-protector -D_FORTIFY_SOURCE=1"
    #TARGET_CPPFLAGS += "-fstack-protector"
    
    # Load default preferences
    require conf/distro/include/arago-prefs.inc
    
    # Allow branding on top of Arago Distro and Core TI-SDK
    # If ARAGO_BRAND is not set in local.conf, default to core
    ARAGO_BRAND ??= "core"
    
    #require conf/distro/include/branding-${ARAGO_BRAND}.inc
    
    # Disable polkit's systemd configuration from meta-oe
    POLKITAUTH = ""
    
    # Disable meta-virtualization sanity check and warning
    SKIP_META_VIRT_SANITY_CHECK = "1"
    
    # Set ENTERPRISE_DISTRO flag to ensure that recipes that have been flagged
    # do not attempt to enable features that have potential commercial
    # licensing issues.
    ENTERPRISE_DISTRO = "1"
    
    # oe-core uses external libav instead of internal libav for gst-ffmpeg. We
    # disable by default the codecs in libav that causes issues with shipping an
    # Arago based SDK. No need to prevent gst-ffmpeg from being used since we
    # disable troublesome software.
    LICENSE_FLAGS_ACCEPTED = "commercial_gst-ffmpeg commercial_gstreamer1.0-libav commercial_faad2 non-commercial_netperf"
    
    # Do not package own copy of perl into devkit, rely on host one
    ASSUME_PROVIDED += "nativesdk-perl"
    BSP_KERNEL_VERSION = "6.6%"
    
    # CONF_VERSION is increased each time build/conf/ changes incompatibly
    CONF_VERSION = "2"
    
    #
    # Where to place downloads
    #
    # During a first build the system will download many different source code
    # tarballs from various upstream projects. This can take a while, particularly
    # if your network connection is slow. These are all stored in DL_DIR. When
    # wiping and rebuilding you can preserve this directory to speed up this part
    # of subsequent builds. This directory is safe to share between multiple builds
    # on the same machine too.
    DL_DIR = "${TOPDIR}/../../../../degum_coreIO_Safety_CEER_TDA4_CoreIO_Toolchain/10056038_GP_COMP_OSPAS120_PerformanceController_TDA4_meta_APTIV_BSP/yocto-build/downloads"
    
    #
    # Where to place shared-state files
    #
    # BitBake has the capability to accelerate builds based on previously built
    # output. This is done using "shared state" files which can be thought of as
    # cache objects and this option determines where those files are placed.
    #
    # You can wipe out TMPDIR leaving this directory intact and the build would
    # regenerate from these files if no changes were made to the configuration.
    # If changes were made to the configuration, only shared state files where the
    # state was still valid would be used (done using checksums).
    SSTATE_DIR = "${TOPDIR}/sstate-cache"
    
    #
    # Shared-state files from other locations
    #
    # As mentioned above, shared state files are prebuilt cache data objects which
    # can be used to accelerate build time. This variable can be used to configure
    # the system to search other mirror locations for these objects before it
    # builds the data itself.
    #
    # This can be a filesystem directory, or a remote url such as http or ftp.
    # These would contain the sstate-cache results from previous builds (possibly
    # from other machines). This variable works like fetcher MIRRORS/PREMIRRORS
    # and points to the cache locations to check for the shared objects.
    #SSTATE_MIRRORS ?= "\
    #file://.* http://someserver.tld/share/sstate/ \n \
    #file://.* file:///some/local/dir/sstate/"
    
    #
    # Where to place the build output
    #
    # This option specifies where the bulk of the building work should be done and
    # where BitBake should place its temporary files and output. Keep in mind that
    # this includes the extraction and compilation of many applications and the toolchain
    # which can use Gigabytes of hard disk space.
    TMPDIR = "${TOPDIR}/arago-tmp"
    
    # By default, DEPLOY_DIR is inside TMPDIR, but can be changed here to be outside
    #DEPLOY_DIR = "${TOPDIR}/deploy"
    
    #
    # Machine Selection
    #
    # You need to select a specific machine to target the build with. There are a selection
    # of emulated machines available which can boot and run in the QEMU emulator:
    #
    #MACHINE ?= "arago"
    
    #
    # Package Management configuration
    #
    # This variable lists which packaging formats to enable. Multiple package backends
    # can be enabled at once and the first item listed in the variable will be used
    # to generate the root filesystems.
    # Options are:
    #  - 'package_deb' for debian style deb files
    #  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
    #  - 'package_rpm' for rpm style packages
    # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
    # We default to ipk:
    PACKAGE_CLASSES ?= "package_ipk"
    
    #
    # SDK/ADT target architecture
    #
    # This variable specified the architecture to build SDK/ADT items for and means
    # you can build the SDK packages for architectures other than the machine you are
    # running the build on (i.e. building i686 packages on an x86_64 host._
    # Supported values are i686 and x86_64
    SDKMACHINE ?= "x86_64"
    
    #
    # Extra image configuration defaults
    #
    # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
    # images. Some of these options are added to certain image types automatically. The
    # variable can contain the following options:
    #  "dbg-pkgs"       - add -dbg packages for all installed packages
    #                     (adds symbol information for debugging/profiling)
    #  "dev-pkgs"       - add -dev packages for all installed packages
    #                     (useful if you want to develop against libs in the image)
    #  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
    #  "tools-debug"    - add debugging tools (gdb, strace)
    #  "tools-profile"  - add profiling tools (oprofile, exmap, lttng valgrind (x86 only))
    #  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
    #  "debug-tweaks"   - make an image suitable for development
    #                     e.g. ssh root access has a blank password
    # There are other application targets that can be used here too, see
    # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
    # We default to enabling the debugging tweaks.
    EXTRA_IMAGE_FEATURES = "debug-tweaks"
    
    #
    # Additional image features
    #
    # The following is a list of additional classes to use when building images which
    # enable extra features. Some available options which can be included in this variable
    # are:
    #   - 'buildstats' collect build statistics
    #   - 'image-swab' to perform host system intrusion detection
    # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
    USER_CLASSES ?= "buildstats"
    
    # By default disable interactive patch resolution (tasks will just fail instead):
    PATCHRESOLVE = "noop"
    
    # By default the machine configuration file sets the IMAGE_FSTYPES.  But if you
    # would like to add additional file system types you can uncomment the
    # following line and add the additional IMAGE_FSTYPES you want created
    # as part of the build flow.  Some common types are listed below and you
    # can remove the ones you do not want.
    # IMAGE_FSTYPES += "jffs2 cramfs ext2.gz ext3.gz squashfs ubi tar.gz tar.bz2 cpio"
    
    #
    # Parallelism Options
    #
    # These two options control how much parallelism BitBake should use. The first
    # option determines how many tasks bitbake should run in parallel:
    #
    # BB_NUMBER_THREADS ?= "1"
    #
    # The second option controls how many processes make should run in parallel when
    # running compile tasks:
    #
    # PARALLEL_MAKE ?= "-j 1"
    #
    # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
    # be appropriate for example
    #
    # NOTE: By default, bitbake will choose the number of processeors on your host
    # so you should not need to set this unless you are wanting to lower the number
    # allowed.
    #
    
    DISTRO  = "aptiv-ospas120"
    MACHINE ?= "j784s4-ospas120"
    
    # Set terminal types by default it expects gnome-terminal
    # but we chose xterm
    TERMCMD = "${XTERM_TERMCMD}"
    TERMCMDRUN = "${XTERM_TERMCMDRUN}"
    
    # Don't generate the mirror tarball for SCM repos, the snapshot is enough
    BB_GENERATE_MIRROR_TARBALLS = "0"
    
    # Uncomment this to remove work directory after packaging to save disk space
    #INHERIT += "rm_work"
    
    # Keep one set of images by default
    RM_OLD_IMAGE = "1"
    
    # Enable local PR service for binary feeds
    PRSERV_HOST = "localhost:0"
    
    # Enable hash equiv server
    BB_SIGNATURE_HANDLER = "OEEquivHash"
    BB_HASHSERVE = "auto"
    
    # It is recommended to activate "buildhistory" for testing the PR service
    INHERIT += "buildhistory"
    BUILDHISTORY_COMMIT = "1"
    
    INHERIT += "image-buildinfo"
    IMAGE_BUILDINFO_VARS:append = " DATETIME DISTRO_NAME IMAGE_BASENAME MACHINE TUNE_PKGARCH"
    IMAGE_BUILDINFO_VARS:append = " MACHINE_FEATURES DISTRO_FEATURES COMMON_FEATURES IMAGE_FEATURES"
    IMAGE_BUILDINFO_VARS:append = " TUNE_FEATURES TARGET_FPU"
    
    INHERIT += "own-mirrors"
    SOURCE_MIRROR_URL = "http://software-dl.ti.com/processor-sdk-mirror/sources/"
    
    INHERIT += "rm_work"
    RM_WORK_EXCLUDE += "u-boot-ospas120 aptiv-coreio-tiny-initramfs"
    
    IMAGE_INSTALL:append = "mtd-utils"
    
    PACKAGECONFIG:append:pn-glib-2.0 = "libpcre2-8" 
    
    BBMASK += "meta-aptiv-ospas120/recipes-bsp/u-boot/"
    
    LICENSE_FLAGS_ACCEPTED:append = "commercial_ffmpeg commercial"
    ASSUME_PROVIDED:remove = "tar-native"
    
    #@TYPE: Machine
    #@NAME: OSPAS120 based on TI TDA4 J784S4
    #@DESCRIPTION: Machine configuration for the Aptiv's J784S4 based OSPAS120
    
    require conf/machine/include/j784s4.inc
    
    PREFERRED_PROVIDER_virtual/bootloader = "u-boot-ospas120"
    PREFERRED_PROVIDER_u-boot = "u-boot-ospas120"
    
    TFA_K3_USART = "0x4"
    OPTEE_K3_USART = "0x4"
    
    KERNEL_DEVICETREE_PREFIX = " \
        ti/k3-j784s4 \
        ti/k3-fpdlink \
        ti/k3-j7200-evm-mcspi-loopback \
        ti/k3-am69-sk \
    "
    
    KERNEL_DEVICETREE = " \
        ti/k3-j784s4-ospas120.dtb \
    "
    
    UBOOT_MACHINE = "j784s4_evm_a72_defconfig"
    
    IMAGE_FSTYPES = "tar.xz wic.xz ext4"
    

  • Hi ,

    You're building kirkstone for 11.X? 11.X should be scarthgap.

    Additionally, does your image recipe have all of the dependencies it requires? It appears that a lot of Linux device trees and modules are missing in your error log.

    Best,
    Jared

  • Hi Jared,

    I am building scarthgap only. I have two layer integrated on top ti's layer. 

    Yes It was building earlier, suddenly build breaks for many PC's.

  • Hi ,

    Yes It was building earlier, suddenly build breaks for many PC's.

    What does this mean? Did the build work at one point in time? If so, what changes did you make?

    Best,
    Jared

  • Yes Build was working at one point of time. then from last week build is failing, No change has done in between

  • Hi ,

    Can you test removing all the built artifacts and starting from scratch?

    Best,
    Jared

  • Hi Jared,

    I had removed all the build artifact and tried it, It is same error.

    Thanks and Regards

    Ankit Kumar Singh

  • Hi ,

    Do you have any other error logs?

    I don't understand how your build could work one day and then fail the next when you've done no changes to any of the sources. The most likely reason would be that a recipe/package failed to build and was corrupted. The solution to this would be to start over from scratch. 

    Best,
    Jared

  • Hi Jared,

    Attaching log for linux-ti-staging build, build fails even after complete clean of directory and fresh cloning also.

     20260722130941.log

  • Hi ,

    I've replicated your issue. It appears there is an issue somewhere with openembedded-core. If you move to the most recent scarthgap commit, the issue no longer appears.

    You can also move to the 11.02.01 SDK, it uses that commit and does not experience the issue.

    Best,
    Jared

  • Hi Jared,

    I tried building with the new SDK, but I'm still seeing the same issue. While debugging, I noticed that the tisdk-default-image build is failing in the linux-firmware recipe.

    Could you please help me debug this issue? Most of our team members are facing the same problem.

    I'm attaching the build log for reference.

    6758.log.txt

    Thanks & regards,
    Albin

  • Hi ,

    What config are you using? Did you try the solution mentioned in my previous reply? What commit is the oe-core source repository at?

    I do not see an issue when building linux-libc-headers with the processor-sdk-analytics-11.02.01-config.txt config.

    Best,
    Jared

  • Hi Jared,

       I tried applying the following patches, but they did not resolve the issue:,

    glibc-testsuite: Do not generate SPDX - openembedded-core - OpenEmbedded Core layer

    cve-update: Avoid NFS caching issues - openembedded-core - OpenEmbedded Core layer

    build-appliance-image: Update to scarthgap head revisions - openembedded-core - OpenEmbedded Core layer

    Unfortunately, we cannot move to SDK 11 at this time due to customer requirements. We need to continue using SDK 10_01_00_05.

    Could you please help identify a fix or workaround that can be applied to SDK 10_01_00_05?

    Thank you for your assistance.

  • Hi ,

    So are you still on Kirkstone?

    Best,
    Jared

  • Hi Jared,

    Thank you for your response. The issue has been resolved after updating the patch pseudo folder below.

    openembedded-core - OpenEmbedded Core layer

  • Hi ,

    I will mark this thread as closed then.

    Best,
    Jared