Greg, I envisioned that this parameter would tell the EDA tool how it should generate the waveform that it passes to the AMI DLL (i.e. how many points per bit should be in the waveform). I think this is like the model telling the tool: "Give the data to me this way, because I can't handle it any other way". Thanks, Arpad ========================================================== From: Gregory R Edlund [mailto:gedlund@xxxxxxxxxx] Sent: Thursday, September 29, 2011 8:32 AM To: Muranyi, Arpad Cc: IBIS-ATM; ibis-macro-bounce@xxxxxxxxxxxxx Subject: Re: [ibis-macro] Samples per bit for AMI Arpad, Do you envision the new samples per bit parameter being used by the EDA tool? Or is it for documentation purposes? There is another way to handle this scenario: we could integrate samples per bit into the quality check list, i.e. the model maker uses the quality check list as a means of communication with the user. Greg Edlund Senior Engineer Signal Integrity and System Timing IBM Systems & Technology Group 3605 Hwy. 52 N Bldg 050-3 Rochester, MN 55901 [Inactive hide details for "Muranyi, Arpad" ---09/28/2011 06:44:32 PM---Hello everyone, I ran across yet another model today whi]"Muranyi, Arpad" ---09/28/2011 06:44:32 PM---Hello everyone, I ran across yet another model today which was misbehaving From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx> To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx> Date: 09/28/2011 06:44 PM Subject: [ibis-macro] Samples per bit for AMI Sent by: ibis-macro-bounce@xxxxxxxxxxxxx ________________________________ Hello everyone, I ran across yet another model today which was misbehaving in our tool because it turned out that it would only work with 64 samples per bit and the user unaware of this used a different value. When I wrote about this topic some time ago, I was wrestling with another AMI model that would only work with 32 samples per bit. Neither of these models came with any documentation on what samples per bit settings they will work with. The problem is that when such models are misbehaving, all kinds of "fun stuff" is starting to happen, anywhere from crashes to explosions :-). I believe that the most robust solution would be to add a reserved parameter for samples per bit to the IBIS-AMI specification so that the model makers would be forced to document in the .ami parameter file sampling rate(s) the model will work with. Making blanket statements in the spec is not going to guarantee that the model maker will actually do anything about it, they may not even read that part of the specification at all... Please look over the attached BIRD draft in which I attempt to solve this problem by adding a reserved parameter to the specification. Questions, comments are welcome. Thanks, Arpad ============================================================== [attachment "SamplingRateBIRD_01.pdf" deleted by Gregory R Edlund/Rochester/IBM]