• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 3779 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.

Unable to find configuration file

David BERNARDI
Prodigy 120 points


Hello,

I'm working on the TMS320C6678 with CCS 5.0.3.00023.

I'm trying to compile an example project (Minimal BIOS project) but I keep having this error :


**** Build of configuration Debug for project MINIMAL_BIOS ****

C:\ti\ccsv5\utils\gmake\gmake -k all
'Building file: ../app.cfg'
'Invoking: XDCtools'
"C:/ti/xdctools_3_23_04_60/xs" --xdcpath="C:/ti/bios_6_33_06_50/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r release -c "C:/ti/ccsv5/tools/compiler/c6000_7.3.1" "../app.cfg"
C:/Users/David/AppData/Local/Temp/make3544-1.sh: Can't open C:/Users/David/AppData/Local/Temp/make3544-1.sh: No such file or directory
C:/ti/xdctools_3_23_04_60/packages/xdc/bld/xdc_rules.mak:313: *** Error: Specified build configuration file '' is not found.  Stop.
js: "C:/ti/xdctools_3_23_04_60/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake: Target `all' not remade because of errors.

Yet, there is a configuration file in the project : "app.cfg".

In Build Settings >Settings>XCDTools>Advanced Options, I see there is a "Build configuration file" field. I'm not sure about what I should put in there. I've tried to put the app.cfg file but it doesn't work.

Any suggestions ?

Thanks,

David.

  • 0
    TI__Mastermind 37985 points

    David,
    "Build configuration file" is an optional file where you can define certain build options that are not available as configuro options. In most cases, you don't need to specify that option. Please verify that the text box for that option is completely empty and that there are no white space characters left in it.

    I was trying to replicate the error you are seeing, but an incorrect build configuration script setting would stop the build before any output in the console. I am using CCSv5.2, so that could account for the different output. There is a short make file Debug/subdir_rules.mk, which contains relevant command lines. Can you post the content of that file?

  • 0 in reply to Sasha Slijepcevic
    Prodigy 120 points

    Sasha,

    "Build configuration file" is completely blank. There are no space characters in it. It still doesn't work.

    There is no "subdir_rules.mk" in that Debug folder. There is a subdir.mk, though : http://pastebin.com/Qd6394Ur

    Strangely, I tried to put a space character in the "Build configuration file" field and It seems to be working. (the "Specified build configuration file '' is not found.  Stop." error doesn't occur anymore).

    I am tempted to mark the topic as answered, but I don't think that's normal...

    Thanks,

    David.

  • 0 in reply to David BERNARDI
    TI__Mastermind 37985 points

    David,
    that's not expected behavior. Before any further debugging, I would recommend removing the example from the workspace and from the disk, and creating it again. If that helps, then the project somehow ended up in an incorrect state and CCS couldn't recover it.

    If you still can reproduce the error reliably with a new project, you should turn on the verbose output so we can see what is the actual configuro command line in both cases, when the error message is displayed and when the project builds. You can turn the verbose output from the same pane where you set the build configuration file. There is an option "Show details during build (-v)", which you should turn on.
    The command line from the file you posted looks wrong, and configuro should fail when encountering that command line. Is the file you posted from the use case when the build works, or from the scenario where it fails?

  • 0 in reply to Sasha Slijepcevic
    Prodigy 120 points

    Sasha,

    I've deleted the example from the workspace and created a new one. I tried that many times with different examples but that error regarding the ' ' configuration file still occurs.

    I turned the "Show details during build" option on. This writes details in an app.cfg file, right ? Here is a copy paste of this file when compilation fails : http://pastebin.com/7PDRreja

    When the compilation works, there is no app.cfg file at all.

    subdir.mk when it fails : http://pastebin.com/2Cx38X0q

    subdir.mk when I dont get the error : http://pastebin.com/v3YXW3bP

    I'm still performing tests and I will let you know if I find anything relevant.

    Thanks,

    David.

  • 0 in reply to David BERNARDI
    TI__Mastermind 37985 points

    David,
    -v option enables a more verbose output in the console window. What you posted in your first link is your configuration script, which is something that I wanted to see anyway, but it doesn't tell me what's the content of the configuro command line. Look at your console window, it should have a different content depending on the option -v being turned on or off.

    The other two files you posted are giving me a pretty good idea about the configuro command line, and they look just the opposite of what would be expected. The configuro command line in the first file looks correct, while the second one looks wrong. At this point you should consider upgrading CCS. The version 5.0.3 is fairly old and it is one of the first CCSv5 releases. There are many bugs that were fixed in later releases.

  • 0 in reply to Sasha Slijepcevic
    Expert 1830 points

    I know this is an old thread, but as I just ran into the exact same problem and the issue seems to be unresolved I wanted to add that in my case the culprit was a cygwin conflict. I tried to solve a cygwin1.dll conflict (leading to occasional cygwin heap corruptions) by renaming the offending cygwin1.dll. That seemed to solve the heap problems but xdc would no longer work, complaining about a missing specified build config ''. With the original cygwin1.dll back in place, that error is gone (but the heap corruptions are back, sigh).

  • 0 in reply to Markus Moll
    TI__Mastermind 37985 points

    Markus,
    do you have both xdc/bin and cygwin/bin in your path? Does the heap get corrupted when using xdc or when using cygwin with other tools? Our standard recommendation for problems with cygwin is to remove cygwin/bin directory from the path when using xdc. If you have problems when using cygwin with other tools, have you tried removing xdc/bin from the path?