topic Re: How to check the code size and memory use in codewarrior V10.3 in CodeWarrior for MCU

How to check the code size and memory use in codewarrior V10.3

pengliang — Fri, 02 Nov 2012 20:43:26 GMT

Hi all,

I am using PE to generate the code for module that I used. Looks like there is lots of code. I want to see how much the code size and data memory usage. How can I do in codewarrior? I just could not find it.

Please guide me

Thanks in advance.

Re: How to check the code size and memory use in codewarrior V10.3

CrasyCat — Mon, 05 Nov 2012 06:58:09 GMT

Hello

Here I would make sure a .map file is generated and I would check the application code and data size in there.

The way map file generation is enabled and information are stored depends on the MCU you are targeting.

Which MCU are you targeting (HC08, Coldfire, Kinetis, ...)?

CrasyCat

Re: How to check the code size and memory use in codewarrior V10.3

pengliang — Mon, 05 Nov 2012 13:23:35 GMT

I am using Kinetis L series KL25Z.

I looked at .map file. but How would I know the flash memory size and data memory size has been used. How to read it?

Thank you

Re: How to check the code size and memory use in codewarrior V10.3

CrasyCat — Mon, 05 Nov 2012 15:10:04 GMT

Hello

Look in your .map file for a section called "Memory Configuration".

If you are using the default linker file you should see at least following memory areas with their start address and size:

m_interrupts: Contains the vector table.

m_text: Contains the application code

m_data: Contains the application data

The size of m_text represents the application code size and the size for m_data represents the application data size.

If you defined additional memory areas in the linker file (*.ld) you may have to consider the additional memory areas as well.

CrasyCat

Re: How to check the code size and memory use in codewarrior V10.3

pengliang — Mon, 05 Nov 2012 15:35:47 GMT

This is what I see in .map file

Memory Configuration

Name Origin Length Attributes

m_interrupts 0x00000000 0x000000c0 xr

m_text 0x00000410 0x0001fbf0 xr

m_data_1FFFF000 0x1ffff000 0x00001000 rw

m_data 0x20000000 0x00003000 rw

m_cfmprotrom 0x00000400 0x00000010 xr

*default* 0x00000000 0xffffffff

Then, m_text length is 1fbf0 which is 130032 byte? the application code is already 130k byte? this is not possible. the application just do some very simple LED toggling. Am I wrong to calculate the application code size?

Please correct me

Thank you

Re: How to check the code size and memory use in codewarrior V10.3

pengliang — Mon, 05 Nov 2012 18:06:19 GMT

Hi CrasyCat,

Thank you. I figured out how to check the memory size. Thank you firstly.

And also, my application code is taking 4500 byte. However, in my application, I only toggling LEDs. why it takes that much program memory. btw, I am using PE to generate drivers. Is there a better way to minimize the program flash size?

Thank you

Re: How to check the code size and memory use in codewarrior V10.3

BlackNight — Mon, 05 Nov 2012 19:14:01 GMT

There is an easy way to dump the code and data size to the console view, see

Code Size Information with gcc for ARM/Kinetis | MCU on Eclipse

As for reducing the code size: by default optimizations are switched off. Enabling compiler and linker optimizations should greatly reduce your footprint. See Tutorial: Freedom with FreeRTOS and Kinetis-L | MCU on Eclipse

which shows how to have an application *with* an RTOS toggling LEDs on a KL25Z can be done with 5 KByte of Flash and 1 KByte of RAM.

Hope this helps,

Erich

Re: How to check the code size and memory use in codewarrior V10.3

pengliang — Mon, 05 Nov 2012 19:28:06 GMT

Thank you for replying.

BTW, do you think 5KB of FLASH for just toggling LEDs is too big?

Re: How to check the code size and memory use in codewarrior V10.3

BlackNight — Tue, 06 Nov 2012 05:27:12 GMT

My RGB 'toggling' LED application comes with waiting routines and Processor Expert LED drivers and full blown startup code. And even with that luxury load, it only takes 3 KByte:

"C:/Freescale/CW MCU v10.3/arm-none-eabi-gcc-4_6_2/bin/arm-none-eabi-size" --format=berkeley Freedom_LED.elf

text data bss dec hex filename

3252 40 1068 4360 1108 Freedom_LED.elf

Stripping off startup code and more would get it well below the above size. What you need at the minimum is the vector table plus just the toggling code, then you get below 1 K for sure. But then it would not be suitable for anything advanced.

Re: How to check the code size and memory use in codewarrior V10.3

pengliang — Tue, 06 Nov 2012 19:38:46 GMT

what if not use PE? it seems PE generated code that taken most of memory size,.

Re: How to check the code size and memory use in codewarrior V10.3

BlackNight — Fri, 09 Nov 2012 09:54:09 GMT

Hi Peng,

it is not PE. It is the startup code and linker settings which adds to the size. I'll see if I can come up with some suggestions how to strip that down to around 400-800 bytes total. But what you can do right away:

There is a linker symbol defined which I think makes sense in the context of using an UART with printf(). But if you are not using this, then you get the startup code down to around 800 bytes (so 2 K less):

go to the linker options, and here remove the two lines marked in yellow below:

Hope this helps,

Erich

Re: How to check the code size and memory use in codewarrior V10.3

pengliang — Fri, 09 Nov 2012 14:11:53 GMT

Erich,

Thank you for helping me to shrink code size. I would try it. but if I remove these two lines, would it affect my code? or give compile error? I am not quite sure what do that two lines do. Does it just do printf() using UART?

Re: How to check the code size and memory use in codewarrior V10.3

BlackNight — Fri, 09 Nov 2012 16:21:52 GMT

Peng,

yes, as long as you are not using these formatter/sprintf() (I think?) things, you can remove it. The linker will complain otherwise, then you can re-add the lines. So safe to remove them.

Erich

Re: How to check the code size and memory use in codewarrior V10.3

pengliang — Fri, 09 Nov 2012 17:02:05 GMT

Great, Thank you very much

Re: How to check the code size and memory use in codewarrior V10.3

BlackNight — Sun, 11 Nov 2012 12:52:31 GMT

In any case: I played a little bit with the settings, and have put some details and background information in this post: Optimizing the Kinetis gcc Startup | MCU on Eclipse

Erich

Re: How to check the code size and memory use in codewarrior V10.3

pengliang — Mon, 12 Nov 2012 13:04:44 GMT

Erich, that is good stuff. Thank you

Re: How to check the code size and memory use in codewarrior V10.3

danielbronson — Mon, 18 May 2015 18:45:12 GMT

If I see this for my Memory Map:

# Memory map:

v_addr p_addr size name

0000C000 0000C000 00000000 .x_Peripherals

00000000 00000000 000000DE .interrupt_vectors .p_Interrupts

00000208 00000208 00004E6C .ApplicationCode .p_Code

00000000 00000000 00000F30 .ApplicationData .x_Data

00000F30 00000F30 00000000 .WIRData .x_Data

00000200 00000200 00000008 .reserved_FCF .p_reserved_FCF

00005074 00000000 000003D8 .data_in_p_flash_ROM .p_flash_ROM_data

00008000 00008000 00004000 .x_internal_ROM

00060000 00060000 00000F41 .ApplicationCodeInRAM .p_internal_RAM

How can I tell how much Flash Memory and RAM I am using?

Thanks for any and all help!

Re: How to check the code size and memory use in codewarrior V10.3

carloszamora — Wed, 01 Jul 2015 19:11:44 GMT

Where/How can I find the .map file? I'm using CodeWarrior and K70. I've been searching for the file location and how to generate it but I have no idea.

Re: How to check the code size and memory use in codewarrior V10.3

BlackNight — Thu, 02 Jul 2015 05:07:14 GMT

Hi Carlos,

the map file is usually where the .elf (application) file is generated. Check the 'Release' or 'Debug' folder in your project.

Erich

Re: How to check the code size and memory use in codewarrior V10.3

carloszamora — Mon, 06 Jul 2015 13:58:05 GMT

For some reason, I can't find either of those folders.The .elf file is also missing. Is there a specific way to generate all of that? I'm currently working on the "hello peg" project for the K70.