SPRADE8B November   2023  – August 2025 F29H850TU , F29H859TU-Q1 , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1 Introduction
  5. 2 Difference Between EEPROM and On-Chip Flash
  6. 3 Overview
    1. 3.1 Basic Concept
    2. 3.2 Single-Unit Method
    3. 3.3 Ping-Pong Method
    4. 3.4 Creating EEPROM Sections (Pages) and Page Identification
  7. 4 Software Description
  8. 5 Ping-Pong Emulation
    1. 5.1 User-Configuration
      1. 5.1.1 EEPROM_PingPong_Config.h
      2. 5.1.2 F28P65x_EEPROM_PingPong.c
    2. 5.2 Testing Example
  9. 6 EEPROM Functions
    1. 6.1  EEPROM_Config_Check
    2. 6.2  Configure_Protection_Masks
    3. 6.3  EEPROM_Write
    4. 6.4  EEPROM_Read
    5. 6.5  EEPROM_Erase
      1. 6.5.1 Erase_Bank
    6. 6.6  EEPROM_GetValidBank
    7. 6.7  EEPROM_UpdateBankStatus
    8. 6.8  EEPROM_UpdatePageStatus
    9. 6.9  EEPROM_UpdatePageData
    10. 6.10 EEPROM_Get_64_Bit_Data_Address
    11. 6.11 EEPROM_Program_64_Bits
    12. 6.12 EEPROM_CheckStatus
    13. 6.13 ClearFSMStatus
  10. 7 Single-Unit Emulation
    1. 7.1 User-Configuration
      1. 7.1.1 EEPROM_Config.h
      2. 7.1.2 F28P65x_EEPROM.c
    2. 7.2 EEPROM Functions
      1. 7.2.1  EEPROM_Config_Check
      2. 7.2.2  Configure_Protection_Masks
      3. 7.2.3  EEPROM_Write
      4. 7.2.4  EEPROM_Read
      5. 7.2.5  EEPROM_Erase
      6. 7.2.6  EEPROM_GetValidBank
      7. 7.2.7  EEPROM_Get_64_Bit_Data_Address
      8. 7.2.8  EEPROM_UpdateBankStatus
      9. 7.2.9  EEPROM_UpdatePageStatus
      10. 7.2.10 EEPROM_UpdatePageData
      11. 7.2.11 EEPROM_Get_64_Bit_Data_Address
      12. 7.2.12 EEPROM_Program_64_Bits
      13. 7.2.13 EEPROM_CheckStatus
      14. 7.2.14 ClearFSMStatus
    3. 7.3 Testing Example
  11. 8 Application Integration
    1. 8.1 Software Functionality and Flow
  12. 9 Adapting to Other Gen 3 C2000 MCUs
  13. 10Flash API
    1. 10.1 Flash API Checklist
      1. 10.1.1 Flash API Do's and Do Not's
  14. 11Source File Listing
  15. 12Troubleshooting
    1. 12.1 General
  16. 13Conclusion
  17. 14References
  18. 15Revision History

5.1.2 F28P65x_EEPROM_PingPong.c

Within F28P65x_EEPROM_PingPong.c, users can choose which Flash Sectors to use for EEPROM emulation. The sectors chosen (if multiple) should be contiguous and in order from least to greatest. Insert only the First and Last sectors to be used for EEPROM. For example, to use sectors 1-10, insert {1,10}. To only use sector 1, insert {1,1}. A valid configuration has the following properties.

  • Imply a valid and consistent amount of sectors between the two EEPROM units
  • Only include a sector(s) that exist on the device
  • Not create an overlap in the Write/Erase Protection Masks between the two units
    • The F28P65x Flash API requires Write/Erase Protection Masks to be configured before programming Flash Memory. Details about the proper configuration of these masks can be found in the F28P65x Flash API Reference Guide.

More details about invalid or dangerous configurations can be found in Section 6.1.

uint16 FIRST_AND_LAST_SECTOR[2][2] = {{1,1},{39,39}};

Additionally, you can choose which set of Flash Sectors to begin emulation in.

uint16 EEPROM_ACTIVE_UNIT = 0;

If set to 0, the first set of Flash Sectors in FIRST_AND_LAST_SECTOR will be the Active EEPROM Unit first, and the second set will be Inactive EEPROM unit at first. If set to 1, the opposite will be true.