SPRADJ0 February   2025 AM2612 , AM2631 , AM2632 , AM2634 , AM263P2 , AM263P4 , AM2732 , AM2732-Q1 , AM620-Q1 , AM623 , AM625 , AM625-Q1 , AM62A3 , AM62A3-Q1 , AM62A7 , AM62A7-Q1 , AM62D-Q1 , AM62P , AM62P-Q1 , AM67 , AM68A , AM69A , DRA821U , TDA4AEN-Q1 , TDA4AH-Q1 , TDA4AL-Q1 , TDA4AP-Q1 , TDA4VE-Q1 , TDA4VEN-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VM , TDA4VP-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 Configurator
  5. 2Software Stack
    1. 2.1 Configurator Plug-in
    2. 2.2 Source Files
    3. 2.3 User Guide
    4. 2.4 Compliance Support Package (CSP)
  6. 3Utilizing the Source - Building Drivers and Examples
    1. 3.1 One-Time Setup
    2. 3.2 Build Instructions
    3. 3.3 Build Command Syntax
  7. 4Obtaining an MCAL package
  8. 5Summary
  9. 6References

One-Time Setup

The Code Composer Studio™ integrated development environment (IDE) and TI Arm® code generation tools (CGT) - compiler Build Dependency tools must be installed on the system used to build the MCAL source. Make sure the paths to these tools are correct under the build/Rules.make file under the TI MCAL package. Edit the relevant paths for these tool directories and other derived applications. Use the exact dependency version in use under the original Rules.make contents. The recommended versions can also be cross-checked from the user guide and release notes to make sure that the versions are compatible with the bundle version that was received.