Article ID: 000077219 Content Type: Troubleshooting Last Reviewed: 02/13/2006

Why does my peripheral component interconnect (PCI) prototype board give different outputs when configured with the ByteBlaster™ download cable than when configured with the EPC1 configuration device provided with the board?

Environment

BUILT IN - ARTICLE INTRO SECOND COMPONENT
Description This may occur for one of the following reasons:
  • The EPC1 device is loaded with a design called demo_board.gdf, which is a pci_a function with a memory unit as its local side. This file is also included in the pci_a build. The PCI board walkthrough uses pci_top.gdf to configure the prototype board. This file only instantiates the pci_a function and does not contain the local-side signals that are in demo_board.gdf.
  • The pci_a function does not support the LOCKn signal. Make sure you tri-state LOCKn. Otherwise, it will drive out and contend with the PCI bus.
  • The local clock signal l_clock supplies the clock to the local side. It is an logic-cell-driven signal, and should not be used for the PCI clock signal because it has a larger skew. Use the provided PCI clock signal assigned to one of the global clock inputs.

Related Products

This article applies to 1 products

Intel® Programmable Devices

Need more help?

Contact support

Disclaimer

1

All postings and use of the content on this site are subject to Intel.com Terms of Use.