NATIONAL UNIVERSITY OF HO CHI MINH CITY
UNIVERSITY OF INFORMATION TECHNOLOGY
FACULTY OF COMPUTER ENGINEERING
LECTURE
Subject: VERILOG
Hardware Design Language
Chapter8: Tasks and Functions
Lecturer: Lam Duc Khai
1
Agenda
1. Chapter 1: Introduction ( Week1)
2. Chapter 2: Fundamental concepts (Week1)
3. Chapter 3: Modules and hierarchical structure (Week2)
4. Chapter 4: Primitive Gates – Switches – User defined
primitives (Week2)
5. Chapter 5: Structural model (Week3)
6. Chapter 6: Behavioral model – Combination circuit &
Sequential circuit (Week4 & Week5)
7. Chapter 7: State machines (Week6)
8. Chapter 8: Tasks and Functions (Week6)
9. Chaper 9: Testbench and verification (Week7)
2
Tasks and Functions in Verilog
• Module cannot be instantiated inside a behavioral
codes.
• A designer is frequently required to implement the
same functionality at many places in a behavioral
design.
• Verilog provides task and functions to break up
large behavioral designs into smaller pieces.
3
Tasks versus Functions in Verilog
• Procedures/Subroutines/Functions in SW
programming languages
– The same functionality, but put in many different
places
• Verilog equivalence:
– Tasks and Functions
– function and task (~ function and subroutine)
– Used in behavioral modeling
– Part of design hierarchy Hierarchical name
4
Differences between...
• Functions • Tasks
– Can enable (call) just another – Can enable (call) other tasks and
function (not task) functions
– May execute in non-zero simulation
– Execute in 0 simulation time
time
– No timing control statements – May contain any timing control
allowed ( next slide ) statements
– At lease one input, none output – May have arbitrary (none, one or
many) inputs, outputs, or inouts
– Return only a single value – Do not return any value
– Not synthesizable
– Synthesizable
5
Timing Control
• Delay #
Used to delay statement by specified amount of simulation time
always
begin
#10 clk = 1;
#10 clk = 0;
end
• Event Control @
Delay execution until event occurs
Event may be single signal/expression change
Multiple events linked by or
always @(posedge clk) always @(x or y)
begin begin
q <= d; s = x ^ y;
end c = x & y;;
end 6
Similarity
• Both
– are defined in a module
– are local to the module
– can have local variables (registers, but not nets) and events
– contain only procedural statements (NOT continuous
statements)
– do not contain initial or always statements, they are only
blocked by “begin …end”.
– are called from initial or always statements or others task
and functions
7
Task and function usage
• Tasks can be used for common Verilog code
- is used for both combinational and sequential logic
• Function are used when the common code
– is used for purely combinational logic
• Functions are typically used for conversions and
commonly used calculations
8
Tasks
• Keywords: task, endtask
• Must be used if the procedure has
– any timing control constructs
– zero or more than one output arguments
9
Tasks (cont’d)
• Task declaration and invocation
– Declaration syntax
task <task_name>;
<I/O declarations>
<variable and event declarations>
begin // if more than one statement needed
<statement(s)>
end // if begin used!
endtask
10
Tasks (cont’d)
• Task declaration and invocation
– Task invocation syntax (call)
<task_name>;
<task_name> (<arguments>);
– input and inout arguments are passed into the
task
– output and inout arguments are passed back to
the invoking statement when task is completed
11
Tasks (cont’d)
• I/O declaration in modules vs. tasks
– Both used keywords: input, output, inout
– In modules, represent ports
• connect to external signals
– In tasks, represent arguments
• pass values to and from the task
12
Task Examples:
Use of input and output arguments
module operation; task bitwise_oper;
parameter delay = 10;
reg [15:0] A, B; output [15:0] ab_and, ab_or,
reg [15:0] AB_AND, AB_OR, AB_XOR; ab_xor;
input [15:0] a, b;
initial
$monitor( …);
begin
#delay ab_and = a & b;
initial ab_or = a | b;
begin
… ab_xor = a ^ b;
end end
endtask
always @(A or B)
begin
bitwise_oper(AB_AND, AB_OR,
AB_XOR, A, B);
end endmodule
13
Task Examples :
Use of module local variables
task init_sequence;
module sequence;
begin
reg clock;
clock = 1'b0;
end
initial endtask
begin
… task asymmetric_sequence;
end begin
#12 clock = 1'b0;
initial #5 clock = 1'b1;
#3 clock = 1'b0;
init_sequence;
#10 clock = 1'b1;
end
always endtask
asymmetric_sequence;
endmodule
14
Functions
• Keyword: function, endfunction
• Can be used if the procedure
– does not have any timing control constructs
– returns exactly a single value
– does not have any output
– has at least one input argument
15
Functions (cont’d)
• Function Declaration and Invocation
– Declaration syntax:
function <range_or_type> <func_name>;
<input declaration(s)>
<variable_declaration(s)>
begin // if more than one statement needed
<statements>
end // if begin used
endfunction
16
Functions (cont’d)
• Function Declaration and Invocation
– Invocation syntax (call):
<func_name> (<argument(s)>);
17
Functions (cont’d)
• Semantics
– much like function in Pascal
– An internal implicit reg is declared inside the
function with the same name
– The return value is specified by setting that
implicit reg
– <range_or_type> defines width and type of the
implicit reg
• type can be integer or real
• default bit width is 1
18
Function Examples: Parity Generator
module parity; function calc_parity;
reg [31:0] addr; input [31:0] address; Same name
reg parity; begin
reg 1 bit calc_parity = ^address;
Initial begin end
… endfunction
end
The implicit reg
endmodule
1 bit width (default)
always @(addr)
begin
parity = calc_parity(addr);
$display("Parity calculated = %b",
calc_parity(addr) );
end
19
Function Examples: Controllable Shifter
module shifter; function [31:0] shift;
`define LEFT_SHIFT 1'b0 input [31:0] address;
`define RIGHT_SHIFT 1'b1 input control; The implicit reg
reg [31:0] addr, left_addr, right_addr; 32 bit width
begin
reg control; shift = (control==`LEFT_SHIFT) ?
(address<<1) : (address>>1);
initial end
begin endfunction
…
end endmodule
always @(addr)begin
left_addr =shift(addr, `LEFT_SHIFT);
right_addr =shift(addr,`RIGHT_SHIFT);
end 20
Tasks and Functions Summary
• Tasks and functions in behavioral modeling
– The same purpose as subroutines in SW
– Provide more readability, easier code management
– Are part of design hierarchy
– Tasks are more general than functions
• Can represent almost any common Verilog code
– Functions can only model purely combinational
calculations
21
