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.

[FAQ] CCS: Why do I need to avoid non-alphanumeric (unicode) characters in my paths?

Guru**** 421380 points

Tool/software: Code Composer Studio

Why do I need to avoid non-alphanumeric/unicode characters in my installation/build/workspace paths?

  • Paths with non-alphanumeric characters can potentially cause various project management and build issues. In some cases, the build may go fine but clicking the Debug button may not start up the debugger. Or going to Project Properties->Debug may result in error: Error reading Debug Properties. Any of these symptoms could occur when using paths with non-alphanumeric characters.

    Examples of non-alphanumeric characters are &, !, (, #, etc. It is recommended to avoid such characters in project names, source/header files/folders, CCS workspace folder names, system temp folder, etc. One exception is the underscore character _, which is normally accepted. A space/whitespace character, while acceptable in most cases, can cause some build issues (especially with SYS/BIOS projects), hence it is recommended to also avoid it.

    Note that many CCS files are cached in the user's home folder. The default workspace location is also in the home folder. If the user's username has non-alphanumeric characters, then this would cause issues since the path to there user's home folder is often a folder named the same as the username.

  • Ki said:
    A space/whitespace character, while acceptable in most cases, can cause build issues with SYS/BIOS projects, hence it is recommended to also avoid it.

    space/whitespace characters can also cause trouble with the GUI Composer runtime:

    https://e2e.ti.com/support/tools/ccs/f/81/p/884673/3276342#3276342