Hi Arpad,
My understanding is that ignore_bits tells the tool when to start collecting
data for eye statistics/post processing.
If the DQS .ami file says Ignore_Bits=100, it means that the DQS model is
telling the tool ‘to accumulate
waveform statistics after the EDA tool has completed simulation of a number of
UI equal to
Ignore_Bits’ – i.e 100 UIs.
It should have no implication on when the clock_times vector gets passed to the
DQ Rx AMI model.
Thanks,
Ambrish.
From: ibis-macro-bounce@xxxxxxxxxxxxx <ibis-macro-bounce@xxxxxxxxxxxxx> On
Behalf Of Muranyi, Arpad
Sent: Tuesday, September 13, 2022 1:55 PM
To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>; ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-macro] What is the relationship between "clock_times" and
"Ignore_Bits"?
EXTERNAL MAIL
Hello Everyone,
I ran into another question with “clock_times” in the context of
Rx_Use_Clock_Input.
How is “Ignore_Bits” come into this picture? I couldn’t find the answer in the
spec…
For example, is the EDA tool expected to suppress (delete) the clock time
values from
the beginning of the clock_times vector returned by a DQS Rx AMI model up to the
point that is defined by Ignore_Bits before passing it into the DQ Rx AMI model?
Let’s say the first clock time generated by the DQS Rx model is around the 5th
bit (UI),
but the DQS .ami file says Ignore_Bits = 100. Is the EDA tool supposed to
remove the
first 95 or so numbers from the clock_times vector and pass a clock_times
vector to the
DQ Rx AMI model that starts only after the 100th bit?
Thanks,
Arpad
========================================================================
