• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. for/generate

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 2466
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

for/generate

archive
archive over 18 years ago

Hi,
I am currently studying psl and having some doubts. I have done a simple edge detector to starting using psl, this is the edge detector:


module edge_detector(sign_i, // Input of the Edge Detector
             rise_o, // Rising Edge Output of the Edge Detector
             fall_o, // Falling Edge Output of the Edge Detector
             clk, // clock
             rst_b, // Synchronous Reset
             );
  
//--------------------- Parameters Declaration ---------------------------------
   parameter SIZE = 1;
       
//-------------------- Inputs Declaration --------------------------------------
   input [SIZE-1:0]sign_i;
   input clk;
   input rst_b;
  
   
//---------------------- Outputs Declaration -----------------------------------
   output [SIZE-1:0]rise_o;
   output [SIZE-1:0]fall_o;

//------------------- Types Declaration ----------------------------------------
   wire       clk;
   wire       rst_b;
   wire [SIZE-1:0]sign_i;
   wire [SIZE-1:0]rise_o;
   wire [SIZE-1:0]fall_o;
   reg  [SIZE-1:0]sign_i_syn;
   reg  [SIZE-1:0]out_ff2;
   wire [SIZE-1:0]out_xor;

   genvar i; // auxiliar variable to generate
   
 generate for(i=0;i
   begin
//------------------------ Sequential Part ------------------------------------
  
   always @(posedge clk)
     begin
       if (!rst_b)
     begin
       
            sign_i_syn[i]
     
     end //if(!rst)  
      
       else 
     begin
      
        sign_i_syn[i]
           //Transform the entering signal in synchronous
          
        out_ff2 [i]
        //Update the second ff output value
        
     end //else
     end //always @(posedge clk)


//-------------------------------- Combinational Part ------------------------

   assign out_xor[i] = (sign_i_syn[i] ^ out_ff2[i]);
// keeps the output from the xor in 1 for 1 period of clock in the rise or fall
 
   assign rise_o[i] = (sign_i_syn[i] & out_xor[i]);
// if the entering sinal has high level and the pulse in the xor output
   // represents a rising edge
       
   assign  fall_o[i] = ~(sign_i_syn[i] | ~out_xor[i]);
// if the entering sinal has low level and the pulse in the xor output
   // represents a falling edge
    
   end // for (generate) 
 endgenerate
 


As can be seing above it is sizeble by parameter. So I have tried to also make sizeble psl.
In the psl introduction from cadence I have found this option:

for i in {0,1,2} generate
begin: check1
    {// psl check_init: assert (!value[i]) @rose(resetn);
end
endgenerate;


So I have tried this:

for i in {0,1,2} generate
begin: check1
{//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
// abort !rst_b)
// report "Rising Edge Failed " severity warning;
//@fell(clk);
end
endgenerate;


And I had this bunch of errors:
for i in {0,1,2} generate
|
ncvlog: *E,EXPLPA (EdgeDetector.v,122|4): expecting a left parenthesis ('(') [12.1.3(IEEE 2001)].
{//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
|
ncvlog: *E,EXPEND (EdgeDetector.v,124|4): Expecting the keyword 'end' [12.1.3(IEEE 2001)].
{//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
|
ncvlog: *E,NOTSTT (EdgeDetector.v,124|33): expecting a statement [9(IEEE)].
{//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
|
ncvlog: *E,EXPSMC (EdgeDetector.v,124|52): expecting a semicolon (';') [10.2.2][10.2(IEEE)].
{//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
|
ncvlog: *E,EXPSMC (EdgeDetector.v,124|63): expecting a semicolon (';') [9.7.3(IEEE)].
{//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
|
ncvlog: *E,EXPSMC (EdgeDetector.v,124|64): expecting a semicolon (';') [9.7.3(IEEE)].
{//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
|
ncvlog: *E,EXPSMC (EdgeDetector.v,124|71): expecting a semicolon (';') [9.7.3(IEEE)].
endgenerate;
|

My next try was to use the regular generate form in verilog:

generate for(i=0;i
begin: Rise
//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
// abort !rst_b)
// report "Rising Edge Failed " severity warning;
//@fell(clk);
end
endgenerate

It really worked, but the probes did not worked!! They are set like this:

probe -create -assertions -transaction -waveform -name RISING edge_detector_tb.edge_detector.Rise[0].RISING


The log result is:
ncsim> probe -create -assertions -transaction -waveform -name RISING edge_detector_tb.edge_detector.Rise[0].RISING
Created probe RISING


Even in the assertion browser, when I click in the assertion and put type transaction it do not appers in the SimVision. It shows no error, only doesn't apper.

Could somebody show me the best way of doing this and explain me why this ways did not work?

Thanks,


Originally posted in cdnusers.org by alexsieh
  • Cancel
  • archive
    archive over 18 years ago

    Well, in my newbe condition in this forum I had problem posting the codes :)

    The first code is :
    module edge_detector(sign_i, // Input of the Edge Detector
    rise_o, // Rising Edge Output of the Edge Detector
    fall_o, // Falling Edge Output of the Edge Detector
    clk, // clock
    rst_b, // Synchronous Reset
    );

    //--------------------- Parameters Declaration ---------------------------------
    parameter SIZE = 1;

    //-------------------- Inputs Declaration --------------------------------------
    input [SIZE-1:0]sign_i;
    input clk;
    input rst_b;


    //---------------------- Outputs Declaration -----------------------------------
    output [SIZE-1:0]rise_o;
    output [SIZE-1:0]fall_o;

    //------------------- Types Declaration ----------------------------------------
    wire clk;
    wire rst_b;
    wire [SIZE-1:0]sign_i;
    wire [SIZE-1:0]rise_o;
    wire [SIZE-1:0]fall_o;
    reg [SIZE-1:0]sign_i_syn;
    reg [SIZE-1:0]out_ff2;
    wire [SIZE-1:0]out_xor;

    genvar i; // auxiliar variable to generate

    generate for(i=0;i begin
    //------------------------ Sequential Part ------------------------------------

    always @(posedge clk)
    begin
    if (!rst_b)
    begin

    sign_i_syn[i]<=1'b0; //If reset occured clear flip flops

    out_ff2<=1'b0;

    end //if(!rst)

    else
    begin

    sign_i_syn[i]<= sign_i[i];
    //Transform the entering signal in synchronous

    out_ff2 [i] <= sign_i_syn[i];
    //Update the second ff output value

    end //else
    end //always @(posedge clk)


    //-------------------------------- Combinational Part ------------------------

    assign out_xor[i] = (sign_i_syn[i] ^ out_ff2[i]);
    // keeps the output from the xor in 1 for 1 period of clock in the rise or fall

    assign rise_o[i] = (sign_i_syn[i] & out_xor[i]);
    // if the entering sinal has high level and the pulse in the xor output
    // represents a rising edge

    assign fall_o[i] = ~(sign_i_syn[i] | ~out_xor[i]);
    // if the entering sinal has low level and the pulse in the xor output
    // represents a falling edge

    end // for (generate)
    endgenerate



    The Second:
    for i in {0,1,2} generate
    begin: check1
    {// psl check_init: assert (!value[i]) @rose(resetn);
    end
    endgenerate;



    The third:

    for i in {0,1,2} generate
    begin: check1
    {//psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
    // abort !rst_b)
    // report "Rising Edge Failed " severity warning;
    //@fell(clk);
    end
    endgenerate;



    The fourth:

    generate for(i=0;i begin: Rise
    //psl RISING: assert always ( rose(sign_i[0]) -> next PULSE(rise_o)
    // abort !rst_b)
    // report "Rising Edge Failed " severity warning;
    //@fell(clk);
    end
    endgenerate


    The sixth:

    probe -create -assertions -transaction -waveform -name RISING edge_detector_tb.edge_detector.Rise[0].RISING

    Thanks and sorry about that,


    Originally posted in cdnusers.org by alexsieh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    I tried doing this using IUS 6.11 and everything seemed to work fine for me. I did have to interpolate a little since the code that I cut-and-pasted from this thread needed some massaging to compile.

    Your original syntax problem appears to be because you put some PSL code into your HDL model without using the "// psl" comment prefix. So the Verilog parser was trying to parse the PSL as if it was Verilog. If the Cadence examples have code without the PSL prefix in them, then I think that they are wrong. Can you point me to the document you were referencing?

    Secondly, using a Verilog loop-generate seems to work fine. If anyone can tell me how to upload a 'tar.gz' file to this forum, I could post an example that takes everything thru the process and displays the assertion as a transaction in a waveform window at the end. Personally, I think it is a little too much code to post in-line.


    Originally posted in cdnusers.org by TAM
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    HI,

    To attach a file do not use "Quick Reply" but click "Add Reply instead. 

    You can use the "Message Attachments" field to attach files to upload.

    Regards,

    JB


    Originally posted in cdnusers.org by jb
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Ok then. :-)

    Here is a small example that, if you run it using IUS 6.11, should pop up a waveform window with your assertion displayed as a transaction.


    Originally posted in cdnusers.org by TAM
    pslgen.tar.gz
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information