The attached [C Comp Model] BIRD draft includes changes from the draft shown
during the 5/28 ATM task group meeting.
Changes include:
1. Renaming the keyword to [C Comp Model]
2. Changing instances of "C_comp Model" to "C Comp Model" in the PROPOSED
CHANGES section
3. Updating the Examples section to show two examples illustrating use of
the Mode subparameter options
4. Adding Ext_ref to Figure X
5. Fixing typos related to the Number_of_terminals subparameter in examples
I noticed one other area that I think needs further discussion/clarification.
There are no rules preventing an I/O or 3-state [Model] from having only one [C
Comp Model] with the Mode subparameter set to Driving or Non-Driving. This
creates an undefined condition for the EDA tool to interpret. Would the one [C
Comp Model] be used for both Driving and Non-Driving states? The Rules of
Precedence statement "The EDA tool shall either use C_comp* or [C Comp Model],
but not both." could be interpreted to require this.
Fixes could include:
1. Allowing the EDA tool to use C_comp for the undefined condition.
(Requires changing the Rules of Precedence statement)
2. Add a rule that I/O and 3-state [Model]s must include either two [C Comp
Model] sections with Driving and Non-Driving modes defined or one [C Comp
Model] with Mode set to All.
Please send feedback by email or plan on further discussion at a future ATM
meeting.
Thanks,
Randy
Attachment:
C_comp_Model_Using_IBIS-ISS_BIRD_rev_5_30_2019.docx
Description: C_comp_Model_Using_IBIS-ISS_BIRD_rev_5_30_2019.docx
