Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
It's a pdf file and without any explaination.
I guess google is characterized for different location.
Actually, I met problem while I read Cadence LEC document:
ADD PIN CONSTRAINTS
ONE_Hot Specifies that only one of the pins can have a high value.
ONE_Cold Specifies that only one of the pins can have a low value.
ZERO_ONE_Hot All pins can have a low value, but only one can have a high value.
ZERO_ONE_Cold All pins can have a high value, but only one can have a low value.
The definition of one-hot as given here ("in which only one
signal in the collection is active at a given time") is useful one,
but is not the normal definition of one-hot. (In OVL, the Open
Verification Library, this check is known as zero_one_hot.)
This will cause confusion.
Change the definition of ONE_HOT to "...in
which one and only one signal in the collection
is active at a given time", and add a second
attribute ZERO_ONE_HOT with the definition
"...in which at most one signal in the collection
is active at a given time". Similarly for
ONE_COLD and ONES_ONE_COLD.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.