SPRADA3 july   2023 AM2631 , AM2631-Q1 , AM2632 , AM2632-Q1 , AM2634 , AM2634-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1 Introduction
  5. 2 Device Nomenclature
  6. 3 R5 Cores and TCM in AM263x
    1. 3.1 R5 Core Nomenclature in Am263x
  7. 4 Example Support for AM263x Family
  8. 5 IPC Example Support for Two-Core Devices (AM2632)
    1. 5.1 Option 1 Using MulticoreImageGen.js
    2. 5.2 Option Two (Migration Guide from a Four-Core System Project to a Two-Core System Project)
  9. 6 System Project Example Support for Two-Core Devices (AM2632)
  10. 7 Target Configuration in CCS
    1. 7.1 Prerequisites
    2. 7.2 Creating a Target Configuration
  11. 8 Connecting to the Target Core
  12. 9 Hardware Description for Launch Pad and Control Card
    1. 9.1 Launchpad Pinout for Standard Analog Devices
    2. 9.2 ADC and DAC Mapping in Launchpad for Standard Analog
    3. 9.3 Pinmux Mapping - Standard Analog - Launch Pad
    4. 9.4 ADC and DAC Mapping in Control Card for Standard Analog
  13. 10Summary
  14. 11References

1 Introduction

The current MCU_PLUS_SDK for AM263x is developed to support the entire series of AM263x devices. This document points out the examples of SDK designed for different subset devices of AM263x and explains the steps to modify existing examples to support the subset devices AM2632 and AM2631.

The AM263x LaunchPad™ Development Kit and ControlCARD are developed for the superset device AM2634. The users working on other AM263x SOCs can get started on the AM2634 EVMs as these are pin-to-pin compatible with AM2632 and AM2631. This document™ explains how to adapt these EVMs for the other family of devices. Users working on different AM263x family of devices can seamlessly use the same SDK libraries and EVMs for their different SOC projects.