[verilog] change from always@ to assign

  • Thread starter hoheiho
  • Start date
  • Tags
    Change
In summary, the conversation discusses two different codes that are meant to output a recover signal based on certain conditions. The first code (code i) uses an always block while the second code (code ii) uses assign statements. However, the results of the second code are not as expected. The person is asking for help in identifying the issue with the second code.
  • #1
hoheiho
47
0

Homework Statement


Halo, I have written a always@ (code i,pic1) which can output what I want but the result is delayed 1 clock cycle, therefore I have changed it to assign (code ii,pic2)and try to output the recover signal immediately when pcreg_1 is changed. But waveform is not what I wanted. Did I miss somethings in (code ii)? The recover is high in 2 clock cycle and I cannot get 0.

code i
Code: 
always @(posedge clk)
begin
  if (store)
      if (m2==pcreg_1)
        recover = 0;
      else
        recover = 1;
  else
      if (m1==pcreg_1)
        recover = 0;
      else
        recover = 1;     
end

code ii
Code: 
assign recover = (store && (m2==pcreg_1))? 1'b0:1'b1;
assign recover = (!store && (m1==pcreg_1))? 1'b0:1'b1;

Could anyone give me a hand for me :(?

Thank you very much for help
Ivan
 

Attachments

  • pic1.jpg
    pic1.jpg
    11.1 KB · Views: 583
  • pic2.jpg
    pic2.jpg
    10.6 KB · Views: 566
Physics news on Phys.org
  • #2
Did anyone can see what's the problem :(?
 

FAQ: [verilog] change from always@ to assign

What is the difference between using always@ and assign in Verilog?

The always@ block in Verilog is used to describe a sequential logic process, where the output is dependent on the current and previous inputs. It is used to model registers, flip-flops, and other sequential elements. On the other hand, the assign statement is used to describe combinational logic, where the output is solely based on the current inputs and does not have any memory.

When should I use always@ and when should I use assign in my Verilog code?

You should use always@ when you need to model sequential logic, such as registers or flip-flops. This is because the always@ block allows you to use non-blocking assignments, which are necessary for proper modeling of sequential elements. You should use assign when you need to model combinational logic, such as logic gates or multiplexers.

Can I use both always@ and assign in the same Verilog code?

Yes, you can use both always@ and assign in the same Verilog code. In fact, it is common to use both in a single module. You can use always@ to model sequential logic and assign to model combinational logic within the same module.

What are the advantages and disadvantages of using always@ compared to assign in Verilog?

The main advantage of using always@ is that it allows you to model sequential logic accurately and efficiently. It also allows for easy simulation and verification of the code. On the other hand, the main disadvantage of using always@ is that it can lead to complex and difficult-to-maintain code if not used properly. Assign, on the other hand, is simple and easy to use, but may not accurately model sequential logic and can lead to race conditions if used incorrectly.

Are there any specific coding guidelines for using always@ and assign in Verilog?

Yes, there are some recommended coding guidelines for using always@ and assign in Verilog. Some common guidelines include using non-blocking assignments in the always@ block, avoiding mixing blocking and non-blocking assignments in the same always@ block, and using assign for simple combinational logic. It is also important to properly document and comment code using always@ and assign for better understanding and maintenance.

Similar threads

Engineering Verilog for a Simple Vending Machine
Replies
1
Views
1K
Mealy FSM Edge Detector Code Problems
Replies
1
Views
4K
Verilog testbench timing diagram
Replies
1
Views
2K
[verilog]confuse on CPU's system bus
Replies
1
Views
2K
4-Bit Shift Register in Verilog
Replies
1
Views
21K
Verilog Serial Adder in Behavioral Description
Replies
1
Views
19K
Counter from 0 to 11 then back to 0 (system verilog)
Replies
6
Views
10K
Engineering Issue with shift registers — PIPO, PISO, SIPO and SISO
Replies
10
Views
2K
Help writing a FIR Filter in Verilog
Replies
1
Views
3K
Odd parity checker using Verilog
Replies
1
Views
9K

Hot Threads

Recent Insights

Back
Top