Logic Development PCI interface (LD_PCI)

Why using a Logic Development PCI

Logic Development has made FPGA projects with PCI interface and has a lot of PCI system know how. That know how lead to the decision of making an internal developed PCI interface instead of using PCI cores from other vendors. Why making a “new” PCI interface when it is already done by other companies? The reasons for this are:

• The design flow setup was very complicated with PCI cores used so far.
• The signalling on the user side of PCI core has a complexity similar to the PCI bus itself.
• The PCI was only a core, i.e. to just make e.g. a simple register a lot of user side code was necessary. That why the LDPCI is called a PCI interface instead of “just” a PCI core.

Using a LD_PCI you get:

• Simple design flow setup.
• Easy integration with user part of the design.
• Possible to outsource the whole design, and let Logic Development make the whole design.
• Completive prices LD_PCI licences.
• Fully tested on real world hardware (PC’s and SBC’s)
• Windows 2000/XP driver with easy to use API.
• Linux driver with easy to use API.

LD_PCI system block diagram

The LD_PCI system gives you an effective PCI infrastructure from the FPGA/HW environment to your PC application running Windows or Linux. There are two lanes of data flow from the application to/from the FPGA. The slave part of the PCI interface in the FPGA is typical used for control and status data. The shared/DMA buffer in the PC main memory is typical used for burst data and is the fast lane where it is possible to get data to/from the PC without CPU load at full PCI bus speed.

Datasheet and other PCI information

The LDPCI data sheet: LD PCI IF DataSheet
Windows/Linux PCI driver data sheet: LD PCI driver
Introduction to the PCI bus: PCInote1
PCI presentation from Memec Touren 29-30 November 2004: Memec Touren 2004 PCI interface

For other information and pricing contact Logic Development ApS.