CCS: Known Issue: CCS on Linux crashing on startup

Here's a workaround for the issue while we figure out the root cause.

Open  <install dir>/ti/eclipse/ccstudio.ini in a text editor.  Comment out the first two lines by inserting a # at the start of the line. It would look like this:

#-vm
#jre/lib/amd64/server/libjvm.so

Although the quick fix (removing the -vm) worked for starting CCS, I also see an (probably related) issue with the XDCtools:

A SYS/BIOS project (for C6678 DSP) that compiled before does not build anymore. Same thing when I create a fresh "Typical" SYS/BIOS Template it does not build either:

**** Build of configuration Debug for project gfaulttest2 ****

/localdata/home/me/ti/ccsv7/utils/bin/gmake -k -j 12 all -O
gmake[1]: Entering directory '/localdata/home/me/repositories/BP_GPUDSP/ti_ccs/gfaulttest2/Debug'
Building file: ../app.cfg
Invoking: XDCtools
"/localdata/home/me/ti/xdctools_3_32_02_25_core/xs" --xdcpath="/localdata/home/me/ti/bios_6_46_04_53/packages;/localdata/home/me/ti/openmp_dsp_c667x_2_06_00_00/packages;/localdata/home/me/ti/ctoolslib_2_2_0_0/packages;/localdata/home/me/ti/edma3_lld_2_12_03_27/packages;/localdata/home/me/ti/framework_components_3_40_02_07/packages;/localdata/home/me/ti/framework_components_3_40_02_07/examples;/localdata/home/me/ti/pdk_c667x_2_0_5/packages;/localdata/home/me/ti/ccsv7/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r release -c "/localdata/home/me/ti/ti-cgt-c6000_8.1.3" --compileOptions "-g --optimize_with_debug" "../app.cfg"
subdir_rules.mk:10: recipe for target 'build-1863261585-inproc' failed
gmake[1]: *** [build-1863261585-inproc] Segmentation fault (core dumped)
gmake: *** No rule to make target 'build-1863261585', needed by 'configPkg/compiler.opt'.
gmake[1]: Leaving directory '/localdata/home/me/repositories/BP_GPUDSP/ti_ccs/gfaulttest2/Debug'
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

I also tried installing oracle JVM 1.8.0_131 as default instead of OpenJDK 7 with no luck.
The XDCtools 3.50.2.20_core show the same issue, too.
My system is 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.

My workaround is to bypass ccstudio and just run the eclipse directly, so far all is correct, but interface a little different.

 <install dir>/ti/eclipse/  ./eclipse

I have the same issue. With the quick fix I can start CCS again but I cannot compile anymore due to the XS segmentation fault.

Looking at the XS script it is using LD_LIBRARY_PATH="${ROOT}:${ROOT}/jre/lib/amd64/server:${ROOT}/jre/lib/amd64$_cur"

My system: 4.8.0-56-generic #61~16.04.1-Ubuntu SMP Wed Jun 14 11:58:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

Silver Diamond said:

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

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)

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 

ChrisF said:

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

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.

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.

You are right..... thanks.

But, it doesn't compile completely as you can see here...

**************************************************************************************

# making package.mak (because of package.bld) ...

...

#
# making package.mak (because of package.bld) ...
...

subdir_rules.mk:24: recipe for target 'build-326279697-inproc' failed
Picked up JAVA_TOOL_OPTIONS: -Xss1280k
Picked up JAVA_TOOL_OPTIONS: -Xss1280k
gmake: *** Deleting file `package.mak'
Picked up JAVA_TOOL_OPTIONS: -Xss1280k
gmake: *** Deleting file `package.mak'
gmake: *** No rule to make target `.configuro'.  Stop.
js: "/home/ybonin/ti/xdctools_3_32_01_22_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake[1]: *** [build-326279697-inproc] Error 1
gmake: *** [build-326279697] Error 2
**************************************************************************************

Any clue ???

Good, however on linux Kernel 4.10.0-24-generic (Ubuntu 17.04) I also had to comment 2 lines on the top of the ccstudio.ini file to make it work.

It will be nice to have this info added back on TI wiki. http://processors.wiki.ti.com/index.php/Download_CCS

#-vm
#jre/lib/amd64/server/libjvm.so

Hello,

We had the problem with Likux Kernel 3.13.0-121 so we downgrade it until found a combination of Lunix Kernel-CCS that works.

These are the versions:

• Linux ialbar 3.13.0-119-generic #166-Ubuntu SMP Wed May 3 12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
• CCS v5.5 and CCS v6.2.

We hope that this information will be helpful to someone.

Best regards.

This workaround doesn't work for me.

Would it be possible to get more information about the problem and how it's affecting CCS/xdc?

Thank you

The workaround JAVA_TOOL_OPTIONS= -Xss2560k has been working for me. It fixed both CCS and XDC issues.

Annette Keller said:

This workaround doesn't work for me.

Would it be possible to get more information about the problem and how it's affecting CCS/xdc?

Hi,

I am not sure if that is your case, but I needed to run my CCS as sudo and was unable to apply the workaround. In this case, before I set the Java options I started a persistent sudo subshell. In other words:

user@host:~$ cd /opt/ti/ccsv7/eclipse
user@host:/opt/ti/ccsv7/eclipse$ sudo -i
user@host:/opt/ti/ccsv7/eclipse# set JAVA_TOOL_OPTIONS=-Xss2560k
user@host:/opt/ti/ccsv7/eclipse# ./ccstudio &

By the way, when running as sudo the -Xss1280 issued segfaults for me.

Hope this helps,

Rafael 

Hi,

I can attest that updating my Ubuntu 16.04/64 with today's kernel patches is enough to allow CCS to be properly launched. The packages installed today were:

Linux said:

user@host:~$ ls -lt /var/lib/dpkg/info

-rw-r--r-- 1 root root 1510 Jun 29 09:05 nautilus.list
-rw-r--r-- 1 root root 728 Jun 29 09:05 nautilus-data.list
-rw-r--r-- 1 root root 198 Jun 29 09:05 linux-headers-generic-hwe-16.04.list
-rw-r--r-- 1 root root 716176 Jun 29 09:05 linux-headers-4.8.0-58-generic.list
-rw-r--r-- 1 root root 1093378 Jun 29 09:05 linux-headers-4.8.0-58.list
-rw-r--r-- 1 root root 192 Jun 29 09:05 linux-image-generic-hwe-16.04.list
-rw-r--r-- 1 root root 174 Jun 29 09:05 linux-generic-hwe-16.04.list
-rw-r--r-- 1 root root 330340 Jun 29 09:05 linux-image-extra-4.8.0-58-generic.list
-rw-r--r-- 1 root root 80015 Jun 29 09:05 linux-image-4.8.0-58-generic.list
-rw-r--r-- 1 root root 515 Jun 29 09:05 libnautilus-extension1a:amd64.list
(...)

My kernel is still 4.8.0-58

Linux said:

user@host:~$ uname -a
Linux host 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Regards,

Rafael