[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: TRDY# Hang...
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: TRDY# Hang...
- From: Alan Deikman <alan@znyx.com>
- Date: Thu, 20 Feb 1997 11:46:41 -0800
- Resent-Date: Thu, 20 Feb 1997 11:46:41 -0800
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"YjXNJ2.0.Ds4.MdA3p"@dart>
- Resent-Sender: pci-sig-request@znyx.com
>
>How should a system behave if ????
>-Frame# was asserted for a valid address
>-IRDY# asserted
>-DEVSEL# asserted
>-TRDY# never came down and the system hung.....
>Abnormalities in PCI targets are related to DEVSEL not responding but not
>TRDY#.
You don't mention the STOP# signal, but I assume that you mean that
the target never asserts STOP# to cause a Retry or Target-Abort.
See page 40-41 of the 2.1 specification.
Otherwise, it is not the system but the system's owner that should
respond by removing the target device. A target should never decode
an address if it cannot respond.
I suppose you could make a master more robust by timing out the
access, but why bother.
Regards,
--------------------------------
Alan Deikman, ZNYX Corporation
alan@znyx.com
§ ä Ñ