procedural assignments in verilog

Verilog Assignments

Variable declaration assignment, net declaration assignment, assign deassign, force release.

• Procedural continuous

Legal LHS values

An assignment has two parts - right-hand side (RHS) and left-hand side (LHS) with an equal symbol (=) or a less than-equal symbol (<=) in between.

The RHS can contain any expression that evaluates to a final value while the LHS indicates a net or a variable to which the value in RHS is being assigned.

Procedural Assignment

Procedural assignments occur within procedures such as always , initial , task and functions and are used to place values onto variables. The variable will hold the value until the next assignment to the same variable.

The value will be placed onto the variable when the simulation executes this statement at some point during simulation time. This can be controlled and modified the way we want by the use of control flow statements such as if-else-if , case statement and looping mechanisms.

An initial value can be placed onto a variable at the time of its declaration as shown next. The assignment does not have a duration and holds the value until the next assignment to the same variable happens. Note that variable declaration assignments to an array are not allowed.

If the variable is initialized during declaration and at time 0 in an initial block as shown below, the order of evaluation is not guaranteed, and hence can have either 8'h05 or 8'hee.

Procedural blocks and assignments will be covered in more detail in a later section.

Continuous Assignment

This is used to assign values onto scalar and vector nets and happens whenever there is a change in the RHS. It provides a way to model combinational logic without specifying an interconnection of gates and makes it easier to drive the net with logical expressions.

Whenever b or c changes its value, then the whole expression in RHS will be evaluated and a will be updated with the new value.

This allows us to place a continuous assignment on the same statement that declares the net. Note that because a net can be declared only once, only one declaration assignment is possible for a net.

Procedural Continuous Assignment

• assign ... deassign
• force ... release

This will override all procedural assignments to a variable and is deactivated by using the same signal with deassign . The value of the variable will remain same until the variable gets a new value through a procedural or procedural continuous assignment. The LHS of an assign statement cannot be a bit-select, part-select or an array reference but can be a variable or a concatenation of variables.

These are similar to the assign - deassign statements but can also be applied to nets and variables. The LHS can be a bit-select of a net, part-select of a net, variable or a net but cannot be the reference to an array and bit/part select of a variable. The force statment will override all other assignments made to the variable until it is released using the release keyword.

Verilog: Continuous & Procedural Assignments

Continuous Assignment

Continuous assignment is used to drive a value on to a net in dataflow modeling. The net can be a vector or scalar, indexed part select, constant bit or part select of a vector. Concatenation is also supported with scalar vector types.

module Conti_Assignment (addr1,addr2,wr,din,valid1,valid2,dout); input [31:0] addr1,addr2; input [31:0] din; output [31:0] dout; input valid1,valid2,wr;

wire valid; wire [31:0] addr;

//Net (scalar) continuous assignment assign valid = valid1 | valid2;

//Vector continuous assignment assign addr[31:0] = addr1[31:0] ^ addr2[31:0];

//Part select & Concatenation in Continuous assignment assign dout[31:0] = (valid & wr) ? {din[31:2],2'b11} : 32'd0;

Regular & Implicit Assignment

Regular continuous assignment means, the declaration of a net and its continuous assignments are done in two different statements. But in implicit assignment, continuous assignment can be done on a net when it is declared itself. In the below example, `valid` is declared as wire during the assignment. If signal name is used to the left of the continuous assignment, an implicit net declaration will be inferred. In the below code `dout` is not declared as net, but it is inferred during assignment.

module Implicit_Conti_Assignment (addr1,addr2,wr,din,valid1,valid2,dout); input [31:0] addr1,addr2; input [31:0] din; output [31:0] dout; input valid1,valid2,wr;

//Net (scalar) Implict continuous assignment wire valid = (valid1 | valid2);

//Implicit net declaration -dout assign dout[31:0] = (valid & wr) ? {din[31:2],2'b11} : 32'd0;

Procedural Assignment

We have already seen that continuous assignment updates net, but procedural assignment update values of reg, real, integer or time variable. The constant part select, indexed part select and bit select are possible for vector reg.

There are two types of procedural assignments called blocking and non-blocking. Blocking assignment, as the name says, gets executed in the order statements are specified. The "=" is the symbol used for blocking assignment representation. Non-blocking assignment allows scheduling of assignments. It will not block the execution. The symbol "<=" is used for non-blocking assignment representation and mainly used for concurrent data transfers.

Following example shows the differences in the simulation result by using blocking and non-blocking assignments.

/* module Nonblocking_Assignment (addr1,addr2,wr,din,valid1,valid2,data,aout); input [31:0] addr1,addr2; input [31:0] din; output [31:0] data,aout; input valid1,valid2,wr;

reg [31:0] data,aout, addr; reg valid;

always @(addr1,addr2,wr,din,valid1,valid2) begin valid <= (valid1 | valid2); addr <= (addr1[31:0] | addr2[31:0]); data <= (valid & wr) ? {din[31:2],2'b11} : 32'd0; aout <= wr ? addr: {addr1[15:0],addr2[31:16]}; end initial $monitor($time,"NON-BLOCKING: Values valid1=%b, valid2=%b, wr=%b, addr1=%d, addr2=%d, data=%d, aout=%d", valid1,valid2,wr,addr1,addr2,data,aout); endmodule */ module Blocking_Assignment (addr1,addr2,wr,din,valid1,valid2,data,aout); input [31:0] addr1,addr2; input [31:0] din; output [31:0] data,aout; input valid1,valid2,wr;

always @(addr1,addr2,wr,din,valid1,valid2) begin valid = (valid1 | valid2); addr = (addr1[31:0] | addr2[31:0]); data = (valid & wr) ? {din[31:2],2'b11} : 32'd0; aout = wr ? addr : {addr1[15:0],addr2[31:16]}; $monitor($time,"BLOCKING: Values valid1=%b, valid2=%b, wr=%b, addr1=%d, addr2=%d, data=%d, aout=%d", valid1,valid2,wr,addr1,addr2,data,aout); end endmodule

module test; reg valid1,valid2,wr; reg [31:0] addr1,addr2,din; wire [31:0] data,aout;

Blocking_Assignment Block_Assign(addr1,addr2,wr,din,valid1,valid2,data,aout);

//Nonblocking_Assignment Nonblock_Assign(addr1,addr2,wr,din,valid1,valid2,data,aout);

initial begin valid1 = 0; valid2 = 0; addr1 = 32'd12; addr2 = 32'd36; din = 32'd198; wr = 1;

#5 valid1 = 1; #10 valid1 = 0; valid2 = 1; #10 addr1 = 32'd0; addr2 = 32'd0; #5 wr = 0; #12 wr = 1;

/* ncsim> run 0NON-BLOCKING: Values valid1=0, valid2=0, wr=1, addr1= 12, addr2= 36, data= X, aout= x 5NON-BLOCKING: Values valid1=1, valid2=0, wr=1, addr1= 12, addr2= 36, data= 0, aout= 44 15NON-BLOCKING: Values valid1=0, valid2=1, wr=1, addr1= 12, addr2= 36, data= 199, aout= 44 25NON-BLOCKING: Values valid1=0, valid2=1, wr=1, addr1= 0, addr2= 0, data= 199, aout= 44 30NON-BLOCKING: Values valid1=0, valid2=1, wr=0, addr1= 0, addr2= 0, data= 0, aout= 0 42NON-BLOCKING: Values valid1=0, valid2=1, wr=1, addr1= 0, addr2= 0, data= 199, aout= 0 ncsim: *W,RNQUIE: Simulation is complete. */

/* ncsim> run 0BLOCKING: Values valid1=0, valid2=0, wr=1, addr1= 12, addr2= 36, data= 0, aout= 44 5BLOCKING: Values valid1=1, valid2=0, wr=1, addr1= 12, addr2= 36, data= 199, aout= 44 15BLOCKING: Values valid1=0, valid2=1, wr=1, addr1= 12, addr2= 36, data= 199, aout= 44 25BLOCKING: Values valid1=0, valid2=1, wr=1, addr1= 0, addr2= 0, data= 199, aout= 0 30BLOCKING: Values valid1=0, valid2=1, wr=0, addr1= 0, addr2= 0, data= 0, aout= 0 42BLOCKING: Values valid1=0, valid2=1, wr=1, addr1= 0, addr2= 0, data= 199, aout= 0 ncsim: *W,RNQUIE: Simulation is complete. ncsim> exit */

Procedural Blocks

In Verilog, procedural blocks such as initial and always blocks allow for the execution of multiple statements in sequence. These blocks are the foundation of procedural assignments where variables can be assigned values that may change over time, simulating the dynamic behavior of digital circuits.

• The Verilog-AMS Language
• Initial and Always Processes
• Assignment Statements

Assignment Statements 

Blocking assignment .

A blocking assignment evaluates the expression on its right hand side and then immediately assigns the value to the variable on its left hand side:

It is also possible to add delay to a blocking assignment. For example:

In this case, the expression on the right hand side is evaluated and the value is held for 10 units of time. During this time, the execution of the code is blocked in the middle of the assignment statement. After the 10 units of time, the value is stored in the variable on the left

Nonblocking Assignment 

A nonblocking assignment evaluates the expression on its right hand side without immediately assigning the value to the variable on the left. Instead the value is cached and execution is allowed to continue onto the next statement without performing the assignment. The assignment is deferred until the next blocking statement is encountered. In the example below, on the positive edge of clk the right-hand side of the first nonblocking assignment is evaluated and the value cached without changing a. Then the right-hand side of the second nonblocking assignment statement is evaluated is also cached without changing b. Execution continues until it returns to the event statement, once there the execution of the process blocks until the next positive edge of the clk. Just before the process blocks, the cached values finally assigned to the target variables. In this way, the following code swaps the values in a and b on every positive edge of clk:

Adding delay to nonblocking assignments is done as follows:

Using nonblocking assignment with delay in this manner is a way of implementing transport delay , as shown below:

Blocking versus Nonblocking Assignment 

Nonblocking statements allow you to schedule assignments without blocking the procedural flow. You can use the nonblocking procedural statement whenever you want to make several register assignments within the same time step without regard to order or dependence upon each other. It means that nonblocking statements resemble actual hardware more than blocking assignments.

Generally you would use nonblocking assignment whenever assigning to variables that are shared between multiple initial or always processes if the statements that access the variable could execute at the same time. Doing so resolves race conditions.

Blocking assignment is used to assign to temporary variables when breaking up large calculations into multiple assignment statements. For example:

Procedural Continuous Assignment 

Two types of continuous assignment are available in initial and always processes: assign and force .

The target of an assign statement must be a register or a concatenation of registers. The value is continuously driven onto its target and that value takes priority over values assigned in procedural assignments. Once a value is assigned with an assign statement, it can only be changed with another assign statement or with a force statement. Execution of deassign releases the continuous assignment, meaning that the value of the register can once again be changed with procedural assignments. For example, the following implements a D-type flip-flop with set and reset:

Assign statements are used to implement set and reset because they dominate over the non-blocking assignment used to update q upon positive edges of the clock c . If instead a simple procedural assignment were used instead, then a positive edge on the clock could change q even if r or s were high.

A force statement is similar to assign , except that it can be applied to both registers and nets. It overrides all other assignments until the release statement is executed. Force is often used in testbenches to eliminate initial x-values in the DUT or to place it in a particular state. For example:

Procedural continuous assignments

Till now we have seen two types of assignments i.e. continuous assignment and procedural assignment .

The continuous assignment is used to drive net data type variables using the ‘assign’ statements whereas procedural assignments are used to drive reg data type variables using initial and always block statements.

Verilog also provides a third type of assignment i.e. procedural continuous assignment that drives net or reg data type variables for a certain period of time by overriding the existing assignments.

There are two types of procedural continuous assignments

assign and deassign

Force and release.

The assign and deassign statements control reg type variable values by overriding existing procedural assignments for a limited time period. After the execution of the deassign statement, another procedural or procedural continuous assignment can change the variable value once again, till then the previous value can hold.

The d1 = 3 is assigned at #5 time units and deassign at #10 time units.The d1 = 3 retains till next assignment d1 = 7 happens at 20 time units.

The force and release statements control net and reg data type variable values by overriding existing procedural, continuous or procedural continuous assignments for a limited time period. After the execution of the release statement for the reg data type variable, another procedural or procedural continuous assignment can change the variable value once again, till then the previous value can hold. The value of the previous continuous assignment retains in the case of the net data type variable.

The d1 belongs to the reg data type and d2 belongs to the net data type. Both variables are forced at #5 time units and released at #10 time units Once, it is released, 

• The d1 value remains the same (d1 = 3) until it is changed to d1 = 7 at 20 time units.
• The d2 value holds a previously assigned value using continuous assignment (d2 = 2).

Verilog Tutorials

A procedural continuous assignment assigns a value to a register.

Description:

A procedural continuous assignments overrides any other procedural assignment. After the procedural continuous assignment is executed, it remains in force on the assigned register or net until it is deassigned, or until another procedural continuous assignment is made to the same register or net.

The keywords assign and deassign can be used for registers, or a concatenation of registers only. It can not be used for memories and bit- or part-select of a register.

Deassign and release de-activate a procedural continuous assignment. The register value remains after the de-activation until a new value is assigned.

A procedural continuous assignment is not the same as a continuous assignment. Procedural continuous assignments are declared inside procedural blocks.

Continuous assignment

Verilog Continuous Assignment Statements Tutorial

Continuous assignment statements are an essential aspect of Verilog that allows you to assign values to signals without using procedural blocks. Unlike procedural assignments found in always blocks, continuous assignments are used for modeling combinational logic. In this tutorial, we will explore continuous assignment statements in Verilog and learn how to use them to describe the behavior of combinational circuits efficiently.

Introduction to Continuous Assignment Statements

Continuous assignment statements in Verilog are used to specify the relationship between input and output signals in a combinational circuit. They allow you to assign a value to a signal continuously, meaning the assignment is continuously evaluated as the inputs change. Continuous assignments are used outside procedural blocks and are ideal for describing combinational logic or interconnections between signals.

Example of Continuous Assignment Statements:

Another example:, steps to use continuous assignment statements.

To use continuous assignment statements in Verilog, follow these steps:

• Identify the combinational logic relationship between input and output signals.
• Use the 'assign' keyword to create a continuous assignment statement.
• Specify the output signal on the left-hand side and the combinational logic expression on the right-hand side of the assignment.
• Ensure that the right-hand side expression does not contain any procedural constructs, as continuous assignments are not allowed to contain procedural statements.
• Continuous assignments are evaluated in parallel with no explicit sequencing, making them suitable for combinational logic modeling.

Common Mistakes with Continuous Assignment Statements

• Using procedural statements such as if-else or case statements within continuous assignments.
• Missing the 'assign' keyword before the continuous assignment statement, leading to syntax errors.
• Attempting to use continuous assignments for modeling sequential logic, which is not their intended use.
• Using continuous assignments for outputs in modules with procedural assignments, leading to unexpected behavior.
• Not considering the propagation delays of combinational logic when using continuous assignments, which may affect simulation results.

Frequently Asked Questions (FAQs)

• Q: Can I use continuous assignments inside an always block? A: No, continuous assignments are not allowed inside always blocks. They are used outside procedural blocks to model combinational logic.
• Q: What is the difference between continuous assignments and procedural assignments? A: Continuous assignments are evaluated continuously for combinational logic, while procedural assignments in always blocks are used for modeling sequential logic that executes based on clock edges or event triggers.
• Q: Can I use continuous assignments for bidirectional signals? A: No, continuous assignments can only be used for assigning values to output or wire signals, not bidirectional signals or registers.
• Q: How do continuous assignments affect the simulation time of a Verilog design? A: Continuous assignments add negligible overhead to the simulation time as they represent combinational logic and are evaluated in parallel with no explicit sequencing.
• Q: Can I use continuous assignments for modeling arithmetic operations? A: Yes, continuous assignments can be used to model arithmetic operations in combinational logic. For example, you can use continuous assignments to describe the addition or subtraction of signals.
• Verilog tutorial
• HTMl tutorial
• JAVASCRIPT tutorial
• Computer tutorial
• Ansible tutorial
• Salt tool tutorial
• Devops Chef tutorial
• Cucumber tutorial
• Deep Learning tutorial
• CSS tutorial

Some results uranium dioxide powder structure investigation

• Processes of Obtaining and Properties of Powders
• Published: 28 June 2009
• Volume 50 , pages 281–285, ( 2009 )

Cite this article

• E. I. Andreev 1 ,
• K. V. Glavin 2 ,
• A. V. Ivanov 3 ,
• V. V. Malovik 3 ,
• V. V. Martynov 3 &
• V. S. Panov 2  

116 Accesses

7 Citations

Explore all metrics

Features of the macrostructure and microstructure of uranium dioxide powders are considered. Assumptions are made on the mechanisms of the behavior of powders of various natures during pelletizing. Experimental data that reflect the effect of these powders on the quality of fuel pellets, which is evaluated by modern procedures, are presented. To investigate the structure of the powders, modern methods of electron microscopy, helium pycnometry, etc., are used. The presented results indicate the disadvantages of wet methods for obtaining the starting UO 2 powders by the ammonium diuranate (ADU) flow sheet because strong agglomerates and conglomerates, which complicate the process of pelletizing, are formed. The main directions of investigation that can lead to understanding the regularities of formation of the structure of starting UO 2 powders, which will allow one to control the process of their fabrication and stabilize the properties of powders and pellets, are emphasized.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA) Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Rent this article via DeepDyve

Institutional subscriptions

Similar content being viewed by others

Investigation of the Properties of Uranium-Molybdenum Pellet Fuel for VVER

Investigation of the Influence of the Energy of Thermal Plasma on the Morphology and Phase Composition of Aluminosilicate Microspheres

Evaluation of the possibility of fabricating uranium-molybdenum fuel for vver by powder metallurgy methods.

Patlazhan, S.A., Poristost’ i mikrostruktura sluchainykh upakovok tverdykh sharov raznykh razmerov (Porosity and Microstructure of Chaotic Packings of Solid Spheres of Different Sizes), Chernogolovka: IKhF RAN, 1993.

Google Scholar  

Andreev, E.I., Bocharov, A.S., Ivanov, A.V., et al., Izv. Vyssh. Uchebn. Zaved., Tsvetn. Metall. , 2003, no. 1, p. 48.

Assmann, H., Dörr, W., and Peehs, M., “Control of HO 2 Microstructure by Oxidative Sintering,” J. Nucl. Mater. , 1986, vol. 140,issue 1, pp. 1–6.

Article   ADS   CAS   Google Scholar  

Download references

Author information

Authors and affiliations.

Elektrostal’ Polytechnical Institute (Branch), Moscow Institute of Steel and Alloys, ul. Pervomaiskaya 7, Elektrostal’, Moscow oblast, 144000, Russia

E. I. Andreev

Moscow Institute of Steel and Alloys (State Technical University), Leninskii pr. 4, Moscow, 119049, Russia

K. V. Glavin & V. S. Panov

JSC “Mashinostroitelny Zavod”, ul. K. Marksa 12, Elektrostal’, Moscow oblast, 144001, Russia

A. V. Ivanov, V. V. Malovik & V. V. Martynov

You can also search for this author in PubMed   Google Scholar

Corresponding author

Correspondence to K. V. Glavin .

Additional information

Original Russian Text © E.I. Andreev, K.V. Glavin, A.V. Ivanov, V.V. Malovik, V.V. Martynov, V.S. Panov, 2009, published in Izvestiya VUZ. Poroshkovaya Metallurgiya i Funktsional’nye Pokrytiya, 2008, No. 4, pp. 19–24.

About this article

Andreev, E.I., Glavin, K.V., Ivanov, A.V. et al. Some results uranium dioxide powder structure investigation. Russ. J. Non-ferrous Metals 50 , 281–285 (2009). https://doi.org/10.3103/S1067821209030183

Download citation

Published : 28 June 2009

Issue Date : June 2009

DOI : https://doi.org/10.3103/S1067821209030183

Share this article

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

• nuclear fuel
• uranium dioxide
• uranium protoxide-oxide
• crystallite
• agglomerate
• conglomerate
• surface morphology
• ADU-ammonium diuranate
• Find a journal
• Publish with us
• Track your research

SSH-MOZHAYSK - FSSH-VOSTOK-ELEKTROSTAL head to head game preview and prediction

Oops! We detected that you use AdBlocker...

Please disable adblocker to support this website. Thank you!

I disabled all my adblockers for this website. Reload...

Open Modalf