Stats

  • Locked Locked
  • Replies 2
  • Subscribers 67
  • Views 14081
  • 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

ahb evc: Hw can I do a random back to back transfer with random address

Anukrishnan

Hi ,

I want to do a random back to back transfers, by constraining the ahb evc in specman.Basically I need the htrans as 2-0-2-2-2-2-0-2-0-2-2-2-2-  etc  with random address .So how can I constrain the ahb-evc  to get a sequence like this? Thanks in advance.

 

Parents

  • Hi, thanks in advance. I have a similar question.

    I want to send multiple SINGLE bursts with no intervals in between. like 2-2-2-2-2-2-2-2...

    However, when I use the following source code, I got a couple of IDLE cycles like 2-2-0-2-2-2-0-2-0-2..., and I don't understand why. Can you help me?

    (I am using non_blocking_write api instead of do burst, so there will be no 1 cycle loss between bursts.)

    struct ahb_trans{

    trans_type : vr_ahb_burst_kind;
    trans_dir : vr_ahb_direction;
    trans_size : vr_ahb_transfer_size;
    trans_addr : vr_ahb_address;
    trans_data : vr_ahb_data;

    };

    extend vr_ahb_master_seq_kind : [ MY_SEQ ];

    extend MY_SEQ vr_ahb_master_seq {

    !ahb_trans;

    for i from 0 to 10 {

    gen ahb_trans;

    non_blocking_write( ahb_trans.trans_addr,
                                         {ahb_trans.trans_data},
                                          ahb_trans.trans_type,
                                          ahb_trans.trans_size);

    };

    };

Reply

  • Hi, thanks in advance. I have a similar question.

    I want to send multiple SINGLE bursts with no intervals in between. like 2-2-2-2-2-2-2-2...

    However, when I use the following source code, I got a couple of IDLE cycles like 2-2-0-2-2-2-0-2-0-2..., and I don't understand why. Can you help me?

    (I am using non_blocking_write api instead of do burst, so there will be no 1 cycle loss between bursts.)

    struct ahb_trans{

    trans_type : vr_ahb_burst_kind;
    trans_dir : vr_ahb_direction;
    trans_size : vr_ahb_transfer_size;
    trans_addr : vr_ahb_address;
    trans_data : vr_ahb_data;

    };

    extend vr_ahb_master_seq_kind : [ MY_SEQ ];

    extend MY_SEQ vr_ahb_master_seq {

    !ahb_trans;

    for i from 0 to 10 {

    gen ahb_trans;

    non_blocking_write( ahb_trans.trans_addr,
                                         {ahb_trans.trans_data},
                                          ahb_trans.trans_type,
                                          ahb_trans.trans_size);

    };

    };

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.