Because of this line in your linker command file ...
.text : {}>> FLASH | FLASH2 /* CODE */ The .text section may be split across the FLASH and FLASH2 memory ranges. If you want more details on section splitting, please see this application note.
[quote user="Stephen Phillips1"]I have an ISR (function?) routine that is in the memory area called FLASH does it make sense for that to call a function that is in the .text section (so that it can be anywhere in memory) or just leave the .text:_isr section to itself (I doubt I will have need of greater than 0xBB80 in size for ISR execution just a suspicion),. I was wondering if it would "make sense" to do that or just leave the ISRs too their own FLASH memory.[/quote]
The link command file has this line ...
.text:_isr : {} > FLASH /* ISR CODE SPACE */ The effect is that the _isr subsection of .text is allocated to the FLASH memory range. No part of it will ever go to FLASH2. I do not know why the isr routines are set aside the like this. I recommend you ask in the MSP430 forum about that.
[quote user="Stephen Phillips1"]I was looking for the syntax information for the link command files, I found a lot of examples but ... no syntax let alone BNF diagrams (hehe).[/quote]
The best information is in the linker chapter of the Assembly Language Tools manual you have already found in CCS. You can also find it online here.
[quote user="Stephen Phillips1"]The help seemed a little messed up[/quote]
I'd appreciate if you would post a screen shot of that.
Thanks and regards,
-George