• 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. sys. verilog code - need explanation

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 1345
  • 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

sys. verilog code - need explanation

archive
archive over 18 years ago

HI, I am new to s.verilog - any help with the code below will be great!
what does the code below actually mean? anyone explain plz?

why is LOC_IDLE triggered?

LOC :
        begin
          varc_sel[3:0] = { LOC_DRAIN ,
                                  LOC_GETDEL ,
                                  LOC_BUFDEL ,
                                  LOC_IDLE } ;
          case (varc_sel[3:0])
            4'b1000 ,
            4'b0100 ,
            4'b0010 ,
            4'b0001 ,
            4'b0000 :
              begin
               
              end
            default :
              begin
                 $write("ERROR:");
                 $display(" Invalid arc in, fsm:SM, state:LOC") ;
                 $display(" Instance: %m");
                 $display(" Time: %t", $time);


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

    Yes, you are correct. The way the case works is it looks at the value of varc_selA and then selects the branch that matches the value. In the example, if the value is 8, 4, 2, 1, or 0 it will branch to the 'begin...end'. If it doesn't match any branch, then the default branch will be executed.

    I'm reposting my previous text since the formatting got screwed up.

    Somewhere I assume varc_sel is defined to be an enum like:

    typedef enum bit [2:0] {LOC_DRAIN, LOC_GETDEL, LOC_BUFDEL, LOC_IDLE} loc_t;
    loc_t varc_sel;

    The way enums work is that you can refer to the labels by name, but underneath there are actual values for those labels. By default, it starts with 0 and counts up. You can change the default behavior by providing your own values in the definition. If you used the defaults, then LOC_IDLE would be equal to 3 which would never be selected in the case. However, you could use the following enum definition to make the assignment one-hot:

    typedef enum bit [2:0] {LOC_DRAIN=1, LOC_GETDEL=2, LOC_BUFDEL=4, LOC_IDLE=8} loc_t;


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

    Yes, you are correct. The way the case works is it looks at the value of varc_selA and then selects the branch that matches the value. In the example, if the value is 8, 4, 2, 1, or 0 it will branch to the 'begin...end'. If it doesn't match any branch, then the default branch will be executed.

    I'm reposting my previous text since the formatting got screwed up.

    Somewhere I assume varc_sel is defined to be an enum like:

    typedef enum bit [2:0] {LOC_DRAIN, LOC_GETDEL, LOC_BUFDEL, LOC_IDLE} loc_t;
    loc_t varc_sel;

    The way enums work is that you can refer to the labels by name, but underneath there are actual values for those labels. By default, it starts with 0 and counts up. You can change the default behavior by providing your own values in the definition. If you used the defaults, then LOC_IDLE would be equal to 3 which would never be selected in the case. However, you could use the following enum definition to make the assignment one-hot:

    typedef enum bit [2:0] {LOC_DRAIN=1, LOC_GETDEL=2, LOC_BUFDEL=4, LOC_IDLE=8} loc_t;


    Originally posted in cdnusers.org by tpylant
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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