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.

CCS/66AK2E05: External toolchain

Expert 4486 points
Part Number: 66AK2E05

Tool/software: Code Composer Studio

Hello, 

Our board is based on the 66SK2E05 using Arago Linux OS. We are using the EVMK2E eval board for prototyping. 

The bundled compiler is concerning since we want to build the application with the same compiler we build our OS with. The available packages are: a target specific Linux SDK (not Arago), GCC ARM toolchain, Arago LInux (configured to use the external toolchain), and code composer (newer toolchain that builds a target that doesn't load on the system). We have exported the ARM SDK from Arago so we have a command-line build environment that is purpose built for the target. We have used Makefiles CMake, and some Meson/Ninja. 

Is there a practical way for code composer studio to use the external toolchain that the SDK and Arago uses? 

We need Code Composer Studio to support external command-line build systems like CMake and Makefile.  Code Composer Studio can generate build configuration files but we need to be able to compile and link stand-alone without Code Composer Studio.

We would prefer to use newer compilers but the Arago Linux code base will not compile with anything newer than GCC 4.8 which precludes us from using recent Linux distro releases.  It is not the ARM compiler that is the issue.  It uses the local OS compilers to build a native cross-compiler toolchain and it fails when compiling some autogenerated files that are components of the toolchain that are native shared libraries.  We are using Ubuntu 18.04 LTS in a virtual machine for development.  It has been used on a Fedora 32 host and a Fedora 30 host. We need to get out of the virtual machine to the enterprise network to access version control services.

Thanks! 

  • Hi, JDJ,

    I don't quite follow what you mean that Arago Linux is configured to use external toolchain, and what is the Arago Linux vs non-Arago Linux (I think this you meant the Kernel in the SDK)? I think to Linux (or Linux Kernel to be precise), the version and its source are what matter. What version is the "Arago Linux" and where is it from?

    My understanding of the cross-compiler. There is only one and I believe it is developed by Linaro which TI bundled it in the SDK. If you go to Linaro site, it points you to the ARM Developer website for the latest Cortex-A family GCC 8.3-2019.03 which is what TI SDK is using.Customer mentioned that it is using a newer version.GCC 4.8? This doesn't sound familiar and is not the cross-compiler version. 

    If customer tries to compile and build the cross-compiler binaries natively on Ubuntu machine. That is not in our support scope, and why does customer wants to do it instead of downloading the cross-compiler binaries from ARM developer's website?

    Rex

  • The software is from: 

    We followed the documentation to configure and build Linux and did not specify a version but just started using the default branch. We are using master branch at commit 83d2564 (date July 23 2020).  We are using CCS-10.1.0 because we were having problems with CCS-9.x.x and thought an upgrade might fix the problem, but It turned out that I needed to reference a gel file for the target configuration.

  • Hi, JDJ,

    Why not using the kernel in the PLSDK 6.3? I believe the master branch misses some patches for KS2 which can't be upstreamed. Besides, We have never used CCS to build kernel, and don't know what's involved. The kernel build instruction is in PLSDK Kernel User's Guide:

    http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_Kernel_Users_Guide.html

    Rex