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.

file permission problems, build fails, CCS V5.5

Hello,

I am having repeated problems with file permissions while building with CCS V5.5.  For instance, this is but one error that occurs (the first), when rebuilding my project:

"acfg.s62", ERROR! : [E1000] Cannot open source file acfg.s62: Permission denied

This seems to occur at random, as I had been building the project without issue, when all of a sudden this started after a file edit.  It had happened previously, so I moved my project to a new directory.  Which seemed to resolve it, until randomly it began again in the new directory as well.  

I've tried all kinds of security things, under the Windoze Security tab, opening up permissions, adding full control, etc.  But no solution yet.

Here is another error, further along on the failed build (I changed the project name to "a" in the error messages intentionally, when cutting and pasting here)

Fatal error #5: could not open source file "acfg_c.c"

1 fatal error detected in the compilation of "acfg_c.c".
Compilation terminated.

>> Compilation failure
gmake: *** [acfg_c.obj] Error 1

I've looked through a lot of other E2E posts, trying to find an answer, but without luck.

Regards,

Robert

  • Hello Robert,
    Are the source files version controlled? Are you working with files on a network drive or are they all local to the PC?

    Thanks
    ki
  • Hi,

    The source files are version controlled (Accurev), but the .s62 file that it's having permissions problems with (the first one), is not version controlled, since it's a generated file.

    The files are all local to the PC, but the version controlled repositories are network.

    Thanks,
    Robert
  • Can you post the full build output that appears in the build console?

    Thanks
    ki
  • I would like to just cut and paste, but it contains proprietary naming. I will relay as much as possible, despite that.

    **** Build of configuration Debug for project a ****

    "C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all
    'Building file: ../a.tcf'
    'Invoking: TConf'
    "C:/ti/bios_5_42_01_09/xdctools/tconf" -b -Dconfig.importPath="C:/ti/bios_5_42_01_09/packages;" "../a.tcf"
    'Finished building: ../a.tcf'
    ' '
    'Building file: acfg.s??'
    'Invoking: C6000 Compiler'
    "C:/ti/ccsv5/tools/compiler/c6000_7.4.4/bin/cl6x" -mv6740 --abi=coffabi -g --include_path="C:/ti/ccsv5/tools/compiler/c6000_7.4.4/include" --include_path="project path removed"
    .
    .
    .
    more --include_path
    .
    .
    .
    --include_path="C:/ti/bios_5_42_01_09/packages/ti/rtdx/include/c6000" --display_error_number --diag_warning=225 --set_error_limit=5 --preproc_with_compile --preproc_dependency="acfg.pp" "acfg.s??"
    "acfg.s62", ERROR! : [E1000] Cannot open source file acfg.s62: Permission
    denied

    >> Compilation failure
    gmake: *** [acfg.obj] Error 1
    'Building file: acfg_c.c'
    'Invoking: C6000 Compiler'
    "C:/ti/ccsv5/tools/compiler/c6000_7.4.4/bin/cl6x" -mv6740 --abi=coffabi -g --include_path="C:/ti/ccsv5/tools/compiler/c6000_7.4.4/include" --include_path="project path removed"
    .
    .
    .
    more --include_path
    .
    .
    .
    -include_path="C:/ti/bios_5_42_01_09/packages/ti/rtdx/include/c6000" --display_error_number --diag_warning=225 --set_error_limit=5 --preproc_with_compile --preproc_dependency="acfg_c.pp" "acfg_c.c"
    Fatal error #5: could not open source file "acfg_c.c"
    1 fatal error detected in the compilation of "acfg_c.c".
    Compilation terminated.

    >> Compilation failure
    gmake: *** [acfg_c.obj] Error 1
    ~
    ~
  • My development efforts are on hold, until this can be resolved. Any further help would be appreciated.
  • Hi Robert,
    Due to the seemingly random nature of the issue, it is hard to pin down. It is likely some strange issue with the build tools... but one thing I ask if you can do is if you are willing to update your CCS version as CCSv5.5 is fairly old and deprecated in support. Note that you can use the same build tools and DSP/BIOS version with CCSv6.

    Also, make sure you have your Windows environment variables TMP and TEMP pointing to a writable and valid directory. There have been similar reported issues when these variables were not pointing to valid directories (or were not defined at all).

    Thanks
    ki
  • My environment variables were pointing to a valid, writable TMP and TEMP directory. I upgraded to CCS V6, and initially had some problems trying to create a new project. But those were resolved by finding, and using, the .cproject file from the CCS V5 work. I can now build, load and run. Hopefully the permissions problems don't re-appear.

    Unfortunately, my application is no longer running the same under CCS V6, as under CCS V5, but that is a different problem.

    Thanks,
    Robert