SPRADR6 April   2025 F29H850TU , F29H859TU-Q1 , TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1 , TMS320F28075 , TMS320F28075-Q1 , TMS320F28076 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28378D , TMS320F28378S , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S , TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S , TMS320F28P550SG , TMS320F28P550SJ , TMS320F28P559SJ-Q1 , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 Getting Started
  5. 2Overview
  6. 3Migration Support Feature
    1. 3.1 Project Detection
    2. 3.2 Setup Migration Settings Page
    3. 3.3 Migration Execution
      1. 3.3.1 Running Migration Check on a Standalone File
      2. 3.3.2 Running Migration Check on a Project
    4. 3.4 Quick Fixes
    5. 3.5 Migration Report
    6. 3.6 Bitfield Migration
  7. 4Summary
  8. 5References

3.5 Migration Report

Migration Report plays a crucial role in analyzing code changes when transitioning between C2000 devices. This provides a structured overview of modifications, helping users assess migration complexity, identify potential issues, and select the best target device. With detailed diagnostics and export capabilities, Migration Report make sure of a simplified and efficient migration process.

This report can be generated after executing the migration, either for the entire project or a specific active file. This flexibility allows developers to focus on critical sections while maintaining a comprehensive overview of the migration impact.

There are multiple ways to generate and export the migration report:

  1. Enter CTRL+SHIFT+P and click C2000: Export Migration Report.
  2. Extension tree methods:
    1. Navigate to Migration Support > Export Migration Report in the C2000 IDEA - Features pane.
    2. Click the icon as shown in Figure 3-18, next to Migration Devices under the detected project in the C2000 IDEA - Projects pane.
Export Migration Report (Extension Tree) Figure 3-18 Export Migration Report (Extension Tree)

Once generated, the report can be exported and saved to a desired location using the file browser, verifying that migration data is readily available for further analysis and documentation.

Key Sections in Migration Report

  1. Migration Info - provides an overview of the migration process
    1. Source and Target Devices: displays the original device and the selected migration device or devices.
    2. Ignored Symbols, Files & Folders: lists excluded symbols, files, and directories that were not considered during migration.
    3. Processed Files: specifies the analyzed files that underwent migration.
    4. Migration Time: indicates the time taken for each file’s migration, offering insights into performance and complexity.
  2. Migration Diagnostics - highlights detected changes and potential issues in the migration process
    1. Classification: each detected change is categorized as a warning or an error, based on severity.
    2. Detailed Code Change Analysis: provides a clear explanation of the differences between the source and target device.
    3. Location: specifies the exact Line (Ln) and Column (Col) of the affected code, making issue resolution more efficient.
Migration Report Figure 3-19 Migration Report

By exporting the report and saving for documentation, developers can reference migration details whenever needed. The report is particularly useful for analyzing migration complexity across multiple target devices, helping developers assess potential challenges and determine the best approach for migration. With clear insights into code modifications and potential roadblocks, developers can make informed decisions about selecting an excellent migration device.

With structured diagnostics, export capabilities, and detailed insights, the Migration Report is an indispensable resource for verifying a seamless and efficient transition between C2000 devices.