Other Parts Discussed in Thread: MSPWARE
Tool/software: Code Composer Studio
I have a question about the code size differences between debug and release builds.
I am using ccs 6.1.3 with 15.12.2.lts on 32 bit Linux. I am not using mspware or driverlib.
A few years ago I developed a small battery operated dredging depth calibration
unit based on a f4783 mcu. Now I have a few units back for upgrade purposes and
I wanted to remotely control IO lines, and more, that control the inner workings of the unit.
So I implemented a command interpreter which I first tested on a fr6989 launchpad.
The Flash and RAM code size of the debug and release builds are respectively :
13596 - 900
9584 - 900
So well within the available memory size of the f4783. But when I try to run a debug
session the RAM size grows to 2464 bytes :
MSP430: Loading complete. There were 13596 (code) and 32 (data) bytes written
to FLASH/FRAM. The expected RAM usage is 2464 (uninitialized data + stack) bytes.
The stack and heap are set to 80 bytes both.
The .map file also shows 900 bytes RAM (maybe the "memory allocation" window
gets it's info from there ?).
I know and understand that debugging functionality adds some code. What I do
not understand is why there is no error on the code size exceeding the limit of
the f4783 or is there no such check ?
Is there a way to know for sure how much code gets added to the debug size ?
(other then subtracting the reported code sizes)
The problem now with my program is that the previous command entered is the one
that gets executed when entering the next command.
I have not found out yet if things are related.