Installation and Compiling OMAP-L138 (DSP) on Ubuntu Server

Hi Ben,

Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages. Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics.

For OMAPL138, ( For both ARM and DSP cores ) for building ( non -OS ) based low level driver programs,  CCS is recommended. For CCS setup you can use either Linux ( ubuntu ) machine or Windows machine.

For OMAPL138, ( For ARM ), linux-3.3-psp03.22.00.06.sdk is provided. Through which you can boot linux on ARM core.

Ben said:

I would like to set up a build environment for OMAP-L138 software on a headless Ubuntu 14.04 LTS Server.  I have already set up CCS on a Ubuntu desktop system, and that is working fine.

When you say it is working fine, did you try building any of the pdk / starterware examples using CCS and ran on OMAPL138 board through emulator?

Ben said:

The DSP build environment, however, is giving me problems.  Is there a way to use the TI bin installers for XDC Tools and SYS/BIOS that do not require the GUI environment?  Are there separate installers (other than the bin installers) that are needed?  

Which installers you used? Please specify its versions.

Ben said:

The product we are building uses xdctools_3_25_03_72, bios_5_42_01_09, and c6000_7.4.4.  Is there anything else needed for installing and using the DSP compilers on a headless Linux server?  

Please provide which TI software product you are using? For OMAPL138, we have many such as MCSDK ( PDK) , Starterware.

So that, we can comment on it about the dependencies.

 

 

Shankari,

Thanks for your reply.  To answer your questions:

> When you say it is working fine, did you try building any of the pdk / starterware examples using CCS and ran on OMAPL138 board through emulator?

I installed CCS 5.5.0 -- along with ARM cross-compiling tools provided by CriticalLink -- on a Ubuntu desktop machine, and I can build everything I need for our target OMAP-L138 device.  Our software builds, loads, and ultimately runs on the target.

Having accomplished that step, I now need to set up a build environment on a separate, command-line only, Ubuntu Server 14.04 LTS machine.

> Which installers you used? Please specify its versions.

From TI:

ccs_setup_5.5.0.00077.bin  (includes bios_5_42_01_09, ccsv5, xdais_7_21_01_07, xdctools_3_25_03_07)

EDMA3_LLD_setuplinux_01_11_03_01.bin

From CriticalLink:

angstrom-eglibc-i686-armv5te-toolchain-qte-v2012.05.tar.bz2

release_2012-08-10.run

release_2014-01-13.run

All of the CriticalLink tools install just fine on my Ubuntu Server machine because they are all command-line oriented.  The TI bin installers, however, do not run on the Ubuntu Server because they seem to require a GUI capability on the host machine.

The TI installers work just fine on my Ubuntu _desktop_ machine, but my Ubuntu Server machine does not have the gnome GUI desktop -- it is command-line, only.

What do I need to do to install the TI build tools that are included in CCS 5.5.0 on the Ubuntu Server 14.04 LTS machine and perform builds there?

Thanks for your help.

Regards,

Ben

Shankari,

So the guys at CriticalLink were very helpful about the TI installation .bin executables. After installing the prerequisites found at:

processors.wiki.ti.com/.../Linux_Host_Support_CCSv6

One can then install EDMA3_LLD_setuplinux_01_11_03_01.bin with the following command:

$ sudo ./processors.wiki.ti.com/.../Linux_Host_Support_CCSv6 --mode console

I tried it, and the installation appeared to succeed.



Regarding ccs_setup_5.5.0.00077.bin, they suggested going over to the Ubuntu desktop and running:

$ ./ccs_setup_5.5.0.00077.bin --help

I did this, and it produced the following:

$ ./ccs_setup_5.5.0.00077.bin --help
Usage: ccs_setup_5.5.0.00077.bin [options ...]

Available Options:
--debug run installer in debug mode
--debugconsole run installer with a debug console open
--help display this information
--localrepo [ARG] points to a local copy of the installer
repository
--manifestfile [ARG] ccs_manifest.xml file
--mode [ARG] set the mode to run the installer in
Available values: console, default, silent or
standard
--prefix [ARG] set the installation directory
--response-file [ARG] a file to read installer responses from
--save-response-file [ARG] a file to write installer responses to when the
installer exits
--setupfile [ARG] ccs_installini.xml file
--temp [ARG] set the temporary directory used by this program
--test run installer without installing any files
--update run the installer in update mode
--updaterepo [ARG] points to a local copy of the update repository
--version display installer version information


So the ccs_setup_ ... 00077.bin also has "--mode console" option that I can use on my Ubuntu Server. That's great.

So my questions for you:

Is there a way to tell the ccs_setup_...00077.bin installer to skip all of the Eclipse GUI items and install only the items necessary for a makefile to compile source code?

Could the "--manifestfile [ARG] ccs_manifest.xml file" or "--setupfile [ARG] ccs_installini.xml file] options be used for this?

What would the content of the xml files be?

Thanks for your help.

Regards,

Ben