Tool/software:
Where does CCS place the binary image files after building?
I found ".out" files but they don't seem to be just the images, since they are huge (260+ KB) compared to the flash size. Are these ELF files or some other format?
Tool/software:
Where does CCS place the binary image files after building?
I found ".out" files but they don't seem to be just the images, since they are huge (260+ KB) compared to the flash size. Are these ELF files or some other format?
The *.out file generated by CCS projects typically consists of the target binary code that is to be loaded and executed on the target and also the associated DWARF debug symbols to be loaded to the CCS debugger to provide source level debug visibility. When the *.out file is loaded to CCS, the CCS debugger would read the information in the file to know which part of the file is code to be loaded to the target and where in target memory it needs to be loaded and then load it there. Then the rest of the debug symbols would be loaded to the CCS debugger to be used for source level debug.
The *.out file is typically ELF format though other formats were used in the past.
https://software-dl.ti.com/ccs/esd/documents/sdto_cgt_A-Brief-History-of-TI-Object-File-Formats.html
Thanks
ki
Hi Ki,
How would we generate just the binary image that we can load onto flash? The ELF format is useful for debug probes, but our OTA will have to load images without using the probe.
Nick
There are utilities part of the compiler package that can generate a hex/binary from the *.out file. It is these hex/binary files that are used for flashing in a production environment. This utility is often integrated with CCS properties (see "Hex Utility"):