Remote update block gives pof_error...

weird - i replied before but i don't see my reply now.

We have a scripted flow:

set_global_assignment -name STRATIXIII_UPDATE_MODE REMOTE

set_global_assignment -name STRATIXIII_CONFIGURATION_SCHEME "ACTIVE SERIAL"

set_global_assignment -name USE_CONFIGURATION_DEVICE ON

set_global_assignment -name ON_CHIP_BITSTREAM_DECOMPRESSION ON

set_global_assignment -name STRATIXII_CONFIGURATION_DEVICE EPCS64

It works normally and is well tested. But if/when we get another failing image, I would like to find out why. And to find out, I need to know what altera check when they declare a "POF_error" in their remote update block.

If they are only reading a few bytes in the header, then which bytes is it? And how would that protect against partially loaded designs? I don't think they read the whole file - it all happens too quickly...