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.

where to find the code size in ccs v5

Other Parts Discussed in Thread: TM4C123GH6PGE

Good day, 

I want to determine the code size of my program in the flash memory of  EK-LM4F232 in code composer v5.

Where can I get this information.

Thanks,

  • Hi,

    You can find the static memory usage by inspecting the linker map file that is automatically generated inside the output directory (Debug or Release).

    From the project explorer, you can open the output directory and search for a file with extension .map. Among other info, it will show the device's memory regions and their usage.

    Hope this helps,

    Rafael

  • Hi, Thanks for this info.

    This has helped a lot.

  • Do you know which sections are counted toward the 16kB code size limit for the free version of CCS?

  • Brandon Gardner said:

    Do you know which sections are counted toward the 16kB code size limit for the free version of CCS?

    See response from this thread.

  • desouza said:

    You can find the static memory usage by inspecting the linker map file that is automatically generated inside the output directory (Debug or Release).

    Could CCS translate to decimal values in next release? (other tools do it)

    Or at least summarize main values in decimal.

  • CCSv6 (currently in Beta) has a view called 'Memory Allocation" view that summarizes the memory usage, and shows it in decimal values. This short video gives an overview.

  • I want to know how much flash memory of TM4C123GH6PGE in code composer v6 is utilised if,

    my .out file is of 326kb and actual flash is of 256kb, but .map file shows

    name origin length used unused
    FLASH 00000000 00040000 00006cd6 0003932a
    SRAM 20000000 00008000 00000bff 00007401

    is my code exceeds the flash? please provide me the information about this
  • sreelakshmi pemmaka said:
    my .out file is of 326kb and actual flash is of 256kb

    The .out file contains information which is not loaded into the flash memory of the target. e.g. the .out file can also contain symbolic debug information and therefore the size of the .out file isn't an indication of the flash usage.

    The .map file shows the program uses 0x6cd6 bytes out of the total of 0x40000 bytes of flash, which means only approx 11% of the flash size is used.

  • Hello All,

    I am facing a similar issue of memory maping and havent gone through it much. 

    Kindly support me with below query

    I am having below detail which I got it from .map file. 

    SRAM (RWX) : origin = 0x20000000, length = 0x0008000

    But my data memory is exiding 0x8000 so I am unable to flash the program.

    I have checked in memory allocation tab, SRAM memory I can use till 32kb.

    Can any one help me out to solve this issue??

    Thanks in advance.

    Mitesh

  • Hello All,

    I am using a code for interfacing graphical LCD and while interfacing I have given bitmaps value in header file. which is getting compiled. but as soon as i call those image in my while loop, my SRAM Memory is getting used. I dont know is there any point which I am missing with compiler or any thing?
  • Mitesh Sirodaria said:
    I am using a code for interfacing graphical LCD and while interfacing I have given bitmaps value in header file. which is getting compiled.

    If the bitmaps don't need to change at run time, then if bitmaps are declared as const the bitmaps should be placed in flash by the compiler / linker thus reducing the SRAM usage.

    How are the bitmaps defined in the header file?

  • This was directed to poster "Mitesh" - as addition to the sound advice advanced by Chester...

    Firm/I are not fans of (any) single vendor restricted IDE - thus we avoid CCS. (hard to imagine that ONE vendor - and only ONE vendor - will always (best) satisfy our needs!)

    We've enjoyed success w/in the display field - and never would store such image data w/in the (limited) MCU space. External memory - especially fast, modern, 4 bit, serial flash (perhaps even 2 such devices - yielding 8 bits) completely AVOID MCU memory overflow...

  • Hello Chester,

    I have added a new header file with bitmaps as const char but it still affects my SRAM Memory. If I don't call those variables(images) in my main function it reduces my memory but as soon as I add it in my main function, SRAM Memory usage gets increased. Although my header file is already added in the project.

    Hello CB1_mobile,

    I have been using it with PIC controller as well in which I am not facing issue. but while I am using the same with tiva it is creating the issue.

    I have hardly used 15 images in my display and for that it shows me SRAM Memory issue. For such small application is it necessary for adding external memory?

    Thanks for immediate Replies,
    Mitesh
  • Mitesh Sirodaria said:
    I have added a new header file with bitmaps as const char but it still affects my SRAM Memory. If I don't call those variables(images) in my main function it reduces my memory but as soon as I add it in my main function, SRAM Memory usage gets increased. Although my header file is already added in the project.

    Can you show your code, and the increase in SRAM memory usage?

  • Mitesh Sirodaria said:
    For such small application is it necessary for adding external memory?

    Will your applications "always" be so small?   If not - what then?   (a band-aid solution may not offer long-term comfort)

    Image & font data do not belong w/in limited MCU memory space unless the application is extremely high volume - which is unlikely to result for the vast majority - here...

    Your move to proper, external memory will insure that a proper solution is delivered now - and long into the future.   (when you are surely going to exceed limited capacity, MCU space.)   Further - it is likely that w/proper use of external storage - you may chose an MCU w/reduced memory size - reducing your cost...

  • I opened the .map file and found this :

    run origin load origin length init length attrs members
    ---------- ----------- ---------- ----------- ----- -------
    00000000 00000000 00005298 00005298 r-x
    00000000 00000000 0000026c 0000026c r-- .intvecs
    0000026c 0000026c 00004e14 00004e14 r-x .text
    00005080 00005080 0000019a 0000019a r-- .const
    00005220 00005220 00000078 00000078 r-- .cinit
    20000000 20000000 00000304 00000000 rw-
    20000000 20000000 00000200 00000000 rw- .stack
    20000200 20000200 000000a0 00000000 rw- .bss
    200002a0 200002a0 00000064 00000000 rw- .data

    Which of them Will be the Code Size