The RAM and Flash memory available in this device is completely different from F28 memory architecture. The F28 memcfg driver was responsible for the following functionalities :

• Configuring RAM ownership
  • In F29, all the RAMs are accessible from all the CPUs. There is no hardware settings to configure the RAM ownership.
• Configuring access protection
  • Access protection can be achieved using SSU module.
• Error handling
  • In F29, error handling is done as part of ESM module. This module can be used to configure the error events. Status can be read/cleared/forced in ESM module.
• RAM initialization
  • Memss driver in F29 can be used for RAM initialization.
• RAM test mode configuration
  • Memss driver in F29 can be used for test mode configuration.

Driverlib API mapping

The F28 Memcfg and F29 Memss drivers are completely different. Please refer to the api guide for more details on F29 Memss driver.