Digital Core Design, one of the most experienced (since 1999) IP Core providers and a System-on-Chip design house, introduced to its portfolio the DTPCI32DC. It’s a Dual Clock 32-bit PCI Bus Target Interface IP Core which meets all requirements of the PCI 3.0 specification for a target device. Moreover, it compromises a minimal gate count with a high-bandwidth data transfer.
Bytom, July the 14th, 2016 - The DTPCI32DC is a 32-bit target interface which meets all requirements of the PCI 3.0 specification for a target device. It compromises a minimal gate count with a high-bandwidth data transfer. The Core’s main feature is the presence of two clock domains. - They enable flexibility and higher performance as well – says Tomek Krzyzak, VCEO of DCD – When time required for implementation becomes crucial, theDTPCI32DC brings a domain crossing.
Saved time can be used for a specific system implementation instead. The user-friendly back-end interface can be very easily and effectively tailored to the design needs.
The Core supports up to six Base Address Registers and Expansion ROM address register with both I/O and Memory space decoding from 16 bytes up to 4 GB. Another important feature is a cache wrapping hardware support and a cacheline pre-fetching capability. The DTPCI32DC is accepting size cache lines which are powered from 2 up to 128. It enables also target-disconnect with data, without data or by a target abort. Moreover, the DTPCI32DC is capable to work with 66 MHz clock frequency in the most popular technologies. It assures the PCI timing requirements, as well as other parameters like FIFOs depths number or Base Address Registers (they can be easily configured at the pre-synthesis stage).
More information & evaluation requests: http://dcd.pl/ipcore/1112/dtpci32dc/
- —Â Fully supports PCI specification 3.0 protocol
- —Â Stable clock domain crossing regardless of the clock frequencies
- —Â Cache wrapping (cache lines must be powers of 2)
- —Â User controlled burst data transfer
- —Â Possible no-wait state transactions
- —Â Automatic handling of configuration space read/write access
- —Â Parity generation and parity error detection
- —Â Single interrupt support
- —Â Configurable FIFOs depth
- —Â Supported backend initiated burst termination (with and without data)
- —Â No tri-state buffers