• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Subscribers 102 subscribers
  • Views 307 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM4378: SDK Build GCC version problem

Berkay Somali
Prodigy 170 points
Part Number: AM4378

Hi, 

I am trying to build an SDK from scratch following the instructions here: https://software-dl.ti.com/processor-sdk-linux/esd/AM437X/08_02_00_24/exports/docs/linux/Overview_Building_the_SDK.html

Our goal is to build a new boot kernel with minimal configuration that will take us to login. We then would like to add peripherals to diagnose which peripheral may be problematic (causing kernel panic, etc.)

However when we blindly follow the instructions, we got stuck during build of base image with the below error:

$[linux-devkit]:~/ti-processor-sdk-linux-am437x-evm-08.02.00.24/tisdk/build> MACHINE=am437x-evm bitbake tisdk-base-image

ERROR: Unable to start bitbake server (None)
ERROR: Server log for this session (/home/zebra/ti-processor-sdk-linux-am437x-evm-08.02.00.24/tisdk/build/bitbake-cookerdaemon.log):
--- Starting bitbake server pid 20169 at 2022-11-12 15:25:41.652825 ---
ERROR: Failed to obtain external Arm toolchain version: Execution of '/opt/gcc-arm-9.2-ti2020.01-armv5-x86_64-arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -v' failed: command not found
ERROR: Failed to obtain external Arm toolchain version: Execution of '/opt/gcc-arm-9.2-ti2020.01-armv5-x86_64-arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -v' failed: command not found
ERROR: Error: EXTERNAL_TOOLCHAIN path '/opt/gcc-arm-9.2-ti2020.01-armv5-x86_64-arm-none-linux-gnueabi' does not exist

It seems like bitbake is looking for gcc-arm-9.2-ti2020.01-armv5-x86_64-arm-none-linux-gnueabi toolchain but it should look for gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf... correct?

How can we solve this? Thank!

Berkay

  • 0
    Prodigy 96 points

    I am facing the same issue. Can anyone please help?

  • 0 in reply to Ankita Gupta
    TI__Guru 57906 points

    Can you all please try building it on Ubuntu 18.04 x64 (our currently supported Linux distribution) to see if that issue still occurs?

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 96 points

    Is there a way to make it work on Fedora36?

  • 0 in reply to Andreas Dannenberg
    Prodigy 170 points

    Already using Ubuntu 18.04 per TI Guide recommendation... As a matter of fact we first used Ubuntu 20 but we could not go far, getting the error that we should use the Ubuntu 18.04 then switched to Ubuntu 18.04... One detail: Using server VM, not local installation. 

    Regards, 

    Berkay

  • 0 in reply to Andreas Dannenberg
    Prodigy 96 points

    Btw, I did try on Ubuntu 18.04 VM, and still I see the same error.



    --- Starting bitbake server pid 22285 at 2022-11-15 10:05:53.518059 ---
    WARNING: Layer meta-psdkla should set LAYERSERIES_COMPAT_meta-psdkla in its conf/layer.conf file to list the core layer names it is compatible with.
    ERROR: Failed to obtain external Arm toolchain version: Execution of '/opt/gcc-arm-9.2-ti2020.01-armv5-x86_64-arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -v' failed: command not found
    ERROR: Failed to obtain external Arm toolchain version: Execution of '/opt/gcc-arm-9.2-ti2020.01-armv5-x86_64-arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -v' failed: command not found
    ERROR: Error: EXTERNAL_TOOLCHAIN path '/opt/gcc-arm-9.2-ti2020.01-armv5-x86_64-arm-none-linux-gnueabi' does not exist

  • 0
    TI__Guru 57906 points
    Berkay Somali said:
    $[linux-devkit]:~/ti-processor-sdk-linux-am437x-evm-08.02.00.24/tisdk/build> MACHINE=am437x-evm bitbake tisdk-base-image

    I just noticed the [linux-devkit] in your prompt. This is usually the result of doing a 'source environment-setup' from the linux-devkit folder part of the SDK installer. Which is for cross-compiling purposes. Is this what you setup, and tried building Yocto from within this environment?? If that's what happened, that is not the way this is intended to to be used. You'd want to do the Yocto build from a clean environment. Part of this should be doing a `source build/conf/setenv' from the Yocto tree that was setup.

    Regards, Andreas