125MHz PCIe application clock on a large cyclone V

I did try adding pipeline bridges, with more than 3 or 4 slaves per bridge it fails timing.

With that many bridges it is hard to see what is what.

Once I get away from the PCIe BAR avalon master (which has deep levels of logic on it avalon outputs and waitrequest input) the problems seem to be associated with the address comparators and the slave arbiters generating waitrequest.

I'm wondering whether asserting read/write a cycle after the address and giving a timequest a multi-cycle constraint on the address might help?

Telling qsys to ad 1 cycle of additional latency just makes things worse!

I'm not sure where it adds the latch, but it isn't anywhere near the right place.