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/AM3352: Changing config.ini in \ ti \ ccsv8 \ eclipse \ configuration

Part Number: AM3352
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hi CCS support Team,

My customer has the following question.

He create the workspace on the network drive for CCSv8,

and add "osgi.locking = none" at the end of config.ini in \ ti \ ccsv8 \ eclipse \ configuration

for not locked.

He can use the workspace on the network drive without any lock, so far.

 

Question:

Does this setting to add "osgi.locking = none at the end of config.ini in \ ti \ ccsv8 \ eclipse \ configuration"

make any influences the behavior of Something against CCS, and is there anything outside of TI's warranty?

 

Best regards,

Kanae

  • Kanae,

    I would expect adding that to the ini file to be ok. I have asked the development team about it to see if they are aware of any potential issues. Will there be multiple users running CCS from the same location at the same time?

    Regards,
    John
  • Hi John,

     

    Thank you for your support.

    I will check it to my customer.

     

    If he does not use the workspace with multiple users running CCS

    from the same location at the same time.

    In other words, if he would like to use the network drive

    just for saving his own local PC disk space, are there any potential issues?

     

    Best regards,

    Kanae

  • Hi Kanae, 

    The reason why osgi.locking=none is required is because eclipse\configuration does not have write permissions. You can add osgi.locking=none, but installing updates  (certain SW packages) might not behave correctly. Could you check with customer if changing write permissions on ccs directory is possible, if updating/installing packages will be needed?

    Martin

     

  •  

    Hi Martin,

     

    Thank you for your reply!

    I have check your questions to my customer.

     

    He will just use the workspace in the network drive

    for saving his own local PC disk space, it is not used by several persons.

     

    And he can give the authority to write the folder using for the workspace

    to the target user.

    This folder will be used by one person, so he would like to set the folder

    without access limitation.

    Is the setting no problem?

     

    Best regards,

    Kanae

  • Hello, 

    I believe that if eclipse directory is writable then there is no need for osgi flag to be added to ccstudio.ini file. 

    Martin

  • Hi Martin,

    Thank you for your reply.
    My customer is concerned about changing the ccsstudio.ini file within the CCS specification.
    If he changes it, it is covered under warranty, or not?
    And also he would like to make sure that he does not need to change the ini file after installing CCSv8
    when he use the network drive for his own drive and he can give the authority to write the drive using for the workspace.
    Is his understanding correct?

    Best regards,
    Kanae
  • Hi Kanae, 

    CCS installation directory, specifically, ccsv8\eclipse directory needs to be writable. 

    Workspace directory can be created in CCS installation directory or it can exist elsewhere, this is a user choice. CCS will need to have write permissions to workspace directory as well. 

    If both locations are writable, then you do not need to modify ccstudio.ini

    Martin

  • Hi Martin,

    Thank you for your reply.
    I understand that my customer can use any drive such as a network/USB,
    if the directory can be writable, and it is not needed to modify ccstudio.ini.

    I really appreciate your support!

    Best regards,
    Kanae