• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 530 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.

Yocto build is no longer working.

Fred Fisher
Intellectual 602 points


Hello,

It did work and when it did not work I tried this another machine that is has already produced images using TI/yocto builds and it too fails.

~/tisdk/build$ MACHINE=am62-evm bitbake -k tisdk-base-image
ERROR: Unable to start bitbake server (None)
ERROR: Server log for this session (/home/fred/tisdk/build/bitbake-cookerdaemon.log):
--- Starting bitbake server pid 2657 at 2023-04-14 09:23:49.908110 ---
ERROR: Failed to obtain external Arm toolchain version: Execution of '${DEF_TOOLCHAIN_PATH}/bin/INVALID-linux-gcc -v' failed: command not found
ERROR: Failed to obtain external Arm toolchain version: Execution of '${DEF_TOOLCHAIN_PATH}/bin/INVALID-linux-gcc -v' failed: command not found
ERROR: Error: EXTERNAL_TOOLCHAIN path '${DEF_TOOLCHAIN_PATH}' does not exist

  • 0
    TI__Guru 70202 points

    Can you double check your Linux environment has the correct cross-toolchain variables setup as per SDK v8.x instructions? If done correctly the below command output should look something like this (path may be different, that's okay, if valid):

    $ env | grep TOOLCHAIN
TOOLCHAIN_PATH_ARMV8=/opt/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu
TOOLCHAIN_PATH_ARMV7=/opt/gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf

    Note that those changes won't persist and will need to be re-entered each time unless you add those to .bashrc for example. On my build machine I've done the below so I don't need to re-define those env variables all the time:

    $ tail -n5 ~/.bashrc 
# Toolchain definitions as required by TI SDK Yocto builds
export TOOLCHAIN_PATH_ARMV7=/opt/gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf
export TOOLCHAIN_PATH_ARMV8=/opt/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu

    Regards, Andreas

  • +1
    TI__Guru 70202 points

    Oh I just noticed your MACHINE definition is incorrect. It should be MACHINE=am62xx-evm, then this specific error should go away.

  • 0 in reply to Andreas Dannenberg
    Intellectual 602 points

    Oh my, I feel really stupid now. That will be tried and see what happens, thank you.