AM263P4: tmu operations example: understanding how sections are mapped to TCMx regions without using linker.cmd

Part Number: AM263P4
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Running tmu_operations_am263px-cc_r5ss0-0_nortos_ti-arm-clang example successfully.

The example maps .testData and .trigData to R5F_TCMA and also .trigTest to R5F_TCMB but

  • there are no entries in the .sysconfig sections. 
  • the 3 mentioned sections are not in the generated linker.cmd.

During build, there is even a warning:

Yet, after the build, it is linked to the proper R5F_TCMA and R5F_TCMB regions.

Can you please help explain, how this happens?  Thanks.

  • Hi Huey.

    I was able to reproduce the same behavior from my end, as the sections are not defined in the syscfg sections the generated linker.cmd won't specify them explicitly. It looks like the compiler is assigning memory regions based on availability to these sections although ideally these will have to be defined in the syscfg itself. We will pick this up and fix this in the next release.

    Thanks,

    Aswathy