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.

access C674x CPU Register with CCS5 / CGT version change

Other Parts Discussed in Thread: CCSTUDIO

        !WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.C6000_6.1.compilerID.ABI

My questions:

1) Why does the keyword 'cregister' show in black instead of purple (it is not recognized as keyword in CCS5 and hasn't been in CCS4 either )

2) Can I use both '__cregister' (like in the c6x.h) and 'cregister' (like in spru187t, example 6-1) or is there a difference in behavior?

3) I didn't set the --coffabi compiler option manually, it was set automatically when I switched to CGT 7.3.1 (which is a nice feature but might cause problems). Why doesn't it get removed automatically when switching back to 6.1.14? Are there other settings that are changed when I go from 6.1.14 to 7.3.1 and back?

4) How can I get rid of the syntax error (I wouldn't want to go back to assembler code to modify IER unless there is a compiler directive to reserve one or two registers for my own assembler code)?


By the way, I opened another thread on the same topic last tuesday and got a confirmation email, but the thread is not available any more and I didn't get any reply, either.

Andreas44690 posted <a href="http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/p/158609/575800.aspx#575800">C674x CPU Register with CCS5 / CGT version change</a> in OMAP-L13x, AM1x and C674x Processors Forum.



  • Pictures were missing ...

    After migration from CCS4 to CCS5 5.1.0.09000 I get a syntax error for the following lines in my main.c file:

    extern cregister volatile unsigned int IER;
    extern __cregister volatile unsigned int CSR;

    (Those lines are identical to the ones from ...\ccsv5\tools\compiler\c6000\include\c6x.h. In that file, no syntax error is shown).

    As a consequence, the symbols IER and CSR cannot be resolved. I tried both compiler versions 6.1.14 and 7.3.1. I use those statements on file scope (I also tried as first lines in main.c).

    My environment is





    Another strange thing: After switching back to CGT 6.1.14, I get the error message:



    !CONFIGURATION: {0} [Mon Jan 16 15:16:10 CET 2012]

        !TOOL: {0}

            !WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.C6000_6.1.compilerID.ABI

    My questions:

    1) Why does the keyword 'cregister' show in black instead of purple (it is not recognized as keyword in CCS5 and hasn't been in CCS4 either )

    2) Can I use both '__cregister' (like in the c6x.h) and 'cregister' (like in spru187t, example 6-1) or is there a difference in behavior?

    3) I didn't set the --coffabi compiler option manually, it was set automatically when I switched to CGT 7.3.1 (which is a nice feature but might cause problems). Why doesn't it get removed automatically when switching back to 6.1.14? Are there other settings that are changed when I go from 6.1.14 to 7.3.1 and back?

    4) How can I get rid of the syntax error (I wouldn't want to go back to assembler code to modify IER unless there is a compiler directive to reserve one or two registers for my own assembler code)?

  • Andreas44690 said:
    1) Why does the keyword 'cregister' show in black instead of purple (it is not recognized as keyword in CCS5 and hasn't been in CCS4 either )

    This is coming from the live syntax checker in the editor.  It recognizes cregister as a valid keyword but not __cregister.  This checker is separate from the compiler, the code should compile fine but the syntax checker in the editor is not aware of all TI special keywords.  The __cregister one will need to be added to our list.  I have filed a defect to track this.  SDSCM00042924

    Someone else will respond to the other issues.

    john

  • Your other thread is here: http://e2e.ti.com/support/development_tools/compiler/f/343/t/158609.aspx

    Looks like it was inadvertantly moved to forum wich is not visible externally, which was why you couldn't find it. Sorry about that!
    Please check the answer there in addition to John's reply above and let us know if any questions remain.

  • John, as the other thread appeared again, I will answer in

    http://e2e.ti.com/support/development_tools/compiler/f/343/t/158609.aspx#575800

    Andi