SPRACK2A September 2019 – March 2020 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
This migration guide describes the hardware and software differences to be aware of when moving between F28004x and F28002x C2000™ MCUs. This document shows the block diagram between the two MCUs as a visual representation on what blocks are similar or different. It also highlights the features that are unique between the two devices for all available packages in a device comparison table. A good starting point for migration would be the 64-PM package, which is pinout compatible between F28004x and F28002x, so a 64-PM PCB hardware section has been added. Section 2 discusses hardware considerations when migrating between F28004x and F28002x with the 64-PM package. The digital general-purpose input/output (GPIO) and analog multiplex comparison tables show pin functionality between the two MCUs. This is a good reference for hardware design and signal routing when considering a move between the two devices. Lastly, the F28002x software support is only in EABI format. The EABI migration is discussed in Section 4.
C2000, Code Composer Studio are registered trademarks of Texas Instruments.
All other trademarks are the property of their respective owners.