• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 928 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 V6.1 suddenly stopped building all projects

Richard9776
Prodigy 180 points

Yesterday, CCS suddenly stopped building projects. All of them. I get this output:

**** Build of configuration Debug for project ceiDsp ****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all

'Building file: ../app.cfg'

'Invoking: XDCtools'

"C:/ti/xdctools_3_25_03_72/xs" --xdcpath="C:/ti/bios_6_35_04_50/packages;C:/Clearcase/rbossard_MV_v14.02.00/Keysets/Keysets_GT/ceiDsp/MyRepository/packages;C:/ti/ccsv6/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.C64P -p compunetix.omap3730 -r release -b "C:/Clearcase/rbossard_MV_v16.01.00/Keysets/Keysets_GT/ceiDsp/MyRepository/packages/compunetix/omap3730/config.bld" -c "C:/ti/ccsv6/tools/compiler/c6000_7.4.14" --compileOptions "-g --optimize_with_debug" "../app.cfg"

js: "C:/ti/xdctools_3_25_03_72/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: Error: can't open input file '../app.cfg'

gmake: *** [configPkg/linker.cmd] Error 1

gmake: Target `all' not remade because of errors.

**** Build Finished ****

I've reinstalled CCS 6.1, switched compiler versions, switched and reinstalled xdc and sys/bios vesions. The projects are in source control under clearcase  and I've loaded past versions of projects where I know they've built. Nothing makes any difference. I've looked through E2E and found nothing that seems to help. The xdc and compiler versions are shown above and I'm using sys/bios 6.35.4.50. I've deleted the workspace, deleted all the CCS files and directories under my \users profile.  I'm at a loss for what else to try or look for. Can anyone help? My development work is completely shut down.

Oh and I'm running windows 7 pro service pack 1 and is pretty up to date with patches.

Rick

  • 0
    TI__Guru**** 478571 points
    Hi Rick,

    does "app.cfg" exist in the root location of the project directory? It seems to be having problems accessing that file.

    Thanks
    ki
  • 0 in reply to Ki
    Prodigy 180 points
    Yes. It is in the project root and opens just fine. I also went back and loaded some old versions of the project from source control that I _absolutely_ know built properly. Same result there and with every other pre-existing project on my PC. It's something systemic. Are there any registry, path, system variables that could be messed up? Maybe the problem isn't in CCS directly. That gave me an idea to create a brand new sys/bios project and see what happens.
  • 0 in reply to Ki
    Prodigy 180 points

    Problem solved. It was a registry change meant to change the default path in the command prompt window.

  • 0 in reply to Richard9776
    Intellectual 270 points
    Richard,

    I seem to be having the same problem. Could you provide any further information on what changes caused the issue, or where I could look to locate the problem? I am having no luck so far.

    Much appreciated,
  • 0 in reply to Jonathan Thomson
    Prodigy 180 points
    I was annoyed that my command windows opened pointing to a network drive (U:\) and researched how to change it to C:\. I made the following change to the windows registry from instructions I found on www.sevenforums.com :

    In regedit
    go to "HKEY_CURRENT_USER \ Software \ Microsoft \ Command Processor"
    add the key "Autorun"
    set the value of the key (in my case) to "cd /d c:\"

    Removing the key fixed the CCS problem.
    I don't really understand why this breaks CCS as I make no use of the U: drive, but it did.
    Hope it helps you.