Use Cases for AI Assistance - Use Cases for AI Assistance - 2026.1 English - UG1400

Vitis Unified Software Platform Documentation: Embedded Software Development (UG1400)
Document_ID
UG1400
Release_Date
2026-07-31
Version
2026.1 English
The following procedures are practical AI-assisted use cases.

Use Case: Diagnose Build Failures

  1. In the Flow Navigator, build your component.
  2. When the build finishes, open the Output view in the bottom panel.
  3. Locate the first failing error message.
  4. Copy the error line and surrounding context lines.
  5. Click the AI Chat tab.
  6. Paste the error block into the message field. Type a prompt such as: 
    Analyze this Vitis build error. Give root cause in one sentence, then propose minimal edits and list each changed line.
  7. Review the response.
  8. For each suggested edit, open the relevant file and review the proposed change.
  9. Apply only the edits you approve.
  10. Save the file and rebuild the component.
  11. Confirm the original error no longer appears.

Use Case: Update Project Configuration

  1. Open the target configuration file in the editor.
  2. In AI Chat, type a specific edit request, such as: 
    Update launch.json to point program to the current ELF under the workspace and keep existing debug arguments unchanged.
  3. For each proposed edit, open the configuration file and verify the change matches the suggestion.
  4. Ask AI Chat to explain each changed line if the suggestion is unclear.
  5. Apply approved edits. Save the file.
  6. Rebuild or relaunch to validate the change.

Use Case: Interpret IDE-generated reports

  1. Run a build, analysis, or debug operation that generates a report.
  2. Open the relevant report view or output panel.
  3. If the report is verbose or unclear, copy the relevant section.
  4. Click the AI Chat tab.
  5. Paste the report content into the message field. Type a prompt such as: 
    Explain this build report. What do the warnings mean and what should I fix first?
  6. Review the explanation and suggested next steps.
  7. Open the relevant source files and apply fixes.