incremental compilation tests

--- Quote Start ---

Hi all,

I'm performing some tests about Quartus incremental compilation.

I've created a simple design: the top level file is a ".bdf" in which are present two modules, a counter and a counter_check. I've created two partition: the counter partition and the counter_check partition, so opening the "design partitions window" I can see three partitions, the top, created by default, and the other two created by me. I've compiled the whole design and than set the netlist type of all the partitions to "postfit" and fitter preservation level to "placement and routing". Then I've tried to compile the whole design again: I expected to see the "post-fit netlist status" unchanged (i.e. with the time and date of the previous compilation), instead the "post-fit netlist status" is updated to the time of my last compilation!!! In the fitter report page I can see that Quartus has preserved the fitter results of my last compilation so I expected to see the same in the "post-fit netlist status"...

Is it normal?

Any advice is welcomed.

Thank u in advance.

--- Quote End ---

Hi,

but routing and placement are preserved ?

Kind regards

GPK

Thank u iverson for your feedback.

Pletz, to be rigorous my compilation report is:

Ermes Incremental Compilation Preservation Summary

Type Value

Placement

-- Requested 41 / 41 ( 100.00 % )

-- Achieved 40 / 41 ( 97.56 % )

Routing (by Connection)

-- Requested 23 / 23 ( 100.00 % )

-- Achieved 23 / 23 ( 100.00 % )

So It seems that the routing is preserved at all, while the fitter is preserved at 97.56 %, even if I've not changed anything. I have also set the "netlist type" to post fit (strict) but I have the same behaviour!!!

Could anybody explain me what is happening? or Is there anybody using incremental compilation with a different feedback?

Thank u in advance