SK-AM62: Yocto build keeps crashing

Part Number: SK-AM62

I am running the following for TI-SDK 9.00.00.03:

cd tisdk/build
. conf/setenv
export TOOLCHAIN_PATH_ARMV7=$HOME/gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf
export TOOLCHAIN_PATH_ARMV8=$HOME/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu
export TI_SECURE_DEV_PKG=../core-secdev-k3
MACHINE=am62xx-evm bitbake -k tisdk-default-image

It gets so far and then crashes.  The xterm goes away & there's no indication of error.  Also, QT5 keeps failing to build.  Is anyone else having this trouble with default-image?

  • More information:  I am running Yocto on Ubuntu 22.04.  I've seen other complaints about using Yocto with Ubuntu 22.04.  Is this a known issue with TI -SDK as well?

  • I am running the following for TI-SDK 9.00.00.03:

    I can build this under Ubuntu 22.04 without issues; it's our officially supported distro for SDK v9.x

    export TOOLCHAIN_PATH_ARMV7=$HOME/gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf
    export TOOLCHAIN_PATH_ARMV8=$HOME/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu
    export TI_SECURE_DEV_PKG=../core-secdev-k3

    Try leaving out these 3 steps, they do not apply to SDK v9.x. With SDK v9.x we switched to Yocto-internal toolchains (so no more TOOLCHAIN_PATH variables needed --> this is still in the docs but will be fixed), and the TI_SECURE_DEV_PKG is also managed internally. Then try setting everything up from scratch in a clean folder, also making sure you installed all of the prerequisites listed here https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/09_00_00_03/exports/docs/linux/Overview_Building_the_SDK.html#prerequisites-one-time-setup

    Regards, Andreas

  • Thanks for the clarification on the documentation.  I do have all the requirements loaded, that was the first thing I did.  I'll try this and let you know if it resolves this problem.  I also tried "thinlinux" build, it also failed.  It was having trouble with git clone of powervr submodule.  Is this all part of the same problem?

  • Still hanging here with "tisdk-default-image".  I got rid of the EXPORT Lines, started with a fresh workspace. 

    Here is what I ran:

    git clone git.ti.com/.../oe-layersetup.git $WorkDir/tisdk
    cd $WorkDir/tisdk
    ./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-09.00.00-config.txt

    cd $WorkDir/tisdk/build
    . conf/setenv
    MACHINE=am62xx-evm bitbake -k tisdk-default-image

    I get to 4800 of 11xxx tasks and it hangs.  I try to restart bitbake:

    cd $WorkDir/tisdk/build
    . conf/setenv
    MACHINE=am62xx-evm bitbake -k tisdk-default-image

    Here is what I get now:

    NOTE: Reconnecting to bitbake server...
    NOTE: Retrying server connection (#8)... (Traceback (most recent call last):
    File "/home/pholden/Projects/TAE/workspaces/tps-bridge-external/tps_fw/tisdk/sources/bitbake/lib/bb/main.py", line 449, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
    File "/home/pholden/Projects/TAE/workspaces/tps-bridge-external/tps_fw/tisdk/sources/bitbake/lib/bb/server/process.py", line 581, in connectProcessServer
    sock.connect(os.path.basename(sockname))
    BlockingIOError: [Errno 11] Resource temporarily unavailable
    )
    ERROR: Unable to connect to bitbake server, or start one (server startup failures would be in bitbake-cookerdaemon.log).

  • NOTE: Reconnecting to bitbake server...
    NOTE: Retrying server connection (#8)... (Traceback (most recent call last):
    File "/home/pholden/Projects/TAE/workspaces/tps-bridge-external/tps_fw/tisdk/sources/bitbake/lib/bb/main.py", line 449, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
    File "/home/pholden/Projects/TAE/workspaces/tps-bridge-external/tps_fw/tisdk/sources/bitbake/lib/bb/server/process.py", line 581, in connectProcessServer
    sock.connect(os.path.basename(sockname))
    BlockingIOError: [Errno 11] Resource temporarily unavailable
    )
    ERROR: Unable to connect to bitbake server, or start one (server startup failures would be in bitbake-cookerdaemon.log).

    I know this is an older thread but let me add one more comment here. Sometimes if bitbake crashes (esp. in scenario when it runs out of memory) it leaves "dangling" threads behind in the system, that prevents you from re-starting it.

    There are two things you can do to get out of this situation:

    1. Restart/reboot your system

      or

    2. Look for bitbake threads in the system (`ps aux | grep -i bitbake`), record their process IDs, and manually kill them (`kill -9 <PID>`)

    Regards, Andreas

  • I gave up on tisdk-default and got things going using tisdk-base.  I had to get a newer, faster desktop with more disk space.  Setting up DL_DIR and prefetching all the packages first helped quite a bit with the build too.