Gerry's ULTIMATE VHDL Pong Tutorial

WELCOME TO

GERRY'S ULTIMATE VHDL PONG TUTORIAL

VGA Interfacing and Control using MENTOR GRAPHICS "HDL DESIGNER" Software

and the "Altera DE1" Development Board.

(SEE MY DEVOTED DE1 PAGE AT THE LINK BELOW)

http://www.digital-circuitry.com/MyLAB_IC_PROG_DE1.htm

The Software used in this tutorial is called "HDL Designer" by Mentor Graphics, along with the Various companion programs such as

"ModelSim" and "Precision Synthesis".

Just to inform you all before we go any further...

I will NOT be giving out the full VHDL source code files for download.

If you are new to VHDL programming, I recommend that you review my "VHDL" page as an Introduction.

-= VHDL =-

However, if you are already programming and understand VHDL to some degree then you can skip the Intro and move on ahead.

-= Companion Textbook for this Project=-

A highly recommended Textbook for this project is one of the two books shown Below:

"RAPID PROTOTYPING OF DIGITAL SYSTEMS"

These particular textbooks contain some great information on VGA interfacing and it provides some of the Basic VHDL code for creating a VGA controller. I highly recommended that you purchase one of these books to help solidify your understanding.

This Tutorial will show you how to program the Altera DE1 Development Board, to produce the required VGA control and data signals for displaying 2D color graphics on a VGA Computer Monitor. This in turn, will allow you to produce a basic 2D PONG style Video Game.

Many VHDL PONG style games have been demonstrated online. Such as this one below. This is similar to what your final project will look like once completed. However you are free to add more features to the game if you have the time to do so before the end of your Semester.

Additional features can be added to your Game for those of you who wish to go beyond the outline of this Tutorial. Features such as a Score Board, Time Limit, Sound Effects, or even a Joystick/Game pad Control Interface for two players.
This is definitely encouraged as it will help solidify your understanding of the VHDL code.

This Tutorial uses a screen resolution of (640 x 480) with a 60Hz screen refresh rate. If you want to go all out and attempt to use higher resolution settings such as (800 x 600), (1024 x 768) or even (1600 x 1200) then by all means do so. You would definitely be up for some major bonus points if you can get it to work.

Visit the link below for a list of the various VGA signal timing requirements for different resolution settings.

http://tinyvga.com/vga-timing

This Tutorial can easily be applied to other Development Boards and other VHDL software packages.

Boards such as The Altera DE2, Altera UP1,UP2, CPLDT-2 and Many more. You can even use a Universal Programmer to Program your own CPLD or FPGA. There is also the option of using a JTAG interface Programmer and wiring it up yourself to a JTAG compatible FPGA. This allows you to use a $15.00 JTAG programmer like the Altera "USB-BLASTER" to program your own "Off-the-Shelf" CPLD or FPGA. As long as the FPGA you purchase supports a JTAG interface; then you can wire it up yourself and simply Program it with the same Logic Software you use with your DE1 development board.

Pretty Awesome!!

For a detailed explanation on the JTAG interface, Check out my "JTAG Interface" Page and Instructional Video at the Link Below:

http://www.digital-circuitry.com/MyLAB_IC_PROG_JTAG_ISP.htm

I have prepared a set of Instructional Videos for this project for your review. The videos will cover the concepts needed for you to combine 10 separate VHDL BLOCKs in HDL Designer, to produce a PONG Style Video Game on your Altera DE1 Development Board. You will Interface your DE1 to a VGA monitor using the onboard DB-15 VGA port.

Now, as this is a popular TERM Project for many Colleges and Universities... I will NOT be providing VHDL Source Code files for you to just download, copy and paste into your project and then submit it to your professor and get a free ride for this Project.

I will have various Instructional videos that will go over the fundamental concepts of the project; and I will also have some general VHDL "ARCHITECTURE" and "PROCESS" examples for each of the 10 VHDL blocks. It will be up to you to apply the example code to your own project. I believe it is important that you write out your own code, run simulations and see how things work through trial and Error.

Just Remember...You can do this !!

Try writing out some VHDL code yourself, run MultiSim simulations and you will see how quickly you can learn.

So again, I will NOT be giving out the VHDL source code files for download.

If you use this webpage and my Instructional Video's as a Guide, You will do just fine! :)

You can do this !!

Now, if I were to answer the 100's of e-mails you all send me, asking for help with your VHDL code, I would not be able to find the time to work or even eat. :) So please Register, and ask all of your VHDL related questions on the edaboard.com CPLD/FPGA Digital Design Forum.

http://www.edaboard.com/forum30.html

If you need some help with your VHDL code or other Engineering related projects...the edaboard.com forum is the place to go. You can talk with other Professionals in the industry to help troubleshoot and solve your VHDL coding issues. Their Forum web-based GUI is outfitted with both "CODE" and "COMMENT" formatting. This makes your Message posts very clear and organized. Having your message posts clearly formatted this way, allows others to assist you more efficiently and in a timely manner. So this is a Fantastic resource and I highly recommend that you join.

The VGA Interface

The VGA interface was Standardized by IBM in 1987 with signal requirements to display color images on a Cathode Ray Tube computer Monitor or (CRT) for short. When LCD monitors were later released, they adopted the same VGA signal standard in order to function with the current computer infrastructure out in the world.

CRT - Cathode Ray Tube

CRT & LCD Differences

CRT & LCD - Cutaway Diagram

Therefore LCD Monitors have an internal translator circuit that converts VGA Signals to the required Liquid Crystal display control Signals. This all happens automatically inside the LCD Monitors circuitry and it works all the same to us. So we don't have to worry about it.

We're Good to Go!

The VGA Interface - Signal Requirements

Basically there are 5 separate signal requirements for the VGA interface to function. These are H-SYNC & V-SYNC resolution control signals and the RED, GREEN and BLUE color display signals.

The H-SYNC & V-SYNC signals you send to the monitor, dictate which Resolution setting you are attempting to use. Depending on the monitor, it may only support a specific resolution, where other Monitors may support more than one. The Monitor stores reference signal Patterns for all of the available resolution settings, within an EEPROM memory chip that is part of the monitors internal circuitry.

Each resolution setting requires a specific H-SYNC & V-SYNC frequency Pulse width, and Duty Cycle. These signal requirements have been Standardized by IBM. We will be using the oldest and smallest screen resolution size available, as most VGA monitors will support it.

That being the VGA 640 x 480 Resolution with a 60Hz Refresh Rate.

The RED, GREEN and BLUE color control signal lines, each use Analog Voltage levels between (0.0 to 0.7 Volts DC) to determine the amount of color intensity used for each Pixel. As you know, all colors are made up from mixing various amounts of RED, GREEN and BLUE together.

H-SYNC & V-SYNC Pulse Signals

Try and view the H-SYNC and V-SYNC signals like Custom "COUNTERS" that are constantly running and counting up to their MAXIMUM declared value, resetting to zero and then counting up once again. Every time the H-SYNC counter resets to zero, the V-SYNC counter is only incremented by 1.

The animated GIF Image shown below shows how the H-SYNC & V-SYNC signals are used together to create the Screen Refresh Cycle. When you look at these signals like (X & Y) counters, they essentially count through each Pixels on the screen from the Top Left corner all the way down in sequence to the Bottom Right corner. This process repeats 60 times per second, due to the fact that we are using a 60Hz refresh rate.

The H-SYNC and V-SYNC signal patterns that we send to the VGA monitor, when working together, they create the Zig-Zag scanning effect as shown below. Now, depending on the Frequency, Pulse Width and Duty Cycle of these signal patterns...we can create different resolution settings for the monitor to display.

So we have a specific H-SYNC and V-SYNC signal Pattern for creating the Zig-Zag scanning cycle of a 640 X 480 screen resolution, and we also have another H-SYNC and V-SYNC signal Pattern for a 1600 X 1200 screen resolution, and many more.

The Image above is actually showing what's called Interlaced Frames. You don't really need to worry about that right now, as we are not using this particular format. The animated image is mainly being used to show you the basic concept of a screen "Refresh Cycle".

Now the fact that we are using a resolution setting of (640 x 480) this means that we have 640 Pixels that run from the left side of our screen to the Right Side. This also means that we have 480 Pixels that run from the Top of the screen to the Bottom.

In other words, what we have here is a 640 X 480 Pixel Matrix.

You can consider the Top Left corner of the Screen as the starting point for your H-SYNC and V-SYNC counters starting at Zero. The H-SYNC Counter then proceeds to increment through all 640 pixels on the first horizontal row from Left to Right. Once it reaches the end of the Row, it then resets to the beginning. However this time, it also moves down by one pixel to the next Row and increments the V-SYNC counter by 1.

This process is repeated until the V-SYNC counter counts to 479, which brings it to the last Row at the Bottom of the screen. Then, when the H-SYNC counter reaches the last pixel on the Bottom Right corner of the Screen (639), both the H-SYNC and V-SYNC counters are reset to Zero.

This brings us back to the Top Left corner pixel and the entire counting Process starts all over again.

A single pass over the entire screen is called a "Screen Refresh Cycle" and this is repeated 60 times per second to refresh the screen and update each pixel for a particular color... and in turn, this produces an Image on the screen.

Review the Animated GIF image above to get a better understanding of this "Screen Refresh" process in action.

-= Overview of our 10 Block VHDL Circuit =-

-= VHDL BLOCKS - Architecture Examples =-

Below I have provided some VHDL "Architecture" and "PROCESS" examples similar to what you would need for each of the 10 VHDL Blocks to perform their specific function. It is up to you to figure out how to apply the code to your own project, and generate the signals you need.

VHDL BLOCK #1 - The Clock Divider

The clock divider should be a snap for you to figure out, so no real need for an example. For our VGA project we require a CLOCK signal of 25.175 MHz. 25 MHz in our case is fine. We accomplish this by dividing the DE1 boards 50Mhz Clock signal in half.

For MultiSim simulations:

For a 50MHz CLOCK setting use a Clock Period of 20ns.

For a 25MHz CLOCK setting use a Clock Period of 40ns.

VHDL BLOCK #2 & #3 - A typical MOD Counter Example

(My MOD_25 Counter with a Power ON Reset line, and a 25Mhz Clock)

Single MOD Counter Example

VHDL BLOCK #2 and #3: MOD COUNTER EXAMPLE ARCHITECTURE MOD_25_arch OF MOD_25_nty IS SIGNAL SIG_h_count : STD_LOGIC_VECTOR (10 DOWNTO 0):= (others => '0'); BEGIN Counter_A <= SIG_h_count; PROCESS (Por, clk_25Mhz) BEGIN IF(Por = '1') THEN SIG_h_count <= "00000000000"; ELSIF (rising_edge(clk_25Mhz) AND SIG_h_count = 24) THEN SIG_h_count <= "00000000000"; ELSIF(rising_edge(clk_25Mhz)) THEN SIG_h_count <= SIG_h_count + 1; END IF; END PROCESS; END ARCHITECTURE MOD_25_arch;

If you are having trouble getting the VGA controller Pulses to function properly, try changing the reset State of the MOD counters. Try these counter values below and and run some simulations.

MOD-800 = Counts from 0 to 793

MOD-525 = Counts from 0 to 522

VHDL BLOCK #4 & #5 - The Horizontal & Vertical Decoder State Machines

(MOMENTARY PULSES FOR OUTPUT LINES)

Be aware that this particular VHDL State machine will only create Momentary Logic High Pulses on your outputs. The output STATE_ lines will remain HIGH for only 1 Clock Pulse, based on the input CLK source used for this particular VHDL Block.

(The STATE_outputs need to be fed into a "Latch" circuit to be held HIGH for any length of time.)

Single State Machine Example

VHDL BLOCKS #4 and #5: H / V - DECODER STATE MACHINE EXAMPLE ARCHITECTURE DECODER_arch OF DECODER_nty IS BEGIN ------------------------------------ STATE SIGNALS & "Horizontal counter has Reset" Signal ----------------------------- ---------------------------------------------------------------------------------------------------------------------- PROCESS (MOD_COUNTER) BEGIN CASE (MOD_COUNTER) IS -- At counter value Binary "00000000000" Only State_A output is logic HIGH for 1 Clock pulse ONLY!! WHEN "00000000000" => State_A <= '1'; State_B <= '0'; clk_full_h_count_cycle <= '0'; -- | -- | -- | -- \_/ -- MORE CASE STATEMENTS CAN BE ADDED IF REQUIRED -- -- (You can also add MORE STATE_ LINES within the Case statement. My examples here only have two "STATE_A" & "STATE_B" ) -- | -- | -- | -- \_/ WHEN "01100100000" => -- At Counter value Binary "01100100000" only the State_B output Port is Logic HIGH for 1 Clock pulse ONLY!!. State_A <= '0'; State_B <= '1'; clk_full_h_count_cycle <= '0'; --( THIS LINE WAS NOT USED IN THIS EXAMPLE BUT COULD HAVE BEEN IF IT WAS REQUIRED) WHEN OTHERS => -- At any other counter value than what is declared above, all output ports are Logic LOW. State_A <= '0'; State_B <= '0'; clk_full_h_count_cycle <= '0'; END CASE; END PROCESS; END ARCHITECTURE DECODER_arch;

Above are some examples of various counter State Pulses.

In the screen Capture shown above, Pay close attention to the time difference between the two Markers,

and how they relate to the other States Shown.

The Horizontal & Vertical "SYNC" & "DISPLAY_TIME" Signals

(LATCH CIRCUIT STATE MACHINES AS SHOWN BELOW)

-= Horizontal "SYNC" Signal Timing Waveforms=-

In the "SIGNAL TIMING" Diagrams that follow, they show the Horizontal & Vertical "SYNC" Pulses and also the Horizontal and Vertical "DISLAY_TIME" Pulses. These Waveform patterns occur in a repeating sequence and I have indicated the starting and stoping points of this repeating pattern.

I have also included the H-DECODER and V-DECODER Momentaty HIGH PULSE States, in relation to the waveform Pattern in question.

-= Horizontal "DISPLAY_TIME" Signal Waveforms =-

-= Vertical "SYNC" Signal Waveforms =-

-= Vertical "DISPLAY_TIME" Signal Waveforms =-

(LATCH CIRCUIT STATE MACHINES)

The VHDL Code below is an Example of a "Latch" circuit that will activate an output signal to remain either HIGH or LOW for any length of time until the output in question is assigned to change its state (LATCH RESET). Input Pulses are used to as Triggers to initiate any changes. This is essentially the type of circuit that you need to implement for each of the signals as shown in the above Waveform diagrams.

"LATCH" circuit EXAMPLES used to Generate the HORIZONTAL and VIRTICAL "SYNC" and "DISPLAY" signals. ARCHITECTURE HORZ_VERT_arch OF HORZ_VERT_nty IS BEGIN --------------------------------------------- PROCESS "LATCH #1" ---------------------------------------------------------- -------------------------- Holds output HIGH for a certain number of clock pulses -------------------------------------- Process (State_000, State_25) BEGIN CASE State_000 IS WHEN '1' => OUTPUT_A <= '1'; -- OUTPUT_A will Rise to a Logic HIGH STATE ONLY! when "State_000" => '1' WHEN OTHERS => null; -- OUTPUT_A will remain "LATCHED" in a HIGH state until assigned to equal a Logic '0'. END CASE; CASE State_25 IS WHEN '1' => OUTPUT_A <= '0'; -- OUTPUT_A has been assigned to equal a Logic '0'. WHEN OTHERS => null; -- Latch "RESET" by the Momentary PULSE of "State_25". END CASE; END PROCESS; --------------------------------------------- PROCESS "LATCH #2" ---------------------------------------------------------- -------------------------- Holds output HIGH for a certain number of clock pulses -------------------------------------- Process (State_100, State_246) BEGIN CASE State_100 IS WHEN '1' => OUTPUT_B <= '0'; -- OUTPUT_B has been assigned to equal a Logic '0'. WHEN OTHERS => null; -- Latch "RESET" by the Momentary PULSE of "State_100". END CASE; -- | -- | -- | -- \_/ -- MORE CASE STATEMENTS CAN BE ADDED IF REQUIRED -- -- (You can also add MORE STATE_ LINES within the Case statement. -- You Can also add multiple PROCESSes if required -- -- | -- | -- | -- \_/ CASE State_246 IS WHEN '1' => OUTPUT_B <= '1'; -- OUTPUT_B will Rise to a Logic HIGH STATE ONLY! when "State_246" => '1' WHEN OTHERS => null; -- OUTPUT_B will remain "LATCHED" in a HIGH state until assigned to equal a Logic '0'. END CASE; END PROCESS; END ARCHITECTURE HORZ_VERT_arch;

Displaying Objects on the Screen

Now things do get a little more complicated here. I will have a couple of "DISPLAY PROCESS" examples to guide you along the way, however it is up to you to figure out how to add the Movement controls to your objects. :)

The best way to understand how basic colored objects are displayed on the screen is as Follows:

Try to look at the Horz. and Vert. MOD counters, more like an (X & Y) 2D coordinate system on a Map.

So envision our Horz. and Vert. MOD counters like the X & Y position coordinates for a Flashlight that is scanning the screen. This Flashlight is checking Labels on every pixel it comes across. The Labels indicate which color that particular Pixel should display. Red, Green or Blue, or any combination of the three.

The way we do this in VHDL is to use an additional set of std_logic_vectors or (COUNTERS) just like that used to generate the H-SYNC and V-SYNC signals. The Counter Pairs become the (X & Y) Reference coordinates for each individual object that we display on the screen. This means that we will need an (X & Y) Counter pair, for each separate object that we have on the Screen.

So, as our Horz. and Vert. MOD counters are running through the screen Refresh cycle, if at any point the counters happen to have the exact same X and Y coordinates as one of the New (X & Y) Counter Pairs.......:

(Y_REFERENCE_COUNTER = V-COUNTER ... "AND".... X_REFERENCE_COUNTER = H-COUNTER)

then we can use this condition to activate the RGB lines to start displaying a particular color. I REPEAT!!... "STARTING" from those (X & Y) coordinates. This means that you have to ADD the number of (X & Y) pixels for the object that you wish to display, to the Statement shown above. Because you have essentially only told the system where to start painting the colors but not actually which way to go...UP/DOWN/LEFT/RIGHT or even where to stop.

Here is a Hint.

(Y_REFERENCE_COUNTER = V-COUNTER ... "AND".... X_REFERENCE_COUNTER = H-COUNTER + size)

There is still a little more to it, so review the "DISPLAY PROCESS" examples I have provided below, and see if you can figure it out. :)

"BALL" Display PROCESS Example - VHDL Block #7

BALL Display PROCESS Example ============================================================================================== BEGIN pixel_ROW <= V-COUNTER (10 downto 0); -- 10-bit Counter values from 11-bit Counters pixel_COLUMN <= H-COUNTER (10 downto 0); ---------------------------- BALL SIZE --------------------------------- ------------------------------------------------------------------------ size <= CONV_STD_LOGIC_VECTOR(8,11); --------------- COLORS FOR PIXEL DATA ON VIDEO SIGNAL ------------------ ------------------------------------------------------------------------ BALL_RED <= '1'; -- BALL is RED (Color RED turned on) BALL_GREEN <= NOT BALL_on; -- TURN OFF GREEN & BLUE when displaying the BALL. BALL_BLUE <= NOT BALL_on; --------------------------------------- RGB DISPLAY PROCESS ------------------------------------------ ------------------------------------------------------------------------------------------------------ -- As the Horizontal & Vertical scanning lines (AKA counters) increment through each X & Y coordinate....& the particular counter address -- where the BALL resides, the BALL_on is <= '1'. In turn diplaying the assigned color for those particular coordinates of the screen. RED color in our case. -- which results in a red square being displayed for the ball coordinates. RGB_DISPLAY: PROCESS (BALL_Y_position, BALL_X_position, pixel_COLUMN, pixel_ROW, size) BEGIN IF (BALL_X_position <= pixel_COLUMN + size) AND -- As the Pixel_column counter scans across the screen horizontally, (BALL_X_position + size >= pixel_COLUMN) AND -- and the Ball edge is detected. As the Pixel_column counter is counting -- within the ball coordinates (Side edge to side edge of the ball on the x axis) (BALL_Y_position <= pixel_ROW + size) AND -- As the Pixel_ROW counter scans across the screen Vertically, and the Ball edge (BALL_Y_position + size >= pixel_ROW) THEN -- is detected. As the Pixel_ROW counter is counting within the the ball coordinates -- (Top edge to Bottom edge of the ball on the Y axis) BALL_on <= '1'; ELSE BALL_on <= '0'; END IF; END PROCESS RGB_DISPLAY; END ARCHITECTURE BAL_arch;

"PADDLE #1" Display PROCESS Example - VHDL Block #8 & #9

PADDLE #1 Display PROCESS Example ============================================================================================== BEGIN PAD1_pixel_ROW <= V-COUNTER (10 downto 0); -- 10-bit Counter values from 11-bit Counters PAD1_pixel_COLUMN <= H-COUNTER (10 downto 0); PAD1_X_position_REF <= PAD1_X_position; PAD1_Y_position_REF <= PAD1_Y_position; ---------------------------- PADDLE #1 SIZE --------------------------------- ------------------------------------------------------------------------ PAD1_VERT_size <= CONV_STD_LOGIC_VECTOR(64,11); PAD1_HORZ_size <= CONV_STD_LOGIC_VECTOR(16,11); ------------------------- Paddle #1 CENTER ADDRESS -------------------------- ------------------------------------------------------------------------ PAD1_X_position <= CONV_STD_LOGIC_VECTOR(590,11); --------------- COLORS FOR PIXEL DATA ON VIDEO SIGNAL ------------------ ------------------------------------------------------------------------ PADDLE_01_BLUE <= '1'; -- Paddle #1 is BLUE (Color BLUE turned on) PADDLE_01_GREEN <= NOT PAD1_on; -- TURN OFF GREEN & RED when displaying Paddle #1. PADDLE_01_RED <= NOT PAD1_on; --------------------------------------- RGB DISPLAY PROCESS ------------------------------------------ ------------------------------------------------------------------------------------------------------ -- As the Horizontal & Vertical scanning lines (AKA counters) increment through each X & Y coordinate....& the particular counter address -- where Paddle #1 resides, the PAD1_on is <= '1'. In turn diplaying the assigned color for those particular coordinates of the screen. RED color in our case. -- which results in a red Rectangle being displayed for the Paddle #1 coordinates. RGB_DISPLAY: PROCESS (PAD1_Y_position, PAD1_X_position, PAD1_pixel_COLUMN, PAD1_pixel_ROW, PAD1_VERT_size, PAD1_HORZ_size) BEGIN IF (PAD1_X_position <= PAD1_pixel_COLUMN + PAD1_HORZ_size) AND -- As the PAD1_pixel_column counter scans across the screen horizontally, (PAD1_X_position + PAD1_HORZ_size >= PAD1_pixel_COLUMN) AND -- and the Paddle #1 edge is detected. As the PAD1_pixel_column counter is -- counting within the Paddle #1 coordinates (Side edge to side edge of the -- paddle #1 on the x axis) (PAD1_Y_position <= PAD1_pixel_ROW + PAD1_VERT_size) AND -- As the PAD1_pixel_ROW counter scans across the screen Vertically, and the (PAD1_Y_position + PAD1_VERT_size >= PAD1_pixel_ROW) THEN -- Paddle #1 edge is detected. As the PAD1_pixel_ROW counter is counting within -- the the Paddle #1 coordinates (Top edge to Top edge of the Paddle #1 on the -- Y axis) PAD1_on <= '1'; ELSE PAD1_on <= '0'; END IF; END PROCESS RGB_DISPLAY; END ARCHITECTURE PADDLE_01_ARCHIT;

Also review pages 208 and 209 from the Accompanying Textbook I mentioned earlier.

-= Bouncing Ball =-

Below are 2 "PROCESS" examples that might give you some ideas to get a Ball bouncing on the Screen.

Review the two examples, Try the Code, manipulate it, change it around with your own ideas... try different things and see if you can get a Ball to display and bounce on the Screen.

Now, to get the Ball Collisions working with the Paddles....this may prove to be more challenging.

Hopefully these "PROCESS" examples will help get you started and thinking of better ways of writing your own VHDL code.

============================================================================================================= - PROCESS EXAMPLE #1- ============================================================================================================= ------------------------------------ BALL Movement in the Y AXIS PROCESS ------------------------------- ------------------------------------------------------------------------------------------------------------------ MOVE_BALL_Y: PROCESS BEGIN WAIT UNTIL (Vert_sync_PULSE'EVENT AND Vert_sync_PULSE = '1'); -- Move ball once every Vertical sync pulse --=============================================== -- BALL - HITS BOTTOM moving LEFT or RIGHT --=============================================== IF ((BALL_Y_position >= SCREEN_Y_BOTTOM - size) AND (BALL_X_motion <= LEFT_DIRECTION)) OR ((BALL_Y_position >= SCREEN_Y_BOTTOM - size) AND (BALL_X_motion <= RIGHT_DIRECTION)) THEN --------------- Ball MOVES UP -------------- BALL_Y_motion <= UP_DIRECTION; -- Move "UP" on the Screen by 2 Pixels every Vertical sync Pulse --=============================================== -- BALL - HITS TOP moving LEFT OR RIGHT --=============================================== ELSIF ((BALL_Y_position <= SCREEN_Y_TOP + size) AND (BALL_X_motion <= LEFT_DIRECTION)) OR ((BALL_Y_position <= SCREEN_Y_TOP + size) AND (BALL_X_motion <= RIGHT_DIRECTION)) THEN --------------- Ball MOVE DOWN -------------- BALL_Y_motion <= DOWN_DIRECTION; -- Move "DOWN" on the Screen by 2 Pixels every Vertical sync Pulse ============================================================================================================= - PROCESS EXAMPLE #2- ============================================================================================================= MOVE_BALL_X: PROCESS BEGIN WAIT UNTIL (Vert_sync_PULSE'EVENT AND Vert_sync_PULSE = '1'); -- Move ball once every Vertical sync pulse --=============================================== -- BALL - HITS RIGHT moving UP --=============================================== -- IF the BALL_X_Position value reaches the "RIGHT" side of the screen AND is moving UP ---------- IF ((BALL_X_position >= SCREEN_X_RIGHT - size) AND (BALL_Y_motion <= UP_DIRECTION)) THEN --------------- Ball MOVES LEFT -------------- BALL_X_motion <= LEFT_DIRECTION; -- Move "LEFT" on the Screen by 2 Pixels every Vertical sync Pulse --=============================================== -- BALL - HITS RIGHT moving DOWN --=============================================== -- IF the BALL_X_Position value reaches the "RIGHT" side of the screen AND is moving DOWN ---------- ELSIF ((BALL_X_position >= SCREEN_X_RIGHT - size) AND (BALL_Y_motion <= DOWN_DIRECTION)) THEN --------------- Ball MOVES LEFT -------------- BALL_X_motion <= LEFT_DIRECTION; -- Move "LEFT" --=============================================== -- BALL - HITS LEFT moving UP --=============================================== -- IF the BALL_X_Position value reaches the "LEFT" side of the screen AND is moving UP ---------- ELSIF ((BALL_X_position <= SCREEN_X_LEFT + size) AND (BALL_Y_motion <= UP_DIRECTION)) THEN --------------- Ball MOVE RIGHT -------------- BALL_X_motion <= RIGHT_DIRECTION; -- Move "RIGHT" on the Screen by 2 Pixels every Vertical sync Pulse --=============================================== -- BALL - HITS LEFT moving DOWN --=============================================== -- IF the BALL_X_Position value reaches the "LEFT" side of the screen AND is moving DOWN ---------- ELSIF ((BALL_X_position <= SCREEN_X_LEFT + size) AND (BALL_Y_motion <= DOWN_DIRECTION)) THEN --------------- Ball MOVE RIGHT -------------- BALL_X_motion <= RIGHT_DIRECTION;

-= Ball Collisions =-

(VIDEO PART #4 - TO BE POSTED)

ADDITIONAL NOTES REGARDING BALL COLLISONS:

The details below regarding paddle collisions might be a bit overkill for most of you. However, if you are a perfectionists and are getting really frustrated because the ball collisions with your paddles are not behaving the way you want them to....you may want to read the details shown below:

It is important to realize that no matter which direction the ball is travelling, UP, DOWN or on an Angle; the conditions that you apply to each paddle for a Ball Collision; each condition will cause the same response regardless of which side the Ball collides on the Paddle.

This is because it is single object.

The collision conditions for each paddle are based on its X&Y counter Pair.

To have different collision responses for each of the 4 sides,

you in turn need 4 Separate Counter pairs or 4 separate sides that make up one paddle.

The "RGB" Concatenation & Display Block

This Block is simply a group of "AND" gates that join or "CONCATENATE" all of the RGB colors together into one MASTER RGB Output.

So you essentially have a Multi-Input "AND" gate for each of the individual RGB Colors. One for all of the RED colors, one for all of the GREEN, and one for all of the BLUE. Finally this MASTER RGB output can only be active during the Horizontal Display Time "AND" the Vertical Display Time. So yet another "AND" gate is used activate the MASTER RGB output... only when H-DISPAY_TIME & V-DISPLAY_TIME are in a Logic HIGH state.

Altera DE1 Board - Unused RGB lines must be tied to GND.

It is important to make sure that you tie any unused RGB input lines to GND. As these can sometimes cause the unconnected signals to Float, producing interference and noise on your VGA monitor.

Well that about sums it up Folks. :)

Hopefully this Tutorial will at least get you a little closer to finalizing your VHDL PONG Projects!

Fun Stuff!!

Cheers Everyone!

-Gerry

-= END =-

Current Time:
-= HOME =- -= BLOG =- -== BIO ==- -=CONTACT=- -=MY LAB=- -=CHIPPERY=- -PROJECTS- -= LINKS =- -= VHDL =- -=YouTube=-	Gerry's Current Research & Development Projects Programmer -= SEGA =- -= ALTERA LP6 =- -= NKK SMART DISPLAY =- Gerry's Completed Projects GAME GEAR -== SMS ==- GAME BOY -== NGPC ==- -=VHDL VGA PONG=- -== LCD DISPLAYS ==-
	WELCOME TO GERRY'S ULTIMATE VHDL PONG TUTORIAL VGA Interfacing and Control using MENTOR GRAPHICS "HDL DESIGNER" Software and the "Altera DE1" Development Board. (SEE MY DEVOTED DE1 PAGE AT THE LINK BELOW) http://www.digital-circuitry.com/MyLAB_IC_PROG_DE1.htm The Software used in this tutorial is called "HDL Designer" by Mentor Graphics, along with the Various companion programs such as "ModelSim" and "Precision Synthesis". Just to inform you all before we go any further... I will NOT be giving out the full VHDL source code files for download. If you are new to VHDL programming, I recommend that you review my "VHDL" page as an Introduction. -= VHDL =- However, if you are already programming and understand VHDL to some degree then you can skip the Intro and move on ahead. -= Companion Textbook for this Project=- A highly recommended Textbook for this project is one of the two books shown Below: "RAPID PROTOTYPING OF DIGITAL SYSTEMS" These particular textbooks contain some great information on VGA interfacing and it provides some of the Basic VHDL code for creating a VGA controller. I highly recommended that you purchase one of these books to help solidify your understanding. This Tutorial will show you how to program the Altera DE1 Development Board, to produce the required VGA control and data signals for displaying 2D color graphics on a VGA Computer Monitor. This in turn, will allow you to produce a basic 2D PONG style Video Game. Many VHDL PONG style games have been demonstrated online. Such as this one below. This is similar to what your final project will look like once completed. However you are free to add more features to the game if you have the time to do so before the end of your Semester. Additional features can be added to your Game for those of you who wish to go beyond the outline of this Tutorial. Features such as a Score Board, Time Limit, Sound Effects, or even a Joystick/Game pad Control Interface for two players. This is definitely encouraged as it will help solidify your understanding of the VHDL code. This Tutorial uses a screen resolution of (640 x 480) with a 60Hz screen refresh rate. If you want to go all out and attempt to use higher resolution settings such as (800 x 600), (1024 x 768) or even (1600 x 1200) then by all means do so. You would definitely be up for some major bonus points if you can get it to work. Visit the link below for a list of the various VGA signal timing requirements for different resolution settings. http://tinyvga.com/vga-timing This Tutorial can easily be applied to other Development Boards and other VHDL software packages. Boards such as The Altera DE2, Altera UP1,UP2, CPLDT-2 and Many more. You can even use a Universal Programmer to Program your own CPLD or FPGA. There is also the option of using a JTAG interface Programmer and wiring it up yourself to a JTAG compatible FPGA. This allows you to use a $15.00 JTAG programmer like the Altera "USB-BLASTER" to program your own "Off-the-Shelf" CPLD or FPGA. As long as the FPGA you purchase supports a JTAG interface; then you can wire it up yourself and simply Program it with the same Logic Software you use with your DE1 development board. Pretty Awesome!! For a detailed explanation on the JTAG interface, Check out my "JTAG Interface" Page and Instructional Video at the Link Below: http://www.digital-circuitry.com/MyLAB_IC_PROG_JTAG_ISP.htm I have prepared a set of Instructional Videos for this project for your review. The videos will cover the concepts needed for you to combine 10 separate VHDL BLOCKs in HDL Designer, to produce a PONG Style Video Game on your Altera DE1 Development Board. You will Interface your DE1 to a VGA monitor using the onboard DB-15 VGA port. Now, as this is a popular TERM Project for many Colleges and Universities... I will NOT be providing VHDL Source Code files for you to just download, copy and paste into your project and then submit it to your professor and get a free ride for this Project. I will have various Instructional videos that will go over the fundamental concepts of the project; and I will also have some general VHDL "ARCHITECTURE" and "PROCESS" examples for each of the 10 VHDL blocks. It will be up to you to apply the example code to your own project. I believe it is important that you write out your own code, run simulations and see how things work through trial and Error. Just Remember...You can do this !! Try writing out some VHDL code yourself, run MultiSim simulations and you will see how quickly you can learn. So again, I will NOT be giving out the VHDL source code files for download. If you use this webpage and my Instructional Video's as a Guide, You will do just fine! :) You can do this !! Now, if I were to answer the 100's of e-mails you all send me, asking for help with your VHDL code, I would not be able to find the time to work or even eat. :) So please Register, and ask all of your VHDL related questions on the edaboard.com CPLD/FPGA Digital Design Forum. http://www.edaboard.com/forum30.html If you need some help with your VHDL code or other Engineering related projects...the edaboard.com forum is the place to go. You can talk with other Professionals in the industry to help troubleshoot and solve your VHDL coding issues. Their Forum web-based GUI is outfitted with both "CODE" and "COMMENT" formatting. This makes your Message posts very clear and organized. Having your message posts clearly formatted this way, allows others to assist you more efficiently and in a timely manner. So this is a Fantastic resource and I highly recommend that you join. The VGA Interface The VGA interface was Standardized by IBM in 1987 with signal requirements to display color images on a Cathode Ray Tube computer Monitor or (CRT) for short. When LCD monitors were later released, they adopted the same VGA signal standard in order to function with the current computer infrastructure out in the world. CRT - Cathode Ray Tube CRT & LCD Differences CRT & LCD - Cutaway Diagram Therefore LCD Monitors have an internal translator circuit that converts VGA Signals to the required Liquid Crystal display control Signals. This all happens automatically inside the LCD Monitors circuitry and it works all the same to us. So we don't have to worry about it. We're Good to Go! The VGA Interface - Signal Requirements Basically there are 5 separate signal requirements for the VGA interface to function. These are H-SYNC & V-SYNC resolution control signals and the RED, GREEN and BLUE color display signals. The H-SYNC & V-SYNC signals you send to the monitor, dictate which Resolution setting you are attempting to use. Depending on the monitor, it may only support a specific resolution, where other Monitors may support more than one. The Monitor stores reference signal Patterns for all of the available resolution settings, within an EEPROM memory chip that is part of the monitors internal circuitry. Each resolution setting requires a specific H-SYNC & V-SYNC frequency Pulse width, and Duty Cycle. These signal requirements have been Standardized by IBM. We will be using the oldest and smallest screen resolution size available, as most VGA monitors will support it. That being the VGA 640 x 480 Resolution with a 60Hz Refresh Rate. The RED, GREEN and BLUE color control signal lines, each use Analog Voltage levels between (0.0 to 0.7 Volts DC) to determine the amount of color intensity used for each Pixel. As you know, all colors are made up from mixing various amounts of RED, GREEN and BLUE together. H-SYNC & V-SYNC Pulse Signals Try and view the H-SYNC and V-SYNC signals like Custom "COUNTERS" that are constantly running and counting up to their MAXIMUM declared value, resetting to zero and then counting up once again. Every time the H-SYNC counter resets to zero, the V-SYNC counter is only incremented by 1. The animated GIF Image shown below shows how the H-SYNC & V-SYNC signals are used together to create the Screen Refresh Cycle. When you look at these signals like (X & Y) counters, they essentially count through each Pixels on the screen from the Top Left corner all the way down in sequence to the Bottom Right corner. This process repeats 60 times per second, due to the fact that we are using a 60Hz refresh rate. The H-SYNC and V-SYNC signal patterns that we send to the VGA monitor, when working together, they create the Zig-Zag scanning effect as shown below. Now, depending on the Frequency, Pulse Width and Duty Cycle of these signal patterns...we can create different resolution settings for the monitor to display. So we have a specific H-SYNC and V-SYNC signal Pattern for creating the Zig-Zag scanning cycle of a 640 X 480 screen resolution, and we also have another H-SYNC and V-SYNC signal Pattern for a 1600 X 1200 screen resolution, and many more. The Image above is actually showing what's called Interlaced Frames. You don't really need to worry about that right now, as we are not using this particular format. The animated image is mainly being used to show you the basic concept of a screen "Refresh Cycle". Now the fact that we are using a resolution setting of (640 x 480) this means that we have 640 Pixels that run from the left side of our screen to the Right Side. This also means that we have 480 Pixels that run from the Top of the screen to the Bottom. In other words, what we have here is a 640 X 480 Pixel Matrix. You can consider the Top Left corner of the Screen as the starting point for your H-SYNC and V-SYNC counters starting at Zero. The H-SYNC Counter then proceeds to increment through all 640 pixels on the first horizontal row from Left to Right. Once it reaches the end of the Row, it then resets to the beginning. However this time, it also moves down by one pixel to the next Row and increments the V-SYNC counter by 1. This process is repeated until the V-SYNC counter counts to 479, which brings it to the last Row at the Bottom of the screen. Then, when the H-SYNC counter reaches the last pixel on the Bottom Right corner of the Screen (639), both the H-SYNC and V-SYNC counters are reset to Zero. This brings us back to the Top Left corner pixel and the entire counting Process starts all over again. A single pass over the entire screen is called a "Screen Refresh Cycle" and this is repeated 60 times per second to refresh the screen and update each pixel for a particular color... and in turn, this produces an Image on the screen. Review the Animated GIF image above to get a better understanding of this "Screen Refresh" process in action. -= Overview of our 10 Block VHDL Circuit =- -= VHDL BLOCKS - Architecture Examples =- Below I have provided some VHDL "Architecture" and "PROCESS" examples similar to what you would need for each of the 10 VHDL Blocks to perform their specific function. It is up to you to figure out how to apply the code to your own project, and generate the signals you need. VHDL BLOCK #1 - The Clock Divider The clock divider should be a snap for you to figure out, so no real need for an example. For our VGA project we require a CLOCK signal of 25.175 MHz. 25 MHz in our case is fine. We accomplish this by dividing the DE1 boards 50Mhz Clock signal in half. For MultiSim simulations: For a 50MHz CLOCK setting use a Clock Period of 20ns. For a 25MHz CLOCK setting use a Clock Period of 40ns. VHDL BLOCK #2 & #3 - A typical MOD Counter Example (My MOD_25 Counter with a Power ON Reset line, and a 25Mhz Clock) Single MOD Counter Example VHDL BLOCK #2 and #3: MOD COUNTER EXAMPLE ARCHITECTURE MOD_25_arch OF MOD_25_nty IS SIGNAL SIG_h_count : STD_LOGIC_VECTOR (10 DOWNTO 0):= (others => '0'); BEGIN Counter_A <= SIG_h_count; PROCESS (Por, clk_25Mhz) BEGIN IF(Por = '1') THEN SIG_h_count <= "00000000000"; ELSIF (rising_edge(clk_25Mhz) AND SIG_h_count = 24) THEN SIG_h_count <= "00000000000"; ELSIF(rising_edge(clk_25Mhz)) THEN SIG_h_count <= SIG_h_count + 1; END IF; END PROCESS; END ARCHITECTURE MOD_25_arch; If you are having trouble getting the VGA controller Pulses to function properly, try changing the reset State of the MOD counters. Try these counter values below and and run some simulations. MOD-800 = Counts from 0 to 793 MOD-525 = Counts from 0 to 522 VHDL BLOCK #4 & #5 - The Horizontal & Vertical Decoder State Machines (MOMENTARY PULSES FOR OUTPUT LINES) Be aware that this particular VHDL State machine will only create Momentary Logic High Pulses on your outputs. The output STATE_ lines will remain HIGH for only 1 Clock Pulse, based on the input CLK source used for this particular VHDL Block. (The STATE_outputs need to be fed into a "Latch" circuit to be held HIGH for any length of time.) Single State Machine Example VHDL BLOCKS #4 and #5: H / V - DECODER STATE MACHINE EXAMPLE ARCHITECTURE DECODER_arch OF DECODER_nty IS BEGIN ------------------------------------ STATE SIGNALS & "Horizontal counter has Reset" Signal ----------------------------- ---------------------------------------------------------------------------------------------------------------------- PROCESS (MOD_COUNTER) BEGIN CASE (MOD_COUNTER) IS -- At counter value Binary "00000000000" Only State_A output is logic HIGH for 1 Clock pulse ONLY!! WHEN "00000000000" => State_A <= '1'; State_B <= '0'; clk_full_h_count_cycle <= '0'; -- \| -- \| -- \| -- \_/ -- MORE CASE STATEMENTS CAN BE ADDED IF REQUIRED -- -- (You can also add MORE STATE_ LINES within the Case statement. My examples here only have two "STATE_A" & "STATE_B" ) -- \| -- \| -- \| -- \_/ WHEN "01100100000" => -- At Counter value Binary "01100100000" only the State_B output Port is Logic HIGH for 1 Clock pulse ONLY!!. State_A <= '0'; State_B <= '1'; clk_full_h_count_cycle <= '0'; --( THIS LINE WAS NOT USED IN THIS EXAMPLE BUT COULD HAVE BEEN IF IT WAS REQUIRED) WHEN OTHERS => -- At any other counter value than what is declared above, all output ports are Logic LOW. State_A <= '0'; State_B <= '0'; clk_full_h_count_cycle <= '0'; END CASE; END PROCESS; END ARCHITECTURE DECODER_arch; Above are some examples of various counter State Pulses. In the screen Capture shown above, Pay close attention to the time difference between the two Markers, and how they relate to the other States Shown. The Horizontal & Vertical "SYNC" & "DISPLAY_TIME" Signals (LATCH CIRCUIT STATE MACHINES AS SHOWN BELOW) -= Horizontal "SYNC" Signal Timing Waveforms=- In the "SIGNAL TIMING" Diagrams that follow, they show the Horizontal & Vertical "SYNC" Pulses and also the Horizontal and Vertical "DISLAY_TIME" Pulses. These Waveform patterns occur in a repeating sequence and I have indicated the starting and stoping points of this repeating pattern. I have also included the H-DECODER and V-DECODER Momentaty HIGH PULSE States, in relation to the waveform Pattern in question. -= Horizontal "DISPLAY_TIME" Signal Waveforms =- -= Vertical "SYNC" Signal Waveforms =- -= Vertical "DISPLAY_TIME" Signal Waveforms =- (LATCH CIRCUIT STATE MACHINES) The VHDL Code below is an Example of a "Latch" circuit that will activate an output signal to remain either HIGH or LOW for any length of time until the output in question is assigned to change its state (LATCH RESET). Input Pulses are used to as Triggers to initiate any changes. This is essentially the type of circuit that you need to implement for each of the signals as shown in the above Waveform diagrams. "LATCH" circuit EXAMPLES used to Generate the HORIZONTAL and VIRTICAL "SYNC" and "DISPLAY" signals. ARCHITECTURE HORZ_VERT_arch OF HORZ_VERT_nty IS BEGIN --------------------------------------------- PROCESS "LATCH #1" ---------------------------------------------------------- -------------------------- Holds output HIGH for a certain number of clock pulses -------------------------------------- Process (State_000, State_25) BEGIN CASE State_000 IS WHEN '1' => OUTPUT_A <= '1'; -- OUTPUT_A will Rise to a Logic HIGH STATE ONLY! when "State_000" => '1' WHEN OTHERS => null; -- OUTPUT_A will remain "LATCHED" in a HIGH state until assigned to equal a Logic '0'. END CASE; CASE State_25 IS WHEN '1' => OUTPUT_A <= '0'; -- OUTPUT_A has been assigned to equal a Logic '0'. WHEN OTHERS => null; -- Latch "RESET" by the Momentary PULSE of "State_25". END CASE; END PROCESS; --------------------------------------------- PROCESS "LATCH #2" ---------------------------------------------------------- -------------------------- Holds output HIGH for a certain number of clock pulses -------------------------------------- Process (State_100, State_246) BEGIN CASE State_100 IS WHEN '1' => OUTPUT_B <= '0'; -- OUTPUT_B has been assigned to equal a Logic '0'. WHEN OTHERS => null; -- Latch "RESET" by the Momentary PULSE of "State_100". END CASE; -- \| -- \| -- \| -- \_/ -- MORE CASE STATEMENTS CAN BE ADDED IF REQUIRED -- -- (You can also add MORE STATE_ LINES within the Case statement. -- You Can also add multiple PROCESSes if required -- -- \| -- \| -- \| -- \_/ CASE State_246 IS WHEN '1' => OUTPUT_B <= '1'; -- OUTPUT_B will Rise to a Logic HIGH STATE ONLY! when "State_246" => '1' WHEN OTHERS => null; -- OUTPUT_B will remain "LATCHED" in a HIGH state until assigned to equal a Logic '0'. END CASE; END PROCESS; END ARCHITECTURE HORZ_VERT_arch; Displaying Objects on the Screen Now things do get a little more complicated here. I will have a couple of "DISPLAY PROCESS" examples to guide you along the way, however it is up to you to figure out how to add the Movement controls to your objects. :) The best way to understand how basic colored objects are displayed on the screen is as Follows: Try to look at the Horz. and Vert. MOD counters, more like an (X & Y) 2D coordinate system on a Map. So envision our Horz. and Vert. MOD counters like the X & Y position coordinates for a Flashlight that is scanning the screen. This Flashlight is checking Labels on every pixel it comes across. The Labels indicate which color that particular Pixel should display. Red, Green or Blue, or any combination of the three. The way we do this in VHDL is to use an additional set of std_logic_vectors or (COUNTERS) just like that used to generate the H-SYNC and V-SYNC signals. The Counter Pairs become the (X & Y) Reference coordinates for each individual object that we display on the screen. This means that we will need an (X & Y) Counter pair, for each separate object that we have on the Screen. So, as our Horz. and Vert. MOD counters are running through the screen Refresh cycle, if at any point the counters happen to have the exact same X and Y coordinates as one of the New (X & Y) Counter Pairs.......: (Y_REFERENCE_COUNTER = V-COUNTER ... "AND".... X_REFERENCE_COUNTER = H-COUNTER) then we can use this condition to activate the RGB lines to start displaying a particular color. I REPEAT!!... "STARTING" from those (X & Y) coordinates. This means that you have to ADD the number of (X & Y) pixels for the object that you wish to display, to the Statement shown above. Because you have essentially only told the system where to start painting the colors but not actually which way to go...UP/DOWN/LEFT/RIGHT or even where to stop. Here is a Hint. (Y_REFERENCE_COUNTER = V-COUNTER ... "AND".... X_REFERENCE_COUNTER = H-COUNTER + size) There is still a little more to it, so review the "DISPLAY PROCESS" examples I have provided below, and see if you can figure it out. :) "BALL" Display PROCESS Example - VHDL Block #7 BALL Display PROCESS Example ============================================================================================== BEGIN pixel_ROW <= V-COUNTER (10 downto 0); -- 10-bit Counter values from 11-bit Counters pixel_COLUMN <= H-COUNTER (10 downto 0); ---------------------------- BALL SIZE --------------------------------- ------------------------------------------------------------------------ size <= CONV_STD_LOGIC_VECTOR(8,11); --------------- COLORS FOR PIXEL DATA ON VIDEO SIGNAL ------------------ ------------------------------------------------------------------------ BALL_RED <= '1'; -- BALL is RED (Color RED turned on) BALL_GREEN <= NOT BALL_on; -- TURN OFF GREEN & BLUE when displaying the BALL. BALL_BLUE <= NOT BALL_on; --------------------------------------- RGB DISPLAY PROCESS ------------------------------------------ ------------------------------------------------------------------------------------------------------ -- As the Horizontal & Vertical scanning lines (AKA counters) increment through each X & Y coordinate....& the particular counter address -- where the BALL resides, the BALL_on is <= '1'. In turn diplaying the assigned color for those particular coordinates of the screen. RED color in our case. -- which results in a red square being displayed for the ball coordinates. RGB_DISPLAY: PROCESS (BALL_Y_position, BALL_X_position, pixel_COLUMN, pixel_ROW, size) BEGIN IF (BALL_X_position <= pixel_COLUMN + size) AND -- As the Pixel_column counter scans across the screen horizontally, (BALL_X_position + size >= pixel_COLUMN) AND -- and the Ball edge is detected. As the Pixel_column counter is counting -- within the ball coordinates (Side edge to side edge of the ball on the x axis) (BALL_Y_position <= pixel_ROW + size) AND -- As the Pixel_ROW counter scans across the screen Vertically, and the Ball edge (BALL_Y_position + size >= pixel_ROW) THEN -- is detected. As the Pixel_ROW counter is counting within the the ball coordinates -- (Top edge to Bottom edge of the ball on the Y axis) BALL_on <= '1'; ELSE BALL_on <= '0'; END IF; END PROCESS RGB_DISPLAY; END ARCHITECTURE BAL_arch; "PADDLE #1" Display PROCESS Example - VHDL Block #8 & #9 PADDLE #1 Display PROCESS Example ============================================================================================== BEGIN PAD1_pixel_ROW <= V-COUNTER (10 downto 0); -- 10-bit Counter values from 11-bit Counters PAD1_pixel_COLUMN <= H-COUNTER (10 downto 0); PAD1_X_position_REF <= PAD1_X_position; PAD1_Y_position_REF <= PAD1_Y_position; ---------------------------- PADDLE #1 SIZE --------------------------------- ------------------------------------------------------------------------ PAD1_VERT_size <= CONV_STD_LOGIC_VECTOR(64,11); PAD1_HORZ_size <= CONV_STD_LOGIC_VECTOR(16,11); ------------------------- Paddle #1 CENTER ADDRESS -------------------------- ------------------------------------------------------------------------ PAD1_X_position <= CONV_STD_LOGIC_VECTOR(590,11); --------------- COLORS FOR PIXEL DATA ON VIDEO SIGNAL ------------------ ------------------------------------------------------------------------ PADDLE_01_BLUE <= '1'; -- Paddle #1 is BLUE (Color BLUE turned on) PADDLE_01_GREEN <= NOT PAD1_on; -- TURN OFF GREEN & RED when displaying Paddle #1. PADDLE_01_RED <= NOT PAD1_on; --------------------------------------- RGB DISPLAY PROCESS ------------------------------------------ ------------------------------------------------------------------------------------------------------ -- As the Horizontal & Vertical scanning lines (AKA counters) increment through each X & Y coordinate....& the particular counter address -- where Paddle #1 resides, the PAD1_on is <= '1'. In turn diplaying the assigned color for those particular coordinates of the screen. RED color in our case. -- which results in a red Rectangle being displayed for the Paddle #1 coordinates. RGB_DISPLAY: PROCESS (PAD1_Y_position, PAD1_X_position, PAD1_pixel_COLUMN, PAD1_pixel_ROW, PAD1_VERT_size, PAD1_HORZ_size) BEGIN IF (PAD1_X_position <= PAD1_pixel_COLUMN + PAD1_HORZ_size) AND -- As the PAD1_pixel_column counter scans across the screen horizontally, (PAD1_X_position + PAD1_HORZ_size >= PAD1_pixel_COLUMN) AND -- and the Paddle #1 edge is detected. As the PAD1_pixel_column counter is -- counting within the Paddle #1 coordinates (Side edge to side edge of the -- paddle #1 on the x axis) (PAD1_Y_position <= PAD1_pixel_ROW + PAD1_VERT_size) AND -- As the PAD1_pixel_ROW counter scans across the screen Vertically, and the (PAD1_Y_position + PAD1_VERT_size >= PAD1_pixel_ROW) THEN -- Paddle #1 edge is detected. As the PAD1_pixel_ROW counter is counting within -- the the Paddle #1 coordinates (Top edge to Top edge of the Paddle #1 on the -- Y axis) PAD1_on <= '1'; ELSE PAD1_on <= '0'; END IF; END PROCESS RGB_DISPLAY; END ARCHITECTURE PADDLE_01_ARCHIT; Also review pages 208 and 209 from the Accompanying Textbook I mentioned earlier. -= Bouncing Ball =- Below are 2 "PROCESS" examples that might give you some ideas to get a Ball bouncing on the Screen. Review the two examples, Try the Code, manipulate it, change it around with your own ideas... try different things and see if you can get a Ball to display and bounce on the Screen. Now, to get the Ball Collisions working with the Paddles....this may prove to be more challenging. Hopefully these "PROCESS" examples will help get you started and thinking of better ways of writing your own VHDL code. ============================================================================================================= - PROCESS EXAMPLE #1- ============================================================================================================= ------------------------------------ BALL Movement in the Y AXIS PROCESS ------------------------------- ------------------------------------------------------------------------------------------------------------------ MOVE_BALL_Y: PROCESS BEGIN WAIT UNTIL (Vert_sync_PULSE'EVENT AND Vert_sync_PULSE = '1'); -- Move ball once every Vertical sync pulse --=============================================== -- BALL - HITS BOTTOM moving LEFT or RIGHT --=============================================== IF ((BALL_Y_position >= SCREEN_Y_BOTTOM - size) AND (BALL_X_motion <= LEFT_DIRECTION)) OR ((BALL_Y_position >= SCREEN_Y_BOTTOM - size) AND (BALL_X_motion <= RIGHT_DIRECTION)) THEN --------------- Ball MOVES UP -------------- BALL_Y_motion <= UP_DIRECTION; -- Move "UP" on the Screen by 2 Pixels every Vertical sync Pulse --=============================================== -- BALL - HITS TOP moving LEFT OR RIGHT --=============================================== ELSIF ((BALL_Y_position <= SCREEN_Y_TOP + size) AND (BALL_X_motion <= LEFT_DIRECTION)) OR ((BALL_Y_position <= SCREEN_Y_TOP + size) AND (BALL_X_motion <= RIGHT_DIRECTION)) THEN --------------- Ball MOVE DOWN -------------- BALL_Y_motion <= DOWN_DIRECTION; -- Move "DOWN" on the Screen by 2 Pixels every Vertical sync Pulse ============================================================================================================= - PROCESS EXAMPLE #2- ============================================================================================================= MOVE_BALL_X: PROCESS BEGIN WAIT UNTIL (Vert_sync_PULSE'EVENT AND Vert_sync_PULSE = '1'); -- Move ball once every Vertical sync pulse --=============================================== -- BALL - HITS RIGHT moving UP --=============================================== -- IF the BALL_X_Position value reaches the "RIGHT" side of the screen AND is moving UP ---------- IF ((BALL_X_position >= SCREEN_X_RIGHT - size) AND (BALL_Y_motion <= UP_DIRECTION)) THEN --------------- Ball MOVES LEFT -------------- BALL_X_motion <= LEFT_DIRECTION; -- Move "LEFT" on the Screen by 2 Pixels every Vertical sync Pulse --=============================================== -- BALL - HITS RIGHT moving DOWN --=============================================== -- IF the BALL_X_Position value reaches the "RIGHT" side of the screen AND is moving DOWN ---------- ELSIF ((BALL_X_position >= SCREEN_X_RIGHT - size) AND (BALL_Y_motion <= DOWN_DIRECTION)) THEN --------------- Ball MOVES LEFT -------------- BALL_X_motion <= LEFT_DIRECTION; -- Move "LEFT" --=============================================== -- BALL - HITS LEFT moving UP --=============================================== -- IF the BALL_X_Position value reaches the "LEFT" side of the screen AND is moving UP ---------- ELSIF ((BALL_X_position <= SCREEN_X_LEFT + size) AND (BALL_Y_motion <= UP_DIRECTION)) THEN --------------- Ball MOVE RIGHT -------------- BALL_X_motion <= RIGHT_DIRECTION; -- Move "RIGHT" on the Screen by 2 Pixels every Vertical sync Pulse --=============================================== -- BALL - HITS LEFT moving DOWN --=============================================== -- IF the BALL_X_Position value reaches the "LEFT" side of the screen AND is moving DOWN ---------- ELSIF ((BALL_X_position <= SCREEN_X_LEFT + size) AND (BALL_Y_motion <= DOWN_DIRECTION)) THEN --------------- Ball MOVE RIGHT -------------- BALL_X_motion <= RIGHT_DIRECTION; -= Ball Collisions =- (VIDEO PART #4 - TO BE POSTED) ADDITIONAL NOTES REGARDING BALL COLLISONS: The details below regarding paddle collisions might be a bit overkill for most of you. However, if you are a perfectionists and are getting really frustrated because the ball collisions with your paddles are not behaving the way you want them to....you may want to read the details shown below: It is important to realize that no matter which direction the ball is travelling, UP, DOWN or on an Angle; the conditions that you apply to each paddle for a Ball Collision; each condition will cause the same response regardless of which side the Ball collides on the Paddle. This is because it is single object. The collision conditions for each paddle are based on its X&Y counter Pair. To have different collision responses for each of the 4 sides, you in turn need 4 Separate Counter pairs or 4 separate sides that make up one paddle. The "RGB" Concatenation & Display Block This Block is simply a group of "AND" gates that join or "CONCATENATE" all of the RGB colors together into one MASTER RGB Output. So you essentially have a Multi-Input "AND" gate for each of the individual RGB Colors. One for all of the RED colors, one for all of the GREEN, and one for all of the BLUE. Finally this MASTER RGB output can only be active during the Horizontal Display Time "AND" the Vertical Display Time. So yet another "AND" gate is used activate the MASTER RGB output... only when H-DISPAY_TIME & V-DISPLAY_TIME are in a Logic HIGH state. Altera DE1 Board - Unused RGB lines must be tied to GND. It is important to make sure that you tie any unused RGB input lines to GND. As these can sometimes cause the unconnected signals to Float, producing interference and noise on your VGA monitor. Well that about sums it up Folks. :) Hopefully this Tutorial will at least get you a little closer to finalizing your VHDL PONG Projects! Fun Stuff!! Cheers Everyone! -Gerry -= END =-
VHDL VGA PONG USER VISITS hit counter html