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

How to Setup and Use the Tool

  1. Download and install the latest version of CCS. Version 21.0.1 is the latest version.
     Download CCStudioFigure 3-1 Download CCStudio
  2. Open CCS -> check for updates, Install updates (CCStudio IDE AI MD Files)
     Install UpdatesFigure 3-2 Install Updates
     Update the AI MD FilesFigure 3-3 Update the AI MD Files
  3. Once updates are installed, restart CCS.
  4. Setting up AI provider:
    1. Go to help and click -> Get Started with AI
       Setup AI Assiatant in CCSFigure 3-4 Setup AI Assiatant in CCS
      Configure the AI provider in the toolbox
      • Claude code subscription from anthropic: skip this and go next page where the user has an option to sign in using Anthropic account.
      • Onprem AI provider setup : Use the console to enter URL, Auth Token and other parameters.
      • Github: Follow this Appnote-ccs_ai_litellm_copilot
      • Deepseek/Qwen: Follow this Appnote-ccs_ai_cline
       Select and Sign In To AI Provider
                                    PortalFigure 3-5 Select and Sign In To AI Provider Portal
  5. A Claude code window opens.
    1. Set permission mode to Auto
    2. Type /mcp and check if all mcp servers are connected
       Auto Mode
                                                        Selection to Avoid Multiple Approvals Figure 3-6 Auto Mode Selection to Avoid Multiple Approvals
  6. Migrating a project
    1. Type /migrate-to-ti and press Enter and skills are invoked, asking for project path selection
       Starting the
                                                        Migrate-to-ti Skill Figure 3-7 Starting the Migrate-to-ti Skill

      Select the path where the project is located and target device as LP-AM13E230.

      Figure 3-8 shows a basic prompt for migrating example from competition to AM13E320-LP

       Sample Prompt
                                                                to Migrate a Project Figure 3-8 Sample Prompt to Migrate a Project
  7. Once the migration starts, the skill generates and migrates a code, configures sysconfig and prompts the user for selection, once the migration is complete, the skill:
  1. If all steps are complete, then the process concludes by generating a migration report:
 Sample Migration ReportFigure 3-9 Sample Migration Report