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.
Part Number: MSP430FR5992
Customer will stay with MSP430 GCC and wants to know:
With the "large" memory model for data and code (option -mlarge) the code will be about 20% larger than the "small" memory model (option -msmall).
This is unusable for us.
With a "large" memory model only for code, and "small" model for data, the code would be about 5% larger. This is acceptable.
Is there an option to have "large" model for code and "small" model for data ?
If no, is it planned to have such possibility in the near future ?
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Clemens Ladisch:
According to the latest MSP430 GCC Users Guide www.ti.com/lit/SLAU646 we support that
Whom can I contact?
In reply to BO:
Clemens, meanwhile I found the TI-internal supporter. But anyway thank you for the hint with www.somniumtech.com/news/somnium-partner-texas-instruments Regards, Bernd
I apologize for the delay. I can confirm the following is correct ...
Clemens LadischGCC has nothing but the "-msmall" and "-mlarge" options. The msp430 target code makes no effort whatsoever to distinguish between code and data accesses.
Documentation on the entire GCC compiler (all targets it supports!) can be found at https://gcc.gnu.org/onlinedocs/ . Search it for the section titled MSP430 Options. The only options related to memory model are -mshort and -mlarge. The description of these options is very short. To see what they do, build an example source file and inspect it like this ...
% ofd430 --obj_display=none,battrs file.o
OBJECT FILE: file.o
Build Attributes in ".MSP430.attributes"
Format Version: 'A'
<0> Vendor Name: "mspabi" (ABI for the Texas Instruments MSP430 Architecture)
Tag_ISA 2 (MSPX)
Tag_Code_Model 1 (small code)
Tag_Data_Model 1 (small data)
The utility ofd430 is from the TI compiler toolset. But you can use it on object files built with the GCC compiler. You will see that all you can get are small code and small data, or large code and large data. No other combinations are supported. The TI compiler supports several other combinations and variations.
The GCC MSP430 compiler is in maintenance only mode. No new work is planned.
Thanks and regards,
TI C/C++ Compiler Forum ModeratorPlease click This Resolved My Issue on the best reply to your questionThe CCS Youtube Channel has short how-to videosThe Compiler Wiki answers most common questionsTrack an issue with SDOWP. Enter your bug id in the Search box.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.