Posts

Showing posts from 2017

Spartan 7 now available

"Xilinx announced today that its Spartan-7 family of FPGAs is now available for order and shipping to standard lead times. As a key member of Xilinx's Cost-Optimized Portfolio, this device family is designed to meet the needs of cost-sensitive markets by delivering low cost and low power entry points that are I/O optimized for connectivity with industry leading performance-per-watt"

For more information:
Spartan-7 general availability announcement
Spartan-7 device page

Match rockets

Image

Introduction to Verilog

Image
This blog motto is FPGA projects in VHDL. It also includes free VHDL books. But, in a past comment on Hacker News I saw this nice Verilog short guide and I knew I have to share it here.

Besides, the FPGA world is evolving. In my experience, it is not enough to know one manufacturer. You may need more. Nor it is enough to know only VHDL. You'd better know also Verilog. And even start thinking to learn other resources and tools, like HLS.

So, now that I have finished (more or less) for publishing this link, here it is

The short, 32 page guide includes the following subjects:

Gate-Level ModellingData TypesOperatorsOperandsModulesBehavioral ModelingFunctionsComponent InferenceFinite State MachinesCompiler DirectivesSystem Tasks and FunctionsTest Benches, andMemories This short and useful Introduction to Verilog is published by Carleton University 




DTMF encoding and decoding

Image
Dual Tone Multi-Frequency (DTMF) is a method for encoding and decoding up to sixteen digits and special characters to be sent over a voice channel.

DTMF was first developed by Bell Systems in United States, for use in push-button dialing telephones (in constrant to prior phones, which had a mechanic rotary dialing system).

DTMF is standardized by ITU-T Recommendation Q.23

A DTMF keypad consists of a matrix of sixteen push buttons organized in four rows by four columns. Each button, when pressed, generates a pair of tones. The tones belong to two groups, a low frequency group (697 to 941 Hz) and a high frequency group (1209 to 1633 Hz). On the picture below you can see the buttons and associated frequencies:


Pressing an '8' generates two tones, one low frequency tone of 852 Hz and one high frequency tone of 1336Hz.

The frequencies were selected so no one would be an harmonic of another DTMF frequency.

As it usually is for many digital transmission systems, the encoder is quite …

Timers block - Part three

Image
In the first part of this tutorial, we commented about the implementation of a single timer.
The second part presented the implementation of a register based timers block,

In this (third) part of the tutorial we will see a different way to implement the timers block. The timers block is a rather thirsty animal, let's see how many resources it needs for several configurations:


Quantity of LUTQuantity of FFSingle 32 bit timer 43 3316 x 32 bit timers block 704 52832 x 32 bit timers block 1,408 1,05632 x 64 bit timers block 2,848 2,080

These numbers can be obtained by changing the DATA_W and TIMERS parameters on the VHDL package file and running synthesis for each configuration. After synthesis, in Vivado, we can get the number of used resources by taking a look at "Report utilization".

A single 32 bit timer takes 33 flip-flops which is quite reasonable. Thirty-two are needed for the timer alone. As the quantity of timers increases (or their width, or both), the quantity of F…

FPGA internal tri-state buses

Image
For many designers, the first time we saw the internal memory blocks in an FPGA came as a little shock.

Some of us were used to RAM devices used in Board Design. These devices use bidirectional data buses. Even the fastest memories, DDRn DRAMs, use bidirectional data buses ('n' has changed over the years, from plain DDR to current DDR4).

So, how comes that internal memories on an FPGA have TWO data buses? Isn't that a waste of resources? Why don't FPGAs have internal tri-state buses?

Well, until around fifteen years ago, some FPGA devices DID have internal tri-state buffers. With the evolution of semiconductors technology, internal tri-state buffers were abandoned. So today, FPGAs don't have tri-state buffers but have unidirectional buses only. Since most memories are readable and writable, two unidirectional data buses are needed between a controller (CPU, internal FPGA logic) and the memory.

If this answer is enough for you, you can stop reading here. If you wan…

The MicroZed chronicles - free FPGA book

Image
Adam Taylor is the well known author of the MicroZed Chronicles blog on Xilinx website. His Chronicles have been running for several years, and Adam has already compiled entries from his blog in two books. The first book is offered for free on the FPGARelated website for registered users.

This is a partial list of the book contents:


Introduction to the ZynqSoftware environment and configurationThe Boot loaderXADCMultiplexed IOTimers, clocks and watchdogsProcessing System and Programmable LogicDMAAdding an Operating SystemMultiProcessingetc.The book can be find here. Author Adam Taylor is a regular contributor on Xilinx Xcell Daily Blog and he also has his own website.




Xilinx Announces General Availability of Virtex UltraScale+ FPGAs in Amazon EC2 F1 Instances

Image
"Xilinx today announced that its high-performance Xilinx® Virtex® UltraScale+™ FPGAs are available in Amazon Elastic Compute Cloud (Amazon EC2) F1 instances. This instance provides programmable hardware acceleration with FPGAs and enables users to optimize their compute resources for the unique requirements of their workloads...

... F1 instances will be used to solve complex science, engineering, and business problems that require high bandwidth, enhanced networking, and very high compute capabilities. They are particularly beneficial for applications that are time sensitive such as clinical genomics, financial analytics, video processing, big data, security, and machine learning. "


The Virtex Ultrascale+ family is based on the new 16 nm FinFET+ technology, and has the following features:
Up to 8GB of HBM Gen2 integrated in-package Up to 500Mb of on-chip memory integration Integrated 100G Ethernet MAC with RS-FEC and 150G Interlaken coresUp to four speed-grade improvement wit…

Size of wind turbines over the years

Image

Square waveform generator

Image
On the following three-part tutorial, a square waveform generator is presented.
The requirements for the project are to generate a sequence of square waveforms with different frequencies. For each frequency a number of cycles is generated (different for each one). For each frequency, a distinct duty cycle is also defined.

In this implementation the frequency is defined in Hz., and the active high time in ns. The VHDL code does not validate the parameters, i.e, if the active high time for any frequency is longer than its period, the output will be always '1' for that frequency. For each frequency, a number of cycles is defined.

This project was born over a discussion in Xilinx forums. Once I did the project for a specific configuration I started thinking about a way to make a generic solution, and this tutorial tries to reflect the design process of this small project.

The code is presented below. Three different frequencies FREQ1..3 are defined for this example, 242KHz, 23kHz …

The single biggest reason why startups succeed

Big Gross (himself an entrepreneur who has founded quite a few startups) analyzes the main reasons for success and failure of startups, and pinpoint a surprising main reason for that.

As time goes by

Image
The comics strip says it all...
... or maybe not.

There are so many missing:

Ethernet, Fast Ethernet, Gigabit EthernetThe diverse Windows versions... and Unix, and LinuxSerial Rapid IO, InfinibandPDAs, disc-man, MP3-player, tablets, digital camerasADSL, optic fiber, and so many others...

BTW, I first thought about this comics strip while reading about IoT. Will it be a success or will it be forgotten?
I remember that in its time, ATM was also thought to be "the next thing, for sure". Well, it didn't happen...
What would your list have?

VHDL or Verilog?

Image
This question gets asked again and again, by beginners and experienced designers alike. When I saw it posted on the FPGA group at reddit at reddit some time ago, I liked the answer from user fft32, so with his permission, I reproduce it here with some minor changes and additions. VHDL compared to VerilogVHDL: A bit verbose, clunky syntax. I never liked that different constructs have different rules for the "end" tag, like "end synth" for architectures, versus "end component mux" for components. I always find myself looking up the syntax of packages and functions.Strongly typed: It's a bit of a pain to have to make a (0 downto 0) vector to do something like a carry-in, but at the end of the day, it can save you time debugging problems. You don't scratch your head as to why your 10-bit vector is only 0 to 1, because you assigned a 1-bit value to it (a thing you could do in Verilog, but in VHDL would produce a compile error). Also, by default Verilog…

Timers Block - Part two

Image
On the previous entry of this series we went through the VHDL source file and simulation of a Timer component. In this entry, we will instantiate several Timer components to create a timer bank (or block of timers). For this purpose we will instantiate the 'Timer' component presented on the first part of the tutorial several times. The instantiation is done inside a VHDL construct called a FOR GENERATE loop (see lines 50 - 61). The code is attached below:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62libraryieee; useieee.std_logic_1164.all; useieee.numeric_std.all; usework.top_pack.all; entitytop_timer_blkisport ( clk:instd_logic; rst:instd_logic; -- inputs data_in:instd_logic_vector (DATA_W-1downto0); -- Data bus, connected to all timers load:instd_logic; -- Load control common to all timers…

High Speed Serial I/O - free book

Image
This book was published by Xilinx in 2005. While in our very dynamic profession, some of the technologies explained can be a bit outdated, the basic concepts are there for anyone who wishes to learn or refresh his/her concepts about high speed serial links. Inside the book you will find data about: Serdes transceivers basics8b/10b, 64b/64b encodingClock recoveryLine equalizationChannel BondingSignal IntegrityPower considerationsBoard design considerations, etc.Book Title: High Speed Serial I/O made simple








SoC and MPSoC

Image
SoC stands for System on Chip. Many electronic applications are based on microprocessors, memories, and peripherals. Traditionally the integration of these system components has been done at the board (PCB) level.

The never-stopping progression in electronic miniaturization has made possible for many of these components (processor, memories, peripherals) to be integrated in a single package, thus called SoC.

On the FPGA arena, it is usual to see applications where the FPGA is integrated with a processor (or processors) at the heart of the system. Until around five years ago, the processors integrated on the FPGAs were mainly soft-core processors, like Nios for Intel-Altera or Microblaze for Xilinx.

Lately, the two major FPGA manufacturers have returned to the trend of including high performance processors as hard-IP on their FPGAs.

In the FPGA world, as in the rest of the digital world, most processors are multi-core. So the acronym MPSoC, means Multi Processor System on Chip.



As an …

Timers block

Image
Hi. In this series of articles, we will experiment with the definition, implementation, simulation and synthesis of a block of timers in VHDL. Along the way, we will: Test the VHDL code blocks using Vivado simulator.Synthesize and implement the VHDL code on Xilinx's Zynq FPGA.Originally this project was used on a relatively small FPGA. The logic for the timers didn't fit so I used the internal memory to implement the solution. In many of my designs I have seen that it is the LUTs (and not the FFs or the internal RAM) what tends to be under heavy utilization. So using the block RAM to implement register (or timers) banks can be a way to fit a design into a device.
So first, let's start with the code for a single timer component:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48libraryieee; useieee.std_logic_1164.all; useieee.numeric_std.all; entitytimerisgeneric ( DATA_W :natu…