Does the 'remote update' block actually work on Cyclone V?

I'm trying to get the 'remote update' (ie the reload the fpga from EPCQ) block to work on a cyclone V using quartos 14.1.

I've managed to expose the epcq pins to 'user' logic and can successfully update the epcq from a .pof file.

(If you add the 'JTAG to EPCQ bridge' you get an option to expose the pins that generates a 'test_sfl' component.)

I've also instanciated the 'remote update' block and linked it to an avalon slave.

If I then try to read any of the 'parameters' (aka registers) I get 1s for all the defined bits and 0s for the others (so parameter 0 (reset reason) returns 0x1f).

Writes to 'page select' are ignored (reads back 0xffffff).

Looking inside the remote update block there is a 'CYCLONEV_RUBLOCK' block.

With signaltap I can see some serialised accesses to the block - including my write data, but the output bitstream is always 1s.

I've not tried to force a reconfig - I want to know I've set the base address first.

Anyone any ideas?

David

FWIW: Getting factory/user images to be useful is going to be 'interesting' since we are (effectively) a PCIe card.

We may load the 'user' image on request from the Linux kernel - when we can reprobe the PCIe bus.