[quote user="Chester Gillon"]E.g. changes the linker command file for a MSP430FR6989 to cause the div16u.obj and mult32_f5hw.obj object files in the rts430x_lc_rd_eabi.lib (large code, restricted data) run time library to be moved to RAM: #ifdef __TI_COMPILER_VERSION__ #if __TI_COMPILER_VERSION__ >= 15009000 ram_funcs { *(.TI.ramfunc) rts430x_lc_rd_eabi.lib (.text) rts430x_lc_rd_eabi.lib (.text) #ifndef __LARGE_DATA_MODEL__ } load=FLASH, run=RAM, table(BINIT) #else } load=FRAM | FRAM2, run=RAM, table(BINIT) #endif #endif #endif [/quote]With that linker command file modification had to disable the Memory Protection Unit in the project settings, to avoid getting the following linker errors about undefined symbols related to the MPU: undefined first referenced symbol in file --------- ---------------- MPUSEG C:/ti_ccs6_1_3/ccsv6/tools/compiler/msp430_15.12.2.LTS/lib/rts430x_lc_rd_eabi.lib __mpusam C:/ti_ccs6_1_3/ccsv6/tools/compiler/msp430_15.12.2.LTS/lib/rts430x_lc_rd_eabi.lib __mpuseg C:/ti_ccs6_1_3/ccsv6/tools/compiler/msp430_15.12.2.LTS/lib/rts430x_lc_rd_eabi.lib For some reason, specifying the complete run time library name for the functions to be placed in RAM was causing the linker to use the generic __mpu_init function from the compiler rts430x_lc_rd_eabi.lib library to be used, rather than the MSP430FR69xx specific CCS ccsv6\ccs_base\msp430\lib\FR59xx\MSPMPU_INIT_LIB_CCS_msp430_large_code_restricted_data.lib By changing the linker command file to not refer to a specific run time library for the functions to place in RAM found could then leave the MPU enabled in the project settings: #ifdef __TI_COMPILER_VERSION__ #if __TI_COMPILER_VERSION__ >= 15009000 ram_funcs { *(.TI.ramfunc) rts430*.lib (.text) rts430*.lib (.text) #ifndef __LARGE_DATA_MODEL__ } load=FLASH, run=RAM, table(BINIT) #else } load=FRAM | FRAM2, run=RAM, table(BINIT) #endif #endif #endif The updated project is attached. (Please visit the site to view this file)
↧