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: Known Issue: CCS on Linux crashing on startup

Guru 281875 points

Replies: 35

Views: 16123

Tool/software: Code Composer Studio

There is a known issue with CCS on Linux crashing on startup (segmentation fault). This issue occurs after updating the Linux environment with the latest available packages. This issue is under investigation.

Sorry for the inconvenience

Thanks

ki

UPDATE 1: Please use the workaround in the post below:

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/604599/2226461#2226461

This addresses both the CCS startup issue and the xdc build failure

UPDATE 2: The latest Linux update has a fix for this issue. This was confirmed in Ubuntu 16.04 (kernel 4.4.0-83.106)

-----------------------------------

Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

Having CCS problems? Check out the CCS Troubleshooting Guide

Looking for CCS Training? Check out the CCS Training Site

Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

35 Replies

  • In reply to Allef Silva28:

    Hello all,

    The issue appears to be related to:

    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

    askubuntu.com/.../eclipse-crashes-with-linux-kernel-4-4-0-81-generic

    The workaround mentioned there seems to also apply to CCS:

    Open terminal

    $ export JAVA_TOOL_OPTIONS=-Xss1280k

    then, from the same terminal, launch the ccstudio application in . /ccsv7/eclipse

    This should help with both CCS startup and the xs build issues.

    NOTE: On some systems, this is enough to start CCS, but not enough to avoid the build error. In those cases, increase the max stack size to 2650k (ex: export JAVA_TOOL_OPTIONS=-Xss2560k)

    This workaround does not need the modification to the ini file mentioned earlier (commenting out the first two lines). A stock ccstudio.ini file can be used with the workaround above.

    We are still investigating. Sorry for all the inconvenience.

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Allef Silva28:

    This is really holding me back, how soon will it be fixed?

    MSP430F5335, MSP430F5359, CCS8, C++14, Windows 10

  • In reply to Silver Diamond:

    Silver Diamond
    This is really holding me back, how soon will it be fixed?

    Did you try the workaround in the post prior to yours?

    Thanks

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki-Soo Lee:

    Ki,

    the workaround solves the issue for me, thank you very much!

    Clarification on the instructions, just in case:
    After the export JAVA_TOOL_OPTIONS=-Xss1280k you need to stay in that terminal, cd your way to your CCS installation,
    in my case cd ~/ti/ccsv7/eclipse and run ./ccstudio
    I recommend not putting it into your .bashrc or similar at this point, since not all eclipse IDEs are impacted (e.g. my Nsight 8.0 runs fine).


    -----

    Confirmed with both project I posted about earlier (using xdctools_3_32_02_25_core and ti-cgt-c6000-8.1.3) on:
    Linux 3.13.0-121-generic #170-Ubuntu SMP Wed Jun 14 09:04:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
    System java -version: Java(TM) SE Runtime Environment (build 1.8.0_131-b11)

  • In reply to ChrisF:

    Faced the same problem with segfault in xdctools today after Ubuntu update.

    Have to uninstall kernek update:

    sudo apt-get remove linux-image-4.8.0-56-generic linux-image-extra-4.8.0-56-generic 

  • In reply to ChrisF:

    ChrisF
    Clarification on the instructions, just in case:
    After the export JAVA_TOOL_OPTIONS=-Xss1280k you need to stay in that terminal, cd your way to your CCS installation,
    in my case cd ~/ti/ccsv7/eclipse and run ./ccstudio
    I recommend not putting it into your .bashrc or similar at this point, since not all eclipse IDEs are impacted (e.g. my Nsight 8.0 runs fine).

    Thanks for the clarification. Yes, you need to run everything from the same terminal.


    Note that this issue was cause by a security fix in the kernal. A new version of the fix that does not cause the issue is being tested and I anticipate will be released soon. So hopefully this workaround will not be needed for long

    Thanks

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki-Soo Lee:

    Ki,

    This workaround also worked for me.

    The only issue was that, even after export the variable and been able to run ccstudio, the Xs compiler still crashed with the Segmentation Fault error.

    The solution was to change the value of the exported variable from "JAVA_TOOL_OPTIONS=-Xss1280k" to "JAVA_TOOL_OPTIONS=-Xss2560k".

    Do you see any problem with this solution?

    Also, to make life easier, I created a bash script in <install folder>/ccsv7/eclipse with name ccstudio.sh where I export the variable and then execute ccstudio. To use it, I just changed the Exec= parameter of the desktop launcher, pointing to this script. This way I can keep using the desktop icon to start the application.


    Thanks.

    Cassiano.
  • Expert 1450 points

    In reply to ChrisF:

    In the past couple days two of our engineers have been unable to build Vision SDK projects and we suspect it is this issue as well. They are both using Ubuntu 16.04 and had CCS7 installed on their PCs.

    /home/linuser/Documents/sdks/tda3/sdk_manager/staging/vision_sdk/binaries/maketemp_configuro_cmd_ipu1_1.bat: line 1: 22759 Segmentation fault      (core dumped) /home/linuser/Documents/sdks/tda3/sdk_manager/staging/vision_sdk/../ti_components/os_tools/linux/xdctools_3_32_00_06_core/xs xdc.tools.configuro --generationOnly -o /home/linuser/Documents/sdks/tda3/sdk_manager/staging/vision_sdk/binaries/obj/vision_sdk/tda3xx-rvp/ipu1_1/release/vision_sdk_configuro -t ti.targets.arm.elf.M4 -p ti.platforms.evmTDA3XX:IPU_1_1 -r release -b /home/linuser/Documents/sdks/tda3/sdk_manager/staging/vision_sdk/build/tda3xx/config_m4.bld --cfgArgs "{mode: \"\", coreName: \"IPU1-CORE1\",  platformMem: \"DDR_MEM_512M\"}" MAIN_APP_ipu1_1.cfg

    In this case the build on the machine was working one day and stopped the next, even when a fresh checkout of the codebase was completed.

  • In reply to BenM:

    Same here. After recent Ubuntu 16.04 updates were installed, CCS v7.1 crashed immediately after the launch. Today I noticed that xds also crashed due to segfault, and no longer able to build even though the source code was not modified at all.

     

  • In reply to ChrisF:

    I have same issue after applying the quick ccs fix. Using 4.10.0-24-generic #28-Ubuntu SMP Wed Jun 14 08:14:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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.