Difference between revisions of "Does Verific support XMR?"

From Verific Design Automation FAQ
Jump to: navigation, search
Line 21: Line 21:
  
  
Not that for XMR support (even though limited), these runtime flags need to be enabled (set to 1) before design analysis:
+
Note that for XMR support (even though limited), these runtime flags need to be enabled (set to 1) before design analysis:
  
 
     veri_preserve_user_nets
 
     veri_preserve_user_nets
 
     db_preserve_user_nets
 
     db_preserve_user_nets
 
     db_allow_external_nets
 
     db_allow_external_nets

Revision as of 13:34, 14 June 2017

Q: Does Verific support cross module references (XMR)?

Verific fully supports XMR with "hierarchy tree" feature. Please refer to Hierarchy Tree

Without this product feature, support for XMR is full in analysis and static elaboration, and is very limited in RTL elaboration.

The main reason for limited support in RTL elaboration for XMR is that for Verilog, the order of elaboration of modules is nondeterministic. If module "foo" has not been elaborated, the elaborator will not be able to resolve "foo.bar". As a collorary, without "hierarchy tree," "circular XMR," as in the testcase below (instance i1 refers to a signal in instance i2, and vice versa), is not supported:

   module sub2(out);
       output out;
       assign top.i1.out = 0;
   endmodule 
   module sub1(out);
       output out;
       assign top.i2.out = 0;
   endmodule
   module top();
       sub1 i1();
       sub2 i2();
   endmodule


Note that for XMR support (even though limited), these runtime flags need to be enabled (set to 1) before design analysis:

   veri_preserve_user_nets
   db_preserve_user_nets
   db_allow_external_nets