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.

preferred cross compile toolchain for am3517

Other Parts Discussed in Thread: AM3517

I actually hardly know where to begin so I will start with a simple question that I have not found addressed either in the wiki or the forum:

What is the preferred toolchain for cross compiling for an am3517 target?

Most of the wiki seems to reference using the code sorcery toolchain, and I think that's what I used to compile uboot and my kernel.

But when I went to try and build Qt it was a huge struggle, and I eventually got the Qt build to work by using the arm-arago-linux-gnueabi toolchain that is included in the v5 SDK at:

$HOME/ti-sdk-am3517-evm-05.02.00.00/linux-devkit

on my Ubuntu VM host.

I am working with a LogicPD am3517 zoom EVM, which came with v4 SDK.

I ugraded that to V5 by using tftpboot and NFS hosted files system in my Ubuntu VM.

I suspect that the linux-devkit, arm-arago-linux-gnueabi toolchain is newer and better that the codesorcery one for am3517 applications, but I'd like to get some confirmation of that. 

Thanks.

  • Hello,

    Both toolchains are based on gcc 4.3.3.  The SDK 05.02 is built using the arago toolchain for the armv7 (Cortex-A8) architecture, so the support libraries in $HOME/ti-sdk-am3517-evm-05.02.00.00/linux-devkit are optimized for Cortex-a8 whereas the Codesourcery toolchain support libs are not.  You would need to purchase an upgraded version of Codesourcery to get the optimized support libs.  We have recently switch over to using the Arago toolchain.  You can build your u-boot and kernel using the Arago toolchain. The Arago toolchain that comes with the SDK is the preferred toolchain.