Digilent Driver

Posted on  by 

Digilent Usb Device Driver Windows 10 Digilent Adept is a unique and powerful solution which allows you to communicate with Digilent system boards and a wide assortment of logic devices. ADEPT for Windows: Adept 2 is a complete redesign of the original Adept framework. The installation program checks if FTDI drivers are already available on the machine and if not installs them. Ubuntu is default equiped with Silabs USB/RS232 drivers, so the FTDI drivers will be installed. It is again possible to specify a location for these drivers.

Video Graphics Array (VGA)

VGA stands for Video Graphics Array. Initially, it refers specifically to the display hardware first introduced with IBM® PS/2 computer in 1987. With the widespread adoption, it now usually refers to the analog computer display standards (defined by VESA®), the DE-15 Connector (commonly known as VGA connector), or the 640x480 resolution itself.

The analog computer display standards is specified, published, copyrighted and sold by the VESA organization (www.vesa.org). The timing information used in this project is an example of how a VGA monitor might be driven in a 640x480 resolution.

A DE-15 connector, commonly known as a VGA connector, is a three row 15-pin D-subminiature Connector (named after their D-shaped metal shield). The name of each pin is shown in Fig. 1 below. We will only concentrate on the 5 signals out of 15 pins in this project. These signals are Red, Grn, Blue, HS, and VS. Red, Grn, and Blue are three analog signals that specify the color of a point on the screen, while HS and VS provide a positional reference of where the point should be displayed on the screen. By properly driving these five signals according to the VGA timing specification, we can display everything we want on any monitors. To understand how these signals should be driven, we need to take a look at how our monitors actually work.

Digilent Driver

In a recent blog post by Adam Taylor, he examines how to approach using Pmods if there is not a driver available. His solution is to use the Pmod bridge in the Zynq SoC’s PL (programmable logic) to correctly map Pmod ports on a development board and to create a Zynq PS (processing system) driver.

Vivado Digilent Driver

Driver

For his example, he uses a Digilent’s DA4 octal DAC Pmod integrated with Digilent’s dual ADC AD2 Pmod.

The Pmod bridge allows for the definition of input types for both the top and bottom rows of the Pmod connector. This setup allows for the user to select from either GPIO, UART, IIC, or SPI interfaces. This helps the Pmod connector align with the standard for interface type.

For his example, he used a SPI interface on the top row. Then he selected the actual SPI communication channel.

As we are using the Zynq SoC, we have two options. The first would be to use an AXI SPI IP block within the PL and connected to the bridge. The second approach—and the one I am going to use—is to connect the bridge to the Zynq PS’ SPI using EMIO. This choice provides us with the ability to wire the pins from the PS SPI ports to the bridge inputs directly

To do this, he mapped the pins for this example, his diagram for the Pmod DA4 is shown below.

He uses the SPI drivers created by the BSP to drive the DA4, and to interact with his device. Then he drove a simple ramp output with the Analog Discovery monitoring the DAC output. One this was working as expected, he connected the DA4 and the AD2 together so that the Zynq SoC could receive the signal:

Digilent Usb Driver Windows 10

If you are interested in this project or learning more about Pmod drivers, please check out the original post and/or his git hub repository.

Coments are closed