Compiler/TMS320C6713: Linker script defined sections in output .hex file

kowalski

Part Number: TMS320C6713

Tool/software: TI C/C++ Compiler

Hi,

Let say i write a linker script to define different sections (.data, .bss, .txt), and compile it into .hex file using Code Composer studio.

a) How linker actually maps these sections in output .hex file (not a.out file, as .out can't be burn to flash.), as according to https://en.wikipedia.org/wiki/Intel_HEX, there is no sections defined inside .hex file neither there is a header to describe header sections. so why even we write these sections in linker script if they are not gonna appear in output .hex file??? Am i missing something???

b) second, if this output file is burn to some flash memory and processor like tms320c6713 is boot from this flash, how the processor gonna distinguish b/w these section even .hex doesn't contains any sections or

sections description???

Kindly correct me if i am wrong, any reference to understand these concepts will be highly appreciable.

Thanks in advance.

over 7 years ago

0 Keith Barkley over 7 years ago

Guru 35580 points

It is all done in code.

0 George Mock over 7 years ago

TI__Guru**** 232670 points

Once a program is loaded into the system, the organizing principle of the section is no longer present. Execution begins, and code and data begin interacting.

So it is with a hex file. A hex file has no concept of sections. A hex file is yet another way to represent the code and data that is loaded to the system.

Thanks and regards,

-George

Code Composer Studio™︎

Code Composer Studio forum

Compiler/TMS320C6713: Linker script defined sections in output .hex file