The EtherCAT SubDevice information is generated on the fly and by default is not stored anywhere, it’s simply emulated. However, the SDK provides a set of functions to store the EtherCAT SubDevice information content in a physical storage. Therefore, after a hardware reset the SDK will use the content from the non-volatile memory instead of the content generated on the fly. For detailed implementation overview refer to the file, YOUR_SDK_VERSION_DIRECTORY\examples\industrial_comms\ethercat_subdevice_demo\common\os\freertos\ESL_eeprom.c

For more information on non-volatile memory interface, please refer the page Non-Volatile Memory (NVM).

Function	Description
EC_API_SLV_EEPROM_cbRegisterInit	Register non-volatile memory initialization function
EC_API_SLV_EEPROM_cbRegisterRead	Register non-volatile memory read function
EC_API_SLV_EEPROM_cbRegisterWrite	Register non-volatile memory write function