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 Version 5.1.0.07001 systemHeap always in L2RAM

Hi,

I'm using the pdk_C6678_1_0_0_14 and the CCS version 5.1.0.07001 and I have the following problems.

1.- I used to change in previous CCS versions the systemHeap (using the CCS environment) between L2RAM, DDR3 or MSMCSRAM.

I installed the version 5.1.0.07001 and when I try to change the systemHeap, it remains in always in L2RAM.

2.-I Received in problems window, the message "Type 'Task_Params' could not be resolved" but the compilation succeeded.

Please, could you help me?

 

Thanks in advance.

Shmulik.

 

  • Ensure that you have your heap configured correctly instead of relying on default value (if you are).  Heap Size Configuration is a great thread explaining how to configure the default heap.  The lines in your .cfg file you care about most are the following:

    BIOS.heapSize                 = 0x300000; // change size to your specific requirements
    BIOS.heapSection              = "systemHeap";
    Program.sectMap["systemHeap"] = "DDR2";   // change "DDR2" to whatever MEMORY section you have defined in your platform definition (or in your linker command file if you use one)

    As for the  "could not be resolved" error, that is just coming from the Code Analysis plug-in.  It got broken in M7 (I posted a thread about it), and TI's stance is that they are not going to support it, so you need to go disable those checks.  In Eclipse, go to Window-->Preferences-->C/C++-->Code Analysis settings and disable the entire "Syntax and Semantic Errors" section.  (If you use Log_info/print/etc() functions, you should also disable the "Suggested parenthesis..." check as well unless you don't mind the warnings.)  Note that your project may be overriding these global workspace settings, so verify it's the same in your project's properties as well.

  • Hi Alex,

    Thanks for your response, it's very useful, but why is not possible in this version to change parameters from the graphical windows that appears when you press twice to the SRIO_test.cfg file in the project manager?
    I did it in previous versions without problems.

    Thanks.
    Shmulik

  • You should be able to do it in the XGCONF tool like you want.  Plug in the values, save, and then switch to the "Source" tab and verify.  You should be able to find the lines I cited above.  The only thing I am not 100% sure about is if it will allow you to specify the MEMORY region to place the section in, and that is the root of your problem.  I suspect that without explicitly and manually updating the .cfg file, the xdctool will just default to just placing it in your platform's data section.

    I'm old-school when it comes to my applications, so I rarely use XGCONF and, instead, manually create and update my configuration and linker command files in a text editor.  Given that you prefer to use the GUI, I will step back and let someone else more experienced with XGCONF help you out.

  • Hi,

    1.-  I have no problem to try with editor, but I suppose that in some cases CCS will create a new cfg file during the project build,

    and in this case CCS will overwrite my changes in the cfg file. I'm right?

    2- Another question, you wrote 'disable the entire "Syntax and Semantic Errors" section' , it means that additional errors in that will be desabled with

    this option are unnecessaries?

  • Hi,

    1.-  I have no problem to try with editor, but I suppose that in some cases CCS will create a new cfg file during the project build,

    and in this case CCS will overwrite my changes in the cfg file. I'm right?

    2- Another question, you wrote 'disable the entire "Syntax and Semantic Errors" section' , it means that additional errors that will be desabled 

    for disabling the whole "Syntax and Semantic Errors" section are unnecessaries?

    Thanks.

     

    Shmulik

  • No, the graphical configuration tool is very good at allowing for both modes.  If you use the tool to add something new, it will just stick it at the end.  If use it to update something already defined, it will update the relevant lines in the .cfg file in-place--the only thing you lose, of course, are any comments you may have added to the line.

    About the code analysis tool, keep in mind that is strictly for editor annotations only.  If you truly have a syntax or semantic error, your compiler or linker will complain, worry not!  What's annoying, though, is the debug launcher treats all errors in the "Problems" pane the same, so even though it's not a compile or link error, you will still get the nag screen about there being errors and "Are you sure you want to launch?" confirmations. (One solution, of course, is just to change the check from an error message to a warning or info message instead of disabling it altogether, but that's a personal preference.  I like my builds to be 100% clean.)

    You can hand-pick which errors to disable, of course, but the more components of SYS/BIOS you start using, more of different types of errors will show up.  In the end, I just decided to turn that section off altogether to save myself the grief.