[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Simulating/verifying PCI bidir requirements
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: Simulating/verifying PCI bidir requirements
- From: bradshaw@nlc.com (Lee Bradshaw)
- Date: Wed, 18 Dec 1996 11:21:41 -0800 (PST)
- Cc: pci-sig@znyx.com (pci-sig)
- In-Reply-To: <199612172326.PAA20340@gluon.Eng.Sun.COM> from "Kevin Normoyle" at Dec 17, 96 03:26:22 pm
- Resent-Date: Wed, 18 Dec 1996 11:21:41 -0800 (PST)
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"VEioH3.0.VK7.YK4ko"@dart>
- Resent-Sender: pci-sig-request@znyx.com
Hi Kevin,
You could try bus keepers (which generally exist on internal tristate
busses) in your testbench:
buf (weak1, weak0) frame_hold (frame, frame);
This buffer won't pull the signal high, but it should hold the last driven
state. Depending on the timing between grants, this buffer can also
detect the input to the frame driver in your chip going low before the
output enable is turned off. Pullups would normally mask this error as
well.
Kevin Normoyle wrote:
>
>
>1) Sustained Tri-State signals are driven (by you) high in the last cycle
>you drive them.
>(this one is tricky, because if you put in a dumb pullup model, it will
>pull the undriven signal to 1 during the dead cycle, so your simulation
>might "pass")
--
O
o\
~~ __|=\
<_____\>
~~~ ~ O
Lee Bradshaw bradshaw@nlc.com \
Next Level Communications (707) 588-5968 | ~~
6153 State Farm Drive FAX (707) 588-8653 | ~ ~
Rohnert Park, CA 94928 caveat lector |~ ~~ ~
® € o