Fixed NonVolatile Status

This MotoHawk™ block returns the current status of the Fixed NonVolatile memory.

Block ID

motohawk_fnv_status

Library

MotoHawk_lib/Data Storage Blocks

Description

NOTE: that when an application contains no Fixed NonVolatile Manager or Fixed NonVolatile data, this block will always output a status of 254.  

Block Parameters

This MotoHawk™ block has no user-definable parameters. Listed below are the status indicators.

"motohawk_fnv_status_enum" is a script that returns a cell array with the enumeration. It can be used in the Enumeration field of a probe to decode the return value of this block.

NOTE: An implementation may not support all possible status values available.

Value	Description
0: Loading FNV from Factory Defaults to RAM	This is set while performing the copy from factory defaults to the working copy in RAM.
1: Loading FNV to RAM	This is set while performing the copy from Fixed NonVolatile storage to the working copy in RAM .
2: Storing FNV	This is set while performing the copy from the working area in RAM to the FixedNonVolatile storage.
3: FNV Memory Corruption. Loaded Factory Defaults	This occurs when the system detects un-recoverable corruption in the FixedNonVolatile storage area. The system has restored NonVolatile factory defaults.
4: User requested refresh of FNV from Factory Defaults.	This occurs if the user requested that FixedNonVolatile factory defaults be loaded irrespective of their previous state.
5: Successful refresh of FNV values from last power cycle	This is the normal occurrence when the model restarts, and the system was able to reload the FixedNonVolatile values into the working area and no errors occur.
6: Buffered array size does not match. Loaded Factory Defaults	This occurs when using Buffered EEPROM on an applicable Target, and the chosen CRC array size does not match the stored CRC array size. FixedNonVolatile Factory Defaults will be loaded
7: FNV data has been stored successfully.	FixedNonVolatile data has been stored successfully. This occurs when executing the NonVolatile storage command block successfully. On successful completion, power can safely be removed.
8: FNV data store request has failed.	FixedNonVolatile data has FAILED to be stored successfully. This occurs when executing the NonVolatile storage command block unsuccessfully.
9: FNV selectively initialised.	The user can request via the FixedNonVolatileManager that certain FixedNonVolatile data be initialised on first power-up after reprogramming. This state indicates that the FixedNonVolatiles have been successfully loaded with selected variables initialised.
10: FNV values restored from Backup.	This occurs when the system was forced to use a backup copy of FixedNonVolatile data as the primary copy could not be verified (E.g. bad powerdown, memory corruption or device fault).
11: Storing FNV startup flags.	System is currently updating FixedNonVolatile power up flags.
12: FNV Memory read error. Loaded Factory Defaults.	An attempt to read FixedNonVolatile memory has FAILED. Factory Defaults will be loaded.
13: Version Mismatch. Loaded Factory Defaults.	The FixedNonVolatile memory driver software version previously stored in target is incompatible with the driver version of the currently loaded application. The system shall load factory defaults and update stored driver version to match the currently loaded application.
254: FNV status is not available as no data is defined.	This occurs when this block is in an application that contains no Fixed NonVolatile data.