Memory Access (MemAcc)

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

Service to return the version information of the MemAcc module.

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

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.

Returns the consolidated job result of the address area referenced by 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.

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

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.

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.

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.

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.

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

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.

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.

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

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

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

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

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

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

Returns the status of the MemAcc job referenced by addressAreaId.

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.

Unique address area ID type.

Logical memory address type.

Postbuild configuration structure type.

General data type.

Job length type.

Index type for Mem driver hardware specific service table.

Asynchronous job status type.

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

Type for asynchronous jobs.

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

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

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

Asynchronous job result type.

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

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

Function pointer for the Mem_JobResultType 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_Write service for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

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_PropagateError service for the invocation of the Mem driver API via function pointer interface.

Function pointer for the Mem_BlankCheck 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_Resume service for the invocation of the Mem driver API via function pointer interface. Tags: atp.Status=draft

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

Memory driver instance ID type

Memory driver configuration structure type

Physical memory device address type

Physical memory device length type

Asynchronous job result type

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

General data type

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

The MemAcc module shall check static configuration param- eters statically (at the latest during compile time) for correctness.

The MemAcc module shall split memory access requests for the Mem driver layer according to page/page burst, respectively sector/sector burst sizes.

In case the start address or the length of a memory request is not aligned to the physical segmentation of the respective memory device, MemAcc shall reject such job requests with E_NOT_OK .

If MemAccNumberOfEraseRetries is set to a value > 0, MemAcc shall retry the Mem driver erase operation according to the configured value if the Mem driver erase operation resulted in MEM_JOB_FAILED .

The MemAcc module shall coordinate conflicting memory accesses by multiple upper layers.

{DRAFT} The MemAcc module shall only coordinate conflict- ing resource accesses. The access dependencies shall be configurable in the config- uration tool.

The MemAcc module shall support multiple memory access requests from different upper layers for distinct memory areas at the same time. In case there is a hardware resource conflict, the memory stack shall still accept the access request and process it once the resource is free.

All MemAcc services, i.e. erase, read and write, shall sup- port access requests which cross memory device boundaries based on the logical/- physical memory mapping.

Based on MemAccAddressAreaPriority , MemAcc shall prioritize memory access requests from AUTOSAR BSW upper layer modules.

If a job end notification function is configured by MemAc- cJobEndNotificationName , MemAcc shall notify the upper layer BSW module by calling the configured notification function.

If the MemAcc module is not able to process a job request, e.g. due to a pending request on the same address area or due to an invalid parameter, the job request shall be rejected by an E_NOT_OK return code.

The MemAcc module shall allow only one job request per address area.

Once a job request was accepted, the job processing status shall be set to MEMACC_JOB_PENDING .

In case the last memory operation was canceled, the job result shall be set to MEMACC_MEM_CANCELED .

The prioritization of memory operations shall use the Mem_Suspend and Mem_Resume service if the memory hardware supports this func- tionality. If the memory hardware does not support a suspend/resume functionality, the prior- itization shall be implemented on a page/page burst, respectively sector/sector burst basis.

The service MemAcc_Init shall initialize the MemAcc mod- ule internal states. If MemAccMemInvocation is set to INDIRECT_DYNAMIC or INDIRECT_STATIC , MemAcc_Init shall also initialize all available Mem drivers by calling the Mem driver's individual initialization functions.

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_GetVersionInfo shall raise the development error MEMACC_E_PARAM_POINTER if the argument is a NULL pointer.

When the MemAcc_Cancel service is called by an upper layer, the MemAcc module shall wait for the completion of a pending Mem job and stop further processing of the current MemAcc job.

In case no MemAcc job is pending, the MemAcc_Cancel service shall just return without any further action, i.e., the result of the last MemAcc job shall not be affected.

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_Cancel shall check that the MemAcc module has been initialized. If this check fails, MemAcc_Cancel shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_Cancel shall check that the provided addres- sAreaId is consistent with the configuration. If this check fails, MemAcc_Cancel shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_GetJobResult shall check that the MemAcc module has been initialized. If this check fails, MemAcc_GetJobResult shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAccDevErrorDetect , the service MemAcc_GetJobResult shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_GetJobResult shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_GetMemoryInfo shall check that the MemAcc module has been initialized. If this check fails, MemAcc_GetMemoryInfo shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_GetMemoryInfo shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_GetMemoryInfo shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_GetMemoryInfo shall raise the development er- ror MEMACC_E_PARAM_POINTER if the memoryInfoPtr argument is a NULL pointer.

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_GetProcessedLength shall check that the MemAcc module has been initialized. If this check fails, MemAcc_GetProcess- edLength shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_GetProcessedLength shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_GetProcessedLength shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_GetJobInfo shall check that the MemAcc module has been initialized. If this check fails, MemAcc_GetJobInfo shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAccDevErrorDetect , the service MemAcc_GetJobInfo shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_GetJobInfo shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_GetJobInfo shall raise the development error MEMACC_E_PARAM_POINTER if the memoryInfoPtr argument is a NULL pointer.

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_Read shall check that the MemAcc module has been initialized. If this check fails, MemAcc_Read shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Read shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_- Read shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Read shall raise the development error MEMACC_E_PARAM_POINTER if the destinationDataPtr argument is a NULL pointer.

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Read shall raise the development error MEMACC_E_PARAM_ADDRESS_LENGTH if the address range defined by sourceAd- dress and length is invalid, i.e. not aligned to MemReadPageSize or exceeds the configured area.

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Read shall raise the development error MEMACC_E_BUSY if a previous MemAcc job for the same addressAreaId is still being processed.

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_Write shall check that the MemAcc module has been initialized. If this check fails, MemAcc_Write shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Write shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_- Write shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Write shall raise the development error MEMACC_E_PARAM_POINTER if the sourceDataPtr argument is a NULL pointer.

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Write shall raise the development error MEMACC_E_PARAM_ADDRESS_LENGTH if the address range defined by targetAd- dress and length is invalid, i.e. not aligned to MemWritePageSize or exceeds the configured area.

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_Write shall raise the development error MEMACC_E_BUSY if a previous MemAcc job for the same addressAreaId is still being processed.

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_Erase shall check that the MemAcc module has been initialized. If this check fails, MemAcc_Erase shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Erase shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_- Erase shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Erase shall raise the development error MEMACC_E_PARAM_ADDRESS_LENGTH if the address range defined by targetAd- dress and length is invalid, i.e. not aligned to MemEraseSectorSize or exceeds the configured area.

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_Erase shall raise the development error MEMACC_E_BUSY if a previous MemAcc job for the same addressAreaId is still being processed.

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_Compare shall check that the MemAcc module has been initialized. If this check fails, MemAcc_Compare shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Compare shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_- Compare shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_Compare shall raise the development error MEMACC_E_PARAM_POINTER if the dataPtr argument is a NULL pointer.

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_Compare shall raise the development error MEMACC_E_PARAM_ADDRESS_LENGTH if the address range defined by sourceAddress and length is invalid, i.e. not aligned to MemReadPageSize .

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_Compare shall raise the development error MEMACC_E_BUSY if a previous MemAcc job for the same addressAreaId is still being processed.

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_BlankCheck shall check that the MemAcc module has been initialized. If this check fails, MemAcc_BlankCheck shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAccDevErrorDetect , the service MemAcc_BlankCheck shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_BlankCheck shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_BlankCheck shall raise the development error MEMACC_E_PARAM_ADDRESS_LENGTH if the address range defined by sourceAd- dress and length is invalid, i.e. not aligned to MemReadPageSize .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_BlankCheck shall raise the development error MEMACC_E_BUSY if a previous MemAcc job for the same addressAreaId is still being processed.

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_HwSpecificService shall check that the MemAcc module has been initialized. If this check fails, MemAcc_HwSpecificSer- vice shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_HwSpecificService shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_HwSpecificService shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAc- cDevErrorDetect , the service MemAcc_HwSpecificService shall raise the development error MEMACC_E_PARAM_HW_ID if the Mem driver hardware identifi- cation given by hwId is invalid or not assigned to the passed addressAreaId .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_HwSpecificService shall raise the develop- ment error MEMACC_E_BUSY if a previous MemAcc job for the same addressAreaId is still being processed.

If development error detection is enabled by MemAccDevErrorDetect , the service MemAcc_RequestLock shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_RequestLock shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_RequestLock shall raise the development error MEMACC_E_PARAM_POINTER if the lockNotificationFctPtr argument is a NULL pointer.

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_RequestLock shall raise the development error MEMACC_E_PARAM_ADDRESS_LENGTH if the address range defined by address and length is invalid, i.e. not mapped to a specific Mem driver.

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_ReleaseLock shall check that the MemAcc module has been initialized. If this check fails, MemAcc_ReleaseLock shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_ReleaseLock shall raise the development error MEMACC_E_PARAM_ADDRESS_LENGTH if the address range defined by address and length is invalid, i.e. not mapped to a specific Mem driver.

An address area shall only be assigned to one upper layer module.

Within a sub-address area, only a uniform sector size is allowed.

Start address and length of address areas shall be aligned to the physical sectors.

The MemAcc module shall support address areas larger than 4GBytes, thus MemAcc_AddressType and MemAcc_LengthType shall be defined as a 64-Bit types in case the address area configuration of one address area exceeds 4GBytes.

If all address areas don't exceed 4GBytes, MemAcc_Ad- dressType and MemAcc_LengthType shall be defined as a 32-Bit types.

The MemAcc module implementation shall be hardware in- dependent.

If MemAccMemInvocation is set to INDIRECT_DYNAMIC or INDIRECT_STATIC , MemAcc shall call all Mem main functions within MemAcc_- MainFunction . MemAcc_MainFunction shall only call the Mem main function if there is a job request pending for the corresponding Mem driver.

If enabled by MemAccUseMemFuncPtrTable , MemAcc shall call the Mem driver service functions via the Mem driver function pointer table. Otherwise the MemAcc shall directly call the Mem driver service functions.

If enabled by MemAccUseEraseBurst , MemAcc shall align and split the Mem driver erase requests according to the erase burst size of the Mem driver.

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_ActivateMem shall check that the MemAcc module has been initialized. If this check fails, MemAcc_ActivateMem shall raise the development error MEMACC_E_UNINIT .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_ActivateMem shall ensure the validity of the Mem driver binary by checks in the following sequence: 1. Comparing the header address field with the start address of the Mem driver binary (if the Mem driver was not compiled as a relocatable binary) 2. Unique ID validity 3. Availability and consistency of the delimiter field If any of these checks fails MemAcc_ActivateMem shall raise the development error MEMACC_E_MEM_INIT_FAILED .

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_DeactivateMem shall check that the MemAcc module has been initialized. If this check fails, MemAcc_DeactivateMem shall raise the development error MEMACC_E_UNINIT .

The service MemAcc_GetJobResult shall return the con- solidated result of the last MemAcc job.

If development error detection is enabled by MemAccDevErrorDetect , the service MemAcc_ReleaseLock shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_ReleaseLock shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

The MemAcc module implementation shall support multiple Mem drivers.

If development error detection is enabled by MemAccDe- vErrorDetect , the service MemAcc_RequestLock shall check that the MemAcc module has been initialized. If this check fails, MemAcc_RequestLock shall raise the development error MEMACC_E_UNINIT .

If MemAccNumberOfWriteRetries is set to a value > 0, MemAcc shall retry the Mem driver write operation according to the configured value if the Mem driver write operation resulted in MEM_JOB_FAILED .

If enabled by MemAccUseReadBurst , MemAcc shall align and split the Mem driver read requests according to the read burst size of the Mem driver.

If enabled by MemAccUseWriteBurst , MemAcc shall align and split the Mem driver write requests according to the write burst size of the Mem driver.

In case the job processing was completed or no job is currently pending, the job processing status shall be set to MEMACC_JOB_IDLE .

In case the job processing was completed successfully, the job result shall be set to MEMACC_MEM_OK .

In case the job processing was completed but the re- sults of the last MemAcc job didn't meet the expected result, e.g. a blank check operation was applied on a non-blank memory area, the job result shall be set to MEMACC_MEM_INCONSISTENT .

In case the last memory operation was completed but the ECC circuit corrected an ECC error, the job result shall be set to MEMACC_MEM_ECC_CORRECTED .

In case the last memory operation didn't com- plete due to an uncorrectable ECC error, the job result shall be set to MEMACC_MEM_ECC_UNCORRECTED .

In case the memory operation was not successfully com- pleted for any other reason, the job result shall be set to MEMACC_MEM_FAILED .

The service MemAcc_DeInit shall de-initialize the MemAcc module internal states. If MemAccMemInvocation is set to INDIRECT_DYNAMIC or INDIRECT_STATIC , MemAcc_DeInit shall also de-initialize all available Mem drivers by calling the Mem driver's individual de-initialization functions.

After initialization via the MemAcc_Init service, the job result shall be set to MEMACC_MEM_OK .

After initialization via the MemAcc_Init service, the job precessing status shall be set to MEMACC_JOB_IDLE .

If the compare operation determined a mismatch, the result code returned by the MemAcc_GetJobResult service shall be set to MEMACC_MEM_INCONSISTENT , otherwise MemAcc_GetJobResult shall return MEMACC_MEM_OK .

MemAcc_RequestLock shall lock all memory accesses of the Mem driver referenced by the addressAreaId , address and length parameter. If an upper layer calls a MemAcc service function for an address area which is locked for direct memory access, MemAcc shall still accept the memory access request for the address area but shall not forward the access request to the corresponding Mem driver until the lock request is released by the MemAcc_ReleaseLock service.

MemAcc shall wait until the address area referenced by addressAreaId is idle before it calls the lock notification function referenced by lockNotificationFctPtr to notify the upper layer module that the lock of the address area was successfully acquired.

If development error detection is enabled by MemAccDev- ErrorDetect , the service MemAcc_GetJobStatus shall check that the MemAcc module has been initialized. If this check fails, MemAcc_GetJobStatus shall raise the development error MEMACC_E_UNINIT .

The service MemAcc_GetJobStatus shall return MEMACC_JOB_IDLE for the referenced addressAreaId if MemAcc is not pro- cessing a job request.

The service MemAcc_GetJobStatus shall return MEMACC_JOB_PENDING for the referenced addressAreaId if MemAcc is cur- rently processing a job request.

The service MemAcc_GetProcessedLength shall return the processed length of the current MemAcc job referenced by addressAreaId . If the job finished successfully, MemAcc_GetProcessedLength shall return the requested job length of the finished job until a new MemAcc job request is received for the referenced addressAreaId .

If MemAccMemInvocation is set to INDIRECT_DYNAMIC , the service MemAcc_ActivateMem shall initialize the Mem driver referenced by hwId and headerAddress and update the internal driver activation state.

If MemAccMemInvocation is set to INDIRECT_DYNAMIC , the service MemAcc_DeactivateMem shall de-initialize the Mem driver referenced by hwId and headerAddress and update the internal driver activation state.

In case a MemAcc job is still pending, the service MemAcc_DeactivateMem shall return E_NOT_OK without any further action.

If development error detection is enabled by MemAccDevErrorDetect , the service MemAcc_GetJobStatus shall check that the provided addressAreaId is consistent with the configuration. If this check fails, MemAcc_GetJobStatus shall raise the development error MEMACC_E_PARAM_ADDRESS_AREA_ID .

Det_ReportError Det.h Service to report development errors.

Mem_BlankCheck Mem.h 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_GetJob Result 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. Mem_Erase Mem.h 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. Mem_GetJobResult Mem.h Service to return results of the most recent job. Mem_HwSpecificService (draft) Mem.h 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_GetJob Result 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 Mem_Init Mem.h Initialization function - initializes all variables and sets the module state to initialized. Mem_MainFunction Mem.h Service to handle the requested jobs and the internal management operations. Mem_PropagateError Mem.h 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.. Mem_Read Mem.h 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. Mem_Write Mem.h 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.

Module Header File Imported Type Mem.h Mem_AddressType Mem.h Mem_ConfigType Mem.h Mem_DataType Mem.h Mem_HwServiceIdType Mem.h Mem_InstanceIdType Mem.h Mem_JobResultType Mem Mem.h Mem_LengthType Std_Types.h Std_ReturnType Std Std_Types.h Std_VersionInfoType

Type of error Related error code Error value API service called without module initialization MEMACC_E_UNINIT 0x01 API service called with NULL pointer argument MEMACC_E_PARAM_POINTER 0x02 API service called with wrong address area ID MEMACC_E_PARAM_ADDRESS_AREA_ID 0x03 API service called with address and length not belonging to the passed address area ID MEMACC_E_PARAM_ADDRESS_LENGTH 0x04 API service called with a hardware ID not belonging to the passed address area ID MEMACC_E_PARAM_HW_ID 0x05 API service called for an address area ID with a pending job request MEMACC_E_BUSY 0x06 Dynamic MEM driver activation failed due to inconsistent MEM driver binary MEMACC_E_MEM_INIT_FAILED 0x07

Overlayed return value of Std_ReturnType for Mem driver API