• Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 1653 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.

Error 24010 (c_file is missing parameter filename) when compiling CLA-code

Alejandro Navarro
Prodigy 50 points

Hi everybody,

Sometimes when I compile my project (CCS 6.1 for TI F28069 on Control Stick), I get the error:

#24010-D option --c_file is missing its parameter 'filename' cla_tasks.cla

The file cla_tasks.cla contains the code to be executed in the CLA, as expected. This error appears after a "big number" of successful compilations, mostly when switching between Debug and Release configurations (but not always).

Usually this issue gets solved after a random sequence of cleaning workspace, cleaning project, creating a new workspace or even a new project and importing files and settings. I even tried once to force the compilation of the .cla file with the common C-compiler (which obviously did not work), then I reverted the settings, and this got the job done.

However, I would like to know where the cause lies, and which is the most effective way to overcome this error, instead of solving it just by chance.

Any help or information on this issue is welcome. Thank you very much in advance,

Alex.

  • TI__Guru**** 173310 points

    Alejandro Navarro said:
    #24010-D option --c_file is missing its parameter 'filename' cla_tasks.cla

    The message indicates that the --c_file compiler option is being enabled, but that it is missing its parameter. 

    Taking a closer look at the build output in the CCS build console and understanding where the --c_file option is coming from (and if it is even required) and what is being passed to it, should give some clues as to why the error is generated. If you are not able to find the root cause after reviewing the build output, please copy and paste the full output of the CCS build console to a text file and attach it here, so we can take a look at it.

  • in reply to AartiG
    Prodigy 50 points

    Hello AartiG,

    Here is the output of the compiler. The missing parameter of --c_file should be precisely the .cla file, just search "cla_tasks.cla" and "c_file= --preproc" in the log file, if you want to skip the rest.

    compiler_log_20160219.txt

  • in reply to Alejandro Navarro
    TI__Guru**** 173310 points

    Sorry about the delayed reply.

    As you said, the option --c_file is missing its parameter. As far as I know, this option is not required at all, as the .cla extension is sufficient for the compiler to know that it is a CLA C file. You should be ok deleting the option altogether.  Can you check if this option is being set and delete it?

  • in reply to AartiG
    Prodigy 50 points
    Hi AartiG,

    The .cla file was not marked as C-file in the project preferences. I even tried marking and unmarking it again, but both configurations failed. I also tried with different C-compilers (C99 / ANSI C), since the options I am using from C99 are supported by default in the ANSI C mode. As expected, this did not work -- the CLA compiler is independent.

    Actually I have created a new project and set it up from scratch, and the program has compiled without any problem -- formerly this procedure had failed as well.

    However, I would like to know if there is any explanation for this issue, and if it could be improved in future releases of Code Composer. In case this is an inherent "feature" of CCS or Eclipse, it would be useful to have a list of known issues/bugs which can be solved by re-configuring / starting a new project.

    Please understand, as user it is very frustrating and time-consuming to check source code, linker files, settings, etc. many times, when the not-too-bad solution consists of simply starting a new project.

    Thank you very much.
  • in reply to Alejandro Navarro
    TI__Guru**** 173310 points

    Alejandro Navarro said:
    Actually I have created a new project and set it up from scratch, and the program has compiled without any problem -- formerly this procedure had failed as well.

    However, I would like to know if there is any explanation for this issue, and if it could be improved in future releases of Code Composer. In case this is an inherent "feature" of CCS or Eclipse, it would be useful to have a list of known issues/bugs which can be solved by re-configuring / starting a new project.

    Good to know that creating a new project resolved the issue. Unfortunately, I cannot explain the cause of this issue and am not aware of any known bugs in this regard. It seems that this option somehow got inserted into the build, and you were then unable to remove it. If you still have the old project and are willing to share it with us, we could take a look at see if anything stands out.

    I understand such situations can be frustrating and I apologize for the inconvenience caused.