Occasional Contributor
Super ContributorIt's a lot easier to add delay like this using timing constraints. You can use set_min_delay and set_max_delay in your .sdc file to set delay on paths anywhere in your design.
To answer your question, you'd need to run a timing analysis to see what the delay is since it would be unique to the particular device and particular resource used to implement the delay.
Occasional ContributorTo provide some extra info:
This schematic file is purely combinational with 16 back to back LCELLs and each LCELL's output is given to 16:1 Multiplexer. There are only 2 inputs to this file: a) the signal to which delay is generated and b) the 4 bit select input to the MUX.
As you mentioned the delay is unique to particular device, I would like to tell that this was initially implemented on old generation FPGAs in MAXPLUS. I am porting the design to latest Cyclone 10 family. So, I assume the delay generated on old FPGAs are different compared to Cyclone 10 device, hence the number of LCELLs used must be changed.
Could you please elaborate a little more on how to see the delay after timing analysis. In Timequest timing analyser, I used the "Report Timing" option in the Tasks window and I do not know what clock to provide in the dialog box that opens.
From: 198-83-75-152-1-28-datad :
28 is the block number of LCELL; 1 is the 1st instance of the LCELL; datad is the name of input pin to first LCELL.
TO: 198-83-75-152-16-28-combout:
28 is the block number of LCELL; 16 is the 16th instance of LCELL; combout is the name of output pin of 16th LCELL.
When I click Report timing without providing the clock, I get the reply from the tool as "Nothing to report".
