Forum Discussion
FvM
Super Contributor
6 months agoHi,
a .pof file involves different checksum and crc fields. There's an overall crc16 in the two last bytes of the file which is verified when loading the file in programmer. The programmer displays a 32 bit checksum over the total configuration part of the file which may include multiple sectors, e.g. cfm0, cfm1 and ufm for max10, it's apparently only used to distinguish different versions and not stored in the file or verified. Individual sector data may contain additional check fields but they are not documented anywhere as far as I'm aware of. Thus there's no simple way to check configuration data consistency.
a .pof file involves different checksum and crc fields. There's an overall crc16 in the two last bytes of the file which is verified when loading the file in programmer. The programmer displays a 32 bit checksum over the total configuration part of the file which may include multiple sectors, e.g. cfm0, cfm1 and ufm for max10, it's apparently only used to distinguish different versions and not stored in the file or verified. Individual sector data may contain additional check fields but they are not documented anywhere as far as I'm aware of. Thus there's no simple way to check configuration data consistency.