In the PRU ICSS EtherCAT user guide, it is said support to write ESI to board QSPI on the fly, but customer verified it, after write from master, the configuration is really changed, but after power cycle, it recover to the original one again, seems it is just wrote to RAM, not to QSPI memory.
NOTE 2: Both EtherCAT applications support non-volatile storage of ESI EEPROM. The application writes the
data into non-volatile QSPI memory only in INIT and PREOP states. This can be disabled or enabled on full featured
application by defining/undefining EEPROM_SPI macro in tiescbsp.h. This feature cannot be modified in limited
demo
I have another question about this, since the full demo need the .h file converted from ESI file to build together, how can this feature works as the app is not build with new ESI file, but the one in QSPI is the new one?
