• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 353 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.

AM5729: Errors during project build

Gregory Duperon
Expert 6050 points
Part Number: AM5729

I have a customer ramping up on the AM5729.  They are having issues building after cloning the Arago Git repository.  See below:

To summarize, I followed the instruction on this page http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment which is similar to the instruction on this page https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_03_00_106/linux/Overview_Building_the_SDK.html#processor-sdk-build-reference.

Instead of running these commands shown below from the first link, I specified a different config file, machine name and image name (all show in red).

I ran this command which resulted in a successful build.

and this command which failed:

With these errors below:

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

NOTE: Your conf/bblayers.conf has been automatically updated.

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

NOTE: Your conf/bblayers.conf has been automatically updated.

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

NOTE: Started PRServer with DBfile: /home/fc/repo/tisdk/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 36137, PID: 119696

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

ERROR: Failed to obtain external Arm toolchain version: Execution of '/home/fc/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-none-linux-gnueabihf-gcc -v' failed: command not found

Note that I’ve not added any of my code/application at this point.  This is just me trying to build the baseline after cloning the Arago Git repository before I try to add any of my changes. I’m brand new to the Yocto project so I’m still coming up to speed on how to add layers and recipes.

I’m not sure if the build procedure instruction needs to change when using the “arago-dunfell-config.txt” and if so then does it make sense that it works when using the “poky-dunfell-config.txt” file?

  • 0
    TI__Guru** 113800 points

    Hi Gregory,

    We have recently had a couple of threads on a very similar error report:

    I would suggest that you have a look at the following threads:

    1. https://e2e.ti.com/support/processors/f/791/p/901334/3352199#3352199
    2. https://e2e.ti.com/support/processors/f/791/p/937673/3481127#3481127

    The first link should help you resolve the issue.

    Please note that building the arago-dunfell-config.txt or any of the non-release configurations is not guaranteed to work in between releases, so I recommend that you to try the release configuration present in the SDK.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Prodigy 10 points

    Hi Karthik,

    Gregory posted the question on my behalf. From the first link that you provided, I understand that using the "configs/processor-sdk/processor-sdk-06.03.00.106-config.txt" file will result in a successful build. That uses the Yocto 2.6 release which is EOL from the Yocto Project's perspective. This is why I was trying to get a build using the current Yocto 3.1.2 "Dunfell" release. I thought that since there was an "arago-dunfell-config.txt" in the "configs" directory of git://arago-project.org/git/projects/oe-layersetup.git that TI has been able to bring the Arago distribution up to a Yocto release that was not EOL. If this is not the case then do you know when TI will have an SDK for the AM57xx that is using the Yocto "Dunfell" release?

    Thanks,

    John

  • 0 in reply to John Pham1
    TI__Guru** 113800 points

    Hi John,

    We do not yet have a release for AM57 on the dunfell - I believe the release we have a release coming up and I don't have a confirmation of the dates etc.

    Until then, I request you to use the Yocto 2.6 release, although it is EOL from Yocto perspective we have an active usage and support at the moment.

    Regards
    Karthik