MICROSAR MEM AUTOSAR Basic Software Modules for Memory Management Functions The BSW modules in MICROSAR MEM contain functions defined in AUTOSAR Release 3.x. In each memory stack, you will need the BSW modules NVM and MEMIF from MICROSAR MEM. They handle block-oriented and technology-independent access to the memory areas – without requiring prior knowledge of memory attributes. Your memory stack will need additional BSW modules, depending on the use case: > When using flash memory: Flash EEPROM Emulation (FEE) from MICROSAR MEM and a flash driver (FLSDRV) from MICROSAR CAL that is suitable for your hardware. To manage the data, the FEE module needs at least two flash sectors. > When using an EEPROM: EEPROM Abstraction (EA) from MICROSAR MEM and an EEPROM driver (EEPDRV) from MICROSAR CAL that is suitable for your hardware. Overview of Advantages > Exceptionally secure data transactions > Efficient data accesses > Efficient and robust management of nonvolatile memories > Redundant storage of management data increases reliability of FEE and EA modules > Inter-module configuration of the entire memory stack > Platform-optimized memory stack solution from a single source 2/24 The MICROSAR MEM package contains all of the AUTOSAR modules for memory management: NVM, MEMIF, EA and FEE. They support management, checking and restoring of data from nonvolatile memories (Flash or EEPROM). The Basic Software Modules (BSW) from MICROSAR MEM are fast, reliable and robust. It is possible to use multiple flash or EEPROM chips in one ECU. This involves using multiple FEE or IO modules in the ECU soft-ware. Application Areas MICROSAR MEM lets you develop your functional software plat-form- independently. MICROSAR MEM contains AUTOSAR services For special requirements, Vector offers platform-optimized solu-tions, for reading, writing and erasing persistent application data in flash and/or EEPROM memories. This gives the functional soft-ware e. g. for using the EA BSW module in data flashing or opti-mizing the FEE module for specific hardware. hardware-independent access to memory. The application does not need to know the specific type of memory that exists on the platform or whether this memory is internal to the controller or externally connected to it. The following functions are optionally available: > NVM: Block type “DATASET_ROM” with multiple ROM blocks > NVM: Data protection with CRC8 MICROSAR MEM modules