I wouldn't count on any kind of concealment, since tools make the
ami_parameters_out data available at run time. Some models are simply able
to calculate jitter based on inputs. For example, some models produced
jitter that depends on the data rate. The tool still implements the
jitter, but it uses the numbers produced by the model.
Mike
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Mirmak, Michael
Sent: Friday, March 25, 2016 4:11 PM
To: IBIS-ATM (ibis-macro@xxxxxxxxxxxxx)
Subject: [ibis-macro] Simple IBIS-AMI question of the day...
I note that jitter parameters such as Rx_Dj are described in the IBIS
document as having Usage Info, Out, and Dep.
Ignoring Dep for the moment.
The specification defines Info as referring to parameters that may be of
interest to the EDA tool or to the user. Out is defined as referring to
parameters "coming from the AMI_Init and/or AMI_GetWave functions."
If the Usage is Info for a jitter reserved parameter, then I would assume
the jitter values will be read by the EDA tool to ensure it takes jitter
into account properly.
But what about Usage Out? This implies that the functions AMI_Init and/or
AMI_GetWave are generating the jitter. In this case, is Usage Out for
jitter meant to help a model-maker include the jitter in the DLL (and
conceal it from readers of the .ami file) but still make it available to
the tool?
Thanks in advance.
- MM
