• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 1019 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

AM69: ti-processor-sdk-linux-j784s4-evm-09_00_00_06 - SDK Yocto cannot build tisdk-base-image

PROCESSOR-SDK-AM69A: PROCESSOR-SDK-AM69A:

jean briand
Prodigy 70 points
Part Number: PROCESSOR-SDK-AM69A

I cannot even get "ti-processor-sdk-linux-j784s4-evm-09_00_00_06" setup completed. As a last reasorce, I create a VM runnung Ubuntu 22.04 instead of trying to run it on Ubuntu 24.04 or Debian 12.

Same song... the this setup crash again

Here are the last line before the crac:

System has required packages!
--------------------------------------------------------------------------------
Package verification and installation successfully completed
--------------------------------------------------------------------------------
Do you wish to run nfs setup (Press (Y) to run, (n) to skip) ? y
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /targetNFS ]  
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
This step will extract the target filesystem to /targetNFS
 
Note! This command requires you to have administrator priviliges (sudo access)  
on your host.
Press return to continue
xz: (stdin): Compressed data is corrupt
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Failed setup, aborting..
Failed setup, aborting..

What is wrong whit this setup?

  • 0
    Prodigy 70 points

    Finally get it to complete the setup by answering "skip" when asked about creating "tagetNFS" (Already created in past setup trials...). But NOW, I am trying to build, from the yocto-build folder, the system with the commands:

    - ./oe-layertool-setup.sh -f configs/processor-sdk-linux/processor-sdk-linux-09_00_00.txt

    - cd build

    - . conf/setenv

    - MACHINE="j784s4-evm" bitbake -k tisdk-default-image

    and it stopped with these error messages:

    Loading cache: 100% |##################################################################| Time: 0:00:00
    Loaded 3062 entries from dependency cache.
    WARNING: /home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/meta-arago/meta-arago-distro/recipes-core/meta/external-arm-secondary-sdk-toolchain.bb: QA Issue: PN: external-arm-sdk-toolchain-${SECONDARY_TARGET_ARCH} is upper case, this can result in unexpected behavior. [uppercase-pn]
    WARNING: /home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/meta-arago/meta-arago-distro/recipes-core/meta/external-arm-secondary-sdk-toolchain.bb: QA Issue: PN: external-arm-sdk-toolchain-${SECONDARY_TARGET_ARCH} is upper case, this can result in unexpected behavior. [uppercase-pn]
    ERROR: ParseError in None: Not all recipes parsed, parser thread killed/died? Exiting. | ETA: 0:00:21
    ERROR: Parsing halted due to errors, see error messages above

    Summary: There were 2 WARNING messages.
    Summary: There were 2 ERROR messages, returning a non-zero exit code.

    Can someone help me ?

  • 0 in reply to jean briand
    Prodigy 70 points

    ??? Why is it that we have to modify the files in the package to get the system to seems alive?

    the folling file need some changes for the “recette” to work…
     
    “/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/meta-arago/meta-arago-distro/ \
      recipes-core/meta/external-arm-secondary-sdk-toolchain.bb”
     
    FROM:
     
    TARGET_ARCH := "${SECONDARY_TARGET_ARCH}"
    MACHINEOVERRIDES := "${SECONDARY_TARGET_ARCH}"
     
    require recipes-core/meta/external-arm-sdk-toolchain.bb
     
    TO:
     
    TARGET_ARCH := "${secondary_target_arch}"
    MACHINEOVERRIDES := "${secondary_target_arch}"
     
    require recipes-core/meta/external-arm-sdk-toolchain.bb

    Now it move, compiling but generating multiple error messages....

    Can I trust the final result ?

  • 0 in reply to jean briand
    TI__Genius 17235 points

    Hi Jean,

    Can you send me the error messages that bitbake is outputting? Additionally, I've seen the uppercase warning before, and it shouldn't cause the build to fail.

    If bitbake is outputting error messages, then a .wic file should not be generated.

    Can you try the following steps to see if this fixes the issue:

    cd <path-to-SDK>
rm -rf yocto-build
git clone https://git.ti.com/git/arago-project/oe-layersetup.git yocto-build
cd yocto-build
./oe-layertool-setup.sh -f configs/processor-sdk-linux/processor-sdk-linux-09_00_00_07.txt
cd build
. conf/setenv
MACHINE=j784s4-evm bitbake -k tisdk-default-image

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Prodigy 70 points

    I Jared, thanks for the answer. I will first try your recipe and after, I will try again with the old setup to be able to send you all the error message generate during the compile.

    First trial: erro message: "Please make sure local 'en_US.UTF-8' is available on the system.

    executed:

    sudo locale-gen en_US
sudo locale-gen en_US.UTF-8

    and restarted compile, I will keep you inform


     
  • 0 in reply to jean briand
    Prodigy 70 points

    Hi Jared,

    Here is what happenned...

    jean@cclab6vu2204:~/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build$ MACHINE=j784s4-evm bitbake -k tisdk-default-image
    NOTE: Your conf/bblayers.conf has been automatically updated.
    NOTE: Your conf/bblayers.conf has been automatically updated.
    NOTE: Started PRServer with DBfile: /home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/cache/prserv.sqlite3, Address: 127.0.0.1:37757, PID: 17289
    Loading cache: 100% |                                                                                                                                                                              | ETA:  --:--:--
    Loaded 0 entries from dependency cache.
    WARNING: /home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/meta-arago/meta-arago-distro/recipes-core/meta/external-arm-secondary-sdk-toolchain.bb: QA Issue: PN: external-arm-sdk-toolchain-${SECONDARY_TARGET_ARCH} is upper case, this can result in unexpected behavior. [uppercase-pn]
    WARNING: /home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/meta-arago/meta-arago-distro/recipes-core/meta

    /external-arm-secondary-sdk-toolchain.bb: QA Issue: PN: external-arm-sdk-toolchain-${SECONDARY_TARGET_ARCH} is upper case, this can result in unexpected behavior. [uppercase-pn]
    ERROR: ParseError in None: Not all recipes parsed, parser thread killed/died? Exiting.###################################################################                                           | ETA:  0:01:24
    ERROR: Parsing halted due to errors, see error messages above
     
    Summary: There were 2 WARNING messages.
    Summary: There were 2 ERROR messages, returning a non-zero exit code.
    jean@cclab6vu2204:~/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build$  

    Regards,

    Jean Briand

  • 0 in reply to jean briand
    Prodigy 70 points

    Just when to the following cycles (I am desparate to get this to work).

    . conf/setenv
    MACHINE=j784s4-evm bitbake -k tisdk-default-image

    Crashed

    . conf/setenv
    MACHINE=j784s4-evm bitbake -k tisdk-default-image

    Crashed

    . conf/setenv
    MACHINE=j784s4-evm bitbake -k tisdk-default-image

    Now it is working... We will see for how long.

    Jean

  • 0 in reply to jean briand
    Prodigy 70 points

    Hi Jared,

    Already have the following messages:

    ch now buildable
    NOTE: Deferred task mc:k3r5:virtual:native:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/oe-core/meta/recipes-devtools/meson/meson_0.61.3.bb:do_deploy_source_date_epoch now buildable
    NOTE: Deferred task mc:k3r5:virtual:native:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/oe-core/meta/recipes-support/libpcre/libpcre_8.45.bb:do_deploy_source_date_epoch now buildable
    ERROR: openssl-3.0.9-r0 do_unpack: Bitbake Fetcher Error: UnpackError('Unpack command PATH="/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/work/aarch64-oe-linux/openssl/3.0.9-r0/recipe-sysroot-native/usr/bin/perl-native:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/oe-core/scripts:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/work/aarch64-oe-linux/openssl/3.0.9-r0/recipe-sysroot-native/usr/bin/aarch64-oe-linux:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/work/aarch64-oe-linux/openssl/3.0.9-r0/recipe-sysroot/usr/bin/crossscripts:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/work/aarch64-oe-linux/openssl/3.0.9-r0/recipe-sysroot-native/usr/sbin:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/work/aarch64-oe-linux/openssl/3.0.9-r0/recipe-sysroot-native/usr/bin:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/work/aarch64-oe-linux/openssl/3.0.9-r0/recipe-sysroot-native/sbin:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/work/aarch64-oe-linux/openssl/3.0.9-r0/recipe-sysroot-native/bin:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/bitbake/bin:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/hosttools" tar --extract --no-same-owner -z -f /home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/downloads/openssl-3.0.9.tar.gz failed with return value 2', 'www.openssl.org/.../openssl-3.0.9.tar.gz')
    ERROR: Logfile of failure stored in: /home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/build/arago-tmp-default-glibc/work/aarch64-oe-linux/openssl/3.0.9-r0/temp/log.do_unpack.44173
    ERROR: Task (/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/oe-core/meta/recipes-connectivity/openssl/openssl_3.0.9.bb:do_unpack) failed with exit code '1'
    WARNING: rpm-native-1_4.17.1-r0 do_fetch: Failed to fetch URL git://github.com/rpm-software-management/rpm;branch=rpm-4.17.x;protocol=https, attempting MIRRORS if available
    ERROR: Build of do_deploy_source_date_epoch failed
    ERROR: Traceback (most recent call last):
      File "/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/bitbake/lib/bb/build.py", line 763, in exec_task
        return _exec_task(fn, task, d, quieterr)
      File "/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/bitbake/lib/bb/build.py", line 740, in _exec_task
        make_stamp(task, localdata)
      File "/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/bitbake/lib/bb/build.py", line 870, in make_stamp
        bb.parse.siggen.dump_sigtask(file_name, task, stampbase, True)
      File "/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/oe-core/meta/lib/oe/sstatesig.py", line 229, in dump_sigtask
        super(bb.siggen.SignatureGeneratorBasicHash, self).dump_sigtask(fn, task, stampbase, runtime)
      File "/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/bitbake/lib/bb/siggen.py", line 436, in dump_sigtask
        raise err
      File "/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/bitbake/lib/bb/siggen.py", line 426, in dump_sigtask
        with bb.compress.zstd.open(fd, "wt", encoding="utf-8", num_threads=1) as f:
      File "/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/bitbake/lib/bb/compress/_pipecompress.py", line 148, in close
        self._check_process()
      File "/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/bitbake/lib/bb/compress/_pipecompress.py", line 139, in _check_process
        raise CompressionError("Process died with %d" % returncode)
    bb.compress._pipecompress.CompressionError: Process died with -11
     
    ERROR: Task (virtual:native:/home/jean/ti-processor-sdk-linux-j784s4-evm-09_00_00_06/yocto-build/sources/oe-core/meta/recipes-devtools/python/python3-jinja2_3.1.1.bb:do_deploy_source_date_epoch) failed with exit code '1'

    Jean

  • 0 in reply to jean briand
    TI__Genius 17235 points

    Hi Jean,

    Can you try editing the conf/local.conf file and uncomment and set the BB_NUMBER_THREADS and PARALLEL_MAKE variables to half the number of cores of your PC? Then try running bitbake again.

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Prodigy 70 points

    Hi Jared,

    I did a drastic change... pulled out of the dust one of my old computer (Suse board with intel 8 cores porcessor) load ubuntu 22.04 LTS Desktop and started over. Everything seems to work. I have 69% of the work completed and it is proceeding without any error message. I do not know. I was using a VM (Oracle VirtualBox) loaded with the same software, with more horsepower, but something is wrong with that setup. I want to get to the end and start working. The "new" computer is way slower, but at least I am getting somewhere.

    Really sorry for all the problem and I do appreciate your help, thanks again

    Jean Briand

  • +1 in reply to jean briand
    TI__Genius 17235 points

    Hi Jean,

    Glad to hear that you were able to get it running on another device. We use containers for building images, but I'm not sure why your VM wouldn't work as well.

    If you can mark the issue as resolved, then the thread will be closed.

    Best,
    Jared