Honored Contributor
Honored ContributorI would disagree with this, at least fundamentally(I haven't tried it in practice.) Incremental Compilation is supposed to be unaware of synthesis in other partitions. The easiest way to think of it is as if each partition were synthesized like it was its own project. The reason for this is that you can then change one partition and it will only resynthesize that partition. I don't believe there are algorithms to "recheck" parameters in other partitions and see if they've changed of not.
If the parameter doesn't change a lot, then you should change the defaults in the lower level partition to reflect the upper changes and be cognizant anytime you do change these parameters. If they do change a lot and you don't want to have to be updating them, then this is probably not a good boundary to create a partition on. I'm sure there are other solutions like putting the parameters in another file and then sourcing it, or parsing the SOPC system with a script to get them, but probably not ideal. Note that Incremental Compilation does have some limitations. Once you use it a lot, you realize they are fundamental reasons for these limitations and what IC is meant to achieve, but sometimes it takes a little work. Here's a good document to get a better feel for it: http://www.altera.com/literature/an/an470.pdf
