• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 4167 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CCS/CCSTUDIO: Trying to install CCS in a docker container

CCS/CCSTUDIO: Trying to install CCS 9.1.0 in docker container

user4902515
Prodigy 70 points
Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hi,

I want to build my CCS MSP430 project in a docker container running Ubuntu 18.04.

I think I managed to install CCS 9.1.0 using the following command line:

./ccs_setup_linux64_9.1.0.00010.bin --mode unattended --prefix /ti --response-file /home/CCS9.1.0.00010_linux-x64/response.txt

with the attached response file:

Fullscreen 3582.response.txt Download 
CreateDesktopShortcut: No
CreateQuickLaunchShortcut: No
InstallDir: /ti
InstallMode: Standard
LaunchApplication: No
edition_selection: Custom
feature_selections: IDE_MSP430 MSP430_BUILD_DEBUG MSP430_GCC_SUPPORT EMU_MSP430 JRE JRE32 P2APP ECLIPSE ECLIPSECORE P2TOOLS GMF IDE_MAIN IDE_WORKFLOW DVT_COMMON DVT_UIA DVT_VIA_CCS TIREX XULRUNNER INSTALLER IDE_CHROME IDE_TOOLS_COMMON IDE_GC TARGET_CONTENT_CORE TARGET_CONTENT_CORE_LEGACY NODEJS USERGUIDE DS DS_FLASH CLOUDAGENT SYSCONFIG MSVC80 MSVC2012 MSVC2015 MSP430_CGT_HELP CGT_DEFAULTLIBS_MSP430 DMED GCC_MSP430_COMPILER DVT_ENERGYTRACE
product_selections: PF_MSP430

Then, when I try to build my project using this command line:

eclipse -noSplash -data <workspace> -application com.ti.ccstudio.apps.projectBuild -ccs.project <project>

I get the following error:

!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application "com.ti.ccstudio.apps.projectBuild" could not be found in the registry. The applications available are: org.eclipse.ant.core.antRunner, org.eclipse.cdt.codan.core.application, org.eclipse.cdt.core.GeneratePDOM, org.eclipse.cdt.core.CodeFormatter, org.eclipse.cdt.managedbuilder.core.headlessbuild, org.eclipse.e4.ui.workbench.swt.E4Application, org.eclipse.e4.ui.workbench.swt.GenTopic, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.reconciler.application, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication, org.eclipse.equinox.p2.touchpoint.natives.nativePackageExtractor, org.eclipse.equinox.p2.updatesite.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.CategoryPublisher, org.eclipse.help.base.infocenterApplication, org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool, org.eclipse.ui.ide.workbench, com.ti.ccstudio.p2app, com.ti.common.core.initialize.
        at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
        at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1498)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1471)

What am I missing?

  • 0
    TI__Guru**** 463541 points

    Hello,

    Are you able to build your project from the CCS IDE?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 70 points

    Yes I am able to build my project from the IDE. In fact, I managed to build it from the docker container. What was missing was that I needed to add the i386 architecture to the package manager so that the i386 librairies would get installed properly, but I still have an issue.

    After installing CCS 9.1.0, my build works, but I want to use a specific version of the TI Compiler (18.1.6). After installing this version of the the TI Compiler using the following command line:

    eclipse -application org.eclipse.equinox.p2.director -repository software-dl.ti.com/.../ -installIU com.ti.cgt.msp430.17.linux.feature.group

    When I try to launch a new build with the same command line that worked previously, I get nothing. Nothing is printed in the terminal window and the command prompt comes back after a couple of seconds.

    I have attached my Dockerfile (in .txt format) to this thread.

    Any idea what could be the issue?

    Fullscreen 8267.Dockerfile.txt Download 
    FROM ubuntu:18.04

#Install all packages needed
RUN dpkg --add-architecture i386
RUN apt-get update 

RUN apt-get install -y libc6:i386
RUN apt-get install -y libusb-0.1-4:i386
RUN apt-get install -y libgconf-2-4:i386
RUN apt-get install -y build-essential
RUN apt-get install -y libpython2.7

RUN apt-get install -y git

WORKDIR /ccs_install

#Files which define which ccs feature to install
COPY response.txt /ccs_install

#ADD automatically extracts the archive  
ADD CCS9.1.0.00010_linux-x64.tar.gz /ccs_install/

# Install ccs in unattended mode
RUN /ccs_install/CCS9.1.0.00010_linux-x64/ccs_setup_linux64_9.1.0.00010.bin --mode unattended --prefix /opt/ti --response-file /ccs_install/response.txt 	

# TODO: do this in the same step as the ADD and RUN install to remove 800MB in the image.
RUN rm -r /ccs_install

ENV PATH="/opt/ti/ccs/eclipse/:${PATH}"

WORKDIR /home

#RUN eclipse -application org.eclipse.equinox.p2.director -repository http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/codegen/Updates/p2linux/ -installIU com.ti.cgt.msp430.17.linux.feature.group

  • 0 in reply to user4902515
    Prodigy 70 points

    I managed to make it work by installing the compiler with the installer downloaded from http://www.ti.com/tool/download/MSP-CGT-17 instead of going through eclipse's plugin system.

    Here is the updated Dockerfile:

    Fullscreen 8877.Dockerfile.txt Download 
    FROM ubuntu:18.04

#Install all packages needed
RUN dpkg --add-architecture i386
RUN apt-get update 

RUN apt-get install -y libc6:i386
RUN apt-get install -y libusb-0.1-4:i386
RUN apt-get install -y libgconf-2-4:i386
RUN apt-get install -y build-essential
RUN apt-get install -y libpython2.7

RUN apt-get install -y git

WORKDIR /ccs_install

#Files which define which ccs feature to install
COPY response.txt /ccs_install
COPY ti_cgt_msp430_18.1.6.LTS_linux_installer_x86.bin /ccs_install

#ADD automatically extracts the archive  
ADD CCS9.1.0.00010_linux-x64.tar.gz /ccs_install/

# Install ccs in unattended mode
RUN /ccs_install/CCS9.1.0.00010_linux-x64/ccs_setup_linux64_9.1.0.00010.bin --mode unattended --prefix /opt/ti --response-file /ccs_install/response.txt 	

RUN /ccs_install/ti_cgt_msp430_18.1.6.LTS_linux_installer_x86.bin --prefix /opt/ti/ccs/tools/compiler/ --mode unattended --unattendedmodeui minimal

# TODO: do this in the same step as the ADD and RUN install to remove 800MB in the image.
RUN rm -r /ccs_install

ENV PATH="/opt/ti/ccs/eclipse/:${PATH}"

WORKDIR /