Hello everyone, As promised, here is a new BIRD draft to address the questions raised by the parser developer regarding min/typ/max in the AMI portions of the IBIS specification. This is row #15 in the Task List spreadsheet: http://www.vhdl.org/pub/ibis/macromodel_wip/archive/20100831/arpadmurany i/IBISv5.0%20AMI%20specification%20BIRD%20task%20list/IBIS50AMI_TaskList _2010_08_31.pdf I hope to get feedback on this on or before the next ATM teleconference so we can get this right. Thanks, Arpad =================================================================
***************************************************************************** ***************************************************************************** BIRD ID#: ISSUE TITLE: Clarifying min/typ/max in IBIS-AMI REQUESTER: Arpad Muranyi, Mentor Graphics, Inc. DATE SUBMITTED: DATE REVISED: DATE ACCEPTED BY IBIS OPEN FORUM: ***************************************************************************** ***************************************************************************** STATEMENT OF THE ISSUE: Section 6c of the IBIS v5.0 specification is not completely cear about the rules for min/typ/max which need to be spelled out. ***************************************************************************** STATEMENT OF THE RESOLVED SPECIFICATIONS: Replace the following lines: | Increment <typ> <min> <max> <delta> | After expansion, the allowed values of the parameter are | typ+N*delta where N is any positive or negative integer | value such that: min <= typ + N*delta <= max with these lines: | Increment <typ> <min> <max> <delta> |* where min < typ < max and delta is always positive. |* After expansion, the expanded values of the parameter are |* typ + N*delta where N is any positive or negative integer |* value provided by the EDA tool during the expansion process |* so that: min <= expanded values <= max |* The EDA tool is expected to start the sweeps at typ, going |* up closest to max, and then going down closest to min. ***************************************************************************** ANALYSIS PATH/DATA THAT LED TO SPECIFICATION These questions were raised by the parser developed while working on the IBIS v5.0 parser program. Careful reading of the secification revealed that the rules were not completely defined. ***************************************************************************** ANY OTHER BACKGROUND INFORMATION: *****************************************************************************