SPRUIW9C October 2021 – March 2024 TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1
To migrate an existing application that is configured to run from RAM to a Flash-based linker configuration, follow these steps:
device_support\<device>\common\cmd
directory.BEGIN
in TI-provided Flash linker
command files) at the end of boot code execution. Make sure there is a
branch instruction at the Flash entry point to your code initialization (for
example, _c_int00
) function. In the C2000Ware examples, the
entry point code is specified in the codestartbranch.asm
file.Flash_initModule()
driverlib function achieves these
steps. Note that code that initializes the Flash module must execute from a
RAM location. This is accomplished by assigning the Flash initialization
function to the .TI.ramfunc
section. In the linker command
file, map this section to Flash for load, and RAM for execution. The example
cmd files provided in C2000Ware show how to do this correctly..TI.ramfunc
section in the TI-provided Flash linker
command files accomplishes this purpose.ALIGN
directive in the linker command file.type=NOINIT
") in the linker command
file.