Wednesday, December 03, 2008     Register | Login | Search | Contact Us
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Subject: vr_ad with reserved bits but writable
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
e_vangelist
Posts: 5
Online: User is Offline
1/26/2008 1:54 AM  

Hi 'e' folks,

I'm working in the verification of a SOC using vr_ad last version:

reg def BLABLA_0 BLA_REGS 0x01 {
    reg_fld unused  : uint(bits:28) : R: 0:cov;
    reg_fld foo : uint(bits:4):RW:0:cov;
    set_static_info() is {
       static_info.compare_mask = 0xFFFFFFFF;  // compare up to 32 bits
       static_info.description = "Control Reg";
 };

In my test, I perform write -read access on my register: the thing I do not understand , Why the write value chosen by bfm unit does not take care of the fact that unused is R (read only).

Actually, the write value is 0x5e006a9 and of course I collect a dut error due to a mismatch because my unused is R on a spec point of view but writable in DUT.

Have you some hint to constrain the ability to :
perform write with appropriate width on such register (R reg_field and RW reg fields)
and perform read with appropriate width when you have W reg fields and RW reg_fields

Cheers 

Fred

thinkverification
Posts: 28
Online: User is Offline
1/26/2008 7:16 AM  
Hey there Fred,

When you define a register field as R (read only) it doesn't affect the data sent to DUT, but only the shadow one (in e). This is done in order to be able to compare DUT vs. ENV and verify that read-only bits are actually read-only, i.e. - ignore the value written to them. If both ENV and DUT were to ignore the write then you woudn't be able to detect bugs related to RO access.

What you probably need is a different attribute called "RESERVED" or "UNUSED". This would mean that the value of the field is a "don't care" when checked. You could implement this by setting the respective compare_mask to 0.

Another option, of course, is to avoid writing non-default values to the unused fields...

Hope this helps :-)

Yaron




Yaron Ilani
VLSI Verification Specialist
www.ThinkVerification.com
e_vangelist
Posts: 5
Online: User is Offline
1/29/2008 11:00 AM  
Thanks Yaron for your input.

I forgot to mention that we tends to choose registers randomly and not necessary perform all the bunch of it.
I went for a reformatting of the written value according to the wr mask: works perfectly !

cheers

by the way, congratulations for your website: it is pleasant and funny!
thinkverification
Posts: 28
Online: User is Offline
1/29/2008 11:45 PM  
Posted By e_vangelist on 1/29/2008 11:00 AM
Thanks Yaron for your input.

I forgot to mention that we tends to choose registers randomly and not necessary perform all the bunch of it.
I went for a reformatting of the written value according to the wr mask: works perfectly !

cheers

by the way, congratulations for your website: it is pleasant and funny!


Thanks!

Yaron Ilani
VLSI Verification Specialist
www.ThinkVerification.com
Posting to forums is available to community members only.
Login or Register

Forums > Functional Verification > e > vr_ad with reserved bits but writable


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.