SPRADL6 January   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 , TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-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 , TMS320F2808 , TMS320F2808-Q1 , TMS320F2809 , TMS320F2810 , TMS320F2810-Q1 , TMS320F2811 , TMS320F2811-Q1 , TMS320F2812 , TMS320F2812-Q1 , TMS320F28232 , TMS320F28232-Q1 , TMS320F28234 , TMS320F28234-Q1 , TMS320F28235 , TMS320F28235-Q1 , TMS320F28332 , TMS320F28333 , TMS320F28334 , TMS320F28335 , TMS320F28335-Q1 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S , TMS320F28384D , TMS320F28384S , TMS320F28386D , TMS320F28386S , TMS320F28388D , TMS320F28388S , TMS320F28P550SJ , TMS320F28P559SJ-Q1 , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Getting Started
    1. 2.1 Software Installation
      1. 2.1.1 Install Code Composer Studio IDE
      2. 2.1.2 Install C2000 IDEA Extension
    2. 2.2 Import Project
    3. 2.3 Detect Project
    4. 2.4 Basic Commands
    5. 2.5 Global Settings
      1. 2.5.1 Project-less Detection
  6. 3Overview
  7. 4Features
    1. 4.1 Targeted Collateral Delivery
      1. 4.1.1 Key Collateral
      2. 4.1.2 Additional Resources
      3. 4.1.3 Register Vision
    2. 4.2 Developer Efficiency Tools
      1. 4.2.1 Register Coder
      2. 4.2.2 Interrupt Coder
    3. 4.3 Migration Support
      1. 4.3.1 Driverlib Migration
        1. 4.3.1.1 File-Based Migration Check
        2. 4.3.1.2 Project-Based Migration Check
      2. 4.3.2 Bitfield Migration
    4. 4.4 Command List
  8. 5Summary
  9. 6References

Bitfield Migration

The C2000 IDEA Extension can be used to run a F28x-to-F28x or F28x-to-F29x migration check on a file written with bitfield-style code. This code style is characterized by using calls to functions defined in the bitfield source files (ex: InitSysCtrl()) and/or register accesses containing the [base name].[register name].all or [base name].[register name].bit.[field name] syntax.

Follow these steps to enable Bitfield Migration:

  1. Open a C2000 application C-Code file.
  2. Run the migration check by pressing CTRL+SHIFT+P, typing and selecting C2000: Run Bitfield Migration Check on File
  3. Select the current C2000 device the code in the file applies to.
  4. Select the C2000 device to migrate the file to.
  5. The status bar at the bottom right of the screen displays Finished Bitfield Migration from [current device] to [migration device] when finished. All migration concerns in the file are underlined with a red squiggly line.
  6. Review and resolve concerns throughout the file. The following options are provided when the underlined code is hovered over:
    1. Select View Problem to quickly loop through the detected concerns in the file.
    2. Select Quick Fix to mitigate the migration concern. Select one of the below options:
      1. Review migration collateral for [current device] to [migration device]- This option opens a link to the online migration collateral for the specific migration path using the latest version of C2000WARE.
      2. Wrap in device specific #IFDEF for [current device] and [migration device] - This option autogenerates pre-processor wrappers around the line of code so that an updated version of the code can be compiled for the new device. Fill in the line with the //Enter alternate code comment with the modified code and add a #define for the current device somewhere in the file.
      3. Ignore code related errors - This option ignores this migration concern.