Linux: CCS 5.1m7 license problems, CCS 5.1m8.5 only working with sudo

christian bach said:

It seams to be unable to generate the necessary license file.

If the 30-day eval license generation for Linux did not work, you could request a 90-day evaluation license as described in the page below and use that same license file in Linux. Please see the FAQ section in this page for where to request the 90 day extension: http://processors.wiki.ti.com/index.php/Licensing_-_CCS

christian bach said:

My second attempt was to create a second virtual system and install CCS 5.1m8.5 but this one can't be started unless I use the 'sudo' command to start it...

I was able to duplicate this behavior and that looks like a bug. CCS should be installed with root privileges but should not require root privileges to run. I am going to submit this issue to the development team. In the meantime, I suggest that you stay with CCS 5.1M7 and hopefully the above suggestion should allow you to get the licensing going.

I'm having the same issue on CCS 5.1 m8.5, i.e I cannot launch as a user.  I installed CCS using "sudo".  I am now trying to launch CCS as a user and I see this error:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::filesystem::basic_filesystem_error<boost::filesystem::basic_path<std::string, boost::filesystem::path_traits> > > >'
  what():  boost::filesystem::create_directory: Permission denied: "/usr/local/CCSv5.1m8/0"
Aborted

If I look at permissions for CCSv5.1m8 directory this is no surprise:

drwxr-xr-x  9 root root 4096 2011-09-29 15:31 CCSv5.1m8/

That is, only root has write permissions to this directory.  So is this a bug in the installer or do we just need to modify the installation directions?  For example, maybe we need to tell people to execute something like this:

sudo chmod -R a+w /usr/local/CCSv5.1m8/

After making the entire directory structure writeable that at least allowed me to start CCS.  I haven't tried an emulator or anything yet.  That's the next big question mark...

Just a quick update...  Looks like XDS100v2 is working ok (even when I launch as user).  I could not get CCS to communicate with my Blackhawk though.

For reference, the bug tracking # for the CCS permissions issue is SDSCM00041947.

Brad,

Can you let me know if your environment has a TI_APPDATA_DIR variable set? (ie; > echo $TI_APPDATA_DIR)

If this is set, it might change the location where shared objects are stored, so I'm curious to know if this is the reason why it is trying to write to your /usr/local/CCSv5.1m8/ directory.

Thanks.

Ricky

Ricky Lau said:

Can you let me know if your environment has a TI_APPDATA_DIR variable set? (ie; > echo $TI_APPDATA_DIR)

Empty...

Ricky Lau said:

If this is set, it might change the location where shared objects are stored, so I'm curious to know if this is the reason why it is trying to write to your /usr/local/CCSv5.1m8/ directory.

/usr/local/CCSv5.1m8 is where I installed it so it's not surprising that's it's trying to write files in that subdirectory.  The issue is the permissions are not correct inside that directory.

Brad,

We recently finished up our investigation on the issue, and we discovered that the underlying problem seems to be related to the permissions on the Application data folder (located at home directory: ~/.TI/). If the current user does not have write access to this folder or the sub folders/files, it can cause the error you were seeing. We are looking at possible solutions to address this issue.

To work around this issue, you can delete your ~/.TI/ folder.

Please let me know if this works for you.

Thanks.

Ricky

Ricky,

Which problem are you trying to resolve?  I successfully launched CCS 5.1 M8 as user a long time ago.  As I originally reported the solution was the run the following command:

sudo chmod -R a+w /usr/local/CCSv5.1m8/

The only problem that remains is that I cannot launch my BH XDS560v2 emulator.  I'll start a separate thread for that.

Brad

Brad,

Yes, I was only suggesting an alternate workaround to your first problem. But the idea is that CCS should not be using /usr/local/CCSv5.1m8/ as the application data directory. It is only using it because the original location does not have the correct permissions. Using the correct application directory ensures that CCS is running as expected.

Regards,

Ricky