Memory stack
The NVRAM Manager works with the Memory Abstraction Interface (MemIf) module to access the EEPROM Abstraction (Ea) and Flash EEPROM Emulation (Fee). This means that the NVRAM Manager is independent of the hardware memory and will support different types of NV memory devices. In addition, the Crc module provides routines to calculate a checksum that can be stored together with the data in NV memory.
NVRAM Manager
MemIf
Abstraction for the underlying memory abstraction devices for the upper layers to access the devices as a uniform linear memory addressing space.
Fee – Flash EEPROM Emulation
- provides a mechanism to spread the write access such that the FLASH is not overstressed
- manage for each block the information, whether this block is consistent or not
Ea – EEPROM Abstraction
- provides a mechanism to spread the write access such that the EEPROM is not overstressed
- manage for each block the information, whether this block is consistent or not
Memory Hardware Abstraction
Abstracts from the location of peripheral memory devices (on-chip or on-board) and the ECU hardware layout.
Memory Drivers
Drivers for on-chip memory devices and memory mapped external memory devices (Flash, EEPROM).
NVRAM Manager – Basic storage objects
- Is the smallest entity of a “NVRAM block”.
- Several “Basic Storage Objects” can be used to build a NVRAM Block.
- Can reside in different memory locations (RAM/ROM/NV memory)
NV block
Is a basic storage object and represents a memory area consisting of NV user data and (optionally) a CRC value and (optionally) a NV block header.
RAM block
- Is a basic storage object and represents an area in RAM consisting of user data and (optionally) a CRC value.
- Can be permanent or temporarily assigned
- The data area of a RAM block shall be accessible from NVRAM Manager and from the application side
ROM block
Is a basic storage object, resides in the ROM (FLASH) and is used to provide default data in case of an empty or damaged NV block
Interaction overview
Functional interface interaction overview
Documentation
- https://www.autosar.org/
- https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SRS_MemoryServices.pdf
- https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_EEPROMDriver.pdf
- https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_EEPROMAbstraction.pdf
- https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_MemoryAbstractionInterface.pdf
- https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_NVRAMManager.pdf
AUTOSAR articles (for articles written in Romanian please select your language from right part of webpage)
- https://automatic-house.blogspot.com/search/label/AUTOSAR
- https://automatic-house.blogspot.com/2014/08/calcularea-crc-ului-pentru-standardul.html
- https://automatic-house.blogspot.com/2019/03/autosar1-prezentare-generala.html
- https://automatic-house.blogspot.com/2019/03/autosar2-arhitectura.html
- https://automatic-house.blogspot.com/2019/04/autosar3-comstack-can.html
- https://automatic-house.blogspot.com/2019/05/autosar5-comstack-cantp.html
- https://automatic-house.blogspot.com/2019/07/autosar6-communication-services-in.html
- https://automatic-house.blogspot.com/2021/11/autosar-7-cryptostack-basics.html
- https://automatic-house.blogspot.com/2022/11/autosar-8-communication-over-ethernet.html
- https://automatic-house.blogspot.com/2022/11/autosar-9-error-handling-and-diagnostic.html
- https://automatic-house.blogspot.com/2022/11/autosar-10-memory-stack.html
Thank you for attention !
For questions please contact me on email: simedruflorin@automatic-house.ro.
Have a nice day !