CvP initialization vs update modes In Cyclone V

One trick that might work is to drive the PCIe reset signal until the device configuration completes.

Then the 100ms constraint no longer applies.

Some on-board logic is needed to ensure that this only happens at power up.

Whether configuration will complete in 100ms also depends on how much 'stuff' you are trying to download.

The is also an issue with using CvP update mode on cyclone V which seriously affects fmax - see AF_CV51026-2013.07.30-PR.

In essence fmax is reduced during reconfig (for the logic that isn't changed) but the tools can only be told to use the slower timings for the entire image.

A related question - does anyone know how easy Altera have made it to generate completely different images with the same periphery, or to rebuild something that will load onto a perephery that was built many months earlier on a different system.

It also seems that 'remote update' and 'CvP' are mutually exclusive options.

This seems strange as the former is (almost) just a power on reset reconfiguration with a few preserved bits.