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.
Hi,
We have a post in the MSP low-power microcontroller forum about the Memory Allocation View reporting one size, and some of our other tools like MSP-GANG and Fet-Pro430 reporting another code size. They noted that the difference for their MSP430F5529 code was 46 bytes. Here is a link to the thread http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/531320/1933720#1933720
I noticed that on F5529, the interrupt vector table (IVT) is 46 bytes long - this makes me suspect that maybe the Memory Allocation View is not including the IVT in its size calculation. Indeed, the IVT is not in the "FLASH" section but has its own INT00 etc sections in the linker command file.
Does the Memory Allocation View calculate off of the .map file data, rather than the actual generated TI-txt file? If so, it looks like it does not display the IVT sections, so therefore a customer cannot simply sum together all the sections to see the total Flash used. Could this be an enhancement to the tool - to say how much IVT space is used in these sections?
Regards,
Katie
Using CCS 6.1.3, found that if you open the View menu (the white triangle) on the Memory Allocation view, and then use Show -> All Ranges then the interrupt vectors are shown:Katie Pier said:If so, it looks like it does not display the IVT sections, so therefore a customer cannot simply sum together all the sections to see the total Flash used.
Also, the view menu Show -> Filters can be used to change which sections are displayed.
The Default range filters doesn't show the interrupt vectors.
The Memory Allocation view processes the linkInfo.xml file generated by the linker, rather than the .map file.Katie Pier said:Does the Memory Allocation View calculate off of the .map file data, rather than the actual generated TI-txt file?