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.
Hello Community and TI,
right now I did switch my CCS from version 5.1 to a newer version 5.5.
Guess what, TI dicided to switch their output format from COFF to ELF, so my old projects strangly dont compile anymore with a error message that not enough memory:
Description Resource Path Location Type
<a href="file:/D:/Texas%20Instruments/ccsv5/tools/compiler/dmed/HTML/10099.html">#10099-D</a> program will not fit into available memory. placement with alignment fails for section ".cinit" size 0x216 . Available memory ranges: lnk_msp430f5437a.cmd /my filexxxxxxxxxxxxxxxxx line 148 C/C++ Problem
Any ideas about that?
I do understand that TI wanted to get from their own COFF file format to the more standardized ELF file format, but this shouldnt happen on my cost :)
As I understood, COFF and ELF use different interpretations for int, long, float and so on, so perhaps some number formats also are corrupted, can that be?
So what do you recommend, stick to old code composer for my old projects, or migrate everything to the new version and manually put COFF output format instead of ELF.
In the end all that counts is, that my projects can still be programmed on our products, because without programming there is no selling and then there will not be any buying of CodeComposerStudio, a vicious circle.
Best regards,
Seb
Also, what does your this window indicate:
If it indicates elf then try changing it to COFF. As you mentioned above, yes both have different Information Format and hence the .out file size would vary. Just try manually modifying the same to COFF and let us know what you observe.
FYI: http://processors.wiki.ti.com/index.php/A_Brief_History_of_TI_Object_File_Formats
Regards,
Gautam
Hmm ok thanks again, but as I stated above I already know i can switch and it works, but I do not understand exactly why TI did it what is better to manually change it with CCS 5.5 or to still use CCS 5.1 for my old projects in acutal products of ours.
The wiki i already read, thanks anyway.
seb said:but I do not understand exactly why TI did it what is better to manually change it with CCS 5.5 or to still use CCS 5.1 for my old projects in acutal products of ours.
I get it, Seb :)
I'm forwarding your query to TI expert who can give you the answer for your "why".
Regards,
Gautam
seb said:but I do not understand exactly why TI did it what is better to manually change it with CCS 5.5 or to still use CCS 5.1 for my old projects in acutal products of ours.
ELF is more of a standard and more widely used than COFF, and also has several compelling features that are not there in COFF, a short summary of which is here. Hence most TI compilers currently default to the ELF format when creating new projects in CCS. As you noted, the COFF format is still supported.
If you have existing COFF projects that were created with an older version of CCS, you can simply import then into CCS 5.5 and still use the COFF format. Importing the project should not change its existing output format. If you create a new project in CCS 5.5, it will default to ELF, but you have the option of changing the format to COFF. So there is really no reason to stay with CCS 5.1 for old projects.
prithivi raj said:but why for programming any COFF projects take much more time for the CCS6.1.2??
This is a rather generic statement that is hard to comment on without more specifics.
Since this is a very old post that is already closed/answered, I would request you to kindly start a new post if you need specific support/assistance on this.