Book Image

FPGA Programming for Beginners

By : Frank Bruno
5 (1)
Book Image

FPGA Programming for Beginners

5 (1)
By: Frank Bruno

Overview of this book

Field Programmable Gate Arrays (FPGAs) have now become a core part of most modern electronic and computer systems. However, to implement your ideas in the real world, you need to get your head around the FPGA architecture, its toolset, and critical design considerations. FPGA Programming for Beginners will help you bring your ideas to life by guiding you through the entire process of programming FPGAs and designing hardware circuits using SystemVerilog. The book will introduce you to the FPGA and Xilinx architectures and show you how to work on your first project, which includes toggling an LED. You’ll then cover SystemVerilog RTL designs and their implementations. Next, you’ll get to grips with using the combinational Boolean logic design and work on several projects, such as creating a calculator and updating it using FPGA resources. Later, the book will take you through the advanced concepts of AXI and show you how to create a keyboard using PS/2. Finally, you’ll be able to consolidate all the projects in the book to create a unified output using a Video Graphics Array (VGA) controller that you’ll design. By the end of this SystemVerilog FPGA book, you’ll have learned how to work with FPGA systems and be able to design hardware circuits and boards using SystemVerilog programming.
Table of Contents (16 chapters)
1
Section 1: Introduction to FPGAs and Xilinx Architectures
3
Section 2: Introduction to Verilog RTL Design, Simulation, and Implementation
9
Section 3: Interfacing with External Components

Questions

  1. It's best to use blocking assignments in sequential blocks and non-blocking in combinational blocks.

    a) True

    b) False

  2. It is best to reset all sequential elements in a design.

    a) True

    b) False

  3. What are the most common ways of synchronizing?

    a) always @(posedge signal)

    b) always @(negedge signal)

    c) FIFO or a two-stage synchronizer with or without data.

    d) Synchronizers… who needs synchronizers?

  4. When would we use always @(posedge clk) rather than always_ff @(posedge clk)?

    a) When we get tired of typing.

    b) When we need to use an initial statement to preload the register.

    c) When we need to reset the register either synchronously or asynchronously.

  5. When do we need to add debouncing logic?

    a) When we cross clock domains

    b) Whenever we send data from one FF to another

    c) When we are dealing with electromechanical buttons or switches

Challenge

In Chapter 2, with Combinational Logic, we created a design that could perform some simple operations and...