Code in tightly coupled memory

I guess that ALT_LOAD_SECTION_BY_NAME(tc_code) copies the code from where ever the normal loader put it into the M9K block.

Whether this is necessary depends on how the program image was linked, and how it was loaded.

The JTAG loader reads the elf program headers - so can write into multiple disjoint areas - in which case no copy is required (if the program headers are 'correct').

In other cases, a more simple loader might have written the code somewhere else - so the copy is needed.

Putting code (and data) in tightly coupled memory areas gives the same access times as if the data were resident in the instruction/data cache.