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
The C2000 IDEA tool simplifies code migration between C2000 devices by automatically identifying and highlighting changes in driverlib code, including added, removed, or modified Application Peripheral Interfaces (APIs), registers, fields, enums, and macros. This automation reduces manual effort, minimizes the risk of errors, and verifies a smooth and efficient migration process. The automation supports migration for both complete projects and standalone driverlib files, providing flexibility to meet various user requirements. For specific devices, the tool also enables bitfield code migration. C2000 IDEA simplifies migration between F28x-to-F28x and F28x-to-F29x devices by detecting architectural differences and offering targeted recommendations for a more reliable transition. Table 3-1 provides a clear summary of migration support across C2000 devices, helping users quickly assess compatibility and available support for both Driverlib and Bitfield implementations.
|
Device Families |
Driverlib Migration Support |
Bitfield Migration Support |
|---|---|---|
|
F29H85x |
Yes |
No |
|
F28P55x |
Yes |
No |
|
F28P65x |
Yes |
No |
|
F28002x |
Yes |
No |
|
F28004x |
Yes |
No |
|
F28003x |
Yes |
No |
|
F280013x |
Yes |
Yes (To) |
|
F280015x |
Yes |
No |
|
F2838x |
Yes |
No |
|
F2837x |
Yes |
No |
|
F2807x |
Yes |
No |
|
F2803x |
No |
Yes(From) |
This tool supports source files in specific file formats, as illustrated in Table 3-2.
|
Source File Format |
Migration Support |
|---|---|
|
*.c |
Yes |
|
*.h |
Yes |
|
*.asm |
No |
|
*.cmd |
No |
|
*.lib |
No |
|
Linker Files |
No |
Figure 3-1 outlines the key steps required to migrate a standalone file or an entire project, to make sure of a seamless and efficient migration process
Figure 3-1 C2000 IDEA - Migration Flow