All,
I would like to comment on the following situation with the Clock
Forwarding Bird (204)
1. If the Data DLL has "Rx_Use_Clock_Input "Times")
2. The Clock has a DLL that either
a. GetWave_Exist=True and GetWave does not return clock ticks
b. GetWave_Exist False
3. This is problematic for two reasons:
a. The EDA tool does not know until simulation time if GetWave does
not return clock ticks when GetWave_Exist=True
b. If the model make goes through all of the effort of creating a
Data DLL that accepts clock ticks, he should not rely on the EDA tool to
generate clock ticks from a DQS waveform.
I would therefore propose the following change to BIRD204, to replace the
following line:
For "Times" and "Wave" options, if the Clock does not have a DLL or has a
DLL without an AMI_GetWave, then the EDA tool should effectively insert a
passthrough Clock AMI_GetWave function to create the wave or clock_times
output vector required by the Data AMI_GetWave clock_times input.
With
For the "Wave" option, if the Clock does not have a DLL or has a DLL
without an AMI_GetWave, then the EDA tool should effectively insert a
passthrough Clock AMI_GetWave function to create the wave output vector
required by the Data AMI_GetWave clock_times input.
For the "Time" option, the Clock shall have a DLL with an AMI_GetWave that
returns clock_times.
Walter
Walter Katz
Work 508.647-7633
Cell 720.417-3762