TI C28x to c29clang Migration Guide¶

This Migration Guide addresses tasks required and issues encountered when porting your existing TI C28x (cl2000) application to c29clang.

The following components of a TI C28x application need modification when migrating to c29clang:

CCS project (see Migrating cl2000 CCS Projects to c29clang)
Build options (see Migrating Command-Line Options)
C/C++ source code for cl2000 compiler (see Migrating C and C++ Source Code)
C/C++ source code for CLA compiler (see Migrating CLA Code)
Linker command file (see Migrating Linker Command Files for Use With c29clang)
TI C28x assembly code (see Migrating Assembly Language Source Code)

Note

COFF to EABI Migration: Only EABI output is supported for TI C29x. If your TI C28x application has COFF output files, you should first migrate from TI C28x COFF output to TI C28x EABI output before migrating to TI C29x. For information, see C2000 Migration from COFF to EABI.

The following migration aids can help you address issues when converting an existing cl2000 project to use the c29clang compiler:

Clang-Tidy Tool: The c29clang-tidy tool diagnoses changes that need to be made to application code in order to migrate it from TI C28x to c29clang. The c29clang-tidy tool is a clang-based utility for diagnosing and fixing issues in a C/C++ application. It can be run from the command line or from within CCS. For more about using c29clang-tidy, see Migrating Source Code with Clang-Tidy.
C/C++ Source Code Diagnostics: The c29clang compiler diagnostics can help you find proprietary TI pre-defined macro symbols, pragmas, and intrinsics that need to be converted. For more information, see C/C++ Source Migration Aid Diagnostics.
CCS Project Migration: For help converting the build options for an existing cl2000 CCS project to use the c29clang compiler, see Migrating cl2000 CCS Projects to c29clang.

Contents: