Hi Earl
Thank you for your reply, I thought that was the case but hoped there was a work around. Yes I could force something there, is there a way to make the linker use this area automatically as an extension of the "m_text" memory? I tried the following and other options which seemed logical but the linker did not like them.
/* Specify the memory areas */
MEMORY
{
m_interrupts (RX) : ORIGIN = 0x00000000, LENGTH = 0x00000200
m_text (RX) : ORIGIN = 0x00000200, LENGTH = 0x00000200 <ADDED
m_flash_config (RX) : ORIGIN = 0x00000400, LENGTH = 0x00000010
m_text2 (RX) : ORIGIN = 0x00000410, LENGTH = 0x0001FBF0
m_data (RW) : ORIGIN = 0x1FFFE000, LENGTH = 0x00008000
}
/* The program code and other data goes into internal flash */
.text :
{
. = ALIGN(4);
*(.text) /* .text sections (code) */
*(.text*) /* .text* sections (code) */
*(.rodata) /* .rodata sections (constants, strings, etc.) */
*(.rodata*) /* .rodata* sections (constants, strings, etc.) */
*(.glue_7) /* glue arm to thumb code */
*(.glue_7t) /* glue thumb to arm code */
*(.eh_frame)
KEEP (*(.init))
KEEP (*(.fini))
. = ALIGN(4);
} > m_text
It reads like the linker can concatenate ".text" sections.
Thanks again
Dave
