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.

Using Sitra Processors SDK Platform with Centos

Hi,

I understand that the AM335x EVM SDK is supporting ubuntu. But if i'm using CentOs, will it work? Is there anyone of you tries and install on CentOs?

As I'm trying to develop an application for this AM335x board, which I have downloaded and installed the SDK from the website but when I tried to run the "setup.sh" script, it complaints only support ubuntu. Can i know what is the different run the "setup.sh" script and run "source environment-setup" then run my eclipse to compile from the same terminal? 

Any suggestion? 

Thanks.

  • Hi Jenny,

    You are correct that the Host platform for the Sitara SDK is Ubuntu Linux. TI does not have guidelines how to use the SDK on other platforms.

  • HI Biser,

    Thanks for the quick reply. Do you know the setup.sh is to do what? Is it to setup the enviroment-setup for the project by default on the host platform?

    Thanks.
  • Hi, 

    Jenny Liew said:
    Can i know what is the different run the "setup.sh" script and run "source environment-setup"

     

    The setup.sh scripts prepares your host machine for working with the sdk: 

       - checks the linux distribution (version) installed on the PC

       - adds your user to the sudo group, if it does not have sudo rights
       - checks if your host PC has all the necessary libraries, and installs the missing ones. 

       - sets up the target filesystem for TFTP boot. 

       - sets up the minicom to be the debug console for your board. 

    The source environment-setup script sets up your build environment in the console window you're working with. It basically exports the following variables: ARCH, PATH, CROSS_COMPILE, etc. 

    Not sure if the scripts will work on CentOS (I haven't tested this), but even if they don't you should be able to manually set those using the CentOS console commands. 

    Hope this helps. 

    Best Regards, 

    Yordan