WriteBlock
Write Block
Description
Request for copying data from the RAM block to its corresponding NvM block. This function queues the write request and returns the acceptance result synchronously. If the block has a CRC, the RAM block CRC will be recalculated before the data and the CRC are written to the NvM memory, even if the service NvM_SetRamBlockStatus() was called before and the configuration was set that within this service, the CRCcalculation should be done. If writing the data to NvM memory fails, the NvM will retry writing. The number of write retries is a configuration option by software.
Request Type |
|---|
| Asynchronous |
Port Description
The following table describes the ports for this block.
Port | Type | Description |
|---|---|---|
CallFunction | Input | Non-functional port to allow designers to show when the function should be called in their model. |
NvM_SrcPtr | Input | Pointer where the data of a non-permanent RAM block shall be read from. |
Return | Output | Standard return E_OK or E_NOT_OK for the function call. |
Mask Description
The following table describes the parameters for this mask.
Parameter | Description |
|---|---|
NvM Block Name | The block name defined in the m-file with the NVM class. |
Cast Function Return to Void | True: Function will be cast as a 'void' function and the return value is ignored. |
Data Store for NvM_SrcPtr | Data store name for use in model testing for the input argument in the function call. |
Data Store for Return | Data store name for use in model testing for the result of the function call. |
Set Output to NULL_PTR | True: NvM_SrcPtr is ignored and NvM will used the configured PIM (permanent address) |
NvM Block Compatibility
The following table describes which NvM block type is compatible with this function.
NvM Block Type | Compatible |
|---|---|
Native | Yes |
Redundant | Yes |
Data Set | Yes |