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: Memory Allocation Window hides small memory sections

Tool/software: Code Composer Studio

Hi!

Im using a C2000 Piccolo 280045 with CCS 9 at the moment.
I defined some custom memory sections in GSRAM and wondered why some sections don't appear in the memory allocation window but all variables are at the correct address (so the sections MUST exist).

It seems like CCS is hiding all sections below 100 bytes/words.

Why does it happen?
Is it possible to change that behaviour?

Kind regards

Dominik

  • Dominik,

    I don't know of any logic in the view that hides sections below a particular value.  I will confirm with the owner of the view later today.

    I tried out the view on a very small program and it was showing .cinit which is 26 bytes.

    Are the sections showing up in the <project name>_linkinfo.xml file in the build configuration folder (typically \Debug).

    Regards,

    John

  • Excuse me, the exact value is below 101!

    The section appears in this file, but it is obviously hidden (display="no") if the size is below 101: here 100 (0x64)


    <memory_area display="no" color="green">
    <name>RAMGS_COMM</name>
    <page_id>0x0</page_id>
    <origin>0xc000</origin>
    <length>0x64</length>
    <used_space>0x20</used_space>
    <unused_space>0x44</unused_space>
    <attributes>RWIX</attributes>
    <usage_details>
    <allocated_space>
    <start_address>0xc000</start_address>
    <size>0x20</size>
    <logical_group_ref idref="lg-d"/>
    </allocated_space>
    <available_space>
    <start_address>0xc020</start_address>
    <size>0x44</size>
    </available_space>
    </usage_details>
    </memory_area>
  • Interesting that this is directly in the detailed map file.

    I was experimenting with section sizes and not memory area sizes.

    The linker command file defines memory areas and then assigns sections to those areas.
    MEMORY
    {
    }
    SECTIONS
    {
    }

    Section size has no impact on the display. Looks like it explicitly hides small memory areas. I don't know why that is. The Memory Allocation view just reads this file. The file gets generated by the build and the only command line option that I see is to specify that the file gets generated. I will ask what the reason for this is.

    Regards,
    John
  • Dominik,

    I found a way to override what is in the file.

    Click on the little down arrow on the toolbar and select this item:

    That will ignore the display=no setting in the .xml file.

    Regards,

    John

  • Thank you very much! This solved the problem more or less.
    But it would be interesting to know why small areas are hidden and if the threshold can be modified.

    Regards,
    Dominik
  • Looks like the history on this is the feature was originally done for MSP430. On MSP430 each interrupt has its own tiny Memory area. To keep the view from being overly cluttered the code that generates that xml checks for the memory area size and only sets it to display if it is greater than 100.

    I agree that this is confusing for non-MSP430 devices.