Hi Walter, I am confused here. The parent is the IBIS model and has a pointer to AMI dll (Child) - the association is fixed - so how can AMI dll decide the analog-IO model that needs to be picked. Please explain with an example/flow-steps on how the analog model (IBIS v-i/v-t model) would be registered. rgds ..kukal ________________________________ From: Walter Katz [mailto:wkatz@xxxxxxxxxx] Sent: Monday, January 17, 2011 8:26 PM To: Taranjit Kukal; 'IBIS-ATM' Subject: RE: [ibis-macro] Re: BIRD-124: Dependency tables - question? Kukal, Your first sentence is not correct, it should have said: "Looks like the Intent is to associate Analog IO model (different IO-model strengths) to AMI-parameter so that correct Analog IO-model is picked when s specific portion of AMI-code gets executed." Point being that the user configures the registers in a model, and that the registers in the model not only determine how the algorithmic model works but also determine the analog model needed to generate the impulse response of the channel for the algorithmic simulation. Walter From: Taranjit Kukal [mailto:kukal@xxxxxxxxxxx] Sent: Monday, January 17, 2011 9:17 AM To: wkatz@xxxxxxxxxx; 'IBIS-ATM' Subject: RE: [ibis-macro] Re: BIRD-124: Dependency tables - question? Hi Walter, Help me understand this further. Looks like the Intent is to associate Analog IO model (different IO-model strengths) to AMI-parameter so that correct portion of AMI-code gets executed according to Analog IO-model that is picked. However, what I fail to understand is that how this association gets utilized. If the user has to manually set a Key-parameter as per the IBIS buffer-strength to allow picking of dependent parameters then why are not let ami-code do it (Let tables be coded inside of AMI dll). To me, it looks like "Good to have" rather than a real need. Please explain with small example if I am missing the point. rgds ..kukal ________________________________ From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz Sent: Thursday, January 13, 2011 8:32 PM To: Taranjit Kukal; 'IBIS-ATM' Subject: [ibis-macro] Re: BIRD-124: Dependency tables - question? Kukai, The impulse response of the channel must be determined before the AMI DLL is called. The AMI file contains the switches that program the Tx or Rx model. The value of these switches determine the analog model of the driver that is required to determine the impulse response of the channel. Walter From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Taranjit Kukal Sent: Thursday, January 13, 2011 2:11 AM To: IBIS-ATM Subject: [ibis-macro] BIRD-124: Dependency tables - question? 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/>