CCS V.4.21 producer bigger code than CCS 3.1?

Karlheinz Rieber

I am currently evaluating CCS V4.2.1.

For this I imported an existing project which was made some time ago with CCS V3.1. I rebuild all, however the linker outputs that the section .econst does not fit into the flash memory of the used F2812. However that is possible with CCS V3.1. The code generation tools are 4.14 (V3.1) and 5.29 (V4.2.1).

The project settings seems the same, I have not changed them after the project import. I do not assume that the new code generation tools are less efficient, maybe the project settings need some change. The optimisation level is set to 3 in both cases.

Any ideas are welcome ;-)

over 14 years ago

0 AartiG over 14 years ago

TI__Guru**** 173310 points

I would suggest comparing the link map files generated by the two versions and see which sections are differing enough in size to cause the sections to no longer fit in the available memory. If the memory allocation was already tight in the earlier build, then even if some section sizes increased with the newer version of codegen tools you could run into alocation issues.

Do you already have the the --opt_for_space option enabled? If not, you may want to give that a try to see if it helps reduce code size further. The option is documented in the C28x Compiler Users Guide.

0 Karlheinz Rieber over 14 years ago in reply to AartiG

Prodigy 60 points

Thanks for the reply Aarti,

the linker says:

object ".econst", size 0x940c (page 0). Available ranges:

FLASH size: 0x1ff80 unused: 0x87ae max hole: 0x8782

The code is tight, just fitted into the FLASH section before. There is -O3 set in the project settings, I think it is the same as --opt you mentioned. Is there another chance to reduce code size?