RE: Minutes and IMs - 4-state value issue

Brian, ITC members

 

Here is our proposal on the 4-state value issue.

 

SCE-MI 2.0 spec should only support conveying 2 state values (1/0)
through the interface and treat X and Z states as undefined.  

 

This implies that we leave it to the implementers to define what level
of enforcement should be applied when X and Z values are passed to the
SCE-MI API. Users could build their own lint checkers or use what EDA
vendor choose to provide to check/lint the code. The above also implies
that SCE-MI 2.0 should not support 4 states to 2 states coercion and
should not implement different coercions for simulation vs. emulation.
Defining X and Z as undefined also imply that that SCE-MI 2.0
implementation should not be forced to report X and Z states as errors
or warnings. 

 

Thanks,

 

Shabtay

 

 

 

>-----Original Message-----

>Another reminder: Proposals for what to do with 4-state values are due

>tomorrow. We will decide on this at the Thursday meeting. We will also

>close

>on the 1.1 / 2.0 mixing rules.

> 

>Thanks

>Brian