| Newsgroups |
gmane.comp.hardware.texas-instruments.msp430.discuss |
| Organization |
Infinite Factors |
| Message-ID |
<[email protected]> |
On Fri, 5 Feb 2016 10:01:50 -0800, you wrote:
>yes, all outputs are in hex.
Then what about David's comment about the fact that the F235
has 0x4000 bytes of flash and the reported figure for .text
is then 0x5654? (I'd assumed it was decimal; my mistake.)
>The program actually is about 13K in debug mode.
I won't doubt your figure, but the line you reported does
say:
.text 0 00000000 00005654 FAILED TO ALLOCATE
Which, ignorant as I am about your tools, would seem to
differ with your above comment about it being actually 13K.
>Bear in mind this is a production load, I just upgraded the
>tools...works fine with CCSv5.
I believe you and I think you made that clear, earlier.
>I have a call in to TI, just thought
>someone might have done the same thing as I did and discovered the
>problem/fix.
Okay. But don't rely on that in order to move forward. You
need to own the solution here, regardless. If you want to use
the newer tools. Keep in mind that .text includes a number of
other segments, the sizes of which you also haven't
mentioned. What I'd like to see is the memory map/segment
sizes for each of them in CCSv5 and also your later version.
I have to say I remain confused about your comment that the
program is 13K in debug mode -- unless you are talking here
about the CCSv5 case, in which case it would suggest that the
newer version is generating a larger size given your reported
error line.
>I will update the group once I have a chance to chat to TI...
I'll be interested in what you do find out. Thanks for
considering an update, here.
Jon
------------------------------------
Posted by: Jon Kirwan <[email protected]>
------------------------------------
To unsubscribe from the msp430 group, send an email to:
[email protected]