Kukal-There are several useful applications for dependency tables; we do quite often use the application you mention It's more useful than you imagiine. The most critical application, however, is setting driver impedances.
As you may know, the output impedance of a driver typically changes with the swing setting. That is, changing the swing setting changes the bias point, which changes the output impedance of the transistors. Therefore, as we do state in Opal(TM), both the algorithmic and the analog models need to know what the swing setting is. As a matter of good software engineering, it would be best if both models got their information from a single user input.
One could imagine a number of ways to solve this problem, but dependency tables are a particularly simple and flexible solution.
Mike S. On 1/13/2011 2:11 AM, Taranjit Kukal wrote:
Hi,The dependency tables would be useful only if we want to keep same AMI-code (dll) and just change the dependency outside of the code using .ami file. However, I do not see this as common use-model - I would assume that all such dependency should be handled inside of c-code (Algorithmic...) and that we should avoid overloading of .ami file such tables. AMI-code should be able to handle such dependency by coding the right values for dependent parameters based on Key parameters in ami file. Please let me know if I am missing a use-case where this cannot be handled inside the dll.rgds ..kukal Taranjit Kukal | Product Engineering Architect P: 91 120 3984000 www.cadence.com <http://www.cadence.com/>
