KVD KBL KSL KBS KEB KHB KDS KDZ KDH PM KPM HPM KLS KAC KD KBS-L DC/DC Converter USB Driver KVD Kelly KVD Controllers User Manual Kelly KVD Configuration Program (PC Version) Kelly KVD Configuration Program (Android Version) KBL Kelly KBL Controllers User Manual Kelly KBL Controllers Configuration Program -0406 Kelly KBL Assembly Wiring Diagram. Opal Kelly Pins (©) 2017. Design schematics and PCB artwork are available for our breakout boards and other select devices. We do not provide schematics. Opal Kelly has offered SYZYGY as an open standard and free to license by carrier and peripheral manufacturers. This licensing approach is intended to encourage consistency, proliferation, and a healthy ecosystem where carrier and peripheral manufacturers, semi-conductor device manufacturers, educational institutions, and research organizations.

Skip to end of metadataGo to start of metadata

The FrontPanel-enabling modules have been designed to consume as few resources as possible within the FPGA. The resource requirements for each block are listed in the tables below. Keep in mind that these are requirements for an endpoint with all bits used. In many cases, the place and route tools will optimize and remove unused components.

Drivers Opal Kelly USB Devices

Resource	Slice FFs	4-in LUTs	Block RAMs
Host Interface	33	49	0
Wire In	16	14	0
Wire Out	8	5	0
Trigger In	32	21	0
Trigger Out	27	15	0
Pipe In	9	10	0
Pipe Out	0	6	0
BT Pipe In	?	?	?
BT Pipe Out	?	?	?
Register Bridge	?	?	?

Multiple endpoints are attached to the okHE bus on the okHost by using a Wire-OR. Each endpoint is told when it can assert its data on the bus. At all other times, it drives 0. The Wire-OR component performs a bitwise OR operation on each bit of the bus and outputs the result. In this manner, multiple endpoints can share a bus without requiring the use of tristates or a large mux.

The okWireOR is provided as a parameterized helper module in okLibrary.v and okLibrary.vhd. Please refer to the provided samples to see how to instantiate this module.

The host interface is the gateway for FrontPanel to control and observe your design. It contains the logic that lets the USB microcontroller on the device communicate with the various endpoints within the design. Exactly one host interface must be instantiated in any design which uses the FrontPanel components.

The Host Interface component is the only block which is synthesized with your design. It contains a Host Interface core component (provided as a pre-synthesized module) as well as the necessary IOB components to connect to the host interface pins of the FPGA.

NOTE: The okHost is contained in okLibrary.v or okLibrary.vhd. Some details change from device to device so the exact pinouts may differ slightly from the documentation below. Please see the Opal Kelly samples in the FrontPanel installation directory for examples specific to each supported device.

The diagram below illustrates the structural relationships between the various endpoints, the okWireOR, and okHost modules.

okHost

This module must be instantiated in any design that makes use of FrontPanel virtual interface components. The following signals need to be connected directly to pins on the FPGA which go to the USB microcontroller on the device. For a listing of the pin locations for a particular product, please see the user’s manual for that device.

Signal	Direction	Description
okUH[4:0]	Input	Host interface input signals.
okHU[2:0]	Output	Host interface output signals.
okUHU[31:0]	In/Out	Host interface bidirectional signals.
okAA	In/Out	Host interface bidirectional signal

The remaining ports of the okHost are connected to a shared bus inside your design. These signals are collectively referred to as the target interface bus. Each endpoint must connect to these signals for proper operation.

Signal	Direction	Description
okHE[112:0]	Output	Control signals to the target endpoints.
okEH[64:0]	Input	Control signals from the target endpoints.
okClk	Output	Buffered copy of the host interface clock (100.8 MHz).

Instantiation of the okHost is simple in either VHDL or Verilog. Use the templates below in your toplevel HDL design. A more detailed listing can be found later in this manual as one of the examples.

Each endpoint is connected to 48 target interface pins on the okHost module. The direction is from the perspective of the endpoint module.

Signal	Direction	Description
okHE[112:0]	Input	Interface control (host to endpoint)
okEH[64:0]	Output	Interface control (endpoint to host)

These signals are present in every endpoint. In the signal tables for the independent endpoints below, we have left out these common signals.

In addition to the target interface pins, the okWireIn adds a single 32-bit output bus called EP_DATAOUT[31:0]. The pins of this bus are connected to your design as wires and act as asynchronous connections from FrontPanel components to your HDL.

When FrontPanel updates the Wire Ins, it writes new values to the wires, then updates them all at the same time. Therefore, although the wires are asynchronous endpoints, they are all updated at the same time on the host interface clock.

Signal	Direction	Description
EP_DATAOUT[31:0]	Output	Wire values output. (sent from host)

An okWireOut module adds a single 32-bit input bus called EP_DATAIN. Signals on these pins are read whenever FrontPanel updates the state of its wire values. In fact, all wires are captured simultaneously (synchronous to the host interface clock) and read out sequentially.

Signal	Direction	Description
EP_DATAIN[31:0]	Input	Wire values input. (to be sent to host)

The okTriggerIn provides EP_CLK and EP_TRIGGER as interface signals. The Trigger In endpoint produces a single-cycle trigger pulse on any of EP_TRIGGER which is synchronized to the clock signal EP_CLK. Therefore, the single-cycle does not necessarily have to be a single host interface cycle. Rather, the module takes care of crossing the clock boundary properly.

Signal	Direction	Description
EP_ADDR[7:0]	Input	Endpoint address.
EP_CLK	Input	Clock to which the trigger should synchronize.
EP_TRIGGER[31:0]	Output	Independent triggers from host.

The target may trigger the host using this module. EP_TRIGGER[31:0] contains 32 independent trigger signals which are monitored with respect to EP_CLK. If EP_TRIGGER[x] is asserted for the rising edge of EP_CLK, then that trigger will be set. The next time the host checks trigger values, the triggers will be cleared.

Signal	Direction	Description
EP_ADDR[7:0]	Input	Endpoint address.
EP_CLK	Input	Clock to which the trigger is synchronized.
EP_TRIGGER[31:0]	Input	Independent triggers to host.

The okPipeIn module provides a way to move synchronous multi-byte data from the host to the target. As usual, the host is the master and therefore the target must accept data as it is moved through this pipe (up to 100.8 MHz). The EP_WRITE signal is an active high signal which is asserted when data is to be accepted by the target on EP_DATAOUT[31:0]. It is possible that EP_WRITE be asserted for several consecutive cycles without deasserting. In such a case, EP_DATAOUT[31:0] will be changing every clock.

This somewhat simple Pipe In implementation requires that the target interface be very responsive to incoming pipe data. If the target is able to keep up with the throughput, but needs to handle data in a block fashion, coupling the okPipeIn with a FIFO (from the Xilinx CORE generator) is a good solution. Alternatively, an okBTPipeIn can be used.

The timing diagram below indicates how data is presented by the okPipeIn to user HDL. EP_DATAOUT contains valid data for any clock cycle where EP_WRITE is asserted during the rising edge of TI_CLK. Note that the transfer sends 4 words in this example. Although contrived, it is important to note that EP_WRITE may deassert during the transfer. This will generally happen with longer transfers (>256 words).

Signal	Direction	Description
EP_ADDR[7:0]	Input	Endpoint address.
EP_DATAOUT[31:0]	Output	Pipe data output.
EP_WRITE	Output	Active high write signal. Data should be captured when this signal is asserted.

The okPipeOut module implements a simple version of the Pipe Out endpoint to move synchronous multi-byte data from the target to the host. Because the host is master, all reads (on the target side) occur at the host’s whim. Therefore, data must be provided whenever EP_READ is asserted.

This simple implementation of a Pipe Out endpoint requires that the target interface be somewhat responsive to host read requests. If the target is able to keep up with the throughput, but needs to handle data in a block fashion, coupling the okPipeOut with a FIFO (from the Xilinx CORE generator) is a good solution. Alternatively, an okBTPipeOut can be used.

The timing diagram below indicates how the user HDL needs to respond to EP_READ with EP_DATAIN valid data. When EP_READ is asserted for the rising edge of TI_CLK, user HDL must respond with valid EP_DATAIN on the next clock edge, subject to setup and hold times appropriate for (T_AS and T_AH in the FPGA CLB timing documentation). Of course, these times are also subject to the particular routing and logic in your HDL implementation. Note that the transfer sends 4 words in this example. Although contrived, it is important to note that EP_READ may deassert during the transfer. This will generally happen with longer transfers (>256 words).

Signal	Direction	Description
EP_ADDR[7:0]	Input	Endpoint address.
EP_DATAIN[31:0]	Input	Pipe data input.
EP_READ	Output	Active-high read signal. Data must be provided in the cycle following as assertion of this signal.

The Block-Throttled Pipe In module is similar to the okPipeIn module, but adds two signals, EP_BLOCKSTROBE and EP_READY to handle block-level negotiation for data transfer. The host is still master, but the FPGA controls EP_READY. When EP_READY is asserted, the host is free to transmit a full block of data. When EP_READY is deasserted, the host will not transmit to the module.

EP_READY could, for example, be tied to a level indicator on a FIFO. When the FIFO has a full block of space available, it will assert EP_READY signifying that it can accept a full block transfer.

Signal	Direction	Description
EP_ADDR[7:0]	Input	Endpoint address.
EP_DATAOUT[31:0]	Output	Pipe data output.
EP_WRITE	Output	Active-high write signal. Data should be captured when this signal is asserted.
EP_BLOCKSTROBE	Output	Active-high block strobe. This is asserted for one cycle just before a block of data is written.
EP_READY	Input	Active-high ready signal. Logic should assert this signal when it is prepared to receive a full block of data.

The Block-Throttled Pipe Out module is similar to the okPipeOut module, but adds two signals, EP_BLOCKSTROBE and EP_READY to handle block-level negotiation for data transfer. The host is still master, but the FPGA controls EP_READY. When EP_READY is asserted, the host is free to read a full block of data. When EP_READY is deasserted, the host will not read from the module.

EP_READY could, for example, be tied to a level indicator on a FIFO. When the FIFO has a full block of data available, it will assert EP_READY signifying that a full block may be read from the FIFO.

Signal	Direction	Description
EP_ADDR[7:0]	Input	Endpoint address.
EP_DATAIN[31:0]	Input	Pipe data input.
EP_READ	Output	Active-high read signal. Data must be provided in the cycle following as assertion of this signal.
EP_BLOCKSTROBE	Output	Active-high block strobe. This is asserted for one cycle just before a block of data is read.
EP_READY	Input	Active-high ready signal. Logic should assert this signal when it is prepared to transmit a full block of data.

The Register Bridge provides synchronous register file access to a 32-bit data, 32-bit address register space. User HDL is responsible for responding to register reads and writes, but is free to interpret the address in any manner.

Register Writes

Drivers Opal Kelly Usb Devices Download

A register write is signalled with the one-cycle assertion of EP_WRITE. When EP_WRITE is asserted, user HDL should capture both the address (on EP_ADDRESS) and data (on EP_DATAOUT). Register writes may occur to any address in any clock cycle, including multiple consecutive cycles.

Register Reads

Drivers Opal Kelly Usb Devices For Sale

A register read is signalled with the one-cycle assertion of EP_READ. When EP_READ is asserted, user HDL should capture the address (EP_ADDRESS) and respond in the next clock cycle by driving EP_DATAIN with the value requested. Register reads may be requested for any address in any clock cycle, including multiple consecutive cycles.

Drivers Opal Kelly Usb Devices 3.0

Signal	Direction	Description
EP_WRITE	Output	Asserted during a write cycle.
EP_READ	Output	Asserted during a read cycle.
EP_ADDRESS[31:0]	Output	Driven with the requested address during read and write cycles.
EP_DATAOUT[31:0]	Output	Driven with valid data during a write cycle.
EP_DATAIN[31:0]	Input	This value is captured in the cycle following a read cycle.

Drivers Opal Kelly Usb Devices Pc Camera