• State Resolved
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 184 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TDA4VM: [Linux]gcc toolchain issue

ruibo zuo
Prodigy 60 points
Part Number: TDA4VM

Tool/software:

Hello,

We are having some issues when trying to compile the psdkla

PSDKLA: ti-processor-sdk-linux-adas-j721e-evm-09_02_00_05-Linux-x86-Install.bin

PSDKRA： ti-processor-sdk-rtos-j721e-evm-09_02_00_05.tar.gz

We follow the instructions from 1.1.1. Download and Install the SDK — Processor SDK Linux for J721e Documentation

Firstly, install psdkla to /home/tda4/psdkla. And then move /home/tda4/psdkla to a new directory and create a project Git repository baseline together with psdkra.

Now we try to build psdkla, the gcc toolchains reported an error -- gcc cannot be found：

We have changed the "TI_SDK_PATH" in psdkla/Rules.make

We attempted to locate the issue and found that gcc depends on "/home/tda4/psdkla/linux-devkit/sysroots/x86_64-arago-linux/lib/ld-linux-x86-64.so.2", but the file no longer exists.

When we copy psdkla to /home/tda4/psdkla, the problem has been solved.

However, the top-level directory of psdkla for each team member is different and may be working on different servers.

How can we solve this problem without placing a copy of psdkla in directory /home/tda4/psdkla on each server ?

Best regards

Thank you

  • 0
    TI__Guru*** 139750 points

    Hi,

    I believe the toolchain paths are set when you are installing the SDK. So easier solution would be to install PSDKLA where you want it to exist finally.

    - Keerthy

  • 0 in reply to Keerthy J
    Prodigy 60 points
    Keerthy J said:
    I believe the toolchain paths are set when you are installing the SDK. So easier solution would be to install PSDKLA where you want it to exist finally.

    Yes, this is a known solution.

    However, this does not match our actual usage scenario.

    We need to create a Git repository based on the installed SDK, and then develop project code on this Git repository. Multiple project members may use the same Linux host PC to develop different modules of this project, and they should not work in the same path.

  • 0 in reply to ruibo zuo
    TI__Guru*** 139750 points

    Hi Ruibo,

    The SDK is a combined setup and looks for that path. If you are going via a separate git repository then you can download the corresponding ARM toolchains in the server & point the same as $PATH in .bashrc.

    Closing this.

    - Keerthy

  • +1 in reply to Keerthy J
    Prodigy 60 points

    Hi Keerthy，

    Thank you for your reply.


    I have tried to modify CROSS_COMPILE and CROSS_COMPILE_ARMV7 in $PSDKLA/Rules.make (as shown below), and the compilation was successful.

     Please help confirm if the version of the toolchain I am using is correct and if there are any other unknown issues that I did not recognize. Thank you.

    export CROSS_COMPILE=path/to/arm-gnu-toolchain-11.3.rel1-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-
    export CROSS_COMPILE_ARMV7=path/to/arm-gnu-toolchain-11.3.rel1-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf-
  • 0 in reply to ruibo zuo
    TI__Guru*** 139750 points

    Yes. That is what I wanted to you to try. Looks good.

    - Keerthy