KC705 at Atomic Rules
Sunday, January 29, 2012
KC705 Supported
With the release this month of ISE 13.4, we have added the Xilinx KC705 to the list of supported OpenCPI FPGA platforms. We adapted the new AXI-centric Gen2 x4/x8 PCIe endpoint to our uNoC without much drama. Inbound (RX) straddled packets were an interesting twist. Kudos to the Xilinx team for producing such a clean and easy-to-use evaluation kit and help jumpstart our community adoption of 28nm FPGAs in practice. The KC705 is fitted with a Xilinx Kintex-7 XC7K325T device.

KC705 at Atomic Rules
KC705 at Atomic Rules
Thursday, December 1, 2011
North American FPGA Conferences
Atomic Rules is pleased to be a sponsor of two FPGA conferences in 2012:
Additionally, you can check our News and Events page to see what else is in the works.

Shep and Oskar at Demo night, FCCM-2005 (Napa)
- FPGA-2012 in Monterey (ACM/SIGDA)
- FCCM-2012 in Toronto (IEEE)
Additionally, you can check our News and Events page to see what else is in the works.
Shep and Oskar at Demo night, FCCM-2005 (Napa)
Monday, November 28, 2011
SIGINT bliss and the MDO4104
Wednesday, August 31, 2011
FPGA Cross-Vendor Interoperability
A short video showing OpenCPI transport messages between Altera and Xilinx FPGA platforms.
Tuesday, August 16, 2011
Pure PCIe
The PCIe specification does a splendid job of describing how Transaction Level Packets (TLPs) are encoded. The specification precisely defines an interface without dictating an implementation. It’s a terrific concept.
FPGA and ASIC IP vendors, when providing said TLP interfaces to their users, make implementation choices that are specific to their own technological and marketing whims. These choices run the gamut from reasonable to ridiculous: Big-endian vs. Little-endian? Streaming or not? Header vs. Payload? Strict or Uncertain flow-control.? Packing “bubbles” and straddled packets? My goodness: All of these to alter of protocol gods that have little to do with PCIe TLPs themsleves!
Faced with the challenge of achieving interoperability with and between any of these PCIe endpoints; out of necessity, we followed a simple process. We designed a Pure PCIe intermediate “platform” that used nothing other than the “pure” PCIe specification for its definition. In this way, the work involved with adapting any PCIe device (now or future) has one overarching goal: Adapt the variable implementation to the fixed, pure PCIe interface.
The utility of this simple approach is that interconverting between different implementations is now just a matter of hooking them to the other side of the pure PCIe interface. We get multiplicative gains in interoperability for a linear effort in design cost. And we get the verification leverage of only having to compare one unknown (the new protocol) to one bulletproof interface (the PCIe TLP spec) at a time.
The lesson here is that there are indeed clever tactics one can take to embrace the reality that new protocols (some brilliant, some defective) will continue to assault us as they are invented. By recognizing stable, more cardinal interfaces (such as PCIe TLPs), we can adopt them all, without as much drama and cost.
FPGA and ASIC IP vendors, when providing said TLP interfaces to their users, make implementation choices that are specific to their own technological and marketing whims. These choices run the gamut from reasonable to ridiculous: Big-endian vs. Little-endian? Streaming or not? Header vs. Payload? Strict or Uncertain flow-control.? Packing “bubbles” and straddled packets? My goodness: All of these to alter of protocol gods that have little to do with PCIe TLPs themsleves!
Faced with the challenge of achieving interoperability with and between any of these PCIe endpoints; out of necessity, we followed a simple process. We designed a Pure PCIe intermediate “platform” that used nothing other than the “pure” PCIe specification for its definition. In this way, the work involved with adapting any PCIe device (now or future) has one overarching goal: Adapt the variable implementation to the fixed, pure PCIe interface.
The utility of this simple approach is that interconverting between different implementations is now just a matter of hooking them to the other side of the pure PCIe interface. We get multiplicative gains in interoperability for a linear effort in design cost. And we get the verification leverage of only having to compare one unknown (the new protocol) to one bulletproof interface (the PCIe TLP spec) at a time.
The lesson here is that there are indeed clever tactics one can take to embrace the reality that new protocols (some brilliant, some defective) will continue to assault us as they are invented. By recognizing stable, more cardinal interfaces (such as PCIe TLPs), we can adopt them all, without as much drama and cost.
Tuesday, May 31, 2011
Validating PCIe
LeCroy graciously loaned us their exceptional T2-16 PCIe Protocol Analyzer for a few days. This was not nearly enough time to appreciate an instrument that has such deep capabilities. While the T2-16 captures every nook and cranny of the PHY and LINK layers; we remain most-interested in watching what is going on at the Transaction Layer (TL). The T2-16 does this well; but a Ferrari can also take you to the grocery store. Functionally, the most-annoying nit was that the fans on the active interposer and in the chassis itself are screaming loud. And the LAN function didn't work; but USB worked flawlessly. Faced with an intractable, hard-to-understand PCIe issue; this is an instrument we would want by our side.

LeCroy T2-16
LeCroy T2-16
Subscribe to:
Posts (Atom)
