SLAU131V October 2004 – February 2020
An Application Binary Interface (ABI) defines the low level interface between object files, and between an executable and its execution environment. The ABI exists to allow ABI-compliant object code to link together, regardless of its source, and allows the resulting executable to run on any system that supports that ABI. See the MSP430 Optimizing C/C++ Compiler User's Guide (SLAU132) and The MSP430 Embedded Application Binary Interface Application Report (SLAA534) for information on the EABI ABI.
COFF object files are not supported in v15.6.0.STS and later versions of the TI Code Generation Tools. If you would like to produce COFF output files, please use v4.4 of the MSP430 Code Generation Tools and refer to SLAU131J for documentation.
All object files in an EABI application must be built for EABI. The linker detects situations where object modules conform to different ABIs and generates an error.
Note that converting an assembly file from the COFF API to EABI requires some changes to the assembly code.