SDAA601 November   2026 AM13E23019

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Prerequisites
  6. 3How to Setup and Use the Tool
  7. 4Getting Started Fast: AI as a Bootstrap for New Projects
    1. 4.1 Identify the Target Device and Connected Hardware
    2. 4.2 Use SDK and Device-Specific Guidance
    3. 4.3 Start with Import a Matching Example Project
    4. 4.4 Configure Peripherals through SysConfig Using Natural Language
    5. 4.5 Write the Functionally Validated Application Code
    6. 4.6 Build and (If Starter Kit is Present) Flash and Run
  8. 5Debugging Through the Probe: AI-Driven Control Over Real Hardware
  9. 6Migrating Projects from Other MCU Ecosystems
  10. 7Supported Devices and Peripherals
  11. 8Summary
  12. 9References

Migrating Projects from Other MCU Ecosystems

The capability with another broadest practical impact is whole-project migration — taking an existing embedded application written for a different microcontroller family entirely and porting it to the AM13x MCU family, with the AI assisted migration and development tool.

This is a structured, multi-stage pipeline built on a layered knowledge base specifically designed for cross-platform migration. This takes into account the source ecosystem's conventions namely pin configuration, project structure, configuration file formats, HAL-style API patterns versus register level code), manifests that describe each supported target device family (the SDK, unsupported features relative to the source, and known pin-translation formulas), and path-specific guides for common source-to-target combinations that go further — down to peripheral-by-peripheral translation notes for timers, communication interfaces, analog comparators, and more.

A migration proceeds through the following stages:

Source analysis: The tool scans the source project in its entirety, its configuration files, HAL or driver-layer calls, middleware dependencies, and build system. It produces a structured summary of exactly what the project does, how peripherals are configured and used, what clock configuration it relies on, and what pin each signal is wired to and the exact memory requirement

Migration planning: That summary is then matched against the target device's capabilities and known unsupported features, producing a concrete plan: which peripherals map directly, which require a different approach, which source features (if any) are not supported on the target and need a workaround or an explicit scope decision, and a human-readable assessment presented.

Developer checkpoint: The developer must then review the assessment and explicitly command whether to proceed, request changes to the plan, or stop.

Configuration and porting, area by area: For each functional area of the project, the target device's configuration is built up through the same validated SysConfig tooling described previously, including, where a pin-translation table exists for the source-to-target pair, directly resolving pin assignments. The application code is rewritten against the target's actual API, with the same identifier-preservation discipline applied during ordinary development: the structure, naming, and intent of the original code are preserved; only what genuinely needs to change for the new platform does.

Migration report: This is an artifact capturing exactly what was changed, how each API was mapped, if it was fully ported or partially or cannot be ported. All warnings or caveats and what manual verification remains outstanding are put together for developer assessment.

Build verification and Hardware validation: This is described in Debugging Through the Probe: AI-Driven Control Over Real Hardware.