SPRAD20 March   2022 AM2631 , AM2631-Q1 , AM2632 , AM2632-Q1 , AM2634 , AM2634-Q1

 

  1.   Trademarks
  2. 1Introduction
  3. 2A Step-by-Step Guide to Running a Traction Inverter
    1. 2.1 Create Real Time Debug Interface
      1. 2.1.1 Confirm CCS Features
      2. 2.1.2 Create Target Configuration File
      3. 2.1.3 Add Serial Command Monitor Software
      4. 2.1.4 Launch Real Time Debug
    2. 2.2 Configure Control Peripheral and ADC Interrupt With Sysconfig
      1. 2.2.1 Generate PWM for Time Reference
      2. 2.2.2 Synchronize ADC Sampling and Interrupt Service Routine
      3. 2.2.3 Configure DMA for Resolver Excitation via DAC
    3. 2.3 Configure Gate Driver Interface With MSPI
      1. 2.3.1 Confirm Control Card Hardware Configuration for Gate Drivers
      2. 2.3.2 Configure MCSPI for UCC5870 Gate Drivers
      3. 2.3.3 Initialize UCC5870 Gate Drivers
    4. 2.4 Get Samples From ADC and Read Samples Via CCS
      1. 2.4.1 Register and Enable Interrupt
      2. 2.4.2 Add Log Code to Read Samples in Graph at Fixed Rate
      3. 2.4.3 Read ADC Samples in Expression and Graph Windows
    5. 2.5 Generate Space Vector PWM and Drive Motor in Open Loop
      1. 2.5.1 Setup SVPWM Generator Inputs
      2. 2.5.2 Read SVPWM Duty Cycles in Graph Window
      3. 2.5.3 Power Up Inverter and Spin Motor in Open Loop
    6. 2.6 Close Current Loop With Mock Speed
      1. 2.6.1 Add Transformations and Read Id-Iq in Open Loop
      2. 2.6.2 Add Controllers to Close Current Loop
      3. 2.6.3 Read Id-Iq to Close Current Loop
    7. 2.7 Add Software Resolver to Digital Converter
      1. 2.7.1 Generate Excitation for Resolver Hardware
      2. 2.7.2 Add Resolver Software
      3. 2.7.3 Read Resolver Software Outputs
    8. 2.8 Close Speed Loop With Rotor Speed
      1. 2.8.1 Add Speed Loop Controllers
      2. 2.8.2 Add Speed Loop Demo Program
      3. 2.8.3 Read Motor Speed from Graph Window
  4. 3A Brief Guide to Code Migration
    1. 3.1 SoC Architecture Overview
    2. 3.2 SDK Resources Overview
    3. 3.3 Code Migration From AM24
    4. 3.4 Code Migration From C28
  5. 4Summary
  6. 5References

3.2 SDK Resources Overview

A overview of SDK resources is summarized in Table 3-1. More details can be found in "README_FIRST_AM263X.html" under the SDK installation directory. By default, the directory is at a path like "C:\ti\mcu_plus_sdk_am263x_xx_xx_xx_xx". The "examples/" folder is the most important one for beginners. It includes examples matching AM24 for connectivity and C28 examples for control. In most cases, "Ctrl+left click" in CCS guides user to the API declaration headers. Due to the inheritance from C28 and AM24, control API headers includes both declaration and definition as static inline while connectivity API headers only shows declaration. And, the connectivity API definition must be found in source file. Both header and source files are kept in "source/" folder. If CCS can't reach the desired details, there is a good chance that the details stay in one of source files inside the "source/". Another approach is to look into "API Reference" of "README_FIRST_AM263X.html".

Table 3-1 SDK directory structure
Folder/Files Description
${SDK_INSTALL_PATH}/
README_FIRST_AM263X.html Open this file in a web browser to reach SDK user guide
makefile Top level makefile to build the whole SDK using "make"
imports.mak Top level makefile to list paths to dependent tools
docs/ Offline HTML documentation
examples/ Example applications for AM263X, across multiple boards, CPUs, NO-RTOS, RTOS
source/ Device drivers, middleware libraries and APIs
tools/ Tools and utilities like CCS loading scripts, initialization scripts.
${SDK_INSTALL_PATH}/source/
board/ Board peripheral device drivers
drivers/ SOC peripheral device drivers
industrial_comms/ Industrial Communication Protocol stacks and Industrial Protocol FW HAL(Firmware and Hardware Abstraction Layer)
kernel/ NO RTOS and RTOS kernel and Driver Porting layer (DPL) for these environments
${SDK_INSTALL_PATH}/examples/
drivers/ SOC and board focused device driver examples. The examples are based on both NO-RTOS and RTOS.
empty/ Template projects to copy into workspace and customize based on application needs
industrial_comms/ Example for EtherCAT Slave