This list isn't really meant to cover CCE, but since I work on CCE and I'm here, I'll answer.
There might be DWARF2 symbol and debugging information in the .out file, for one, if you built them in. Also there is a certain amount of mandatory overhead for the COFF header, regardless of whether the executable is Debug or Release. ___________________________________________ Chris Recoskie Software Designer Texas Instruments, Toronto http://eclipse.org/cdt > -----Original Message----- > From: mspgcc-users-ad...@lists.sourceforge.net [mailto:mspgcc-users- > ad...@lists.sourceforge.net] On Behalf Of Kevin Schmeichel > Sent: Friday, October 21, 2005 2:02 PM > To: mspgcc-users@lists.sourceforge.net > Subject: [Mspgcc-users] TI CCE binary size > > > sorry for a newbie question, but I've noticed that when I build a binary > using the TI CCE IDE in Debug, I get a large binary file, say around 50k, > but > I'm able to flash and run the program on an msp with only 4k of flash (eg, > msp430F1121A). > > Can anyone tell me what's happening? how does it fit? and how can I > determine the "real" size of the binary (what actually gets loaded on the > flash) as opposed to the size of the .out file? > > thanks, > Kevin > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
