• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 99 subscribers
  • Views 1247 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.

AM625: AM625 Linux SDK build issues

Mukul Bhatnagar
Guru* 84075 points
Part Number: AM625

Posting on behalf of a customer 

--

I'm trying to follow "Building the SDK" here: https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/08_04_01_03/exports/docs/linux/Overview_Building_the_SDK.html#overview-building-the-sdk

 

I'm facing the following problem and can't seem to find where to download "gcc-arm-9.2-ti2020.01-armv5-x86_64-arm-none-linux-gnueabi":

$ MACHINE=am62xx-evm bitbake tisdk-base-image

ERROR: Unable to start bitbake server (None)

ERROR: Server log for this session (/mnt/nvme_4tb/bsps/am62x/tisdk/build/bitbake-cookerdaemon.log):

--- Starting bitbake server pid 4155500 at 2022-11-01 16:52:27.650154 ---

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

​Here are the full steps I'm following:

# Install toolchains to home directory

 

  $ wget https://developer.arm.com/-/media/Files/downloads/gnu-a/9.2-2019.12/binrel/gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf.tar.xz

  $ tar -Jxvf gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf.tar.xz -C $HOME

  $ wget https://developer.arm.com/-/media/Files/downloads/gnu-a/9.2-2019.12/binrel/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu.tar.xz

  $ tar -Jxvf gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu.tar.xz -C $HOME

 

# Setup Yocto

 

  $ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk

  $ cd tisdk

  $ ./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-08.03.00.19-config.txt

  $ cd 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

 

# Build Image

 

  $ MACHINE=am62xx-evm bitbake tisdk-base-image

Can you please review the steps and let me know if I'm missing something or misconfiguring the environment?

  • 0
    TI__Guru**** 169071 points

    Hi,

    Our Yocto expert is out of office this week. Please expect delayed response.

  • 0
    TI__Guru 69727 points

    This seems similar to this issue here https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1160562/processor-sdk-am64x-processor-sdk-linux-for-am64x   The problem there was the build was attempted on Ubuntu 20.04 which is not officially supported at this time. Building on Ubuntu 18.04 worked as expected. Can you please double-check the setup and try building on Ubuntu 18.04.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 180 points

    Using Ubuntu 18.04 indeed fixes the problem. Thanks for the support.

  • 0 in reply to Nate Drude
    TI__Guru 69727 points

    Nata, I appreciate you closing the loop here regarding Ubuntu 20.04. In fact I have been building on Ubuntu 22.04 for test purposes, and did not encounter such issues (there were other issues however, specifically regarding the cross-toolchain installer that is generated as part of the full SDK build). It is interesting to see that only Ubuntu 20.04 creates such issues. While we are at it, we will soon (likely the SDK9.x series) start officially supporting Ubuntu 22.04.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 180 points

     after your comment, I reviewed Ubuntu 20.04. The problem was actually caused by not running sudo dpkg-reconfigure dash before ./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-08.03.00.19-config.txt. This will cause the following error:

    $./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-08.03.00.19-config.txt

...

From meta-arago[recommended]:
    tisdk-tiny-image: Arago TI SDK super minimal base image for initramfs
    tisdk-thinlinux-image: Arago TI SDK Thin Linux image
    tisdk-base-image: Arago TI SDK base image with test tools
    tisdk-bootstrap-base-image: Arago TI SDK bootstrap base image for initramfs
    tisdk-core-bundle: Installer package for TI SDK - NOT for direct use on target
    tisdk-default-image: Arago TI SDK full filesystem image
    tisdk-bootstrap-image: Arago TI SDK bootstrap image usable for board bringup
./oe-layertool-setup.sh: 870: [: no: unexpected operator

    After running sudo dpkg-reconfigure dash it is working in both Ubuntu 18.04 and Ubuntu 20.04 for me.

    Thanks again,

    Nate

  • 0 in reply to Nate Drude
    TI__Guru 69727 points

    Nate,

    thanks again for posting this here. Now that you write that I may have encountered that myself actually a long time ago. Yes re-configuring dash to bash is a very important often missed step!!! You amending this E2E post here will probably help somebody else in the future to connect the dots (symptom -> root cause).

    Regards, Andreas