"Placement fails for object ".text" error message?

Hi Richard,

can you provide more details on the code your're using? Without details it is nearly impossible to help you since IAR supports some things which you need to change when using CCS (i.e. placing code/data at a fixed address).

Rgds
aBUGSworstnightmare 

I have the same problem, using Code Composer Studio Version 4.1.2.00027, the free version, and the MSP430G2231 that was included with the Launchpad development kit.  

I think that it is related to memory somehow.  I am displaying an image that I have created using a bitmap to binary converter on an LCD.  My LCD is 128 x 32 pixels, and when I make full screen pictures the files are 3.31 KB.  I can fit two of these into a header file, plus two smaller (20 x 16 pixels) pictures in the header file, and my code.  When I compile it works great, and the compiler informs me that 

"Code Size - Text: 912 bytes  Data: 1112 bytes"

When I try to load a very slightly larger image, 40 x 16 pixels, it gives me this error: 

Severity and Description Path Resource Location Creation Time Id

placement fails for object ".text", size 0x390 (page 0).  Available ranges: FLASH        size: 0x7e0        unused: 0x368        max hole: 0x368 prototype1 line 0 1302129359254 1127

Doug Jorgesen said:

My question is: Do I need to buy a chip with more memory, or do I need to buy an actual license to CCS to access more memory?  Or do I need to do both?

You'll need a chip with more flash.  The MSP430G2231 has only 2KB of flash.  The free version of CCS apparently lets you go up to 16KB, which seems like plenty for you.

Jeff

Thanks, I'll try out the MSP430F235 and see how it goes.

If you want to see how much of the flash your program uses please enable .map file generation

Project|properties|C/C++Build|MSP430Linker|Basic Options "Input and output sections listed into <file>

Inside the file you will see space occupied for each section, e.g.:

MEMORY CONFIGURATION
           name         origin   length    used   unused  attr   fill
---------------------- -------- -------- -------- -------- ---- --------
SFR                    00000000 00000010 00000000 00000010 RWIX
PERIPHERALS_8BIT       00000010 000000f0 00000000 000000f0 RWIX
PERIPHERALS_16BIT      00000100 00000100 00000000 00000100 RWIX
INFOD                  00001800 00000080 00000000 00000080 RWIX
INFOC                  00001880 00000080 00000000 00000080 RWIX
INFOB                  00001900 00000080 00000000 00000080 RWIX
INFOA                  00001980 00000080 00000000 00000080 RWIX
RAM                    00001c00 00004000 0000158e 00002a72 RWIX
FLASH                  00005c00 0000a380 00001c02 0000877e RWIX

Regards,
Piotr Romaniuk, Ph.D.
ELESOFTROM

Richard Cooke said:

  I'm using the latest version of Code Composer (V4.1.1.00014) and my target is a MSP430F2001.  This program compiled just fine on IAR Kickstart.

If you are able to compile it by IAR, it may be a case of compiler options.
Please try set optimization for size:

Project|Properties|C/C++Build|MSP430Compiler|BasicOptions

Control speed vs. size trade-offs (0-size, 5-speed).

Regards,
Piotr Romaniuk, Ph.D.
ELESOFTROM

Thanks for the details, I didn't know about that option Piotr.  

That raises another question: when I give the compiler a list of bytes like I have in my program to store as a const, does it store them in bytes or words?  

In other words, would I double my memory by rewriting the variables as words and adjusting my program accordingly?

No, the compiler stores them as bytes because you declared the "type" of the array to be unsigned char.  You wouldn't be able to gain any memory efficiency by storing your data as words.

Jeff