DEENESPTFRRUARHIKOZHNL

AUTOSAR Classic Memory Services

Die Memory Services verwalten nicht-flüchtige Datenblöcke (NvM), abstrahieren Flash- und EEPROM-Technologien (MemIf, Fee, Ea) und gewährleisten Datenkonsistenz und Datensicherheit über ECU-Abschaltzyklen hinweg.

주제 맵

상세 보기

개요에서 항목을 선택하세요.

BndM

BndM_Init 함수

Initializes or reinitializes this module.

void BndM_Init(const BndM_ConfigType* ConfigPtr);

This callback function is called when a FLS job has been finished with positive result.

void BndM_JobEndNotification(void);

This callback function is called when a FLS job has been canceled or finished with negative result.

void BndM_JobErrorNotification(void);

Schedule function for the background processing.

void BndM_MainFunction(void);

Cancels the writing

void BndM_WriteCancel(void);

Unique identification of an bulk nv block. The BndM_BlockId is assigned by the BndM.

The elements of this structure data type is the C-structured representation of the configured ImplementationDataPrototype.

This type of the external data structure shall contain the post build initialization data for the BndM.

Result of the asynchronous job finish notifications

Ea

Ea_Cancel 함수

Cancels the ongoing asynchronous operation.

void Ea_Cancel (void);

Erases the block Block Number.

Std_ReturnType Ea_EraseImmediateBlock (uint16 BlockNumber);

Service to return the Job Result.

MemIf_JobResultType Ea_GetJobResult (void);

Service to return the Status.

MemIf_StatusType Ea_GetStatus (void);

Service to get the version information of this module.

void Ea_GetVersionInfo (Std_VersionInfoType* VersionInfoPtr);
Ea_Init 함수

Initializes the EEPROM abstraction module.

void Ea_Init (const Ea_ConfigType* ConfigPtr);

Invalidates the block Block Number.

Std_ReturnType Ea_InvalidateBlock (uint16 BlockNumber);

Service to report to this module the successful end of an asynchronous operation.

void Ea_JobEndNotification (void);

Service to report to this module the failure of an asynchronous operation.

void Ea_JobErrorNotification (void);

Service to handle the requested jobs and the internal management operations.

void Ea_MainFunction (void);
Ea_Read 함수

Reads Length bytes of block Blocknumber at offset Block Offset into the buffer Data Buffer Ptr.

Std_ReturnType Ea_Read (uint16 BlockNumber, uint16 BlockOffset, uint8* DataBufferPtr, uint16 Length);
Ea_SetMode 함수

Function to switch the mode of the underlying EEPROM Driver

void Ea_SetMode (MemIf_ModeType Mode);
Ea_Write 함수

Writes the contents of the Data Buffer Ptr to the block Block Number.

Std_ReturnType Ea_Write (uint16 BlockNumber, const uint8* DataBufferPtr);

Function to be used by the underlying memory abstraction to signal end of job without error.

void NvM_JobEndNotification (void);

Function to be used by the underlying memory abstraction to signal end of job with error.

void NvM_JobErrorNotification (void);

Configuration data structure of the Ea module.

Eep

Eep_Cancel 함수

Cancels a running job.

void Eep_Cancel(void);

Compares a data block in EEPROM with an EEPROM block in the memory.

Std_ReturnType Eep_Compare(Eep_AddressType EepromAddress, const uint8* DataBufferPtr, Eep_LengthType Length);
Eep_Erase 함수

Service for erasing EEPROM sections.

Std_ReturnType Eep_Erase(Eep_AddressType EepromAddress, Eep_LengthType Length);

This service returns the result of the last job.

MemIf_JobResultType Eep_GetJobResult(void);

Returns the EEPROM status.

MemIf_StatusType Eep_GetStatus(void);

Service to get the version information of this module.

void Eep_GetVersionInfo(Std_VersionInfoType* versioninfo);
Eep_Init 함수

Service for EEPROM initialization.

void Eep_Init(const Eep_ConfigType* ConfigPtr);

This callback function provided by the module user is called when a job has been completed with a positive result.

void Eep_JobEndNotification(void);

This callback function provided by the module user is called when a job has been canceled or finished with negative result.

void Eep_JobErrorNotification(void);

Service to perform the processing of the EEPROM jobs (read/write/erase/compare) .

void Eep_MainFunction(void);
Eep_Read 함수

Reads from EEPROM.

Std_ReturnType Eep_Read(Eep_AddressType EepromAddress, uint8* DataBufferPtr, Eep_LengthType Length);

Sets the mode.

void Eep_SetMode(MemIf_ModeType Mode);
Eep_Write 함수

Writes to EEPROM.

Std_ReturnType Eep_Write(Eep_AddressType EepromAddress, const uint8* DataBufferPtr, Eep_LengthType Length);

Used as address offset from the configured EEPROM base address to access a certain EEPROM memory area.

This is the type of the external data structure containing the initialization data for the EEPROM driver.

Specifies the number of bytes to read/write/erase/compare.

Fee

Fee_Cancel 함수

Service to call the cancel function of the underlying flash driver.

void Fee_Cancel (void);

Service to erase a logical block.

Std_ReturnType Fee_EraseImmediateBlock (uint16 BlockNumber);

Service to query the result of the last accepted job issued by the upper layer software.

MemIf_JobResultType Fee_GetJobResult (void);

Service to return the status. AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_FlashEEPROMEmulation

MemIf_StatusType Fee_GetStatus (void);

Service to return the version information of the FEE module.

void Fee_GetVersionInfo (Std_VersionInfoType* VersionInfoPtr);
Fee_Init 함수

Service to initialize the FEE module.

void Fee_Init (const Fee_ConfigType* ConfigPtr);

Service to invalidate a logical block.

Std_ReturnType Fee_InvalidateBlock (uint16 BlockNumber);

Service to report to this module the successful end of an asynchronous operation. AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_FlashEEPROMEmulation

void Fee_JobEndNotification (void);

Service to report to this module the failure of an asynchronous operation.

void Fee_JobErrorNotification (void);

Service to handle the requested read / write / erase jobs and the internal management operations.

void Fee_MainFunction (void);
Fee_Read 함수

Service to initiate a read job.

Std_ReturnType Fee_Read (uint16 BlockNumber, uint16 BlockOffset, uint8* DataBufferPtr, uint16 Length);

Function to switch the mode of the underlying Flash Driver

void Fee_SetMode (MemIf_ModeType Mode);
Fee_Write 함수

Service to initiate a write job.

Std_ReturnType Fee_Write (uint16 BlockNumber, const uint8* DataBufferPtr);

-

void NvM_JobEndNotification (void);

-

void NvM_JobErrorNotification (void);

Configuration data structure of the Fee module.

Fls

This callback function is called when a job has been completed with a positive result.

void Fee_JobEndNotification(void);

This callback function is called when a job has been canceled or finished with negative result.

void Fee_JobErrorNotification(void);

The function Fls_BlankCheck shall verify, whether a given memory area has been erased but not (yet) programmed. The function shall limit the maximum number of checked flash cells per main function cycle to the configured value FlsMaxReadNormalMode or FlsMaxReadFastMode respectively.

Std_ReturnType Fls_BlankCheck(Fls_AddressType TargetAddress, Fls_LengthType Length);
Fls_Cancel 함수

Cancels an ongoing job.

void Fls_Cancel(void);

Compares the contents of an area of flash memory with that of an application data buffer.

Std_ReturnType Fls_Compare(Fls_AddressType SourceAddress, const uint8* TargetAddressPtr, Fls_LengthType Length);
Fls_Erase 함수

Erases flash sector(s).

Std_ReturnType Fls_Erase(Fls_AddressType TargetAddress, Fls_LengthType Length);

Returns the result of the last job.

MemIf_JobResultType Fls_GetJobResult(void);

Returns the driver state.

MemIf_StatusType Fls_GetStatus(void);

Returns the version information of this module.

void Fls_GetVersionInfo(Std_VersionInfoType* VersioninfoPtr);
Fls_Init 함수

Initializes the Flash Driver.

void Fls_Init(const Fls_ConfigType* ConfigPtr);

Performs the processing of jobs.

void Fls_MainFunction(void);
Fls_Read 함수

Reads from flash memory.

Std_ReturnType Fls_Read(Fls_AddressType SourceAddress, uint8* TargetAddressPtr, Fls_LengthType Length);

Sets the flash driver's operation mode.

void Fls_SetMode(MemIf_ModeType Mode);
Fls_Write 함수

Writes one or more complete flash pages.

Std_ReturnType Fls_Write(Fls_AddressType TargetAddress, const uint8* SourceAddressPtr, Fls_LengthType Length);

Used as address offset from the configured flash base address to access a certain flash memory area.

A pointer to such a structure is provided to the flash driver initialization routine for configuration of the driver and flash memory hardware.

Specifies the number of bytes to read/write/erase/compare.

FlsTst

Service for aborting the Flash Test.

void FlsTst_Abort(void);

Service for Flash Test De - Initialization.

void FlsTst_DeInit(void);

Service returns the version information of this module.

void FlsTst_GetVersionInfo(Std_VersionInfoType* versioninfo);

Service for Flash Test initialization.

void FlsTst_Init(const FlsTst_ConfigType* ConfigPtr);

Service for executing the Flash Test in background mode.

void FlsTst_MainFunction(void);

Service for continuing the Flash Test at the point it was suspended.

void FlsTst_Resume(void);

Service for executing foreground Flash Test.

Std_ReturnType FlsTst_StartFgnd(FlsTst_BlockIdFgndType FgndBlockId);

Service for suspending current operation of the Flash Test, until Fls Tst_ Resume is called.

void FlsTst_Suspend(void);

The function Fls Tst_ Test Completed shall be called every time when a complete test cycle had been tested.

void FlsTst_TestCompletedNotification(void);

Service executes a test of ECC hardware. This is only applicable in case the hardware provices such functionality.

Std_ReturnType FlsTst_TestEcc(void);

Service returns error detais monitored from the Flash module.

FlsTst_ErrorDetailsType FlsTst_GetErrorDetails(void);

Service returns the current Flash Test exection state.

FlsTst_StateType FlsTst_GetCurrentState(void);

Service returns the Background Flash Test result.

FlsTst_TestResultBgndType FlsTst_GetTestResultBgnd(void);

Service returns the Foreground Flash Test result.

FlsTst_TestResultFgndType FlsTst_GetTestResultFgnd(void);

Service returns the Flash Test result in background mode.

FlsTst_TestSignatureBgndType FlsTst_GetTestSignatureBgnd(void);

Service returns the Flash Test result in foreground mode.

FlsTst_TestSignatureFgndType FlsTst_GetTestSignatureFgnd(void);

This type specifies the identification (ID) for a Flash block to be tested in foreground mode, which is configured in the configuration structure.

This type of external data structure shall contain the initialization data for the Flash Test.

This type shall specify implementation specific error information monitored in the Flash test module.

This is a state value returned by the API service Fls Tst_ Get Current State().

Return type of API service Fls Tst_ Get Test Result Bgnd().

Return type of API service Fls Tst_ Get Result Fgnd().

Type for test signature in background mode.

Type for test signature in foreground mode

Mem

Triggers a job to check the erased state of the page which is referenced by targetAddress. The result of this service can be retrieved using the Mem_GetJobResult API. If the checked page is blank, the result of the job is MEM_JOB_OK. Otherwise, if the page is not blank, the result is MEM_INCONSISTENT.

Std_ReturnType Mem_BlankCheck(Mem_InstanceIdType instanceId, Mem_AddressType targetAddress, Mem_LengthType length);
Mem_DeInit 함수

De-initialize module. If there is still an access job pending, it is immediately terminated (using hardware cancel operation) and the Mem driver module state is set to unitialized. Therefore, Mem must be re-initialized before it will accept any new job requests after this service is processed.

void Mem_DeInit(void);
Mem_Erase 함수

Triggers an erase job of the given sector/sector batch defined by targetAddress and length. The result of this service can be retrieved using the Mem_GetJobResult API. If the erase operation was successful, the result of the job is MEM_JOB_OK. If the erase operation failed, e.g. due to a hardware issue, the result of the job is MEM_JOB_FAILED.

Std_ReturnType Mem_Erase(Mem_InstanceIdType instanceId, Mem_AddressType targetAddress, Mem_LengthType length);

Service to return results of the most recent job.

Mem_JobResultType Mem_GetJobResult(Mem_InstanceIdType instanceId);

Service to return the version information of the Mem module.

void Mem_GetVersionInfo(Std_VersionInfoType* versionInfoPtr);

Triggers a hardware specific memory driver job. dataPtr can be used to pass and return data to/ from this service. This service is just a dispatcher to the hardware specific service implementation referenced by hwServiceId. The result of this service can be retrieved using the Mem_GetJobResult API. If the hardware specific operation was successful, the result of the job is MEM_JOB_OK. If the hardware specific operation failed, the result of the job is MEM_JOB_ FAILED. Tags: atp.Status=draft

Std_ReturnType Mem_HwSpecificService(Mem_InstanceIdType instanceId, Mem_HwServiceIdType hwServiceId, Mem_DataType* dataPtr, Mem_LengthType* lengthPtr);
Mem_Init 함수

Initialization function - initializes all variables and sets the module state to initialized.

void Mem_Init(const Mem_ConfigType* configPtr);

Service to handle the requested jobs and the internal management operations.

void Mem_MainFunction(void);

This service can be used to report an access error in case the Mem driver cannot provide the access error information - typically for ECC faults. It is called by the system ECC handler to propagate an ECC error to the memory upper layers..

void Mem_PropagateError(Mem_InstanceIdType instanceId);
Mem_Read 함수

Triggers a read job to copy the from the source address into the referenced destination data buffer. The result of this service can be retrieved using the Mem_GetJobResult API. If the read operation was successful, the result of the job is MEM_JOB_OK. If the read operation failed, the result of the job is either MEM_JOB_FAILED in case of a general error or MEM_ECC_ CORRECTED/MEM_ECC_UNCORRECTED in case of a correctable/uncorrectable ECC error.

Std_ReturnType Mem_Read(Mem_InstanceIdType instanceId, Mem_AddressType sourceAddress, Mem_DataType* destinationDataPtr, Mem_LengthType length);
Mem_Resume 함수

Resume suspended memory operation using hardware mechanism. Tags: atp.Status=draft

void Mem_Resume(Mem_InstanceIdType instanceId);

Suspend active memory operation using hardware mechanism. Tags: atp.Status=draft

void Mem_Suspend(Mem_InstanceIdType instanceId);
Mem_Write 함수

Triggers a write job to store the passed data to the provided address area with given address and length. The result of this service can be retrieved using the Mem_GetJobResult API. If the write operation was successful, the job result is MEM_JOB_OK. If there was an issue writing the data, the result is MEM_FAILED.

Std_ReturnType Mem_Write(Mem_InstanceIdType instanceId, Mem_AddressType targetAddress, const Mem_DataType* sourceDataPtr, Mem_LengthType length);

Physical memory device address type

Postbuild configuration structure type

Read data user buffer type

Hardware specific service request identifier type

Job end notification function called by Mem in case the job processing is configured for job end notification.

Asynchronous job result type

Physical memory device length type

MemAcc

MemAcc application job end notification callback. The function name is configurable. Tags: atp.Status=draft

void <AddressAreaJobEndNotification>(MemAcc_AddressAreaIdType addressAreaId, MemAcc_JobResultType jobResult);

Address area lock application callback. The function name is configurable. Tags: atp.Status=draft

void <ApplicationLockNotification>(void);

Dynamic activation and initialization of a Mem driver referenced by hwId and headerAddress.

Std_ReturnType MemAcc_ActivateMem(MemAcc_AddressType headerAddress, MemAcc_HwIdType hwId);

Checks if the passed address space is blank, i.e. erased and writeable. The result of this service can be retrieved using the MemAcc_GetJobResult API. If the address area defined by targetAddress and length is blank, the result is MEMACC_MEM_OK, otherwise the result is MEMACC_MEM_INCONSISTENT.

Std_ReturnType MemAcc_BlankCheck(MemAcc_AddressAreaIdType addressAreaId, MemAcc_AddressType targetAddress, MemAcc_LengthType length);

Triggers a cancel operation of the pending job for the address area referenced by the address AreaId. Cancelling affects only jobs in pending state. For any other states, the request will be ignored.

void MemAcc_Cancel(MemAcc_AddressAreaIdType addressAreaId);

Triggers a job to compare the passed data to the memory content of the provided address area. The job terminates, if all bytes matched or a difference was detected. The result of this service can be retrieved using the MemAcc_GetJobResult() API. If the compare operation determined a mismatch, the result code is MEMACC_MEM_INCONSISTENT. Tags: atp.Status=draft

Std_ReturnType MemAcc_Compare(MemAcc_AddressAreaIdType addressAreaId, MemAcc_AddressType sourceAddress, const MemAcc_DataType* dataPtr, MemAcc_LengthType length);

Dynamic deactivation of a Mem driver referenced by hwId and headerAddress.

Std_ReturnType MemAcc_DeactivateMem(MemAcc_HwIdType hwId, MemAcc_AddressType headerAddress);

Deinitialize module. If there are still access jobs pending, they are immediately terminated and the module state is set to unitialized. Therefore, MemAcc must be re-initialized before it will accept any new job requests after this service is processed.

void MemAcc_DeInit(void);

Triggers an erase job of the given area. Triggers an erase job of the given area defined by targetAddress and length. The result of this service can be retrieved using the Mem_GetJobResult API. If the erase operation was successful, the result of the job is MEM_JOB_OK. If the erase operation failed, e.g. due to a hardware issue, the result of the job is MEM_JOB_FAILED.

Std_ReturnType MemAcc_Erase(MemAcc_AddressAreaIdType addressAreaId, MemAcc_AddressType targetAddress, MemAcc_LengthType length);

Returns detailed information of the current memory job like memory device ID, job type, job processing state or job result, address area as well as address and length.

void MemAcc_GetJobInfo(MemAcc_AddressAreaIdType addressAreaId, MemAcc_JobInfoType* jobInfoPtr);

Returns the consolidated job result of the address area referenced by addressAreaId.

MemAcc_JobResultType MemAcc_GetJobResult(MemAcc_AddressAreaIdType addressAreaId);

Returns the status of the MemAcc job referenced by addressAreaId.

MemAcc_JobStatusType MemAcc_GetJobStatus(MemAcc_AddressAreaIdType addressAreaId);

This service function retrieves the physical memory device information of a specific address area. It can be used by an upper layer to get all necessary information to align the start address and trim the length for erase/write jobs.

Std_ReturnType MemAcc_GetMemoryInfo(MemAcc_AddressAreaIdType addressAreaId, MemAcc_AddressType address, MemAcc_MemoryInfoType* memoryInfoPtr);

Returns the accumulated number of bytes that have already been processed in the current job.

MemAcc_LengthType MemAcc_GetProcessedLength(MemAcc_AddressAreaIdType addressAreaId);

Service to return the version information of the MemAcc module.

void MemAcc_GetVersionInfo(Std_VersionInfoType* versionInfoPtr);

Triggers a hardware specific job request referenced by hwServiceId. Service specific data can be passed/retrieved by dataPtr. The result of this service can be retrieved using the MemAcc_GetJobResult API. If the hardware specific operation was successful, the result of the job is MEMACC_MEM_OK. If the hardware specific operation failed, the result of the job is MEMACC_MEM_FAILED.

Std_ReturnType MemAcc_HwSpecificService(MemAcc_AddressAreaIdType addressAreaId, MemAcc_HwIdType hwId, MemAcc_MemHwServiceIdType hwServiceId, MemAcc_DataType* dataPtr, MemAcc_LengthType* lengthPtr);

Initialization function - initializes all variables and sets the module state to initialized.

void MemAcc_Init(const MemAcc_ConfigType* configPtr);

Service to handle the requested jobs and the internal management operations. Depending on the configuration MemAcc will call the Mem driver main functions.

void MemAcc_MainFunction(void);

Triggers a read job to copy data from the source address into the referenced destination data buffer. The result of this service can be retrieved using the MemAcc_GetJobResult API. If the read operation was successful, the result of the job is MEMACC_MEM_OK. If the read operation failed, the result of the job is either MEMACC_MEM_FAILED in case of a general error or MEMACC_MEM_ECC_CORRECTED/MEMACC_MEM_ECC_UNCORRECTED in case of a correctable/uncorrectable ECC error.

Std_ReturnType MemAcc_Read(MemAcc_AddressAreaIdType addressAreaId, MemAcc_AddressType sourceAddress, MemAcc_DataType* destinationDataPtr, MemAcc_LengthType length);

Release access lock of provided address area. Tags: atp.Status=draft

Std_ReturnType MemAcc_ReleaseLock(MemAcc_AddressAreaIdType addressAreaId, MemAcc_AddressType address, MemAcc_LengthType length);

Request lock of an address area for exclusive access. Once the lock is granted, the referenced lock notification function is called by MemAcc.

Std_ReturnType MemAcc_RequestLock(MemAcc_AddressAreaIdType addressAreaId, MemAcc_AddressType address, MemAcc_AddressType length, void* lockNotificationFctPtr);

Triggers a write job to store the passed data to the provided address area with given address and length. The result of this service can be retrieved using the MemAcc_GetJobResult API. If the write operation was successful, the job result is MEMACC_MEM_OK. If there was an issue writing the data, the result is MEMACC_MEM_FAILED.

Std_ReturnType MemAcc_Write(MemAcc_AddressAreaIdType addressAreaId, MemAcc_AddressType targetAddress, const MemAcc_DataType* sourceDataPtr, MemAcc_LengthType length);

Unique address area ID type.

Logical memory address type.

Type of the function pointer to register an application callback to be notified once the address area lock was successfully acquired.

Postbuild configuration structure type.

General data type.

Type for the unique numeric identifiers of all Mem hardware instances used for hardware specific requests.

This structure contains information the current processing state of the MemAcc module.

Asynchronous job result type.

Asynchronous job status type.

Type for asynchronous jobs.

Job length type.

Physical memory device address type

This structure contains elements for accessing the Mem driver service functions and consistency information. Tags: atp.Status=draft

Function pointer for the Mem_BlankCheck service for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

Memory driver configuration structure type

General data type

Function pointer for the Mem_DeInit service for the invocation of the Mem driver API via function pointer interface.

Function pointer for the Mem_Erase service for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

Function pointer for the Mem_JobResultType service for the invocation of the Mem driver API via function pointer interface.

Index type for Mem driver hardware specific service table.

Function pointer for the Mem_HwSpecificService function for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

Function pointer for the Mem_Init service for the invocation of the Mem driver API via function pointer interface.

Memory driver instance ID type

Asynchronous job result type

Physical memory device length type

Function pointer for the Mem_MainFunction service for the invocation of the Mem driver API via function pointer interface.

This structure contains information of Mem device characteristics. It can be accessed via the MemAcc_GetMemoryInfo() service. Tags: atp.Status=draft

Function pointer for the Mem_PropagateError service for the invocation of the Mem driver API via function pointer interface.

Function pointer for the Mem_Read service for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

Function pointer for the Mem_Resume service for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

Function pointer for the Mem_Suspend service for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

Function pointer for the Mem_Write service for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

MemIf

Invokes the "Cancel" function of the underlying memory abstraction module selected by the parameter Device Index.

void MemIf_Cancel (uint8 DeviceIndex);

Invokes the "Erase Immediate Block" function of the underlying memory abstraction module selected by the parameter Device Index.

Std_ReturnType MemIf_EraseImmediateBlock (uint8 DeviceIndex, uint16 BlockNumber);

Invokes the "Get Job Result" function of the underlying memory abstraction module selected by the parameter Device Index. Available v ia Mem If.h

MemIf_JobResultType MemIf_GetJobResult (uint8 DeviceIndex);

Invokes the "Get Status" function of the underlying memory abstraction module selected by the parameter Device Index.

MemIf_StatusType MemIf_GetStatus (uint8 DeviceIndex);

Returns version information.

void MemIf_GetVersionInfo (Std_VersionInfoType* VersionInfoPtr);

Invokes the "Invalidate Block" function of the underlying memory abstraction module AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_MemoryAbstractionInterface selected by the parameter Device Index.

Std_ReturnType MemIf_InvalidateBlock (uint8 DeviceIndex, uint16 BlockNumber);
MemIf_Read 함수

Invokes the "Read" function of the underlying memory abstraction module selected by the parameter Device Index.

Std_ReturnType MemIf_Read (uint8 DeviceIndex, uint16 BlockNumber, uint16 BlockOffset, uint8* DataBufferPtr, uint16 Length);

Invokes the "Set Mode" functions of all underlying memory abstraction modules.

void MemIf_SetMode (MemIf_ModeType Mode);

Invokes the "Write" function of the underlying memory abstraction module selected by the parameter Device Index.

Std_ReturnType MemIf_Write (uint8 DeviceIndex, uint16 BlockNumber, const uint8* DataBufferPtr);

Denotes the result of the last job.

Denotes the operation mode of the underlying abstraction mod ules and device drivers.

Denotes the current status of the underlying abstraction module and device drive. AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_MemoryAbstractionInterface

NvM

Service to cancel all jobs pending for a NV block.

Std_ReturnType NvM_CancelJobs (NvM_BlockIdType BlockId);

Service to cancel a running Nv M_ Write All request.

void NvM_CancelWriteAll (void);

Service to erase a NV block.

Std_ReturnType NvM_EraseNvBlock (NvM_BlockIdType BlockId);

The function initiates a multi block first initialization request. The job of the function does not care if a block exists in the non - volatile memory or not OR if it is valid (i.e. not corrupted) or not, when processing it.

void NvM_FirstInitAll (void);

Service for getting the currently set Data Index of a datase t NVRAM block

Std_ReturnType NvM_GetDataIndex (NvM_BlockIdType BlockId, uint8* DataIndexPtr);

Service to read the block dependent error/ status information.

Std_ReturnType NvM_GetErrorStatus (NvM_BlockIdType BlockId, NvM_RequestResultType* RequestResultPtr);

Service to get the version information of the Nv M module.

void NvM_GetVersionInfo (Std_VersionInfoType* versioninfo);
NvM_Init 함수

Service for resetting all internal variables.

void NvM_Init (const NvM_ConfigType* ConfigPtr);

Per block callback routine which shall be called by the Nv M module when default data needs to be restored in RAM, and a RO M block is not configured. AUTOSAR CP R20 - of Document ID : AUTOSAR_SWS_NVRAMManager

Std_ReturnType NvM_InitBlockCallbackFunction (NvM_InitBlockRequestType InitBlockRequest);

Service to invalidate a NV block.

Std_ReturnType NvM_InvalidateNvBlock (NvM_BlockIdType BlockId);

Function to be used by the underlying memory abstraction to signal end of job without error.

void NvM_JobEndNotification (void);

Function to be used by the underlying memory abstraction to signal end of job with error.

void NvM_JobErrorNotification (void);

Service for performing the processing of the Nv M jobs.

void NvM_MainFunction (void);

Common callback routine to notify the upper layer that an asynchronous multi block request has been finished. Available v ia Nv M_ Externals.h

Std_ReturnType NvM_MultiBlockCallbackFunction (NvM_MultiBlockRequestType MultiBlockRequest, NvM_RequestResultType JobResult);

Initiates a multi block read request.

void NvM_ReadAll (void);

Service to copy the data of the NV block to its corresponding RAM block.

Std_ReturnType NvM_ReadBlock (NvM_BlockIdType BlockId, void* NvM_DstPtr);

Service to copy the data of the NV block to its corresponding permanent RAM block.

Std_ReturnType NvM_ReadPRAMBlock (NvM_BlockIdType BlockId);

Block specific callback routine which shall be called in order to let the application copy data from Nv M module's mirror to RAM block.

Std_ReturnType NvM_ReadRamBlockFromNvm (const void* NvMBuffer);

Service to restore the default data to its corr esponding RAM block.

Std_ReturnType NvM_RestoreBlockDefaults (NvM_BlockIdType BlockId, void* NvM_DestPtr);

Service to restore the default data to its corresponding permanent RAM block.

Std_ReturnType NvM_RestorePRAMBlockDefaults (NvM_BlockIdType BlockId);

Service for setting the lock status of a permanent RAM block or of the explicit synchronization of a NVRAM block.

void NvM_SetBlockLockStatus (NvM_BlockIdType BlockId, boolean BlockLocked);

Service for setting/ resetting the write protection for a NV block. Availabl e via Nv M.h

Std_ReturnType NvM_SetBlockProtection (NvM_BlockIdType BlockId, boolean ProtectionEnabled);

Service for setting the Data Inde x of a dataset NVRAM block.

Std_ReturnType NvM_SetDataIndex (NvM_BlockIdType BlockId, uint8 DataIndex);

Service for setting the RAM block status of a permanent RAM block or the status of the explicit synchronization of a NVRAM block.

Std_ReturnType NvM_SetRamBlockStatus (NvM_BlockIdType BlockId, boolean BlockChanged);

Per block callback routine to notify the upper layer that an asynchronous single block request has been finished.

Std_ReturnType NvM_SingleBlockCallbackFunction (NvM_BlockRequestType BlockRequest, NvM_RequestResultType JobResult);

Initiates a multi block validation request.

void NvM_ValidateAll (void);

Initiates a multi block write request.

void NvM_WriteAll (void);

Service to copy the data of the RAM block to its corresponding NV block. Available vi a Nv M.h

Std_ReturnType NvM_WriteBlock (NvM_BlockIdType BlockId, const void* NvM_SrcPtr);

Service to copy the data of the permanent RAM block to its corresponding NV block.

Std_ReturnType NvM_WritePRAMBlock (NvM_BlockIdType BlockId);

Block specific callback routine which shall be called in order to let the application copy data from RAM block to Nv M module's mirror.

Std_ReturnType NvM_WriteRamBlockToNvm (void* NvMBuffer);

Identification of a NVRAM block via a unique block identifier. Reserved NVRAM block IDs: 0 - > to derive multi block request results via Nv M_ Get Error Status 1 - > redundant NVRAM block which holds the configuration ID

Identifies the type of reques t performed on a block when signaled via the callback function

Configuration data structure of the Nv M module.

Identifies the type of request performed on a block when signaled via the callback function

Identifies the type of request performed on multi block when signaled via the callback function or when reporting to Bsw M

Type NvM_RequestResultType.

RamTst

Service for continuing the RAM Test after calling 'Ram Tst_ Stop.

void RamTst_Allow(void);

Service changes the current number of tested cells.

void RamTst_ChangeNumberOfTestedCells(RamTst_NumberOfTestedCellsType NewNumberOfTestedCells);

Service for RAM Test deinitialization.

void RamTst_DeInit(void);

The function Ram Tst_ Error shall be called every time when a RAM failure has been detected by the selected test algorithm in the background.

void RamTst_ErrorNotification(void);

Service returns the version information of this module.

void RamTst_GetVersionInfo(Std_VersionInfoType* versioninfo);

Service for RAM Test initialization.

void RamTst_Init(const RamTst_ConfigType* ConfigPtr);

Scheduled function for executing the RAM Test in the background.

void RamTst_MainFunction(void);

Service for allowing to continue the background RAM Test at the point is was suspended.

void RamTst_Resume(void);

Service for executing the full RAM Test in the foreground.

void RamTst_RunFullTest(void);

Service for testing one RAM block in the foreground.

void RamTst_RunPartialTest(RamTst_NumberOfBlocksType BlockId);

Service used to set the test algorithm and its parameter set.

void RamTst_SelectAlgParams(RamTst_AlgParamsIdType NewAlgParamsId);

Service for stopping the RAM Test.

void RamTst_Stop(void);

Service for suspending current operation of background RAM Test, until RESUME is called.

void RamTst_Suspend(void);

The function Ram Tst_ Test Completed shall be called every time when all RAM blocks of the current test configuration have been tested in the background.

void RamTst_TestCompletedNotification(void);

Service returns the current RAM Test algorithm.

RamTst_AlgorithmType RamTst_GetTestAlgorithm(void);

Service returns the ID of the current RAM Test algorithm parameter set.

RamTst_AlgParamsIdType RamTst_GetAlgParams(void);

Service returns the current RAM Test execution status.

RamTst_ExecutionStatusType RamTst_GetExecutionStatus(void);

Service returns the current number of tested cells per main - function cycle.

RamTst_NumberOfTestedCellsType RamTst_GetNumberOfTestedCells(void);

Service returns the current RAM Test result.

RamTst_TestResultType RamTst_GetTestResult(void);

Service returns the current RAM Test result for the specified block.

RamTst_TestResultType RamTst_GetTestResultPerBlock(RamTst_NumberOfBlocksType BlockID);

This is a value returned by the API service Ram Tst_ Get Test Algorithm().

Data type used to identify a set of configuration parameters for a test algorithm.

Configuration data structure of the Ram Tst module.

This is a status value returned by the API service Ram Tst_ Get Execution Status().

Data type used to identify or count RAM blocks given in the test configuration parameters.

Data type of number of tested RAM cells

This is a status value returned by the API service Ram Tst_ Get Test Result().

클러스터 가이드AI 생성

구조화된 NVRAM 블록 및 추상화 드라이버를 통해 하드웨어 독립적으로 영구 데이터를 보존하고 관리합니다.
AI 생성 미검증 모델: gemini-3.8-flash-medium · 노력: medium · 온도: 제어 불가 · 프롬프트: 34f2477a24b6 출처 열린 질문 (1)
인과 앵커: R20-11 R20-11부터 유효 이 사양 릴리스용으로 새로 합성되었습니다.
독일어 가이드에서 번역됨gemini-3.8-flash-low · 2026-10-13 · 독일어 원문

구조화된 NVRAM 블록 및 추상화 드라이버를 통해 하드웨어 독립적으로 영구 데이터를 보존하고 관리합니다.

'Memory Services' 모듈 클러스터는 NVRAM Manager 및 하드웨어 추상화 모듈인 MemIf, Fee, Ea를 통해 비휘발성 애플리케이션 데이터의 하드웨어 독립적 저장 및 일관성 보장을 구현합니다([SWS_NvM_00447], [SWS_MemIf_00039]). 비동기 읽기 및 쓰기 작업은 주기적인 MainFunctions를 통해 처리되며 전자 제어 장치(ECU) 시작(NvM_ReadAll) 및 셧다운(NvM_WriteAll) 시 일괄 실행됩니다 ModemanagementGuide 54쪽. 하드웨어 오류 발생 시에는 DEM([SWS_NvM_00470])에 대한 자동 보고와 함께 다단계 재시도, 중복성 및 ROM 복구 메커니즘이 작동합니다.

'Memory Services' 클러스터는 AUTOSAR Classic BSW 스택에서 비휘발성 데이터의 영구 저장 및 관리를 제공합니다. 이는 서비스 레벨의 NVRAM Manager([SWS_NvM_00447])와 하드웨어 추상화 레벨의 Flash EEPROM Emulation([SWS_Fee_00085]) 및 EEPROM Abstraction([SWS_Ea_00083]) 모듈이 포함된 Memory Abstraction 인터페이스([SWS_MemIf_00039])로 구성됩니다 AUTOSAR SWS NVRAMManager 10쪽.

MemoryServices cluster_app Applikation & BSW-Nutzer cluster_services Services Layer cluster_abstraction Memory Hardware Abstraction Layer cluster_mcal Microcontroller Abstraction Layer (MCAL) SWC Software-Komponenten (SW-C) NvM NVRAM Manager (NvM) SWC->NvM NvM_WriteBlock / ReadBlock DEM Diagnostic Event Manager (DEM) DEM->NvM NvM_GetErrorStatus / ReadBlock MemIf Memory Abstraction Interface (MemIf) NvM->MemIf MemIf_Write / Read / Cancel Fee Flash EEPROM Emulation (Fee) MemIf->Fee Fee_Write / Read (Device 0) Ea EEPROM Abstraction (Ea) MemIf->Ea Ea_Write / Read (Device 1) Fls Flash Driver (Fls) Fee->Fls Fls_Write / Read Eep EEPROM Driver (Eep) Ea->Eep Eep_Write / Read

아키텍처 다이어그램: Memory Services 클러스터의 계층 구조 및 모듈 관계. 출처: [SWS_MemIf_00039], AUTOSAR SWS NVRAMManager 10쪽

데이터 교환은 동기 제어 API와 비동기 쓰기 및 읽기 작업을 통해 수행됩니다. 데이터는 영구 RAM 블록을 통해 암시적으로 교환되거나 모듈 관리 RAM 미러를 통해 명시적으로 교환됩니다([SWS_NvM_00455], [SWS_NvM_00514]) NVDataHandling 12쪽. 대기열에 등록된 작업의 주기적 처리는 주기적으로 실행되는 BSW 메인 함수를 통해 수행되며(NvM_MainFunction, Fee_MainFunction), MemIf는 호출을 하위 드라이버에 상태 비저장 방식으로 위임합니다([SWS_MemIf_00040]) AUTOSAR CP SWS FlashEEPROMEmulation 42쪽.

작동 주기 동안 BswM은 멀티 블록 동작을 조정합니다. 시스템 시작 시 NvM_ReadAll은(는) NV 메모리의 영구 데이터를 RAM으로 읽어 들이고([SWS_NvM_00460]), 셧다운 시에는 NvM_WriteAll이(가) 변경된 데이터를 저장합니다([SWS_NvM_00461]) ModemanagementGuide 54쪽. 잘못된 읽기 또는 쓰기 접근은 재시도와 중복 복사본 또는 ROM 폴백 값을 통해 처리되며, 지속적인 오류는 시스템이 DEM에 보고합니다([SWS_NvM_00470], [SWS_NvM_00279]) ErrorDescription 62쪽.

시스템 아키텍처 & 모듈 클러스터의 역할

AUTOSAR Classic Platform의 메모리 서비스(Memory Services) 모듈 클러스터는 비휘발성 메모리 내 애플리케이션 및 기본 소프트웨어 데이터의 표준화되고 하드웨어 독립적인 관리 및 영속화를 보장합니다. 이 클러스터는 AUTOSAR 기본 소프트웨어 아키텍처의 두 개 계층으로 수직 분할됩니다. 즉, 서비스 계층(Services Layer)의 NVRAM Manager([SWS_NvM_00447])와 하드웨어 추상화 계층(Memory Hardware Abstraction Layer)의 Flash EEPROM Emulation([SWS_Fee_00085]) 및 EEPROM Abstraction([SWS_Ea_00083]) 하위 추상화 모듈을 포함하는 Memory Abstraction Interface([SWS_MemIf_00039])입니다 AUTOSAR SWS NVRAMManager 10쪽.

NVRAM Manager(NvM)는 소프트웨어 컴포넌트(SW-C)뿐만 아니라 Diagnostic Event Manager 모듈(Dem)과 같은 BSW 모듈의 중앙 진입점을 형성합니다 SWS DiagnosticEventManager 238쪽. 이는 비휘발성 메모리의 NV 블록, 휘발성 메모리의 RAM 블록, 그리고 초기화 데이터를 위한 선택적 ROM 블록으로 구성되는 논리적 메모리 블록을 관리합니다([SWS_NvM_00137], [SWS_NvM_00128]). 요구 사항에 따라 native(NVM_BLOCK_NATIVE), redundant(NVM_BLOCK_REDUNDANT) 또는 dataset(NVM_BLOCK_DATASET) 블록 관리 유형이 지원됩니다 AUTOSAR CP RS MemoryServices 10쪽.

모듈 Fee 및 Ea은(는) 각 물리적 저장 매체(Flash 또는 EEPROM)의 특성을 캡슐화하고 논리 블록 번호와 주소 오프셋을 각 MCAL 드라이버(Fls 또는 Eep)의 선형 주소 공간에 매핑합니다([SWS_Fee_00087], [SWS_Ea_00086]) AUTOSAR SWS EEPROMAbstraction 23쪽. 여기서 모듈 MemIf은(는) 자체 버퍼 구조를 유지하지 않고 매개변수 DeviceIndex을(를) 기반으로 대상 모듈에 접근을 전달하는 순수 라우팅 계층 역할을 합니다([SWS_MemIf_00040]).

MemoryServices cluster_app Applikation & BSW-Nutzer cluster_services Services Layer cluster_abstraction Memory Hardware Abstraction Layer cluster_mcal Microcontroller Abstraction Layer (MCAL) SWC Software-Komponenten (SW-C) NvM NVRAM Manager (NvM) SWC->NvM NvM_WriteBlock / ReadBlock DEM Diagnostic Event Manager (DEM) DEM->NvM NvM_GetErrorStatus / ReadBlock MemIf Memory Abstraction Interface (MemIf) NvM->MemIf MemIf_Write / Read / Cancel Fee Flash EEPROM Emulation (Fee) MemIf->Fee Fee_Write / Read (Device 0) Ea EEPROM Abstraction (Ea) MemIf->Ea Ea_Write / Read (Device 1) Fls Flash Driver (Fls) Fee->Fls Fls_Write / Read Eep EEPROM Driver (Eep) Ea->Eep Eep_Write / Read

아키텍처 다이어그램: Memory Services 클러스터의 계층 구조 및 모듈 관계. 출처: [SWS_MemIf_00039], AUTOSAR SWS NVRAMManager 10쪽

모듈 간 상호작용 & 인터랙션 경로

모듈 간의 상호작용은 엄격하게 표준화된 동기 및 비동기 경로를 통해 이루어집니다. 사용자가 NvM_WriteBlock을(를) 통해 쓰기 작업을 시작하면 요청은 먼저 NvM의 관리 블록에 등록됩니다([SWS_NvM_00455]). 동기 호출의 경우 MemIf_Write을(를) 통해 MemIf(으)로 전달되며([SWS_MemIf_00040]), 이는 해당 호출을 Fee_Write 또는 Ea_Write에 넘깁니다([SWS_Fee_00088], [SWS_Ea_00087]) AUTOSAR SWS NVRAMManager 160쪽.

애플리케이션과 NVRAM Manager 간의 데이터 유지 및 동기화와 관련하여 두 가지 핵심 개념이 존재합니다. 영구 RAM 블록을 통한 암시적 동기화(NvMRamBlockDataAddress)와 미러 기반 버퍼를 통한 명시적 동기화(NvMBlockUseSyncMechanism)입니다 NVDataHandling 12쪽. 명시적 동기화의 경우 NvM은 구성된 콜백 루틴 NvMWriteRamBlockToNvCallback 또는 NvMReadRamBlockFromNvCallback을(를) 통해 애플리케이션 RAM과 내부 RAM 미러 간에 페이로드를 복사합니다([SWS_NvM_00514], [SWS_NvM_00515]) EXP NVDataHandling 30쪽.

데이터셋 블록(NVM_BLOCK_DATASET)을 사용할 때 호출자는 사전에 NvM_SetDataIndex을(를) 통해 원하는 데이터셋 인덱스를 선택합니다([SWS_NvM_00448]). 그런 다음 추상화 모듈은 논리 블록 번호와 인덱스로부터 MCAL 드라이버를 위한 정확한 주소 오프셋을 계산합니다([SWS_NvM_00123]) AUTOSAR SWS Flash EEPROM Emulation 21쪽. 취소 요청은 MemIf_Cancel을(를) 통해 하위 모듈 Fee_Cancel 또는 Ea_Cancel(으)로 직접 전달됩니다([SWS_MemIf_00041], [SWS_Fee_00089]).

Memory Services 클러스터 내의 비동기 쓰기 작업NvM UserNvMMemIfFee / EaBSW TaskNvM_WriteBlock(BlockId, DataPtr)Auftrag in Queue registrieren상태를 NVM_REQ_PENDING으로 설정E_OKUse Case: Zyklische Bearbeitung in MainFunctionNvM_MainFunction()MemIf_Write(DeviceIndex, BlockNum, DataPtr)Fee_Write / Ea_Write(...)E_OKE_OK복귀Use Case: Abschluss & BenachrichtigungNvM_MainFunction()Job-Ergebnis auswerten (MEMIF_JOB_OK)Blockstatus aktualisierenSingleBlockCallback(BlockId, NVM_REQ_OK)복귀NvM_GetErrorStatus(BlockId, &RequestResult)NVM_REQ_OK

시퀀스 다이어그램: 콜백 알림 및 폴링을 사용하는 비동기 쓰기 작업. 출처: [SWS_NvM_00455], AUTOSAR SWS NVRAMManager 160쪽

동기화, 재진입성 및 태스크 컨텍스트

NvM_GetErrorStatus([SWS_NvM_00451]), NvM_SetBlockProtection([SWS_NvM_00450]), MemIf_GetVersionInfo([SWS_MemIf_00045])을(를) 포함하여 클러스터의 대부분의 제어 및 상태 API는 동기식으로 구현되며 호출자의 태스크 컨텍스트에서 직접 처리될 수 있습니다 AUTOSAR SWS NVRAMManager 157쪽. 반면에 데이터 전송 함수(NvM_ReadBlock, NvM_WriteBlock, Ea_Write)는 비동기식이며 재진입이 불가능하도록 설계되었습니다([SWS_MemIf_00040], [SWS_Ea_00087]).

진행 중인 작업의 주기적 업데이트는 Schedule Manager(SchM) 또는 BSW 태스크에 의해 주기적으로 호출되는 메인 함수 NvM_MainFunction 및 Fee_MainFunction의 담당입니다 AUTOSAR CP SWS FlashEEPROMEmulation 42쪽. MCAL 드라이버의 비동기 메시지의 경우 알림 Fee_JobEndNotification 또는 Fee_JobErrorNotification이(가) 인터럽트 레벨에서 직접 발생할 수 있습니다([SWS_Fee_00095]). 이는 상태를 MEMIF_JOB_OK(으)로 설정하거나 구성된 알림 루틴을 호출합니다([SWS_Fee_00142], [SWS_Fee_00194]) SWS FlashEEPROMEmulation 37쪽.

해석: 태스크 레벨의 API 호출자와 MainFunctions의 단계적 추가 처리 간의 경쟁 상태를 방지하기 위해 내부 대기열과 관리 속성은 독점 영역으로 보호될 것으로 보이며, MemIf는 상태 비저장 전달 계층으로 작동합니다 AUTOSAR SWS NVRAMManager 160쪽. 질문 Q-a50c3362a14b9e6d (열림)

일반적인 수명 주기 및 동작 모드

클러스터의 수명 주기는 Basic Software Mode Manager(BswM)와 ECU State Manager(EcuM)에 의해 밀접하게 오케스트레이션됩니다. ECU 시작(Startup Phase) 동안 드라이버 다음으로 추상화 모듈이 Fee_Init 또는 Ea_Init([SWS_Fee_00085], [SWS_Ea_00083])을(를) 통해 먼저 동기 초기화된 후, NVRAM Manager가 NvM_Init([SWS_NvM_00447])을(를) 통해 동기 초기화됩니다 AUTOSAR SWS NVRAMManager 156쪽.

초기화에 이어 BswM은 영구로 표시된 모든 RAM 블록을 비휘발성 메모리에서 복원하기 위해 멀티 블록 읽기 작업 NvM_ReadAll을(를) 트리거합니다([SWS_NvM_00460]) ModemanagementGuide 54쪽. NvM은 콜백 함수 BswM_NvM_CurrentJobMode을(를) 통해 진행 상황과 최종 결과를 BswM에 다시 보고합니다([SWS_NvM_00745], [SWS_NvM_00888]). 개별 블록 상태는 BswM_NvM_CurrentBlockMode을(를) 통해 시그널링됩니다([SWS_NvM_00746], [SWS_NvM_00890]) ModemanagementGuide 28쪽.

셧다운 단계에서 시스템은 NvM_WriteAll을(를) 통해 수정된 모든 RAM 블록을 NV 메모리로 영구 다시 쓰도록 지시합니다([SWS_NvM_00461]). Flash 쓰기 주기 횟수를 최적화하기 위해 NvM_SetRamBlockStatus을(를) 통해 블록이 수정되었는지 여부를 지정하여 표시할 수 있습니다([SWS_NvM_00453]) EXP NVDataHandling 18쪽. 조기 웨이크업 이벤트가 발생할 경우 진행 중인 쓰기 프로세스를 NvM_CancelWriteAll을(를) 통해 취소할 수 있습니다([SWS_NvM_00238]) AUTOSAR SWS NVRAMManager 161쪽.

오류 처리, DET 추적 및 성능 저하

클러스터는 다단계 오류 감지 및 디그레이디션 개념을 갖추고 있습니다. 드라이버 및 추상화 레벨에서 발생하는 오류는 반환 상태 MEMIF_JOB_FAILED을(를) MemIf_GetJobResult을(를) 통해 쿼리하거나 NvM_JobErrorNotification을(를) 통해 보고됩니다([SWS_Fee_00091], [SWS_Ea_00095]) ErrorDescription 49쪽.

읽기 오류가 발생하면 NvM은 구성된 복구 메커니즘을 사용합니다. 먼저 재시도(Read Retries)가 수행됩니다([SWS_NvM_00390]). 이것이 실패하면 중복 블록(NVM_BLOCK_REDUNDANT)의 경우 중복 복사본을 읽습니다([SWS_NvM_00171], [SWS_NvM_00531]). 여기서 중복성 손실이 감지되면 NvM은 작업 결과를 NVM_REQ_REDUNDANCY_FAILED(으)로 설정하고 프로덕션 오류 NVM_E_LOSS_OF_REDUNDANCY을(를) DEM에 보고합니다([SWS_NvM_00470], [SWS_NvM_00546]) ErrorDescription 62쪽.

ROM 기본값을 통한 복구에 성공하면 NvM은 결과 NVM_REQ_RESTORED_FROM_ROM을(를) 보고합니다([SWS_NvM_00470]). 모든 복구 조치가 실패하면 NVM_E_REQ_FAILED이(가) DEM에 보고되고([SWS_NvM_00279], [SWS_NvM_00288]) 쿼리 결과가 NVM_REQ_NOT_OK(으)로 설정됩니다([SWS_NvM_00451]). 쓰기 오류가 발생하면 NvM은 요청이 취소되기 전에 쓰기 재시도(NvMMaxNumOfWriteRetries)를 제어합니다([SWS_NvM_00168], [SWS_NvM_00213]) ErrorDescription 56쪽.

이 가이드는 Memory Services 클러스터의 핵심 아키텍처, 모듈 상호작용 및 오류 메커니즘을 요약합니다. 모든 정보는 AUTOSAR Classic Platform의 규범적 사양을 기반으로 합니다.

Module im Cluster

Bulk NvData Manager (BndM)

AUTOSAR Classic Memory Services-Modul Bulk NvData Manager (BndM, Spezifikation: AUTOSAR_CP_SWS_BulkNvDataManager.pdf, AUTOSAR_SWS_BulkNvDataManager.pdf).

BSW ID 23 8 APIs (5 Funktionen, 3 Typen) #include "BndM.h"

EEPROM Abstraction (Ea)

Provides uniform access to external and internal EEPROM devices.

BSW ID 40 16 APIs (15 Funktionen, 1 Typen) #include "Ea.h"

EEPROM Driver (Eep)

AUTOSAR Classic Memory Drivers-Modul EEPROM Driver (Eep, Spezifikation: AUTOSAR_CP_SWS_EEPROMDriver.pdf, AUTOSAR_SWS_EEPROMDriver.pdf, AUTOSAR_SWS_EEPROM_Driver.pdf).

BSW ID 90 16 APIs (13 Funktionen, 3 Typen) #include "Eep.h"

Flash EEPROM Emulation (Fee)

Provides emulation of EEPROM-like data blocks on Flash memory devices.

BSW ID 21 16 APIs (15 Funktionen, 1 Typen) #include "Fee.h"

Flash Driver (Fls)

AUTOSAR Classic Memory Drivers-Modul Flash Driver (Fls, Spezifikation: AUTOSAR_CP_SWS_FlashDriver.pdf, AUTOSAR_SWS_FlashDriver.pdf).

BSW ID 92 17 APIs (14 Funktionen, 3 Typen) #include "Fls.h"

Flash Test (FlsTst)

AUTOSAR Classic Memory Drivers-Modul Flash Test (FlsTst, Spezifikation: AUTOSAR_CP_SWS_FlashTest.pdf, AUTOSAR_SWS_FlashTest.pdf).

BSW ID 104 16 APIs (16 Funktionen, 0 Typen) #include "FlsTst.h"

Memory Driver (Mem)

AUTOSAR Classic Memory Drivers-Modul Memory Driver (Mem, Spezifikation: AUTOSAR_CP_SWS_MemoryDriver.pdf, AUTOSAR_SWS_MemoryDriver.pdf).

BSW ID 91 20 APIs (13 Funktionen, 7 Typen) #include "Mem.h"

Memory Access (MemAcc)

AUTOSAR Classic Memory HW Abstraction-Modul Memory Access (MemAcc, Spezifikation: AUTOSAR_CP_SWS_MemoryAccess.pdf, AUTOSAR_SWS_MemoryAccess.pdf).

BSW ID 41 39 APIs (22 Funktionen, 17 Typen) #include "MemAcc.h"

Memory Abstraction Interface (MemIf)

Abstracts underlying Flash and EEPROM memory drivers.

BSW ID 22 12 APIs (9 Funktionen, 3 Typen) #include "MemIf.h"

NVRAM Manager (NvM)

Provides synchronous and asynchronous block-based data management for non-volatile storage (EEPROM, Flash).

BSW ID 20 36 APIs (30 Funktionen, 6 Typen) #include "NvM.h"

RAM Test (RamTst)

AUTOSAR Classic Memory Drivers-Modul RAM Test (RamTst, Spezifikation: AUTOSAR_CP_SWS_RAMTest.pdf, AUTOSAR_SWS_RAMTest.pdf, AUTOSAR_SWS_RAM_Test.pdf).

BSW ID 93 20 APIs (20 Funktionen, 0 Typen) #include "RamTst.h"