SLAU132V 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. An ABI allows ABI-compliant object files to be linked together, regardless of their source, and allows the resulting executable to run on any system that supports that ABI.
Object files conforming to different ABIs cannot be linked together. The linker detects this situation and generates an error.
The MSP430 compiler now supports only the Embedded Application Binary Interface (EABI) ABI, which uses the ELF object format and the DWARF debug format. If you want support for the legacy COFF ABI, please use the MSP430 v4.4 Code Generation Tools and refer to SLAU132J and SLAU131J for documentation.
All code in an EABI application must be built for EABI. Make sure all your libraries are available in EABI mode before migrating COFF ABI systems to MSP430 EABI.
For more details on the ABI, see Section 5.14.