| поискавой системы для электроныых деталей |
|
OR3LP26B датащи(PDF) 60 Page - Agere Systems |
|
|
|||||||||||||||||||||||||||||
OR3LP26B датащи(HTML) 60 Page - Agere Systems |
|
60 / 184 page ![]() 60 60 Lucent Technologies Inc. ORCA OR3LP26B FPSC Data Sheet Embedded Master/Target PCI Interface March 2000 Lucent Technologies Inc. PCI Bus Core Detailed Description Dual Port (continued) Reset The FPGA application can apply the PCI core’s reset signal tfifoclrn to place the core’s target logic in a known state. Normally, the clear signal will not be used unless a severe problem has occurred in the data flow. The tfifoclrn signal is synchronous with fclk and must be asserted for a minimum of three clock periods. Dur- ing reset, the t_ready signal will go low. After the reset signal is deasserted high, t_ready will continue to be low for 8—10 clock periods. The FPGA application should not continue normal operation until t_ready is asserted high. Understanding and Using the pci_tcfg_stat Status Signals On the Target interface, there are two signals that con- trol and provide status to the FPGA application. The signal pci_tcfg_stat provides the status, and tcfg- shiftenn controls what information the status line pro- vides. The pci_tcfg_stat signal is always active and duplicates the status contained in configuration status register at location offset 0x04, bits 24, 28, and 29. To use this status output, the FPGA application must keep tcfgshiftenn = 1. When high, pci_tcfg_stat provides the wired-OR of the three status lines. If pci_tcfg_stat gets set to a 1, indicating an error, then the FPGA application may set tcfgshiftenn = 0 to determine indi- vidual status. Once low, the pci_tcfg_stat signal will output target abort signaled on the first clock, system error signaled on the second clock, and parity error detected on the third clock. Initiating Target Aborts There may be a need in an application to initiate a tar- get abort condition on the PCI bus. In general, this is asserted for only the most severe cases. The interface signal, fpga_tabort, is used for this purpose. From the PCI core's point of view, it needs to know whether to perform a target abort at the very beginning of a trans- action, so it is not possible to have a transaction started, and then assert the fpga_tabort signal. The signal fpga_tabort needs to be asserted before the transaction begins, and it was designed to be toggled on and off from transaction to transaction. Once an FPGA application determines that it wants to apply a target abort to any master that accesses it, it would assert the fpga_tabort signal high. All future target accesses will be terminated in an abort. In generating this signal, keep in mind that this signal needs to be synchronous to pciclk. |
|
ссылки URL |
| Вашему бизинису помогли Аллдатащит? [ DONATE ] |
Что такое Аллдатащит | реклама | контакт | Конфиденциальность | Ссылка на техническое описание | обмен ссыками | поиск по производителю All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |